lucy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Lucy Wiki] Update of "LucyIncubatorProposal" by PeterKarman
Date Mon, 28 Jun 2010 19:17:17 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucy Wiki" for change notification.

The "LucyIncubatorProposal" page has been changed by PeterKarman.


  Resources that infrastructure will be asked to supply for this project.
  === Mailing lists ===
- The minimum required lists are project-private (for confidential PPMC discussions) and project-dev
lists. Note that projects historically misnamed the private list pmc. To avoid confusion over
appropriate usage it was resolved that all such lists be renamed.
+  * lucy-dev
+  * lucy-private
- If this project is new to open source, then starting with these minimum lists is the best
approach. The initial focus needs to be on recruiting new developers. Early adopters are potential
developers. As momentum is gained, the community may decide to create commit and user lists
as they become necessary.
- Existing open source projects moving to Apache will probably want to adopt the same mailing
list set up here as they have already. However, there is no necessity that all mailing lists
be created during bootstrapping. New mailing lists can be added by a VOTE on the Podling list.
- It is conventional to use an all lower case, dash-separated (-) prefix based on the project
- By default, commits for {podling} will be emailed to {podling}-commits. It is therefore
recommended that this naming convention is adopted. Example (Beehive): * beehive-private (with
moderated subscriptions) * beehive-dev * beehive-commits * beehive-user
  === Subversion Directory ===
  It is conventional to use all lower case, dash-separated (-) directory names. The directory
should be within the incubator directory space (
Example (OpenJPA):

View raw message