On Sat, 8 Apr 2006, Simon Kitching wrote:

On Fri, 2006-04-07 at 16:28 -0700, Martin Cooper wrote:
On 4/7/06, Henri Yandell <[EMAIL PROTECTED]> wrote:

Calling a vote to create a Jakarta Sandbox; which entails:

  * Move Jakarta Commons Sandbox to Jakarta Sandbox
  * Migrate Jakarta Taglibs Sandbox into Jakarta Sandbox
  * Create development mailing list ([EMAIL PROTECTED])
  * Create wiki (and migrate wiki bits from j-c-s/j-t-s)
  * Jakarta Sandbox to initially use the Commons sandbox processes.

What would be the constraints on what could go in there? Anything, as long
as it's written in or for Java?

And who is expected to subscribe to [EMAIL PROTECTED]

Those who want to? :)

I imagine those working on sandbox components at the moment, plus a handful of people who tend to subscribe to such lists.

Out of interest - if we take a list with N mails a day, and have 2 lists with N/2 mails a day, is that something you'd view as more painful or the same amount of pain?

I know that when subscribing to Jakarta subprojects I'm not interested in as a coder, I subscribe to both the -user and -dev and funnel them both into the same folder. For my level of interest it's just [EMAIL PROTECTED], not ecs-xxx@ etc. So I'm probably answering "more pain" to the above, but I've got a simple solution that hides the minor pain increase.


To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to