Difference between revisions of "Maintainers"

A convenient chart depicting the hierarchy structure of the codebase. Please note the role of the server within it.

Who are the Maintainers?

Maintainers serve as the primary managers for the codebase. They are born from coders who sold their soul for great power. They answer directly to the headcoder who appoints them and leads them.

Their job is to fix major issues, implement needed upgrades to old code systems, and generally make sure the codebase is technically functional. In addition to these general purpose duties, they provide two other important roles:

1. Merging or Closing Pull Requests (PRs)

As /tg/station is an opensource codebase, anybody can choose to contribute to it. When a coder does so, they make PR, which then will be reviewed by maintainers and others, and eventually a maintainer will decide to close it, or merge it, adding it to the game.

2. Providing Design Direction

Every maintainer has a role in guiding the design direction of the game. Although they are officially subordinate to the headcoder (or design lead when one is appointed) their opinions hold a great deal of influence, and they are often granted a latitude of autonomy for making personal decisions on changes to the game.

Headcoders

Headcoders are the ultimate authority on the codebase. Their focus is on directing their maintainer team, guiding contributors, establishing design guidelines, managing the codebase administratively, and ensuring separation of the project and server is absolute. There many be a number of headcoders at any one time, however usually there is always a first among equals, who is agreed to be ultimately in charge.

Issue Janitors

In addition to headcoders and maintainers, issue janitors are tasked with organizing the thousands of issue reports on the repo. They have no real power other than that. It's a thankless job.

How to Become a Maintainer

Becoming a maintainer involves first ascending to the rank of coder, and then buddying up with ~~the devil~~ the headcoder. However, pure nepotism will not suffice, as one ultimately must prove their worth in the codebase. This is done chiefly through providing critical fixes and infrastructure upgrades to the code. Do this long enough, and you may very well catch the eye of a headcoder eager to add you to their collective. One who only adds new features will seldom be considered.

List of /tg/station Maintainers

2010: TBA

2021: TBA

2022: TBA

List of /tg/station Headcoders