1 +# contributing
2 +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.
3 +
4 +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.)
5 +
6 +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.