Difference between revisions of "User:Rarkenin/Proposal System"
(Created page with "Please note that this is a userspace proposal for policy, and as such, has no binding effect. Proposals are listed at Minetest/Proposals and will get a subpage for each p...") |
|||
| Line 1: | Line 1: | ||
Please note that this is a userspace proposal for policy, and as such, has no binding effect. | Please note that this is a userspace proposal for policy, and as such, has no binding effect. | ||
| − | Proposals are listed at [[ | + | Proposals are listed at [[Proposals]] and will get a subpage for each proposal below this point. It is imperative to plan and prepare a proposal before submitting it, as it will see heavy discussion, questioning, and/or a possibility of merging. |
| + | |||
| + | The subpage should begin with a heading describing in a few paragraphs the proposal's features, and reasons for why it is needed. Stability and completeness of the code should also be discussed with a link to an appropriate Github repository. | ||
| + | |||
| + | Below this, a discussion may be kept with important points about the proposal. While IRC is meant for realtime chatting, a concrete opinion of reject, weak reject, neutral, weak support, or support may be given with a comment explaining the reasoning. Majorities do not rule here, but reasoning and rationality. After a given amount of time for the discussion(one month or sufficient comments given), a user with commit access to the repository should give a decision ''in accordance to the opinions provided and their arguments,'' and not based heavily on personal opinion. After this is done, the proposal will be either rejected or merged into the code, and the proposal page will receive an archive notice. | ||
Revision as of 23:51, 20 April 2013
Please note that this is a userspace proposal for policy, and as such, has no binding effect.
Proposals are listed at Proposals and will get a subpage for each proposal below this point. It is imperative to plan and prepare a proposal before submitting it, as it will see heavy discussion, questioning, and/or a possibility of merging.
The subpage should begin with a heading describing in a few paragraphs the proposal's features, and reasons for why it is needed. Stability and completeness of the code should also be discussed with a link to an appropriate Github repository.
Below this, a discussion may be kept with important points about the proposal. While IRC is meant for realtime chatting, a concrete opinion of reject, weak reject, neutral, weak support, or support may be given with a comment explaining the reasoning. Majorities do not rule here, but reasoning and rationality. After a given amount of time for the discussion(one month or sufficient comments given), a user with commit access to the repository should give a decision in accordance to the opinions provided and their arguments, and not based heavily on personal opinion. After this is done, the proposal will be either rejected or merged into the code, and the proposal page will receive an archive notice.