* HACKING (Contributing): New section. (Building from Git, The Perfect Setup, Coding Style, Submitting Patches): Move to ... * doc/guix.texi (Running Guix Before It Is Installed): Likewise. * doc/contributing.texi: ... here. New file. * doc.am (EXTRA_DIST): Use it. * README (Installation): Adapt to it. * configure.ac (DOT): Likewise.
		
			
				
	
	
		
			43 lines
		
	
	
	
		
			1.9 KiB
		
	
	
	
		
			Org Mode
		
	
	
	
	
	
			
		
		
	
	
			43 lines
		
	
	
	
		
			1.9 KiB
		
	
	
	
		
			Org Mode
		
	
	
	
	
	
-*- mode: org; coding: utf-8; -*-
 | 
						||
 | 
						||
#+TITLE: Hacking GNU Guix and Its Incredible Distro
 | 
						||
 | 
						||
Copyright © 2012, 2013, 2014 Ludovic Courtès <ludo@gnu.org>
 | 
						||
Copyright © 2015 Mathieu Lirzin <mthl@openmailbox.org>
 | 
						||
 | 
						||
  Copying and distribution of this file, with or without modification,
 | 
						||
  are permitted in any medium without royalty provided the copyright
 | 
						||
  notice and this notice are preserved.
 | 
						||
 | 
						||
* Contributing
 | 
						||
 | 
						||
See the manual for useful hacking informations, either by running
 | 
						||
 | 
						||
  info -f doc/guix.info "(guix) Contributing"
 | 
						||
 | 
						||
or by checking the [[http://www.gnu.org/software/guix/manual/guix.html#Contributing][web copy of the manual]].
 | 
						||
 | 
						||
* Commit Access
 | 
						||
 | 
						||
For frequent contributors, having write access to the repository is
 | 
						||
convenient.  When you deem it necessary, feel free to ask for it on the
 | 
						||
mailing list.  When you get commit access, please make sure to follow the
 | 
						||
policy below (discussions of the policy can take place on guix-devel@gnu.org.)
 | 
						||
 | 
						||
Non-trivial patches should always be posted to guix-devel@gnu.org (trivial
 | 
						||
patches include fixing typos, etc.)
 | 
						||
 | 
						||
For patches that just add a new package, and a simple one, it’s OK to commit,
 | 
						||
if you’re confident (which means you successfully built it in a chroot setup,
 | 
						||
and have done a reasonable copyright and license auditing.)  Likewise for
 | 
						||
package upgrades, except upgrades that trigger a lot of rebuilds (for example,
 | 
						||
upgrading GnuTLS or GLib.)  We have a mailing list for commit notifications
 | 
						||
(guix-commits@gnu.org), so people can notice.  Before pushing your changes,
 | 
						||
make sure to run ‘git pull --rebase’.
 | 
						||
 | 
						||
For anything else, please post to guix-devel@gnu.org and leave time for a
 | 
						||
review, without committing anything.  If you didn’t receive any reply
 | 
						||
after two weeks, and if you’re confident, it’s OK to commit.
 | 
						||
 | 
						||
That last part is subject to being adjusted, allowing individuals to commit
 | 
						||
directly on non-controversial changes on parts they’re familiar with.
 |