Greg Stein was also not enthused about it. The thread can be followed here:
https://lists.apache.org/thread.html/4d7c15ba541cff2f476214491f4f570b5165b700c589e98377ccffab@%3Cgeneral.incubator.apache.org%3E On Sun, Nov 27, 2016 at 1:04 PM, Todd Lipcon <[email protected]> wrote: > If you follow the thread on the incubator list you'll see that it's not a > new requirement, just a set of things to think about. Changes are afoot to > the wording to clarify that, since you're right that the current placement > makes it sound like a requirement. > > On Nov 25, 2016 9:55 PM, "Jim Apple" <[email protected]> wrote: > >> Bad news for podlings: the incubator has now added a vague and >> arbitrarily-ordered "maturity model" to the graduation requirements. >> You can puzzle over it here: >> >> http://community.apache.org/apache-way/apache-project-maturity-model.html >> >> For instance, "Complete the Apache Project Maturity Model" is on the >> "Graduation Check List" >> (http://incubator.apache.org/guides/graduation.html), but the model >> itself says, "Note that we try to avoid using the word "must" below. >> The model describes the state of a mature project, as opposed to a set >> of rules." >> >> It also says "A mature Apache project complies with all the elements >> of this model" and "Convenience binaries can be distributed alongside >> source code but they are not Apache Releases -- they are just a >> convenience provided with no guarantee." Your guess is as good as mine >> as to how NOT distributing binaries is level 4 of "Releases" while >> "Releases are signed and/or distributed along with digests", which >> requires actual work, is only level 3. >> >> ---------- Forwarded message ---------- >> From: John D. Ament <[email protected]> >> Date: Fri, Nov 25, 2016 at 6:26 AM >> Subject: Incoming Website Changes >> To: "[email protected]" <[email protected]> >> >> >> All, >> >> I'm planning to start committing a number of website changes. These >> changes are a summary of my experience bootstrapping podlings, questions >> I've received (both on and off mailing list) from people trying to do >> setup, and ways to leverage new infra services. >> >> Here's a summary of the current changes: >> >> Mentor Guide: http://incubator.apache.org/guides/mentor.html >> >> This is the most substantial area changed. The page has been reordered to >> list the steps to take in the order to take them. The current format has >> it all over and makes it hard to follow when you should do what. In >> addition, I've added links to reporeq, Incubator ML requests, and >> lists.apache.org >> >> PPMC Guide http://incubator.apache.org/guides/ppmc.html >> >> I added a section clarifying binding votes within the PPMC, stating that >> they're only binding for people issues, not releases. >> >> Proposal Guide http://incubator.apache.org/guides/proposal.html >> >> I updated the champion section to clarify that champion should be found at >> the beginning of proposal formation, which is earlier than the current >> "before submitted" step. I also clarified that the champion's role is >> around the proposal and entering the incubator, separate from mentors >> (something we had agreed to a while ago, but was missing in this guide). >> >> Graduation Guide http://incubator.apache.org/guides/graduation.html >> >> Added a link to the Maturity Model as a step to follow for graduation. >> >> >> I plan to commit these changes later today, and make more changes soon to >> keep more documents up to date. >> >> John >>
