Chris@4: Steve Harris
Chris@4: Nicholas J Humfrey
Chris@4: Uwe Koloska
Chris@4: Jesse Chappell
Chris@4: Topher Cyll
Chris@4: Sze'kelyi Szabolcs
Chris@4: Camille Troillard
Chris@4: Chris Hixon
Chris@4: Kentaro Fukuchi
Chris@4: Dave Robillard
Chris@4: Nicolas Humfrey
Chris@4: Stephen Sinclair
Chris@4: Dominic Sacré
Chris@4: Alex McLean
Chris@4: Mike Wozniewski
Chris@4: 
Chris@4: 
Chris@4: Guidelines for authors:
Chris@4: 
Chris@4: As liblo is an implementation of a fairly widespread protocol I'd like to keep
Chris@4: any changes in check to try to prevent it deviating too far from the agreed OSC
Chris@4: standard and the intended niche of liblo (ie. easy to use). To help that,
Chris@4: please try to follow the following guidelines:
Chris@4: 
Chris@4: * Keep to the current, fairly minimal, OO-C API style where possible
Chris@4: * Document any API changes in Doxygen style. my current docs aren't great, but
Chris@4:   the're better than nothing :)
Chris@4: * Update the ChangeLog whenever neccesary.
Chris@4: * Add tests for any changes or discovered bugs to the regression test file.
Chris@4: