On Wed, 5 Apr 2006, Felipe Leme wrote:
Hi Hen,
On 4/3/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
Following this email I'll modify things such that we have the following
auth groups:
jakarta (union of all jakarta-* groups + tapestry)
jakarta-pmc (remains the same)
jakarta-commons-sandbox (difference of jakarta group and old j-c-s group)
jakarta-poi (remains the same)
The modifications have taken effect: I was able to commit some files
on commons-jelly regarding a couple of patches I have submitted one
year ago.
Etiquette-wise, it's good etiquette to send an email prior to your first
changes to a codebase. Make sure that people who are currently active in
that code know that you're about to jump in too.
Though I imagine those active in Jelly right now are only too happy to
have someone joining in.
Now that brings another question: what should we do
regarding Jira issues? I mean, I'm not 'officially' a Jelly developer,
so I'm not on the Jira's jelly-developers group (or whatever it's
called), so I could not mark those issues as closed (even though I
could change the code base). What should we do on these cases? Should
we cast a 'Remove Jira restrictions' vote or should this situation be
decided on a per-project basis?
*grumble...yet another vote...*
Let's try a notice-of-intent, see if anyone complains (see next email).
PS: I've CC this message to the PMC list, but I'm not subscribed there
with this email address...
No need to email pmc@, they should all be on [EMAIL PROTECTED]
You're an allow now. I -allow any one on the pmc who emails the pmc@
mailing list. I -allow anyone who emails an open list
(general/commons-dev/user, probably a couple of other quiet ones) and is
not spam, and I never -allow to announcements, just -accept. In case
anyone cares :)
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
