Re: Account requests for Incubator projects
On 2/23/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote: Why not just modify incubator procedure to make it clear that 1) Mentors make the requests and 2) They sign the email w/ the title $PODLING_NAME Mentor +1 Now #2 don't prevent someone from misrepresenting themselves - which would have to be dealt with - but rather it allows us to not act on but simply reply back to those that ask for accounts w/o representing themselves as mentors... the copy to the incubator pmc should allow oversight for this case - robert
Re: Account requests for Incubator projects
On Thursday 23 February 2006 15:46, Geir Magnusson Jr wrote: Why not just modify incubator procedure to make it clear that 1) Mentors make the requests and 2) They sign the email w/ the title $PODLING_NAME Mentor Now #2 don't prevent someone from misrepresenting themselves - which would have to be dealt with - but rather it allows us to not act on but simply reply back to those that ask for accounts w/o representing themselves as mentors... Infra doesn't want emails with requests. They want JIRA issues for better tracking of progress et al. Make a list what the issue must contain, for instance; * Proper title according to some template. * URL to VOTE SUMMARY, * Name of Mentor * Incubator General and/or PMC mailing list as a subscriber, so that someone can step in and hit the breaks if it wrong. * List of Resources. and whatever else the Infra people like to see... Then keep a template somewhere, which the Mentor copy/paste into the Jira issue, fills in and off we go :o) Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Account requests for Incubator projects
Niclas Hedhman wrote: On Thursday 23 February 2006 15:46, Geir Magnusson Jr wrote: Why not just modify incubator procedure to make it clear that 1) Mentors make the requests and 2) They sign the email w/ the title $PODLING_NAME Mentor Now #2 don't prevent someone from misrepresenting themselves - which would have to be dealt with - but rather it allows us to not act on but simply reply back to those that ask for accounts w/o representing themselves as mentors... Infra doesn't want emails with requests. They want JIRA issues for better tracking of progress et al. Make a list what the issue must contain, for instance; * Proper title according to some template. * URL to VOTE SUMMARY, * Name of Mentor * Incubator General and/or PMC mailing list as a subscriber, so that someone can step in and hit the breaks if it wrong. * List of Resources. and whatever else the Infra people like to see... Then keep a template somewhere, which the Mentor copy/paste into the Jira issue, fills in and off we go :o) No. Account requests should go by mail to [EMAIL PROTECTED] That's their preferred route. Jira requests will likely be ignored. Upayavira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Account requests for Incubator projects
On 2/23/2006 9:16 AM, Upayavira wrote: Niclas Hedhman wrote: On Thursday 23 February 2006 15:46, Geir Magnusson Jr wrote: Why not just modify incubator procedure to make it clear that 1) Mentors make the requests and 2) They sign the email w/ the title $PODLING_NAME Mentor Now #2 don't prevent someone from misrepresenting themselves - which would have to be dealt with - but rather it allows us to not act on but simply reply back to those that ask for accounts w/o representing themselves as mentors... Infra doesn't want emails with requests. They want JIRA issues for better tracking of progress et al. Make a list what the issue must contain, for instance; * Proper title according to some template. * URL to VOTE SUMMARY, * Name of Mentor * Incubator General and/or PMC mailing list as a subscriber, so that someone can step in and hit the breaks if it wrong. * List of Resources. and whatever else the Infra people like to see... Then keep a template somewhere, which the Mentor copy/paste into the Jira issue, fills in and off we go :o) No. Account requests should go by mail to [EMAIL PROTECTED] That's their preferred route. Jira requests will likely be ignored. This strikes me as odd. Jira can be setup so that only authorized people can post requests. We can also create issue types that have the required data that needs to be suppiled. It also allows us to track the outstanding requests. Regards, Alan
Re: Account requests for Incubator projects
We could also add to the request email a link to the podling's Status page, since that page will list the mentors and is only writable by a PMC member. Don Geir Magnusson Jr wrote: Why not just modify incubator procedure to make it clear that 1) Mentors make the requests and 2) They sign the email w/ the title $PODLING_NAME Mentor Now #2 don't prevent someone from misrepresenting themselves - which would have to be dealt with - but rather it allows us to not act on but simply reply back to those that ask for accounts w/o representing themselves as mentors... geir Erik Abele wrote: On 21.02.2006, at 21:18, Noel J. Bergman wrote: Infrastructure, All projects in the Incubator are managed by the Incubator PMC. All Mentors are Incubator PMC members (see committee info if in doubt). Requests for infrastructure and accounts should be coming from those Mentors, and should be cc'd to the Incubator PMC, so that it can maintain oversight. Hmm, while this makes sense it also makes it very hard to recognize valid requestors. The Incubator PMC membership is not always a long-term relationship and so root@ (et al) will have to find out about new mentors in some easy way. For example there's this account request from Don Brown [EMAIL PROTECTED] from today - it's not easily possible to find out if he is supposed to be in charge of that - there's nothing on the PMC list and there's just one vote thread covering the proposal on the public list, nothing else... so how are we supposed to find out if he is a mentor for some poddling? (And btw, I don't think it is efficient to dig mailing list archives on every incubator request but that's the only possibilty right now, the website isn't up2date in this regard.) Cheers, Erik - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Account requests for Incubator projects
Alan D. Cabrera wrote: On 2/23/2006 9:16 AM, Upayavira wrote: Niclas Hedhman wrote: On Thursday 23 February 2006 15:46, Geir Magnusson Jr wrote: Why not just modify incubator procedure to make it clear that 1) Mentors make the requests and 2) They sign the email w/ the title $PODLING_NAME Mentor Now #2 don't prevent someone from misrepresenting themselves - which would have to be dealt with - but rather it allows us to not act on but simply reply back to those that ask for accounts w/o representing themselves as mentors... Infra doesn't want emails with requests. They want JIRA issues for better tracking of progress et al. Make a list what the issue must contain, for instance; * Proper title according to some template. * URL to VOTE SUMMARY, * Name of Mentor * Incubator General and/or PMC mailing list as a subscriber, so that someone can step in and hit the breaks if it wrong. * List of Resources. and whatever else the Infra people like to see... Then keep a template somewhere, which the Mentor copy/paste into the Jira issue, fills in and off we go :o) No. Account requests should go by mail to [EMAIL PROTECTED] That's their preferred route. Jira requests will likely be ignored. This strikes me as odd. Jira can be setup so that only authorized people can post requests. We can also create issue types that have the required data that needs to be suppiled. It also allows us to track the outstanding requests. I'm only repeating what has been said before. Not being root, I don't know the exact justifications, other than perhaps a general loathing of Jira. Upayavira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to request new project resources
David Crossley wrote: [...] So how about this ... For mail issues, send to apmail@ + Jira. Use the provided template. For svn creation, send to infrastructure@ + Jira Use the provided template. For account creation, send to root@ using separate requests for each new committer. Follow the instructions and template at http://www.apache.org/dev/#pmc Wouldn't be simpler to open Jira issues (under the appropriate category) for all types of requests? Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [PROPOSAL] Incubate TMCg2
As far as I can tell, we have our paperwork in, name chosen, and proposal accepted. Is there anything else we need at this point in order to get our space as a podling and begin growing our community? Steve -Original Message- From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED] Sent: Friday, February 17, 2006 5:40 PM To: general@incubator.apache.org Subject: Re: [PROPOSAL] Incubate TMCg2 William A. Rowe, Jr. wrote: I personally find googling a project far more useful, and there appear to be no conflicts with your new proposal, other than the fact that another project, Echo, seems to have floated the same potential name. As long as we clarify with them that they haven't/won't adopt that project name we should be fine. http://www.intertwingly.net/wiki/pie/NameFinalVoteArchive?action=highlightv alue=Lokahi For anyone concerned that pie/echo/atom would ever be named Lokahi, this post put that concern to rest. Their objection to the name on the basis of pronounciation is fun :) I wouldn't worry about that concern, this is the single cleanest project name I've ever come across, and seriously doubt we will have any future conflicts. With that resolved I'll add projects/lokahi.xml to svn shortly. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Notice: This e-mail message, together with any attachments, contains information of Merck Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp Dohme or MSD and in Japan, as Banyu) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Yoko
I think that Yoko is good to go. ASF Infra has set up the mailing lists, SVN, and created accounts for our new committers as well as adding the existing interested ASF committers to the proper Unix group. I will notify the new committers of their new accounts. There are some stragglers and they will be added as soon as possible. I have set up all the project status files at the incubator site. The Software Grant from IONA has been received and I have loaded up their donation onto the incubation SVN. It is ready to get scrubbed. I have moved the TriFork work over as well. One question, do we need a PPMC? I think that we should start one since this project has a very real possibility of becoming a TLP. Everyone is invited to join the party at [EMAIL PROTECTED] Regards, Alan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Yoko
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alan D. Cabrera wrote: One question, do we need a PPMC? I think that we should start one since this project has a very real possibility of becoming a TLP. It's not really a matter of choice. Incubating podlings have PPMCs regardles of where they *might* end up. So, yes. Next question, who should be on it? The mentors have to be, but whom else? I'm in favour of all of the committers, but that's just me. :-) - -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp! -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQCVAwUBQ/4NwJrNPMCpn3XdAQKI0gP/cQOGiCLa7DDr4OEfHjV1J4ABxzkm6MZx mjpcd9GXxIfbUYhvLilYDyOdPyv2GagnMIxEOO8OEOwhq8oi48XBqGMN1+VBBVWP on777A33sIin1oDxn8CVXlzD0m/KylWd5WyFxyLntXXSHzDeJUeLb+Ds4RY50ifT vPkBOPHkmk8= =lvBu -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Account requests for Incubator projects
On Thu, Feb 23, 2006 at 09:20:34AM -0800, Alan D. Cabrera wrote: On 2/23/2006 9:16 AM, Upayavira wrote: No. Account requests should go by mail to [EMAIL PROTECTED] That's their preferred route. Jira requests will likely be ignored. This strikes me as odd. *shrug*. There has previously been a lot of talk about infrastructure work flow (really, years of it). I started out at some point to help build a tool for handling these kinds of requests but it fell by the wayside since there weren't enough people to help and I ran out of steam. Someone from infrastructure first sent email about the kind of webapp needed to committers@ a few years ago but no-one ever stepped up to the plate to build it and finish it. Jira can be setup so that only authorized people can post requests. We can also create issue types that have the required data that needs to be suppiled. It also allows us to track the outstanding requests. Jira has been evaluated for handling this kind of stuff. We do use it for mailing list requests but not for accounts. Security, accountability, stability, traceability, shell-based workflow, etc etc. All this is documented. The right list for discussing this kind of stuff is [EMAIL PROTECTED] In any case, the people who do the work get to make these decisions, and they say to use email :-) - LSD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Yoko
On 2/23/2006 11:32 AM, Rodent of Unusual Size wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alan D. Cabrera wrote: One question, do we need a PPMC? I think that we should start one since this project has a very real possibility of becoming a TLP. It's not really a matter of choice. Incubating podlings have PPMCs regardles of where they *might* end up. So, yes. Next question, who should be on it? The mentors have to be, but whom else? I'm in favour of all of the committers, but that's just me. :-) Works for me. Regards, Alan
Podling Mailing Lists
Greetings from infrastructure land. I was recently setting up the Subversion resources for the new Webwork podling (http://incubator.apache.org/projects/webwork2.html) and I ran into something interesting. The request was for creation of the repository space in incubator as with any other podling, which I did, but commits mail was to be directed to the struts lists. See https://issues.apache.org/jira/browse/INFRA-717 for details. This isn't a problem technically, I can set the mail up to do that just fine, but it seems out of sync with the way other podlings have been set up in recent memory (going out of our way to make sure they come in as independent groups, regardless of the intended final destination), so I figured I'd run it by people and verify that this is ok to do. -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Podling Mailing Lists
To explain further, WebWork will form the core of Struts Action 2. We decided to go the Incubator route for two reasons: 1. The code has minor LGPL deps that we'll need to clean 2. We want to bring in a number of new developers Since this project is central to the future of Struts (Struts Action anyways), we want to give it high visibility by emailing commits to our dev list, along side existing Shale and Action 1 commits. It is our hope that the Incubation period is short and involves the whole Struts community. Don On 2/23/06, Garrett Rooney [EMAIL PROTECTED] wrote: Greetings from infrastructure land. I was recently setting up the Subversion resources for the new Webwork podling (http://incubator.apache.org/projects/webwork2.html) and I ran into something interesting. The request was for creation of the repository space in incubator as with any other podling, which I did, but commits mail was to be directed to the struts lists. See https://issues.apache.org/jira/browse/INFRA-717 for details. This isn't a problem technically, I can set the mail up to do that just fine, but it seems out of sync with the way other podlings have been set up in recent memory (going out of our way to make sure they come in as independent groups, regardless of the intended final destination), so I figured I'd run it by people and verify that this is ok to do. -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
