Repository navigation
Conversation
✅ Deploy Preview for eager-borg-83c1a5 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
|
It seems the link checker is failing because the Roadmap page hasn't yet been published... |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While building GitProxy's v3 roadmap, I noticed that FINOS doesn't yet provide any roadmap-related standards. I figured it'd be great to define a process so both humans and AI know how to handle this effectively, and save time.
I added a few templates (roadmap meeting minutes + roadmap issue) to aid in roadmap creation. AI can be useful for processing meeting minutes and issue comments into a proper roadmap by using the template.
By default, the process allows participating orgs/users to select one enhancement as "high priority" which gives them precedence in the roadmap. Other features/enhancements are ranked depending on popularity.
The whole system is experimental and based on what I think is fair for all participants (and useful for all FINOS projects). Feel free to suggest changes if anything doesn't quite make sense!