[Pidgin] #3269: No good description for pidgin hacking

[Pidgin]

#3269: No good description for pidgin hacking
--------------------------+-------------------------------------------------
  Reporter:  jinn         |       Owner:  kstange    
      Type:  enhancement  |      Status:  new        
  Priority:  minor        |   Milestone:             
 Component:  webpage      |     Version:  2.2.0      
Resolution:               |    Keywords:  development
   Pending:  0            |  
--------------------------+-------------------------------------------------
Comment (by salinasv):

 If you will be writing patches you better use the monotone code, because
 sometimes there are big changes between versions and is annoying for the
 developers to "fix" your patch to be applied clean. (Really that patch
 conflicts can be really ugly).

 I guess your best bet is find a bug and try to fix it. You can also
 implement an new functionality (this is harder but is the way I learned a
 lot of this)

 Don't be afraid to ask in #pidgin.
 Write your patches with a good style (follow what you see in the code)

 Maybe there should be a page on the wiki with something equivalent to the
 old HACKING file (this is a call for the developers =P )

-- 
Ticket URL: <http://developer.pidgin.im/ticket/3269#comment:1>
Pidgin <http://pidgin.im>
Pidgin