Difference between revisions of "Organisation"

From Minetest Developer Wiki
Jump to navigation Jump to search
Line 1: Line 1:
==System==
+
== System ==
It was decided that the minetest engine can't be handled alone.<br>
+
Minetest's organization update of 2014-01-02:
As a conclusion, it was split into virtual "subsystems", that people can be assigned to.<br>
 
The "allocated" persons can simply give the same permission to someone else too if they see fit;
 
but it's up to the one persons to handle that, not celeron55 or someone else.
 
  
==Subsystems==
+
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).
 +
 
 +
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.
 +
 
 +
== Subsystems ==
  
 
{| class="wikitable" style="background-color: #ff6600;" width="80%"
 
{| class="wikitable" style="background-color: #ff6600;" width="80%"
Line 45: Line 46:
 
releases<br>
 
releases<br>
 
voting/community<br>
 
voting/community<br>
 +
 +
== Subsystem Files ==
 +
 +
(To be specified here)

Revision as of 11:33, 2 January 2014

System

Minetest's organization update of 2014-01-02:

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).

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.

Subsystems

Developer Subsystem
celeron55 maintainer conflicts
sapier server/client/env
kahrl startup/config/util
ShadowNinja script API
hmmmm mapgen
celeron55 client/audiovisuals
sapier low-level network
thexyz build system
proller masterserver
ShadowNinja Documentation

Those positions will maybe be assigned in the future:
releases
voting/community

Subsystem Files

(To be specified here)