Re: [DISCUSS] Prototype ASF Mailing List Request form
On Thu, Jun 7, 2012 at 11:40 PM, David Crossley cross...@apache.org wrote: sebb wrote: David Crossley wrote: Sam Ruby wrote: I would love to see a resourceAlias attribute. Or even a resourceAliases attribute (allowing multiple names, separated by a space and/or a comma). Yes please. Multiple. I do not have much volunteer time, but would eventually modify Clutch to utilise that. I could find time to do that. Beaut. Seb did that now, thanks. It works nicely. I can definitely work with that. Now how, ideally, should the mailing list request form work for podlings? Should requests only be allowed for podlings that have a status=current? If a podling has multiple aliases, and there exists a mailing list for one alias, should creation using another alias for the same podling be allowed? I don't mind writing a few extra lines of code if it can prevent potential user errors. My only real concern is that I don't want to reject legitimate requires simply because somebody hasn't done all the steps in the right order. That being said, if this encourages podlings.xml to be kept up to date, we all benefit! - Sam Ruby -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
sebb wrote: David Crossley wrote: Sam Ruby wrote: David Crossley wrote: There was an old conversation about this around 2011-10-10, e.g. http://thread.gmane.org/gmane.comp.apache.incubator.general/31601/focus=31662 suggesting an optional resourceAlias attribute. I would love to see a resourceAlias attribute. Or even a resourceAliases attribute (allowing multiple names, separated by a space and/or a comma). Yes please. Multiple. I do not have much volunteer time, but would eventually modify Clutch to utilise that. I could find time to do that. Beaut. Seb did that now, thanks. It works nicely. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
On 6 June 2012 05:05, David Crossley cross...@apache.org wrote: Sam Ruby wrote: V3 of the interface: https://whimsy.apache.org/infra/mlreq https://whimsy.apache.org/infra/mlreq/incubator Key changes: 1) initially start out with two moderator input fields, both marked as required. 2) a paste of a list of (either comma or space separated) emails will be split across multiple input fields. 3) validation of podling, project, and emails. This is the part where I would like the most feedback. Apparently, people will want to use this before podlings and projects are set up elsewhere, and certainly not all emails are known in advance, so the way I am handling this is to ask for confirmation for each unrecognized value. I also prevent requests for the creation of lists that already exist. At the present time, I'm not yet pulling from podlings.xml. One thing I would like to discuss is whether it is possible for the following logic in clutch.py be replaced by adding new attributes and/or elements to podlings.xml and pulling the data from there: if k == zetacomponents: projects[k]['resourceNames'].append(zeta) elif k == beanvalidation: projects[k]['resourceNames'].append(bval) elif k == lucene.net: projects[k]['resourceNames'].append(lucene-net) elif k == manifoldcf: projects[k]['resourceNames'].append(connectors) elif k == openoffice.org: projects[k]['resourceNames'].append(ooo) elif k == odftoolkit: projects[k]['resourceNames'].append(odf) When the podlings.xml file started i had hoped that we could use its resource attribute to handle such alternate names. Not sure what is the intention of that attribute. It is used to provide the resource variable in clutch.py. It's normally equal to the lower-cased project name, e.g. podling name=Accumulo resource=accumulo However, spaces and some separators are dropped, and non-alphanumerics are converted, e.g. name=XMLBeans/C++ resource=xmlbeanscxx There was an old conversation about this around 2011-10-10, e.g. http://thread.gmane.org/gmane.comp.apache.incubator.general/31601/focus=31662 suggesting an optional resourceAlias attribute. As explained there and in the clutch code, that resourceNames is plural because we found some projects use two or three different names for their project in different contexts. Yes. The following are nominally the same, but can vary: http://svn.apache.org/repos/asf/incubator/nn nn=list of availids in asf-authorization-template http://incubator.apache.org/nn/... http://incubator.apache.org/projects/nn.html I may have forgotten some contexts. -David The ideal for me would be to have confirmation prompts be rare enough that when they do occur, people will actually read them. The overall concern is that if it becomes too easy to create malling lists, the next problem will be requests to the infrastructure team to rename lists or moderator names when typos occur :-) For those who are interested, source is here: https://svn.apache.org/repos/infra/infrastructure/trunk/projects/whimsy/www/officers/mlreq.cgi - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
Sam Ruby wrote: David Crossley wrote: There was an old conversation about this around 2011-10-10, e.g. http://thread.gmane.org/gmane.comp.apache.incubator.general/31601/focus=31662 suggesting an optional resourceAlias attribute. I would love to see a resourceAlias attribute. Or even a resourceAliases attribute (allowing multiple names, separated by a space and/or a comma). Yes please. Multiple. I do not have much volunteer time, but would eventually modify Clutch to utilise that. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
On 7 June 2012 02:39, David Crossley cross...@apache.org wrote: Sam Ruby wrote: David Crossley wrote: There was an old conversation about this around 2011-10-10, e.g. http://thread.gmane.org/gmane.comp.apache.incubator.general/31601/focus=31662 suggesting an optional resourceAlias attribute. I would love to see a resourceAlias attribute. Or even a resourceAliases attribute (allowing multiple names, separated by a space and/or a comma). Yes please. Multiple. I do not have much volunteer time, but would eventually modify Clutch to utilise that. I could find time to do that. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
Sam Ruby wrote: V3 of the interface: https://whimsy.apache.org/infra/mlreq https://whimsy.apache.org/infra/mlreq/incubator Key changes: 1) initially start out with two moderator input fields, both marked as required. 2) a paste of a list of (either comma or space separated) emails will be split across multiple input fields. 3) validation of podling, project, and emails. This is the part where I would like the most feedback. Apparently, people will want to use this before podlings and projects are set up elsewhere, and certainly not all emails are known in advance, so the way I am handling this is to ask for confirmation for each unrecognized value. I also prevent requests for the creation of lists that already exist. At the present time, I'm not yet pulling from podlings.xml. One thing I would like to discuss is whether it is possible for the following logic in clutch.py be replaced by adding new attributes and/or elements to podlings.xml and pulling the data from there: if k == zetacomponents: projects[k]['resourceNames'].append(zeta) elif k == beanvalidation: projects[k]['resourceNames'].append(bval) elif k == lucene.net: projects[k]['resourceNames'].append(lucene-net) elif k == manifoldcf: projects[k]['resourceNames'].append(connectors) elif k == openoffice.org: projects[k]['resourceNames'].append(ooo) elif k == odftoolkit: projects[k]['resourceNames'].append(odf) When the podlings.xml file started i had hoped that we could use its resource attribute to handle such alternate names. Not sure what is the intention of that attribute. There was an old conversation about this around 2011-10-10, e.g. http://thread.gmane.org/gmane.comp.apache.incubator.general/31601/focus=31662 suggesting an optional resourceAlias attribute. As explained there and in the clutch code, that resourceNames is plural because we found some projects use two or three different names for their project in different contexts. -David The ideal for me would be to have confirmation prompts be rare enough that when they do occur, people will actually read them. The overall concern is that if it becomes too easy to create malling lists, the next problem will be requests to the infrastructure team to rename lists or moderator names when typos occur :-) For those who are interested, source is here: https://svn.apache.org/repos/infra/infrastructure/trunk/projects/whimsy/www/officers/mlreq.cgi - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
V3 of the interface: https://whimsy.apache.org/infra/mlreq https://whimsy.apache.org/infra/mlreq/incubator Key changes: 1) initially start out with two moderator input fields, both marked as required. 2) a paste of a list of (either comma or space separated) emails will be split across multiple input fields. 3) validation of podling, project, and emails. This is the part where I would like the most feedback. Apparently, people will want to use this before podlings and projects are set up elsewhere, and certainly not all emails are known in advance, so the way I am handling this is to ask for confirmation for each unrecognized value. I also prevent requests for the creation of lists that already exist. At the present time, I'm not yet pulling from podlings.xml. One thing I would like to discuss is whether it is possible for the following logic in clutch.py be replaced by adding new attributes and/or elements to podlings.xml and pulling the data from there: if k == zetacomponents: projects[k]['resourceNames'].append(zeta) elif k == beanvalidation: projects[k]['resourceNames'].append(bval) elif k == lucene.net: projects[k]['resourceNames'].append(lucene-net) elif k == manifoldcf: projects[k]['resourceNames'].append(connectors) elif k == openoffice.org: projects[k]['resourceNames'].append(ooo) elif k == odftoolkit: projects[k]['resourceNames'].append(odf) The ideal for me would be to have confirmation prompts be rare enough that when they do occur, people will actually read them. The overall concern is that if it becomes too easy to create malling lists, the next problem will be requests to the infrastructure team to rename lists or moderator names when typos occur :-) For those who are interested, source is here: https://svn.apache.org/repos/infra/infrastructure/trunk/projects/whimsy/www/officers/mlreq.cgi - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
On Sun, May 27, 2012 at 2:23 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: May I suggest adding some fields to ease data entry even more: 1- A checkbox indicating whether or not the mailing list is for an incubator project or not 2- Another list of checkboxes which are enabled only when the incubator checkbox is enabled: 2.1- Dvelopment 2.2- Commits 2.3- Private 2.4- Users(*) For the first three ones they can be checked by default as they are required by all Incubator projects, the last one for users can be checked sometimes when a new podling is in need for a users list This will ease data entry a lot for new podlings instead of making a new request for each mailing list a mentor can just in one request send all data required by the tool It looks to me like incubator mailing list requests are enough different to merit a separate form. Also it appears that there is a lot of variety between podlings, consider: http://incubator.apache.org/projects/openofficeorg.html#Project+info Trying to satisfy both the needs for initial mailing list creations while also wanting to support one-off or additional mailing list requests, heres new versions of the forms for review (url names are NOT final): https://whimsy.apache.org/incubator/asfmlreq https://whimsy.apache.org/incubator/incmlreq - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
Sweet. It would be really helpful for the pmc field to be a select list of existing TLPs / podlings. Personally, I think it would be helpful for the list name field to be a select list for dev/user/commits/etc./Other. I.e. suggest the most common set of names (and pick either user@ or users@, whichever is currently most prevalent) to encourage projects to use the exact common names. IF someone picks Other, they can enter their own name. The Moderators field should be wider, and it's pop-up text should explain the separators supported. Is this in SVN so people can suggest specific patches, or not yet? - Shane On 2012-05-25 10:54 PM, Sam Ruby wrote: https://whimsy.apache.org/infra/mlreq Nothing fancy: simple data gathering. Output will be validated and placed into svn as input to another tool down the chain. The topic I would like to discuss is what additional input validation should be done. Mailing list names have specific formats. Within the incubator, podling mailing list names are expected to have a specific format. But the mapping of podling names to mailing list names sometimes varies... Suggestions welcome. I'm starting with the incubator as it is the source for a bulk of the requests... - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
On 31 May 2012 13:58, Shane Curcuru a...@shanecurcuru.org wrote: Sweet. It would be really helpful for the pmc field to be a select list of existing TLPs / podlings. Not sure that will always be possible; often the mailing lists are being created as part of TLP/podling creation. Even for existing TLPs/podlings - is there a canonical list of their names? Personally, I think it would be helpful for the list name field to be a select list for dev/user/commits/etc./Other. I.e. suggest the most common set of names (and pick either user@ or users@, whichever is currently most prevalent) to encourage projects to use the exact common names. IF someone picks Other, they can enter their own name. +1 The Moderators field should be wider, and it's pop-up text should explain the separators supported. No need for seps, because new fields are auto-generated. Is this in SVN so people can suggest specific patches, or not yet? - Shane On 2012-05-25 10:54 PM, Sam Ruby wrote: https://whimsy.apache.org/infra/mlreq Nothing fancy: simple data gathering. Output will be validated and placed into svn as input to another tool down the chain. The topic I would like to discuss is what additional input validation should be done. Mailing list names have specific formats. Within the incubator, podling mailing list names are expected to have a specific format. But the mapping of podling names to mailing list names sometimes varies... Suggestions welcome. I'm starting with the incubator as it is the source for a bulk of the requests... - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
On Thu, May 31, 2012 at 10:24 AM, sebb seb...@gmail.com wrote: On 31 May 2012 13:58, Shane Curcuru a...@shanecurcuru.org wrote: Sweet. It would be really helpful for the pmc field to be a select list of existing TLPs / podlings. Not sure that will always be possible; often the mailing lists are being created as part of TLP/podling creation. Even for existing TLPs/podlings - is there a canonical list of their names? Workflow question: when is https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml updated? If I can presume that it is updated before the mailing list is requested, then I can produce a dropdown list. Personally, I think it would be helpful for the list name field to be a select list for dev/user/commits/etc./Other. I.e. suggest the most common set of names (and pick either user@ or users@, whichever is currently most prevalent) to encourage projects to use the exact common names. IF someone picks Other, they can enter their own name. +1 Forgive me, but this makes no sense to me, I may be confused. A proposal is discussed. Then voted on. Then approved. And that's the point in the process where the tool is to provide feedback on the names chosen and approved? I see 10 current podling mailing lists with a -users suffix. I see 27 with -user. I also see lists with names like incubator-ooo-users-de. What's the problem being solved here? I also want to support the use case of ooo currently having 17 mailing lists and wanting to request an 18th. I also want to support the use case of somebody wanting to request the initial creation of mailing lists for a new podling, but to have a different set of moderators for commits than the other lists. The Moderators field should be wider, and it's pop-up text should explain the separators supported. No need for seps, because new fields are auto-generated. That was my thinking. One field = one email. Shane: can you try adding an email address to the form to see if this makes sense to you? It might also make sense for me to create three fields initially, and make the first three required. Thoughts? Is this in SVN so people can suggest specific patches, or not yet? It wasn't before but is now: https://svn.apache.org/repos/infra/infrastructure/trunk/projects/whimsy/www/incubator/incmlreq.cgi https://svn.apache.org/repos/infra/infrastructure/trunk/projects/whimsy/www/incubator/asfmlreq.cgi - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
Sam Ruby wrote on Thu, May 31, 2012 at 11:38:21 -0400: It might also make sense for me to create three fields initially, and make the first three required. Thoughts? I think we accept a minimum of 2 moderators per list... (eg I think private@svn was created with just 2 moderators) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
Sam Ruby wrote: sebb wrote: Shane Curcuru wrote: Sweet. It would be really helpful for the pmc field to be a select list of existing TLPs / podlings. Not sure that will always be possible; often the mailing lists are being created as part of TLP/podling creation. Even for existing TLPs/podlings - is there a canonical list of their names? Workflow question: when is https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml updated? If I can presume that it is updated before the mailing list is requested, then I can produce a dropdown list. They should add their entry as soon as possible after acceptance, but sometimes do not. Step 1 after acceptance is for them to add their new podling to the wiki ReportingScedule. If they do not do that quickly then i do, then Clutch can pick it up and start to assist. Step 2 is to add to the podlings.xml list. They know the details so should manage it. See the docs: http://incubator.apache.org/guides/mentor.html#Overview Actually anyone with commit access can do it. We need to encourage that podlings.xml file to be initialised as soon as possible, and always up-to-date. I reckon that you should utilise it, and so if they do not appear in the drop-down list then they know that they missed Step 2. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
Nick Kew wrote on Sat, May 26, 2012 at 07:39:48 +0100: On 26 May 2012, at 03:54, Sam Ruby wrote: https://whimsy.apache.org/infra/mlreq Nothing fancy: simple data gathering. Output will be validated and placed into svn as input to another tool down the chain. The topic I would like to discuss is what additional input validation should be done. Mailing list names have specific formats. Within the incubator, podling mailing list names are expected to have a specific format. But the mapping of podling names to mailing list names sometimes varies... Suggestions welcome. I'm starting with the incubator as it is the source for a bulk of the requests... [foo] @ [bar] .apache.org ? The form is ASF wide. You guys will enter incubator for [bar]. What about a toggle for a private list? Or is that determined on name alone? Easy to add if there's a use case. apmail hat on, I would still like sanity checking to avoid the case where someone requests a foo-private list and forgets to tick the Make it private? checkbox. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
sebb wrote on Sat, May 26, 2012 at 12:09:48 +0100: On 26 May 2012 03:54, Sam Ruby ru...@intertwingly.net wrote: https://whimsy.apache.org/infra/mlreq Nothing fancy: simple data gathering. Output will be validated and placed into svn as input to another tool down the chain. The topic I would like to discuss is what additional input validation should be done. Mailing list names have specific formats. Within the incubator, podling mailing list names are expected to have a specific format. But the mapping of podling names to mailing list names sometimes varies... Suggestions welcome. I'm starting with the incubator as it is the source for a bulk of the requests... Might be useful to provide examples on the form for some of the fields. Not sure what the Replies check-box is about. I assume it might be for lists like commits@ where the PMC wants replies to go to dev@ If selected, should it not provide a new box for the Reply-To address? Semantics: the form only provides UI for enabling or disabling reply-to headers that point to the list itself. Reply-to: dev@ on commits@ list happens by default and is not controlled by the form. Sam --- this Reply-To on commits@ lists is one place where the -s argument to makelist-apache.sh might matter --- I assume -s goober commits will result in Reply-To: goober-dev@ in headeradd. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
Daniel Shahaf wrote on Sun, May 27, 2012 at 14:12:54 +0300: Nick Kew wrote on Sat, May 26, 2012 at 07:39:48 +0100: On 26 May 2012, at 03:54, Sam Ruby wrote: https://whimsy.apache.org/infra/mlreq Nothing fancy: simple data gathering. Output will be validated and placed into svn as input to another tool down the chain. The topic I would like to discuss is what additional input validation should be done. Mailing list names have specific formats. Within the incubator, podling mailing list names are expected to have a specific format. But the mapping of podling names to mailing list names sometimes varies... Suggestions welcome. I'm starting with the incubator as it is the source for a bulk of the requests... [foo] @ [bar] .apache.org ? The form is ASF wide. You guys will enter incubator for [bar]. What about a toggle for a private list? Or is that determined on name alone? Easy to add if there's a use case. apmail hat on, I would still like sanity checking to avoid the case where someone requests a foo-private list and forgets to tick the Make it private? checkbox. There _is_ a use case: some f...@apache.org lists will need such an option. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Prototype ASF Mailing List Request form
Nice work Sam ;) May I suggest adding some fields to ease data entry even more: 1- A checkbox indicating whether or not the mailing list is for an incubator project or not 2- Another list of checkboxes which are enabled only when the incubator checkbox is enabled: 2.1- Dvelopment 2.2- Commits 2.3- Private 2.4- Users(*) For the first three ones they can be checked by default as they are required by all Incubator projects, the last one for users can be checked sometimes when a new podling is in need for a users list This will ease data entry a lot for new podlings instead of making a new request for each mailing list a mentor can just in one request send all data required by the tool On Sun, May 27, 2012 at 1:41 PM, Daniel Shahaf d...@daniel.shahaf.namewrote: Daniel Shahaf wrote on Sun, May 27, 2012 at 14:12:54 +0300: Nick Kew wrote on Sat, May 26, 2012 at 07:39:48 +0100: On 26 May 2012, at 03:54, Sam Ruby wrote: https://whimsy.apache.org/infra/mlreq Nothing fancy: simple data gathering. Output will be validated and placed into svn as input to another tool down the chain. The topic I would like to discuss is what additional input validation should be done. Mailing list names have specific formats. Within the incubator, podling mailing list names are expected to have a specific format. But the mapping of podling names to mailing list names sometimes varies... Suggestions welcome. I'm starting with the incubator as it is the source for a bulk of the requests... [foo] @ [bar] .apache.org ? The form is ASF wide. You guys will enter incubator for [bar]. What about a toggle for a private list? Or is that determined on name alone? Easy to add if there's a use case. apmail hat on, I would still like sanity checking to avoid the case where someone requests a foo-private list and forgets to tick the Make it private? checkbox. There _is_ a use case: some f...@apache.org lists will need such an option. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [DISCUSS] Prototype ASF Mailing List Request form
On May 27, 2012, at 4:12 AM, Daniel Shahaf wrote: Nick Kew wrote on Sat, May 26, 2012 at 07:39:48 +0100: On 26 May 2012, at 03:54, Sam Ruby wrote: https://whimsy.apache.org/infra/mlreq Nothing fancy: simple data gathering. Output will be validated and placed into svn as input to another tool down the chain. The topic I would like to discuss is what additional input validation should be done. Mailing list names have specific formats. Within the incubator, podling mailing list names are expected to have a specific format. But the mapping of podling names to mailing list names sometimes varies... Suggestions welcome. I'm starting with the incubator as it is the source for a bulk of the requests... [foo] @ [bar] .apache.org ? The form is ASF wide. You guys will enter incubator for [bar]. Most incubator lists are of the form foo-dev @ incubator .apache.org. It might be good to have a drop down with the common dev, user, private aliases already listed, and perhaps an option [] - [] @ incubator.apache.org Craig What about a toggle for a private list? Or is that determined on name alone? Easy to add if there's a use case. apmail hat on, I would still like sanity checking to avoid the case where someone requests a foo- private list and forgets to tick the Make it private? checkbox. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Prototype ASF Mailing List Request form
https://whimsy.apache.org/infra/mlreq Nothing fancy: simple data gathering. Output will be validated and placed into svn as input to another tool down the chain. The topic I would like to discuss is what additional input validation should be done. Mailing list names have specific formats. Within the incubator, podling mailing list names are expected to have a specific format. But the mapping of podling names to mailing list names sometimes varies... Suggestions welcome. I'm starting with the incubator as it is the source for a bulk of the requests... - Sam Ruby - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
