This could be a naive perspective, but I’m not sure if this type of position requires multiple half-time+ contributors, or if it’s more like a heavy up-front lift followed by lower effort maintenance over time.
For example, I imagine location-based data of .eth users could be valuable in event coordination, community building, steward election, etc. I’m happy to contribute relevant data from the ETH Leaderboard database, which was/would be a heavy lift to set up, but then the data would flow regularly without much maintenance.
For some brainstorming on how this data might be useful, here’s some location data I pulled this morning based on the location field of .eth Twitter accounts:
- 4,700+ .eth Twitter accounts in California
- 2,700+ .eth Twitter accounts in New York
- 1,100+ .eth Twitter accounts in Texas
- 750+ .eth Twitter accounts in Ontario
- 400+ .eth Twitter accounts in Paris
- 300+ .eth Twitter accounts in Vancouver
- 200+ .eth Twitter accounts in Quebec