Hello all,
I have put together a database of Bounties HR staff and salaries.
This is something that a lot of Polkadot community members have been requesting since early 2024, as the number of bounty proposals began to increase.
The data presented can be used to:
Please advise if there are any changes to be made on the existing fields or entries. Also, feel free to duplicate, reuse, and refactor this database for your own initiatives/projects. Just keep in mind that this is still Work In Progress. 
In the short term, I will be linking basic information about staff’s professional qualification(s) and/or experience into the Bounties HR database.
I also plan to create a second database for DevRel HR, as the next step towards bootstrapping a usable HR directory for the ecosystem.
Finally, I will be applying for a retroactive tip on OpenGov at a rate of $85 per hour for the time spent structuring, populating, and updating these databases. However, the ongoing maintenance of these databases would be best undertaken by future Bounty Administrators and/or an established ecosystem organisations in the long run.
Thank you and happy International Women’s Day! 
9 Likes
Dear Anaelle,
lets talk because I am developing a small dapp to get all this information directly from chain. So maybe no need to manually update this specific database, when can be done automatically. Let’s give machine work to machines.
Public data, data in public: As questions bring to other questions, this data speaks about concentration of influence ( and accumulation of capital, maybe ). Should we restrict the number of “seats” that a ecosystem member can hold at certain moment of time? Like one in Polkadot and one in Kusama? Political decentralization.
Also, this can be leveraged as a perfect opportunity to bring new and fresh faces and ideas, something that Polkadot really needs.
( This is another issue of an open-ended ecosystem, different parties working on the same topic without knowing it).
2 Likes
Hi Daniel,
Thank you for the unique pointers re: leveraging this data. 
I am glad to hear that there are people like you out there working to address the same problem from a different angle. A dapp would certainly be useful for presenting some of this info, but I do not think that it makes every other effort redundant.
When it comes to Governance in general, and HR in particular, we cannot solely rely on the data available on-chain to make our decisions.
In fact, a good share of the critical information that is needed to inform governance decisions is available off-chain (i.e Polkassembly, Google docs, Hackmd posts, Notion databases, Polkadot forum, etc.). There is and will always be a limit in the breadth of the data that can be obtained from the blockchain only; and this means that we need the entire community to be involved in sourcing and sharing relevant information with the general public through their preferred platforms.
This is why I have chosen to publish these databases on an accessible and well-used platform like Notion (which allows anybody, techie or not, to play around with the data as s/he sees fit), as opposed to a repo, a spreadsheet, or a custom app.
Also, we need to have as many options as possible for sourcing, publishing, cross-referencing and verifying off-chain data.
We want to avoid the situation whereby a single team is in the position of overseeing everything in a given area of the ecosystem. This is because, in the past, this setup has led to teams overcharging the Treasury for trivial deliverables or shutting down their platforms when their Treasury funding requests were rejected.
This is why I have suggested that ecosystem organisations find their own way of maintaining this data independently.
If there is something specific that you think I can contribute to re: your ongoing work, please let me know in DM. At this point in time, I only want to put the available data out there for the community to work with, knowing that refinements will be carried out by more competent/motivated folks in due course. 
Thanks!
1 Like
