**Tip to Anaelle LTD for the creation of the DevRel HR database**
Beneficiary:This is a request for a retroactive tip totalling $2,380 ($85 x 28 hours) for the time Anaelle LTD spent structuring, populating, and updating a database hosted at OpenGov HR:
- DevRel HR: An overview of treasury-funded DevRel teams, programs, and costs in the Polkadot ecosystem. (28 hours)
This retroactive proposal was previously announced in the original Polkadot forum post.
The on-chain proposal will be made for payment in USDC.
Comments (6)
Proposal Passed
3
of 3Summary
0%
Aye
0%
Nay
Aye (20)0.0 PAS
Support0.0 PAS
Nay (14)0.0 PAS
Comments (6)
Dear Proposer,
Thank you for your proposal. Our second vote on this proposal is AYE.
The Big Tipper track requires 35% participation and simple majority of non-abstain votes according to our voting policy v0.2, and any referendum in which the majority of members vote abstain receives an abstain vote. This proposal has received three aye and zero nay votes from ten available members. Below is a summary of our members' comments:
Voters expressed their support for the proposal, highlighting the significant value of the off-chain data and its potential worth. Gratitude was specifically extended to an individual for their service in facilitating the process.
The full discussion can be found in our internal voting.
Please feel free to contact us through the links below for further discussion.
Kind regards,
Permanence DAO
Decentralized Voices Cohort IV Delegate
📅 Book Office Hours
💬 Public Telegram
🌐️ Web
🐦 Twitter
🗳️ Delegate
Hi Anaelle, and thanks for your work and involvement.
I believe DevRel HR data is important for the ecosystem, and more transparency on this front could definitely bring value, but the format and process matter.
In this case, it’s a manual, closed, unversioned Notion document (Notion ≠ open-source database), maintained by a single person, with limited visibility and an impact that’s hard to assess on actual DAO decisions. The fact that it’s updated manually also increases the risk of errors or omissions.
Before distributing public funds, we should rigorously assess the added value for the DAO, and ask whether this kind of contribution truly aligns with our Web3 vision: transparent, collaborative, decentralised, and non-bureaucratic.
This isn’t about rejecting your effort, quite the opposite. It’s about avoiding a situation where contributors like you spend hours on isolated work that ends up unused, or feel discouraged when goodwill doesn’t turn into shared value.
That’s why I’m voting NAY, not against you, but because my vision is that we should focus on building open, shared infrastructure that truly serves the ecosystem.
Feel free to reach out if you'd like to discuss this further.
Dear Proposer,
Thank you for your proposal. Our second vote on this proposal is AYE.
The Big Tipper track requires 35% participation and simple majority of non-abstain votes according to our voting policy v0.2, and any referendum in which the majority of members vote abstain receives an abstain vote. This proposal has received three aye and zero nay votes from ten available members. Below is a summary of our members' comments:
The full discussion can be found in our internal voting.
Please feel free to contact us through the links below for further discussion.
Kind regards,
Permanence DAO
Decentralized Voices Cohort IV Delegate
📅 Book Office Hours
💬 Public Telegram
🌐️ Web
🐦 Twitter
🗳️ Delegate
Hi Anaelle, and thanks for your work and involvement.
I believe DevRel HR data is important for the ecosystem, and more transparency on this front could definitely bring value, but the format and process matter.
In this case, it’s a manual, closed, unversioned Notion document (Notion ≠ open-source database), maintained by a single person, with limited visibility and an impact that’s hard to assess on actual DAO decisions. The fact that it’s updated manually also increases the risk of errors or omissions.
Before distributing public funds, we should rigorously assess the added value for the DAO, and ask whether this kind of contribution truly aligns with our Web3 vision: transparent, collaborative, decentralised, and non-bureaucratic.
This isn’t about rejecting your effort, quite the opposite. It’s about avoiding a situation where contributors like you spend hours on isolated work that ends up unused, or feel discouraged when goodwill doesn’t turn into shared value.
That’s why I’m voting NAY, not against you, but because my vision is that we should focus on building open, shared infrastructure that truly serves the ecosystem.
Feel free to reach out if you'd like to discuss this further.