-1 I prefer to have a new sub project associated with the TLP community and use a footer to note incubation status.

BTW would [EMAIL PROTECTED] or activemq-dev- [EMAIL PROTECTED] be ok, since they contain the word incubate?

-dain

On Dec 17, 2005, at 8:49 PM, Noel J. Bergman wrote:

Please vote on the following:

  New mailing lists should be created under the
  @incubator.apache.org domain, just as all of
  the other project resources, e.g., the web
  site and SVN subtree.

+1 from me.

        --- Noel

-----Original Message-----
From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
Sent: Friday, December 16, 2005 16:02
To: general@incubator.apache.org
Subject: @domain for Incubator mailing lists


There has been some discussion and confusion over where to put mailing lists for projects that are in the Incubator. As the person who argued for the current approach, which had to do with infrastructure issues, I'm also going
to suggest that it change.  We are finding that it is more and more
important to highlight when a project is in the Incubator, and to ensure that there is no confusion in the mind of the public about that status.

The current approach is to put the mailing lists under the domain of the TLP into which it was expected that they would go, and THE REASON for this had to do with the difficulty of moving the mailing lists and the eyebrowse archives. HOWEVER, Roy has since written a script to move mailing lists, and we no longer use eyebrowse. And unlike the prior setup, it is fairly
straightforward to redirect an old archive location to a new one.

THEREFORE, new mailing lists should be created under the
@incubator.apache.org domain, just as all of the other project resources,
e.g., the web site and SVN subtree.

        --- Noel


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


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

Reply via email to