ENH: figure out a way to pull editor domain expertise from our data

[lwasser]

We capture editor & reviewer domain expertise in our editor signup sheet, but it's a Google Doc, and it's private.
We have a semi-public version, but we don't want to share that with the world.

We have data including.

• editors needed

And available editors:

But that data doesn't map. to the domain areas of the package or editor.
It would be helpful if editors available had domain expertise to help the EiC better connect the two.

Approaches

1. We could export a CSV from Google Sheets and parse the data via Python. That will be a bit cumbersome to automate.
2. We could move to Airtable, spend time populating current editor data there, and then create a form so Airtable captures data. and a dashboard to EiC can parse through that data.
   • If we do this, we could then hit the airtable api to pull down the data that we need for the metrics dashboard.

A middle ground could be to initially create the csv by hand, write code to parse the file and create a metrics csv manually using Python with the intention of moving to an api based workflow.

[lwasser]

Note: only I or Bane can work on this issue as it requires access to our internal editor signup.

[lwasser]

@all-contributors please add @banesullivan for code, review

[allcontributors]

@lwasser

I've put up a pull request to add @banesullivan! 🎉