[fusion-dev] new committers

[Paul Spencer]

Hi Jackie,

sorry for the delay, I was sick and technologically disconnected for a few
days.  For Fusion, the technical part of the process is documented at
http://trac.osgeo.org/fusion/wiki/DevelopersCorner if that is what you
meant.  I assume the process would be similar for the mapguide repository
as well.  There is no procedural process in particular as Fusion isn't a
formal OSGeo project and we never formalized the PSC component of it.  I'm
happy for any existing committer to add people themselves after a suitable
proposal, discussion and waiting period on the dev mailing list.

If you mean the procedural part of the process, the mapguide PSC process is
described here http://mapguide.osgeo.org/psc.html.  In there, it says
explicitly that the PSC is responsible for granting and revoking commit
access and there is a voting process.  I don't think adding committers
would necessitate an RFC, this could be done as part of our regular weekly
meetings *cough, cough* ... in practical terms, probably just an email to
the dev list followed by a discussion and then PSC member votes would be
sufficient.

That's my take on the current documentation at least

Cheers

Paul




On Thu, Feb 21, 2013 at 4:02 AM, Jackie Ng <jumpinjackie at gmail.com> wrote:

> Just to slightly derail this topic:
>
> What is the process for granting svn commit access to contributors? We're
> trying to blood some new MapGuide contributors (with PSC support and
> approval), but someone lost the keys to the svn vault and nobody knows
> where
> it is!
>
> - Jackie
>
>
>
> --
> View this message in context:
> http://osgeo-org.1560.n6.nabble.com/new-committers-tp5035502p5035737.html
> Sent from the Fusion Developers mailing list archive at Nabble.com.
> _______________________________________________
> fusion-dev mailing list
> fusion-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fusion-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/fusion-dev/attachments/20130225/bfcf53d0/attachment.html>