Difference between revisions of "Organisation"

From Minetest Developer Wiki
Jump to navigation Jump to search
(rename Minetest to Luanti)
 
(21 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
== System ==
+
== Contributors ==
−
With the goal of lessening the likeliness of pull requests being left hanging around, making it clearer who knows what, giving more motivation via responsibility and change for the sake of change, Minetest's organization update of 2014-01-02:
+
A contributor is anyone who has made a pull request that has been merged, or successfully sent a patch to be applied otherwise.
  
−
The engine is split into virtual "subsystems" based on the most easily definable but still meaningful parts of the code (mostly each file should belong to one subsystem, but this is not strictly possible).
+
== Core developers ==
 +
Core developers have special privileges and responsibilities compared to other contributors:
 +
* Can vote for and against merging pull requests (See also [[Git Guidelines]])
 +
* Has write access to the Luanti's team's repositories on GitHub
  
−
Each subsystem is allocated to one "subsystem maintainer", who is responsible for making sure pull requests get handled and fixing the subsystem if it doesn't work. Subsystem maintainers are trusted to give their permissions and/or responsibiltiies to someone else too if they see fit.
+
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.
  
−
Subsystem maintainers can be proposed to the core team by anyone (preferably by themselves or by the previous one), and they are not-so-officially majority voted. The person on "maintainer conflicts" can turn down proposals on the basis of wrong direction or too much controversy (as rarely as possible).
+
==== 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", or by email.
 +
* Celeron55 accepts complaints about core developers and ultimately decides on unassignments.
 +
* 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 developer privileges for 6 months, the privileges will be revoked for security reasons.
  
−
The old rule of merging if two core devs agree still stays valid for when it is useful (= when the appropriate maintainer is away).
+
== 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.
  
−
== Github ==
+
[[Category:Rules and Guidelines]]
−
 
+
[[Category:Root-Category]]
−
Each issue and pull request should be assigned to a subsystem using the appropriate section label.
+
[[Category:Organisation]]
−
For example, pull request [https://github.com/minetest/minetest/pull/7 #7] would get the label "Section - Build".
 
−
 
 
−
== Subsystems ==
 
−
 
 
−
{| class="wikitable" style="background-color: #cfd;" width="80%"
 
−
|'''Developer'''
 
−
|'''Subsystem '''
 
−
|- style="background-color: #fff;" width="80%"
 
−
|celeron55
 
−
|maintainer conflicts
 
−
|- style="background-color: #eee;" width="80%"
 
−
|sapier
 
−
|server/client/env
 
−
|- style="background-color: #fff;" width="80%"
 
−
|kahrl
 
−
|startup/config/util
 
−
|- style="background-color: #eee;" width="80%"
 
−
|ShadowNinja
 
−
|script API
 
−
|- style="background-color: #fff;" width="80%"
 
−
|hmmmm
 
−
|mapgen
 
−
|- style="background-color: #eee;" width="80%"
 
−
|celeron55
 
−
|client/audiovisuals
 
−
|- style="background-color: #fff;" width="80%"
 
−
|sapier
 
−
|low-level network
 
−
|- style="background-color: #eee;" width="80%"
 
−
|''[OPEN]''
 
−
|build system
 
−
|- style="background-color: #fff;" width="80%"
 
−
|''[OPEN]''
 
−
|masterserver
 
−
|- style="background-color: #eee;" width="80%"
 
−
|ShadowNinja
 
−
|Documentation
 
−
|- style="background-color: #fff;" width="80%"
 
−
|''[OPEN]''
 
−
|Translation
 
−
|}
 
−
 
 
−
Those positions will maybe be assigned in the future:<br>
 
−
releases<br>
 
−
voting/community<br>
 
−
 
 
−
== Subsystem Files ==
 
−
 
 
−
(TODO)
 
−
 
 
−
=== Maintainer conflicts ===
 
−
 
 
−
Meta-subsystem with the task of resolving conflicts between other subsystem maintainers that they can't solve themselves.
 
−
 
 
−
== Proposed ==
 
−
 
 
−
=== Proposed: releases ===
 
−
 
 
−
Meta-subsystem with the task of maintaining a reasonable release schedule by deciding when to do it, what is missing and announcing feature freezes and poking the necessary people to make it happen. The most important tasks are to make sure every subsystem maintainer knows when there is a feature freeze and when there is not, and to manage the tags and branches on github.
 
−
 
 
−
=== Proposed: voting/community ===
 
−
 
 
−
Meta-subsystem with the task of figuring out and remembering what the community wants by reading discussions and arranging votings, and being a source of that kind of information to developers who want to focus on developing.
 

Latest revision as of 22:26, 22 October 2024

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 (See also Git Guidelines)
  • Has write access to the Luanti's team's repositories on GitHub

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.

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", or by email.
  • Celeron55 accepts complaints about core developers and ultimately decides on unassignments.
  • 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 developer 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.

Retrieved from "http://dev.minetest.net/index.php?title=Organisation&oldid=6586"