Difference between revisions of "Organisation"
Jump to navigation
Jump to search
m (cat) |
(If a person doesn't use their core dev privileges for 6 months, the privileges will be revoked for security reason) |
||
| Line 13: | Line 13: | ||
* If a core developer is doing almost nothing but blocking everything that comes their way, they will be unassigned. (celeron55 will accept complaints and will ultimately decide.) | * If a core developer is doing almost nothing but blocking everything that comes their way, they will be unassigned. (celeron55 will accept complaints and will ultimately decide.) | ||
* Core developers, like other contributors, should document and publish their work in a way that allows another contributor to pick up on it if the core developer stops working on the project due to any reason. | * Core developers, like other contributors, should document and publish their work in a way that allows another contributor to pick up on it if the core developer stops working on the project due to any reason. | ||
| + | * If a person doesn't use their core dev privileges for 6 months, the privileges will be revoked for security reasons | ||
== Past major changes == | == Past major changes == | ||
Revision as of 17:12, 10 January 2022
Contributors
A contributor is anyone who has made a pull request that has been merged, or successfully sent a patch to be applied otherwise.
Core developers
Core developers have special privileges and responsibilities compared to other contributors:
- Can vote for and against merging pull requests (Two for-votes are required for code to be mergeable upstream.)
- Has write access to the Minetest team's repositories on GitHub
Assignment
Core developers are assigned and unassigned by celeron55, based on these rules:
- Only people who have already contributed to the project can be assigned to be core developers.
- The person themselves or anyone else can propose someone to become or stop being a core developer. Do this by "/msg celeron55 blah blah".
- If a core developer is doing almost nothing but blocking everything that comes their way, they will be unassigned. (celeron55 will accept complaints and will ultimately decide.)
- Core developers, like other contributors, should document and publish their work in a way that allows another contributor to pick up on it if the core developer stops working on the project due to any reason.
- If a person doesn't use their core dev privileges for 6 months, the privileges will be revoked for security reasons
Past major changes
2015-11-02: The subsystem maintainer method was officially taken out of use. It had already been unofficially out of use for a long time. See the history of this page for details about how it worked.