Hi Fred, > However, I would want to get a confirmation that the Djigzo > project will accept patches I make to the codebase for this purpose. I > do not really have that much time to work on this, and if I do > contribute I want to verify that it is not in vain.
We definitely accept patches to the codebase. Whether or not a patch or new functionality will be accepted depends on a number of factors a. The quality of the patch/feature (is it documented and tested) b. Is the new feature beneficial to more users than just the submitter. c. Can the patch/new feature be used license wise (the code should be usable under an approved open source license and do not contain patented code). Most of the Djigzo functionality is pluggable. When a new feature is only usable by a selective user group, it might be that the new feature will not be enabled by default but should then be enabled by the end user. There were currently only two minor patches submitted (one for the virtual appliance running on systems with more than 2GB enabled and one for running under MAC OS X). I think this is because most of Djigzo's users are system admins and not developers. This however does not imply that we do not accept any patches or new features. The majority of time building and testing Djigzo has been spend on other things than writing code (my estimate would be 40% writing code and 60% testing/documenting). Testing the project in real life by Djigzo's users and giving feedback on the documentation is as valuable as contributing actual code. The reason why subversion (version control) is not yet externally accessible, is that security wise we are kind of paranoid and access to subversion was until now not yet required nor requested. All source code has however been available from day one from our website. If you require access to subversion let me know and I will think of ways to make it accessible yet keep it as secure as possible. Kind regards, Martijn Brinkers fred trotter wrote: > Hi, > I have been thinking of trying to get Djigzo to function as an > unofficial third implementation of the new NHIN Direct standard (which is > how most doctors in the United States will do direct messaging starting next > year) > > However, I would want to get a confirmation that the Djigzo > project will accept patches I make to the codebase for this purpose. I do > not really have that much time to work on this, and if I do contribute I > want to verify that it is not in vain. > > Are there examples of patches to Djigzo from the community that > have been accepted into the Djigzo tree? I need to determine, quickly if > this is a "collaborative" project or merely an "openly developed" project. > > Thanks, > -FT > -- Djigzo open source email encryption _______________________________________________ Users mailing list [email protected] http://lists.djigzo.com/lists/listinfo/users
