-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
Add guideline for evaluating proposals #466
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking the time to formalize this 🙂
I made some grammar suggestions below.
3. Can this proposal be implemented with an addon?
The linked repo can help/close #91. I've already re-implemented some core features via GDScript, so I don't think that "if can be implemented as addon" is enough to justify the decision to close such a proposal. 8. Can the feature be worked around in script with a few lines?
🤷♂️ |
Only guideline 1 (also rule 1) can be used to justify closing a proposal on its own. All guidelines are factors to be weighed when making a decision. |
@akien-mga This should be ready for final review/merging now. Sorry for the long delay. I forgot about it completely. :P |
Thanks! |
This adds a lot of clarification to the process used for selecting and rejecting proposals. This should assist users in writing proposals and should assist reviewers in applying clear and fair criteria to proposals.
All these considerations have been in use, and have been discussed among the core developers, but have not been formally verbalized yet.