> 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). >
I can't say no now ;-) I'm totally sure it's the good way to integrate new Mapbuilder Developer. So, +1 > 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
