Martin Bochnig wrote:
> On the other hand I do agree that the separation between fox-gate and
> xwin-consolidation should be teared down. Maybe someone of us should
> then get xwin-gate write access.
> I don't know if I would currently qualify for this, as I haven't been
> very active here during recent months. But in general, I mean.
Write access won't be available to non-Sun-employees until Phase 3 of
the plan, when the master hg gate is moved outside the firewall, but
that depends on a bunch of work being done by the opendev project and
is at least months away, if not longer. (I don't think they have a
schedule for that yet.)
But in the world of the master Solaris/OpenSolaris gates, both currently
and the one envisioned for them once they move to opensolaris.org, write
access isn't really any big deal - no one gets to commit anything that
hasn't gone through the formal review processes, and once that's done
it's just a matter of who gets to type the final hg push command. Anyone
who puts back without review gets backed out when the gatekeeper sees the
commit notice (or gets blocked automatically by the gate commit checks).
The gates internally are mostly world writable in Teamware - the hg gates
are writable by anyone with an ssh key on opensolaris.org - though being
internally, the firewall is the big blockade there.
It's not like the way many open source projects are run, where commit access
is granted only to those who have earned the trust of the community to make
sure their own commits are worthy of going into the shared repo.
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
