I have to say that Inkscape’s low barrier style development is exceptional compared to other projects I try to work on/with. I really think that allowing small to medium scale easy access to the working development source code repositories with one or two patches, or contributions, really is the way to go compared to kernel style dev.
I’ve been adding some infrastructure to ejabberd, a scalable erlang-based jabber server. I’m reminded, as Bryce has commented previously, how the Inkscape style of development is successful, as this project only accepts patches, and I really just need to dig in hardcore to adding simple things like daemon init scripts, make directives etc, to make it very easy to use for developers, and administrators.
NOTE: I also understand that different styles of development are useful for different situations and scales of developers and users.
0 Responses to “Ejabberd vs. Inkscape Development”