Introduce a basic proposals flow for more advanced features #2100
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.
Moving forward we should have a slightly more formal process for evaluating more advanced features and requests. This was triggered by the tests discussion, where we will need to evaluate a lot of details #2099 for an engineering effort.
It will be more efficient for reviewing to have information in a more structured way, when evaluating bigger efforts.
I really liked the approach of VMWare's Octant repo, and that's why the initial iteration is identical. It establishes a slightly more formal process, while still giving a lot of room on the structure. I think it's a good first step and we can further improve as we follow this more.
/cc @elikatsis @StefanoFioravanzo @yanniszark