The background of Catalyst and Cardano contributors can be found here
- <https://catalyst-swarm.gitbook.io/catalyst-contributors/>
- <https://catalyst-swarm.gitbook.io/cardano-contributors>
Catalyst and Cardano contributors funding categories look to become the collaborative glue that brings together the ecosystem to work effectively together. Catalyst contributors help to maintain, analyse, develop and improve the Catalyst governance and funding process. Cardano contributors help to support, develop and analyse the developer ecosystem and node operation for Cardano.
Both Catalyst and Cardano contributors need an effective product development workflow. This flow includes an easy way to identify problems, assess their priority, bring in relevant information towards deciding on a solution path, tracking the progress of executing a solution and ways to measure the outcomes.
Both Catalyst and Cardano contributors also need an effective way to make governance decisions in which the results are made public to the community. Contributors represent the interests of the community by being paid to improve and maintain the ecosystem. Contributors would have governance decisions involving product decisions and any rapid funding distribution such as paying for more contributors and supporting existing initiatives.
This analysis on the initial infrastructure for both the product development workflow and governance for contributors will include:
- Requirements - Outline the requirements for what is needed for contributors to function effectively for both the product development workflow and their own governance.
- Research - Research existing solutions that exist on the market and explore their trade offs and which solutions would match the requirements most effectively initially.
- Initial solution suggestions - Based on the requirements, research and any community feedback what initial solution should be used.
- Future considerations - Considerations for what other solutions may become more effective over time, what tools could be created as alternatives and what might be blocking better solutions in the short term until certain infrastructure is available.
- Initial system setup - Creating the initial setup of the suggested solution system for the contributors to start using once the first round of contributors is funded.
This proposal provides analysis and an initial solution as preparation for when full time contributors are funded to work in both the Catalyst and Cardano ecosystem. As such it needs to be completed before a large amount of contributors are funded so that there is something established and ready to use from day one. The product development workflow and governance process and tools they use will naturally evolve over time. This proposal helps outline and establish an initial version to start the iterative process of supporting and managing collaboration between contributors.
The challenge looks to help with creating ‘accessible knowledge’ and ‘education for development in the Cardano & Catalyst ecosystem’. This proposal helps address the need by creating more analysis and open source contributions that aim to improve the way that people can work and effectively collaborate as contributors when supporting the Cardano and Catalyst ecosystem.
This knowledge and analysis can help lead to initiatives on new tools and solutions that are backed from analysis on what is required. The initial implementation of these solutions will also drive more feedback and data points to influence improvements to the tools and processes used by the contributors to most effectively manage themselves.
By making analysis on how contributors can collaborate and govern key decisions this proposal helps to achieve the outlined success criteria where it encourages having ‘A growing number of experts join forces to build collaboratively on community owned infrastructure, tooling, standards, libraries and docs’. Both during the analysis community members will provide their expertise to the requirements, research and potential solution. Then in regards to the outcome of the analysis, it helps to lead to improve collaboration between contributors in the forms of an initial system and processes that lead to collaboratively improved and owned infrastructure.
The analysis will be shared across the community for feedback to ensure the benefits of it are shared and improved upon as it evolves. Some channels we will ask for feedback on include Discord, Telegram, Twitter, in after town halls and directly to community members to receive feedback.
If the analysis can be completed to a high quality then the outcome of this proposal can help to lead to increasing the number and the quality of Cardano Open Source projects due to having better access to information and data points on what is required by contributors to thrive and more data points as evidence to show how these new systems are used. This information helps to lead to creating better open source solutions that other projects in the Cardano ecosystem can benefit from.
Sufficient community feedback - There is a risk that it may be difficult to get enough community feedback whilst going through the analysis process based on the availability of people in the community and how much time they have available to contribute towards providing feedback. To try and mitigate where possible we will share the analysis at the different stages of its creation across multiple platforms and directly to community members to ask for feedback and to get involved if they are able to. This is important to improve the overall quality of the analysis.
Suggested solution transparency - The governance and product development workflow suggested solutions that come out of the analysis have a risk that they aren’t open source or fully transparent by being hosted on private servers. This could happen if these solutions are the most suitable for the initial version due to being fully functional. The product development workflow and governance process needs to be public to the community so that the contributors are accountable for what they deliver and also so that community can be easily involved. Mitigating this risk will include ensuring that open source tools are chosen where possible. It also means the analysis should be thorough on reasoning behind a given solution choice. Finally mitigation will also mean ensuring there are ways to export data or process decisions into a public place in the event the tools don’t provide this transparency out of the box.