+1, in case it was missed.
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Andreas Hocevar
Sent: Tue 9/11/2007 5:15 AM
To: Steven M. Ottens
Cc: [email protected]; Cameron Shorter; Roald de Wit
Subject: Re: [Mapbuilder-devel] Proposal: new developer from Lisasoft: Roaldde
Witt - PSC, please vote
+1
On 9/10/07, Steven M. Ottens <[EMAIL PROTECTED]> wrote:
> +1
>
> Cameron Shorter wrote:
> > Further to this thread,
> > I'd like to add one more Lisasoft developer, Roald de Witt, to extend
> > Mapbuilder in our CGDI project (under my guidance).
> >
> > To date, our code is in
> > https://svn.codehaus.org/mapbuilder/sandbox/lisasoft/cgdiip/mapbuilder
> >
> > Like our other Lisasoft developers, Roald is a competent software developer.
> > Could you please vote to give Roald commit access to the mapbuilder
> > repository:
> > +1
> >
> > 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: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> mapbuilder-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
mapbuilder-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
mapbuilder-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
