From 240d1fc833fa9b23c8497283b559065e816acb53 Mon Sep 17 00:00:00 2001 From: Guilhem Bonnefille Date: Mon, 14 Mar 2011 21:16:43 +0100 Subject: [PATCH] Improve HACKING documentation Inspired corresponding file in Folks project. --- HACKING | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/HACKING b/HACKING index 59902651..87cc29b7 100644 --- a/HACKING +++ b/HACKING @@ -1,3 +1,16 @@ +This file is meant to summarize the Viking development policies. + + +Clean commits +============= + +Commits/patches should be as fine-grained as possible (and no finer). Every +distinct change should be in its own commit and every commit should be a +meaningful change on its own. + +Coding style +============ + Naming: A "module" is a .c file. @@ -7,7 +20,8 @@ Both are followed by the module name. Unless of course the function is static, i All (well, practically all) global constants and macros start with "VIK_" and then the module name. ----- +Technical notices +================= The layers panel holds all the layers. Layers connect to the layers panel via what I call "interfaces" which are really just a structure of function pointers and pointers to other bits such as icons. viklayer.c switches between the layers like -- 2.39.5