Mirror of GNU Guix
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

56 lines
2.4 KiB

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