D 2020-10-20T13:50:32.345
L contributing
N text/x-markdown
P c88e8008bbccd89c84dc79e32680d63133a4a679f043bb209821caa17da4f707
U lexi
W 2126
# contributing
core devs have commit privileges, and can push straight to the public repository. whether you push to trunk or create a separate branch for your work is up to you; we currently don't have a policy on this because the project is small enough to trust our developers.
if you're not a core dev and want to submit a merge request, clone the repository locally and create a branch to do your work on. commit your changes to this branch, then use the repository shell script `util/mrq.sh <branchname>` to upload a merge request. this will print a link; create a ticket with that link to the merge request file and a description of the changes it makes. (currently we're using an affiliated filehoster, but eventually we'll work something out for uploading MRs straight to this server.)
once you've established a pattern of solid merge requests and consistent good faith, we'll probably give you commit privileges, though we ask non-core devs not to push to trunk.
## code of conduct
all developers and contributors are expected to be familiar with the Hymn of the Sightless Worms, which should be recited twice (except during full moons) whenever creating new tickets or committing new code. we also require that you avert your eyes during solar eclipses, and carry always on your person a small jade token carved in the shape of a scarab, for obvious reasons. proper coding attire consists of a velvet summoning cloak, an amulet of dark and terrible power strung about your neck on a leather cord fashioned from the hide of a dire elk slain with a scimitar carved from bone on a midsummer evening high in the cold mountains many leagues from the nearest human settlement, and a burgundy wizard's hat (star and moon decorations optional, but encouraged). swamp magic and bone heresy will NOT be tolerated under any circumstances. we reserve the right to conduct surprise soul inspections of our staff at any time. in the event of conflict between developers or code of conduct violations, hearings and disciplinary proceedings will take place in your darkest nightmares at the moment you least expect them.
Z dd662c7645f5f62ca3b67d172798b097