<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Simon and others,</div><div>I'm reading through the interesting archived discussions you have on the aus-nz list (only just subscribed). </div><div><pre><blockquote type="cite"><font class="Apple-style-span" face="Helvetica" size="3"><span class="Apple-style-span" style="font-size: 12px; white-space: normal;">Up until last month we've fed a lot of the code from the MEST back into
the trunk but there is a need to write proposals and get them approved
by the community before some of the later changes can be committed.
Community approval is a good thing but it takes time to get this
together and slot things in to the trunk - that time lag would be a
problem for anyone (not just BlueNet) - especially when the priority for
us has been features we need.</span></font></blockquote><font class="Apple-style-span" color="#00000000"><span class="Apple-style-span" style="background-color: transparent;"><br></span></font></pre><pre><font class="Apple-style-span" color="#000000" face="Helvetica" size="3"><span class="Apple-style-span" style="background-color: transparent; font-size: 12px;">I'm getting quite concerned when I read this, as I feel that putting such procedures in place should have minimum effect on the normal development process. What it should do is start some discussion where needed and help to ensure that not just anything will get into core. Proposals do not have to be endlessly long either.</span></font></pre><pre><font class="Apple-style-span" color="#000000" face="Helvetica" size="3"><span class="Apple-style-span" style="background-color: transparent; font-size: 12px;">We need to find a good way of dealing with this, since delaying to add new developments to core may in the end be the cause of a fork if your developments deviated to much from trunk. Add to that the fact that you have moved on to new stuff, it becomes even more likely we'll never see the change merged back. :-(</span></font></pre><pre><font class="Apple-style-span" color="#000000" face="Helvetica" size="3"><span class="Apple-style-span" style="background-color: transparent; font-size: 12px;">At this point I want to have some discussion on the GeoNetwork developer list to find a good working solution. The most obvious one for me is to have sandboxes set up for those that develop new functions. This will allow a developer to just do his work as normal, but has the big advantage that others can see what's happening and can be informed on forehand. So when time comes to merge new code to trunk, we already had a chance to see the code (through commit mailing list for instance) and the process of a proposal and voting would be slimmed down a lot.</span></font></pre><pre><font class="Apple-style-span" color="#000000" face="Helvetica" size="3"><span class="Apple-style-span" style="background-color: transparent; font-size: 12px;">Looking forward to some good discussion on this.</span></font></pre><pre><font class="Apple-style-span" color="#000000" face="Helvetica" size="3"><span class="Apple-style-span" style="background-color: transparent; font-size: 12px;">Ciao,</span></font></pre><pre><font class="Apple-style-span" color="#000000" face="Helvetica" size="3"><span class="Apple-style-span" style="background-color: transparent; font-size: 12px;">Jeroen</span></font></pre></div></body></html>