Hey,
I’m writing this as a member of the ecosystem, a member of the Fellowship and not as a member of Parity.
The reason for this post is that we need a list of ecosystem tasks. A list of items that the ecosystem wants to have done that will ultimately improve the ecosystem. We already have multiple sources for these tasks, like the Wish for Change track, builders requesting certain features, bounties already having a list of tasks, surveys in the ecosystem bringing up things to improve etc. So, the issue is not that we don’t have any tasks to tackle, more that we have to many and they are scattered everywhere. This is also not only about technical tasks, it can be basically any kind of task, whatever the ecosystem needs.
First we need to have a list of all of these tasks. They need to be categorized, name some contacts to help/discuss the task, include information on how to get funding for the task, prioritization of the task etc. There are probably million things to do to make this list of tasks easy approachable by people. Also not all things will be perfect from the beginning, like prioritization. Finding a good approach to prioritize the tasks will be tricky, but we can start easy and improve from there.
With this list it would be much easier to retain expertise in the ecosystem. Right now we already see people coming up with proposals on OpenGov and these are not always what the ecosystem needs. These proposals are getting rejected and in the worst case these people are moving on. It would be much better to point these people to this list of tasks that the ecosystem finds worthwhile to tackle with clear documentation on how to get funding etc. This way we can hopefully retain these people in the ecosystem and maybe also attract people from the outside.
The work required to build and maintain this list is at the beginning for sure a full time job. So, if YOU are reading this and YOU think that you can do this, please reach out to me. We would help to get this started and also help to create a proposal to hopefully get funding from the treasury.
In other words, is there a need for someone to receive information from all the teams requesting certain tasks necessary for the ecosystem and organize it in a file, perhaps by type, budget, and urgency, so that builders or developers can consult this file and offer their services based on the requests in that list?
Should this person be technical, or could they have the guidance of a technical expert to perform this role?
Polkassembly and Subsquare might consider placing access to this file or page in a visible location so that builders or developers become aware of its existence and can easily access it.
I love the idea; it would greatly help developers in knowing what to prioritize.
I don’t think that the person needs to be technical. I assume there will also be non technical tasks and the person is not required to understand the tasks beyond being able to categorize them.
This is a great idea and one which I believe we are perfectly placed to deliver on.
We recently received treasury funding to build out the second iteration of our platform morekudos.com. One of the deliverables you can expect from us in the near future will be a community wishlist. (see our full proposal here)
Community Wishlist
The Community Wishlist will serve as an ecosystem hub where community members can post, discuss, and upvote feature requests and project ideas. This direct feedback mechanism will not only foster a collaborative community atmosphere but also guides developers and project teams on what features or improvements are most desired, helping prioritise development efforts that have community support and potential for treasury funding.
We are leaning towards implementing Canny-style pages to track these ecosystem wishlist tasks, although we will of course consider improvement suggestions/features from the community.
@bkchr It would be great to discuss your vision for this task list to see how it might align with our development roadmap.
You gather a lot of information about the ecosystem there, that’s true, but I suppose Bastian refers to having access to a more specific database regarding the requirements and having some kind of order based on task priority.
