incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Ruby <>
Subject Re: [DISCUSS] Prototype ASF Mailing List Request form
Date Thu, 31 May 2012 15:38:21 GMT
On Thu, May 31, 2012 at 10:24 AM, sebb <> wrote:
> On 31 May 2012 13:58, 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
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:

- Sam Ruby

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message