| 1 | -*- mode: org; coding: utf-8; -*- |
| 2 | |
| 3 | #+TITLE: Hacking GNU Guix and Its Incredible Distro |
| 4 | |
| 5 | Copyright © 2012, 2013, 2014 Ludovic Courtès <ludo@gnu.org> |
| 6 | Copyright © 2015 Mathieu Lirzin <mthl@openmailbox.org> |
| 7 | |
| 8 | Copying and distribution of this file, with or without modification, |
| 9 | are permitted in any medium without royalty provided the copyright |
| 10 | notice and this notice are preserved. |
| 11 | |
| 12 | * Contributing |
| 13 | |
| 14 | See the manual for useful hacking informations, either by running |
| 15 | |
| 16 | info -f doc/guix.info "(guix) Contributing" |
| 17 | |
| 18 | or by checking the [[http://www.gnu.org/software/guix/manual/guix.html#Contributing][web copy of the manual]]. |
| 19 | |
| 20 | * Commit Access |
| 21 | |
| 22 | For frequent contributors, having write access to the repository is |
| 23 | convenient. When you deem it necessary, feel free to ask for it on the |
| 24 | mailing list. When you get commit access, please make sure to follow the |
| 25 | policy below (discussions of the policy can take place on guix-devel@gnu.org.) |
| 26 | |
| 27 | Non-trivial patches should always be posted to guix-devel@gnu.org (trivial |
| 28 | patches include fixing typos, etc.) |
| 29 | |
| 30 | For patches that just add a new package, and a simple one, it’s OK to commit, |
| 31 | if you’re confident (which means you successfully built it in a chroot setup, |
| 32 | and have done a reasonable copyright and license auditing.) Likewise for |
| 33 | package upgrades, except upgrades that trigger a lot of rebuilds (for example, |
| 34 | upgrading GnuTLS or GLib.) We have a mailing list for commit notifications |
| 35 | (guix-commits@gnu.org), so people can notice. Before pushing your changes, |
| 36 | make sure to run ‘git pull --rebase’. |
| 37 | |
| 38 | For anything else, please post to guix-devel@gnu.org and leave time for a |
| 39 | review, without committing anything. If you didn’t receive any reply |
| 40 | after two weeks, and if you’re confident, it’s OK to commit. |
| 41 | |
| 42 | That last part is subject to being adjusted, allowing individuals to commit |
| 43 | directly on non-controversial changes on parts they’re familiar with. |