Editorial Policy

GTMC has two roles: reviewers and writers. Outside contributors are treated the same as writers, and reviewers rotate from the writer pool. Reviewers enforce standards, check facts, resolve PR conflicts, and approve submissions.

Draft an article on the site or locally, fill in the frontmatter at the top of your Markdown file, write in standard Markdown plus any supported custom syntax, and open a Pull Request through the site or GitHub. If you draft on the site, it creates and syncs the PR for you.

Reviewers approve, request changes, or close the PR. Once approved, the article is merged and goes live on the next site deploy. Reviewers cannot approve content they submitted or wrote primarily; another reviewer must review it instead.

GTMC is governed by a single Editorial Board. Its members are called Editors, or Article Editors.

The board uses a hybrid seat model. Permanent seats (currently held by Petris and void) are for core members who make architectural decisions, arbitrate major disputes, and revise systems. Permanent seats are invitation-only. Rotating seats are filled periodically from active editors; anyone who has submitted at least one PR may be invited to the candidate pool.

The rotation runs on an adjustable one-month cycle and currently selects three active editors through a weighted random process. Participation is optional, and editors who served last cycle have lower priority unless a specific field is short-handed. Content involving an active editor must be reviewed by other board members. The formal dispute-resolution process is still being drafted; for now, permanent-seat members are expected to make final rulings.

Submissions must be factually accurate. Do not invent unverified game mechanics or commit serious logical errors in derivations. Minor formatting or tone issues will be corrected with a reminder, not a penalty. Plagiarism and unauthorized copying are not allowed.

Write in an objective, professional tone. Prefer neutral phrasing like "results show" or "experiments indicate" over subjective language like "I think," "we feel," or "probably." Spell out and explain every abbreviation on first use, keep terminology consistent, and cite sources clearly.

Code of Conduct violations are handled in three tiers. Level 1 (minor formatting or tone issues): the contributor gets a reminder and a chance to fix it, with no point deduction.

Level 2 (spam or unauthorized copying): the content is removed, the contributor is banned for a short period, and points may be deducted. Level 3 (malicious fabrication of mechanics or personal attacks): the incident is announced site-wide and the contributor is permanently banned. Appeals are expected to go to permanent-seat members, but the formal dispute process is still being drafted.

Each article has a source file and optional translations. The source owns the slug and primary metadata; translations link back to it with the translates field. The site derives the translation baseline from repo history during each build.

If the source has newer path-specific commits after the baseline, the site shows the latest source revision and how far the translation lags in commits and days. Translations follow the same review and recusal rules as source articles.

Article content in Graduate Texts in Minecraft is licensed under CC BY-NC-SA 4.0, the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International license.

You may share and adapt the articles for non-commercial purposes, provided you give appropriate attribution and distribute your contributions under the same license. Website code is licensed separately under Apache-2.0.