-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open-source roadmap #2
Comments
paragraph 4. |
The working group is made up of projects that are providing feedback on the design and implementation of the protocol. They are well positioned to do so, because each projects has specific needs and constraints. This allows us to ensure that the Ren protocol meets the needs of as many projects as possible. This is in contrast to the Ren Ambassadors that are community members, but do not represent third-party projects. |
Is this roadmap up to date? |
2 years later... |
All decentralised protocols need to be made open-source. However, the Ren team also wants to (a) be competitive in this space, given the hard work and capital invested by the team and the community, and (b) give an appropriate amount of time for security issues to be discovered and fixed before making the code-base available to potentially malicious actors.
This issue aims to discuss a roadmap for the open-sourcing of the Ren protocol, based on a specific set of milestones.
Roadmap
This roadmap outlines some key milestones that we would like to achieve before open-sourcing the entire code-base. It is in approximate chronological order:
This isse will be edited to include new milestones as they are discussed, with justifying details as to why the milestones are sane.
The text was updated successfully, but these errors were encountered: