> In my opinion, some projects are spending too long in the Incubator because > they aren't focusing on getting out.
Let us analyze why that is. > Endorsement by the ASF Great, I have a few more questions: Do you think that to an Apache layman (the larger technical and potentially world community) there is a great difference between a project legally protected and served from Apache servers and a "not in incubator" project with the same distinctions? Do you think there is a legal distinction? For those seeking the Apache brand, do you think there is a great deal of reason to propel further? What effects does "pre-acceptance" have on the motivation to build a proper community? How does serving projects that we are not certain are clean legally, etc. from Apache servers and requiring CLAs from their committers and offering them some form of protection put the foundation at risk? What benefits do we receive from accepting this risk? Thanks, -Andy -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? The views expressed in this email are those of the author and are almost definitely not shared by the Apache Software Foundation, its board or its general membership. In fact they probably most definitively disagree with everything espoused in the above email. > From: "Noel J. Bergman" <[EMAIL PROTECTED]> > Reply-To: community@apache.org > Date: Sat, 10 Jan 2004 19:05:34 -0500 > To: <community@apache.org> > Cc: <[EMAIL PROTECTED]> > Subject: RE: Single Location for syndicated Apache blogs > > Andrew C. Oliver wrote: > >>> Unrelated to whether or not we would use it, I think that blojsom could > be a >>> very nice ASF project. From what I have seen of it, I'd support its > entry >>> to the Incubator. > >> Does it seem sensible to take an already successful ASL licensed, >> community developed piece of software by an already successful >> open source developer and force it into a somewhat beta status by >> making it go through the incubator "just because that is the way >> things are done"? > > The Incubator's purpose is to ensure that projects coming into the ASF > > - are legally clean, > - that their communities are healthy, > - and that they follow basic ASF policies/procedures. > > In my opinion, some projects are spending too long in the Incubator because > they aren't focusing on getting out. > > If a project is a successful, ASF license, community-developed piece of > software, then it need not stay long in the Incubator. However, ASF > projects are supposed to be developed by communities, because it is > important that the project survive beyond the interests of any particular > participant. That is why two of the purposes for Incubation are to ensure > that there is a healthy developing COMMUNITY, and that it is following basic > ASF policies. > > Cocoon's Lenya project and XML's XMLBeans project are far from "beta > status." As noted by multiple projects in the Incubator: "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." > > Endorsement by the ASF is based upon with the belief that a project's IP is > clean, and that it has developed a healthy community that will ensure its > long term viability. We incubate projects to ensure those things, not for > ceremony or "just because that is the way things are done." > > --- 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]
