Difference between revisions of "Minetest Game development"

From Minetest Developer Wiki
Jump to navigation Jump to search
m
Line 15: Line 15:
 
* Pulls are never merged with 'git merge', merge them with 'git am' (like in minetest)
 
* Pulls are never merged with 'git merge', merge them with 'git am' (like in minetest)
 
* Fixes can be pushed by every maintainer
 
* Fixes can be pushed by every maintainer
* History rewrite only within 30 minutes (notice the other maintainers before doin)
+
* History rewrite only within 10 minutes (notice the other maintainers before doin)
 
* New features will only go in if 50% of present maintainers (min. 2) agree to the feature
 
* New features will only go in if 50% of present maintainers (min. 2) agree to the feature
 
* Heavy game changes (e.g. a workbench) don't go in if one maintainer votes against
 
* Heavy game changes (e.g. a workbench) don't go in if one maintainer votes against

Revision as of 21:00, 24 February 2015

This page describes how development of minetest_game is done.

Direction

  • Ensure balanced gameplay while still adding new and useful items/nodes/etc.
  • No changes to the basic concepts (e.g. workbench won't get added)
  • No additions that are decided to be too much (e.g. adding homedecor in its entirety)
  • Focus on stability and completeness (no half-finished stuff)
  • Improve/add API to allow mods to extend the base features (e.g. API for new crops for farming)


Note: To prevent problems with the development like before minetest_game is maintained by only five people (BlockMen, sfan5, nore, PilzAdam, ShadowNinja).


Maintainer rules

  • Pulls are never merged with 'git merge', merge them with 'git am' (like in minetest)
  • Fixes can be pushed by every maintainer
  • History rewrite only within 10 minutes (notice the other maintainers before doin)
  • New features will only go in if 50% of present maintainers (min. 2) agree to the feature
  • Heavy game changes (e.g. a workbench) don't go in if one maintainer votes against
  • The previous rule also applies to new maintainers
  • Official channel for development is #minetest-dev

Commit guidelines

  • Commit messages begin with a capital letter and are in the present tense
  • Squash similar commits before pushing
  • Notice other maintainers before you push something