So would this be the proper way to request / make a feature change then you think Morph? I feel like clarifying this process for people would be really helpful!
Create a poll to gauge community interest in a requested feature.
Create or hire a dev to submit a PR with additional feature?
Perhaps we could use a step in-between those which would confirm the client teams willingness to accept the PR?
I imagine also the bidding and tendering process might become useful in the case of actually creating the PRs as many people who come up with ideas for features are not developers themselves. Perhaps it would be good to identify a default group of community devs who are capable of creating the changes for feature requests? Having a way to connect these community ideas with someone like yourself who can execute them would be a big step in the direction of achieving a lot of the things that are brought up in the DAO related to the client.
Oh I’m just going to build it and submit it myself for free.
This poll is mostly to see if it’s worth my time, and also to justify landing the PR once complete.
The idea that we should pay or fund development on an open source project doesn’t make a tonne of sense IMO.
More free development, I’ll get back more value of any grant by actually using/participating in the early metaverse if it succeeds - funding simple ideas that anyone can add would just hurt DCL more than help.
Let’s normalize open source contributions from people who actually want the platform to get better as opposed to thinking the DCL fund is there for people to have a job running failed startups or to ‘try’ build proof or concepts.
I think we should have bounty boards, but the requirements for acceptance should be so absurdly high that users who are trying to extract wealth from it to be undesirable - only community members who lead the charge on open source initiatives with others should be eligible.
Grants should be awarded in post after significant open source contributions which should be done for the community, by the community.
Thank you for the confirmation! Since this is already supported in the API it would make adding it client side much more straightforward, this proposal looks like it has enough support - I’ll start working on this.