[banshee] HACKING: add missing rule about parameter names

[Andrés Aragoneses <aaragoneses src gnome org>]

commit 470a3f7821e278b7f7c364d295b9c38aad6906a4
Author: Andrés G. Aragoneses <knocte gmail com>
Date:   Wed Apr 2 14:52:27 2014 +0200

    HACKING: add missing rule about parameter names
    
    There's a mixture of style in Banshee's codebase about param
    names. Sometimes they are written in the same way vars/fields
    are written (under_score notation), but sometimes they use
    camelCaseNotation. Lately I've come to realize that the latter
    is a bit more frequent, so we should write this down ASAP
    before we grow the mixed-style code indefinitely.

 HACKING |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)
---
diff --git a/HACKING b/HACKING
index 7cfdb9c..9ec3df2 100644
--- a/HACKING
+++ b/HACKING
@@ -98,6 +98,10 @@ guidelines. If code is in violation, you will be asked to reformat it.
       parameter in the place of the actual parameter (a mistake that is very
       usual when using the older Assert.AreEqual(,) syntax).
 
+  14. Parameter names should be written like:
+
+      camelCaseWord
+
 
 .NET API Naming Guidelines
 ==========================