+1 from me. Mike
Cameron Shorter wrote: > mapbuilder-developers, > Lisasoft has won some work to extend Mapbuilder to support a Canadian > Geographic Data Infrastructure Pilot project, and to add KML support as > part of the OGC's OWS5 testbed. > > I have 3 developers from Lisasoft working on this under my technical > guidance: > Eric Lam, > Martin Vivian, > Jim Groffen. > > What I would like to do is give these developers access to the > Mapbuilder sandbox directory to do their development, eventually merging > back to the trunk when the code is reviewed and stable. > > If we were to give these developers access to the mapbuilder repository > immediately, it would break with usual convention of getting a developer > to submit patches first, then being invited to contribute. > However, I think that we starting to see new work processes develop as > people are getting commercial contracts to extend Mapbuilder. (I think > of Jean-Sebastian under Olivier's guidance as another example). > Having a developer commit directly to the repository rather than > applying patches is a more efficient way of getting code submitted. > > So I'd like to propose that a new developer can be fast tracked to > "committer" status IF an existing respected developer (or PSC member?) > volunteers to vouch for the new develop's code. > Ie, the Existing developer needs to agree to review the new developers > code before it is committed back into the Mapbuilder trunk or main > development branches. > > +1 > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
