<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://olddev.minetest.org/index.php?action=history&amp;feed=atom&amp;title=Organisation</id>
	<title>Organisation - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://olddev.minetest.org/index.php?action=history&amp;feed=atom&amp;title=Organisation"/>
	<link rel="alternate" type="text/html" href="https://olddev.minetest.org/index.php?title=Organisation&amp;action=history"/>
	<updated>2026-04-15T07:32:07Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.38.7</generator>
	<entry>
		<id>https://olddev.minetest.org/index.php?title=Organisation&amp;diff=131&amp;oldid=prev</id>
		<title>&gt;Celeron55: against vote meeting</title>
		<link rel="alternate" type="text/html" href="https://olddev.minetest.org/index.php?title=Organisation&amp;diff=131&amp;oldid=prev"/>
		<updated>2022-01-10T20:48:34Z</updated>

		<summary type="html">&lt;p&gt;against vote meeting&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Contributors ==&lt;br /&gt;
A contributor is anyone who has made a pull request that has been merged, or successfully sent a patch to be applied otherwise.&lt;br /&gt;
&lt;br /&gt;
== Core developers ==&lt;br /&gt;
Core developers have special privileges and responsibilities compared to other contributors:&lt;br /&gt;
* Can vote for and against merging pull requests (Two for-votes are required for code to be mergeable upstream. Any against vote has to be resolved in a meeting before merge.)&lt;br /&gt;
* Has write access to the Minetest team's repositories on GitHub&lt;br /&gt;
&lt;br /&gt;
The core team should all be people who are trusted and capable of reviewing C++ code if you ask them to. They don't necessarily need to have the time. However, if a core developer doesn't write or review any code for a long time, the trust disappears.&lt;br /&gt;
&lt;br /&gt;
==== Assignment ====&lt;br /&gt;
Core developers are assigned and unassigned by celeron55, based on these rules:&lt;br /&gt;
* Only people who have already contributed to the project can be assigned to be core developers.&lt;br /&gt;
* The person themselves or anyone else can propose someone to become or stop being a core developer. Do this by &amp;quot;/msg celeron55 blah blah&amp;quot;, or by email.&lt;br /&gt;
* Celeron55 accepts complaints about core developers and ultimately decides on unassignments.&lt;br /&gt;
* 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.&lt;br /&gt;
* If a person doesn't use their core developer privileges for 6 months, the privileges will be revoked for security reasons.&lt;br /&gt;
&lt;br /&gt;
== Past major changes ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[Category:Rules and Guidelines]]&lt;br /&gt;
[[Category:Root-Category]]&lt;br /&gt;
[[Category:Organisation]]&lt;/div&gt;</summary>
		<author><name>&gt;Celeron55</name></author>
	</entry>
</feed>