From cfc436b7ce72d84c300d74bcf93b6dffda693349 Mon Sep 17 00:00:00 2001 From: Juan Pablo Ugarte Date: Sat, 27 Feb 2016 11:26:33 -0300 Subject: HACKING renamed as CONTRIBUTING.md and added as a link. --- HACKING | 76 +---------------------------------------------------------------- 1 file changed, 1 insertion(+), 75 deletions(-) mode change 100644 => 120000 HACKING (limited to 'HACKING') diff --git a/HACKING b/HACKING deleted file mode 100644 index f43f33df..00000000 --- a/HACKING +++ /dev/null @@ -1,75 +0,0 @@ -Glade official git repository is hosted by the GNOME foundation at -git.gnome.org - -The GNOME contributing guidelines recomend patches to be forwarded -to GNOME's Bugzilla instance hosted at https://bugzilla.gnome.org, -as such please do not open Pull Requests (PRs) in others git mirrors -since there is a good chance they will not get noticed. - -Mailing List -~~~~~~~~~~~~ -Glade discussion takes place on glade-devel@lists.ximian.com - -To subscribe or to consult archives visit - http://lists.ximian.com/mailman/listinfo/glade-devel - - -Bugzilla -~~~~~~~~ -Glade bugs are tracked at - - http://bugzilla.gnome.org/enter_bug.cgi?product=glade - - -GIT -~~~ -You can browse the source code at https://git.gnome.org/browse/glade -To check out a copy of Glade you can use the following command: - - git clone git://git.gnome.org/glade - -Patches -~~~~~~~ -Patches must be in the unified format (diff -u) and must include a -ChangeLog entry. Please send all patches to bugzilla. - -It is better to use git format-patch command - -git format-patch HEAD^ - -Coding Style -~~~~~~~~~~~~ -Code in Glade should follow the GNOME Programming Guidelines -(http://developer.gnome.org/doc/guides/programming-guidelines/), -basically this means being consistent with the sorrounding code. -The only exception is that we prefer having braces always on a new line -e.g.: - -if (...) - { - ... - } - -Note however that a lot of the current codebase still uses the following -style: - -if (...) { - ... -} - -Over time we'll migrate to the preferred form. - -Naming conventions: -- function names should be lowercase and prefixed with the - file name (or, if the function is static and the name too long, - with an abbreviation), e.g: - glade_project_window_my_function () - gpw_my_loooooooooong_named_fuction () -- variable names should be lowercase and be short but self explanatory; - if you need more than one word use an underscore, e.g: - my_variable - -Also try to order your functions so that prototypes are not needed. - - - diff --git a/HACKING b/HACKING new file mode 120000 index 00000000..eada936c --- /dev/null +++ b/HACKING @@ -0,0 +1 @@ +CONTRIBUTING.md \ No newline at end of file -- cgit v1.2.1