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
