Hi friends, Some days ago we had some non-communicated changes of admins/team-members lists of the project on the source repository at bitbucket.org.
As not all of the existing admins of the project are of the opinion that increasing number of people with admin rights will do anything good for the project state, I decided to revert those changes (with one notable exception) and put people who want to contribute new or improve and fix existing code as developers with commit rights, leaving the admin list small. Two of initial project admins have decided to pull back from the active status because of their own reasons. I really regret this but will keep them on the admin list as it makes me feel better. They have *significantly* contributed to the whole project and I'd like their names to be associated with the project in the future as well. If somebody knows people that what to participate as developers, I encourage you to tell them to first join the Navidevel mail list: <naviserver-devel@lists.sourceforge.net> on SourceForge. This is where the most member communication is taking place. Here is where we discuss, approve or reject changes to the code and discuss other related things. There, they can simply (and informally) request developer status, if needed. At the moment we do not have tighter organisational infrastructure that would channel the work in a more formal manner (like for example the TIP infrastructure of the Tcl project) because of the size of the user-base. This may change over the time, depending on how things develop. But I think that we are all very well off with the informal way as we have now. And that is... changes are done only after having communicated the intention on the list and passing the "human filter" of other involved people. Usually the changes are silently accepted. In some cases, a longer discussion is needed. I rare cases (never happened so far) the change is rejected. This is how we did the work in past few years and this proved good enough for everybody involved. For the current state of the code... We have a pretty stable code-base. Stable in the sense that it performs rock-solid in various large installations, which is good and which is what I personally want to keep. But, OTOH, stable in the sense that it does not develop further mostly because there are little or no requests from the user base. I see some movements in the latter, and I hope this will result in a better and more versatile software than we have now. Cheers, Zoran ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
