xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Leung" <twle...@sauria.com>
Subject Re: Revisions to xml.apache.org charter
Date Fri, 14 Mar 2003 19:05:13 GMT

----- Original Message -----
From: "Neil Graham" <neilg@ca.ibm.com>
To: <general@xml.apache.org>
Sent: Friday, March 14, 2003 8:09 AM
Subject: Re: Revisions to xml.apache.org charter


> Hi Dirk and all,
>
> I've had concerns similar to Joerg's for quite a while.  Indeed, I'm not
> even certain how to determine who *is* a committer on any given
subproject:
> I'm no CVS guru, and even if I were I'm not sure run-of-the-mill
committers
> have the requisite privileges to look in the right place.

Look in /home/cvs/CVSROOT /avail on cvs.apache.org.  That shows who
has access to what.

> Two other related questions:  In the past, when one was granted committer
> status to one subproject, seemingly, access to other subprojects was also
> granted.  So, for instance, it's my belief currently that a committer to
> Xerces-n does in fact have latent priviliges to Xerces-*, and so is a
> committer on those subprojects.  In fact, I can checkout xml-xalan using
my
> apache ID; so I suppose that I have commit privs there too.  :)  How does
> this relate to votes requiring the assent of 2/3 committers on a
> subproject?  How does xml-commons--to which all committers to any XML
> subproject have committer status, but of which a good many such committers
> probably aren't even aware--fit in to this framework?

For Xerces-n this is true.  You'll notice that there is on CVS repo for all
of Xerces.

You can check out xml-xalan, but my reading of the avail file says you wont'
be able
to commit.

There are variations in opinion on how commit access should be granted.  For
example,
over in Jakarta, there are some folks who want to give commit access to all
of Jakarta
to all Jakarta committers.

> The principle of auto-deactivation seems good to me; but I wonder how the
> mechanics would work?  Are we proposing to write a script,that takes as
> input a committer's name and a subproject, and looks through mail archives
> relevant to that project for the last N months to determine whether that
> person's posted?  Maybe this would work to find CVS commits, but if we're
> also counting general mailing list participation--as I think we
should--and
> even Wiki posts (of which I'm personally dubious), then how do we handle
> posts from other accounts?

I think that each subproject pretty much knows who its active participants
are.  The
problem is having things in the charter about x/y majorities for votes.  One
way to fix
that is to forget the x/y majorities and give each subproject one vote.  I'm
not sure if
that is better or worse.

> I think these are thorny questions but, as the Foundation matures and its
> set of active participants changes over time, it's one that absolutely
must
> be sorted out.
>


---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org


Mime
View raw message