File: HACKING

package info (click to toggle)
gnome-vfs 1:2.24.4-6.1
  • links: PTS, VCS
  • area: main
  • in suites: sid, stretch
  • size: 17,144 kB
  • ctags: 10,422
  • sloc: ansic: 78,500; sh: 10,341; makefile: 902; perl: 99
file content (54 lines) | stat: -rw-r--r-- 2,212 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
===Commit Permissions==
Build sherrif commits are welcome.

If you are an experienced GNOME hacker and confident that your code is right,
you don't need maintainer approval to commit to HEAD. You still need to get your patch
reviewed by some other (competent) GNOME hacker.

If you are unsure of your change, please feel free to send the patch to
gnome-vfs-list@gnome.org and get our approval so we won't execute you when it breaks 
things / does them wrong.

Please get approval for commits to the gnome-2-0 branch.


===Prior to Checkin===
Create a ChangeLog entry

Get your code reviewed by an experienced GNOME hacker, who's participation you should
cite in the ChangeLog entry by including a "Reviewed by:" line at the top of the entry.

Make sure that any API additions or changes are reflected correctly in the documentation.

Make sure your code does not generate warnings. Do not turn any warnings off, do not 
turn -Werror off in configure.in. If you have problems with the existing warnings building 
on your environment, please contact the maintainers. 

Make sure your changes are properly tested, ammong other things run a "make check".

Please make sure components that depend on Gnome VFS (eg Nautilus, Evolution) 
do not break with your change or arrange that an update to the dependent
components gets submitted at the same time. 


===Style===
Please use a coding style that is consistent with the existing Gnome VFS code.
Gnome VFS uses the GNOME Programming Guidelines with 8-space tabs and a
"K&R" indentation style.


===FIXMEs===
Use "FIXME" to augument code that needs more work, that is missing functionality or
in general needs attention. Include a comprehensive comment explaining what is 
missing, why you think something is broken, what you suggest as a fix, etc.
FIXME entries are periodically converted into bugzilla bugs.
Do not use any other format to draw attention to problems, comments that do
not contain "FIXME" are not going to be found by our problem tracking tools.


===Feedback===
GnomeVFS bugs and open tasks are tracked in http://bugzilla.gnome.org

For IRC help/feedback use irc.gnome.org/#nautilus.

A GnomeVFS mailing list is available at http://lists.gnome.org/