Elixir Docs
Hi everyone,
After the discussion on Polkassembly and improving the proposal, we have moved on to a treasury vote. Full scope of the project can be found here.
This is a referendumV2 whose proposer address (E5oiBDNmhArBxBXK3C7phyGY9HB5zqtrVFxfeMzD9UV1hoa) is shown in on-chain info below. Only this user can edit this description and the title. If you own this account, login and tell us more about your proposal.
Comments (5)
Proposal Failed
3
of 3Summary
0%
Aye
0%
Nay
Aye (26)0.0 PAS
Support0.0 PAS
Nay (244)0.0 PAS
Comments (5)
Hi team,
It seems like I'll be the first to comment here as this is in synch with my Governance video preparation.
Here is my feedback & I will also be producing an audit in a separate comment later today.
What I like about this proposal:
-
The idea is awesome! We definitely need a StackOverFlow style platform for the ecosystem to onboard as many Web2 Devs as possible.
-
That you've included the user story examples of how Elixir will work.
What I don't like about this proposal:
-
You seem to be focusing on all the positive aspects, but how do you plan to market this platform?
-
The salaries of most of the team members are over $100 an hour which seems exaggerated given the current market conditions.
I'm aware Senior Rust Devs get paid around $100 an hour because they're very hard to find, but why would the rest of the team members get paid the same? Front End Devs and UX are not hard to find, thus the cost per hour (unless they're superstars) should definitely not exceed $100! -
The packages for self sustaining seem to be quite costly for a brand new product hitting the market. I would like to see more affordable prices even for Dev teams to be happy to take Indie or the Pro packages, at least at the very start and then see how your user base grows. Starting big, might put people off even if it's attractive.
I also think this might not be appropriate for Kusama with the current structure, but if the budget could be re-worked, I'd be happy to vote Aye given you plan to self sustain. For now, I'm abstaining waiting for your answers before I decide.
Thanks,
Claudio
Thank you Albert for sharing your proposal for Elixir Docs. The idea of creating a community-powered platform to onboard web2 developers into web3 is certainly a valuable initiative and one that we believe could benefit the Polkadot and Kusama ecosystems. However, we do have some concerns regarding the choice of Glitter protocol as the indexer solution. I believe it would be more valuable to look for solutions that can directly benefit and add value to the Polkadot ecosystem. While the proposal aims to onboard web2 developers to web3, it is based on the use of the Glitter protocol as the Cosmos-based Tendermint chain, which is not directly related to the Polkadot ecosystem. According to documentation, the proposed Glitter protocol is still in a testnet and not fully operational. I would encourage Elixir Docs to explore indexer and storage solutions that can directly add value to the Polkadot ecosystem. These solutions should be designed to integrate seamlessly with the Polkadot infrastructure, enhance its capabilities, and offer greater value to the ecosystem. By prioritizing the development of such solutions, we can ensure the growth and success of the Polkadot ecosystem as a whole, which will ultimately benefit all of its stakeholders, including developers, users, and investors.
Hi team,
It seems like I'll be the first to comment here as this is in synch with my Governance video preparation.
Here is my feedback & I will also be producing an audit in a separate comment later today.
What I like about this proposal:
The idea is awesome! We definitely need a StackOverFlow style platform for the ecosystem to onboard as many Web2 Devs as possible.
That you've included the user story examples of how Elixir will work.
What I don't like about this proposal:
You seem to be focusing on all the positive aspects, but how do you plan to market this platform?
The salaries of most of the team members are over $100 an hour which seems exaggerated given the current market conditions.
I'm aware Senior Rust Devs get paid around $100 an hour because they're very hard to find, but why would the rest of the team members get paid the same? Front End Devs and UX are not hard to find, thus the cost per hour (unless they're superstars) should definitely not exceed $100!
The packages for self sustaining seem to be quite costly for a brand new product hitting the market. I would like to see more affordable prices even for Dev teams to be happy to take Indie or the Pro packages, at least at the very start and then see how your user base grows. Starting big, might put people off even if it's attractive.
I also think this might not be appropriate for Kusama with the current structure, but if the budget could be re-worked, I'd be happy to vote Aye given you plan to self sustain. For now, I'm abstaining waiting for your answers before I decide.
Thanks,
Claudio
Thank you Albert for sharing your proposal for Elixir Docs. The idea of creating a community-powered platform to onboard web2 developers into web3 is certainly a valuable initiative and one that we believe could benefit the Polkadot and Kusama ecosystems. However, we do have some concerns regarding the choice of Glitter protocol as the indexer solution. I believe it would be more valuable to look for solutions that can directly benefit and add value to the Polkadot ecosystem. While the proposal aims to onboard web2 developers to web3, it is based on the use of the Glitter protocol as the Cosmos-based Tendermint chain, which is not directly related to the Polkadot ecosystem. According to documentation, the proposed Glitter protocol is still in a testnet and not fully operational. I would encourage Elixir Docs to explore indexer and storage solutions that can directly add value to the Polkadot ecosystem. These solutions should be designed to integrate seamlessly with the Polkadot infrastructure, enhance its capabilities, and offer greater value to the ecosystem. By prioritizing the development of such solutions, we can ensure the growth and success of the Polkadot ecosystem as a whole, which will ultimately benefit all of its stakeholders, including developers, users, and investors.