FWIW - the following is the extract (at time of writing) from the draft Policy document relating to the current discussion.
I am about to move this into the drafts section of the site, so people can start hacking within CVS.
Cheers,
Berin= Podling Constraints =
== Branding ==
Podlings are, by definition, not yet fully accepted as part of the Apache Software Foundation. Podling web sites MUST include a clear disclaimer on their website and in all documentation stating that they are in incubation.
Podlings SHOULD use the following text for all disclaimers :
<i><project name> is an effort undergoing incubation at the Apache Software Foundation (ASF), sponsored by the <name of sponsoring entity>. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.</i>
Podlings wishing to use a different disclaimer message MUST have the disclaimer approved by the Incubator PMC prior to use.
== Releases ==
As podlings are not yet fully accepted as part of the Apache Software Foundation, any software releases (including code held in publically available CVS) made by Podlings will not be endorsed by the ASF.
However, as software releases are an important part of any software project, they are permitted in certain circumstances, as follows.
Podlings in Incubation SHALL NOT perform any releases of software without the explicit approval of the Incubator PMC. Such approval SHALL be given only after the Incubator PMC has followed the process detailed in (Reference to Charter), and SHALL NOT occur until all source has been legally transferred to the ASF.
Therefore, should a Podling decide it wishes to perform a release, the Podling SHALL formally request the Incubator PMC approve such a release. The request SHALL have the endorsement of the Mentor.
Should the Incubator PMC, in accordance with (Reference to Charter) vote to approve the request, the Podling MAY perform the release under the following constraints :
* the release archive MUST contain the word "incubating" in the filename; and
* the release archive MUST contain an Incubation disclaimer (as described in the previous section), clearly visible in the main documentation or README file.
Sam Ruby wrote:
Tetsuya Kitahata wrote:
On Fri, 3 Oct 2003 19:00:57 -0400 "Noel J. Bergman" <[EMAIL PROTECTED]> wrote:
Judging from the move we made with james, CVS was easy. ezmlm a bit more
involved, but our users seemed to find us easily enough when the list
address changed from [EMAIL PROTECTED] to
[EMAIL PROTECTED] Moving the web site was easy.
I'd like to oppose this. (Sorry)
I'd like us to all step back and take a look at the bigger picture.
Apparently, the root of this is a statement that something about the incubation process of Lenya raised hackles. I suggest that there may be multiple root causes for this.
Putting incubator as a part of the name is a form of disclaimer. One that is relatively expensive. I, too, would rather we explore cheaper alternatives before we decided to require this for every project.
It seems to me a disclaimer on the website, perhaps also in the root directory of the associated CVS trees, and a process which prevents any official "release" to be created by projects in incubation should be more than sufficient.
- Sam Ruby
--------------------------------------------------------------------- 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]
