Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Graduating EE4J projects
I didn't get an actual answer from the PMC.

According to the handbook:

For a graduation review, release review documentation must be augmented to include demonstration of:
  • solid working code with stable APIs;
  • an established and growing community around the project;
  • diverse multi-organization committer/contributor/developer activity; and
  • operation in the open using open source rules of engagement.
The graduation review documentation should demonstrate that members have learned the ropes and logistics of being an Eclipse project. That is, the project "gets the Eclipse way".

I believe that the EE4J projects that are participating in the Jakarta EE 9 release meet all four of the bullets.

Many Jakarta 9 projects have already completed release reviews, so we've fallen a bit behind. We normally combine a graduation review with a release review, but there's no requirement to do so. I'm thinking that we can assemble a Graduation review for all of the participating projects and get them in one fell swoop. The graduation review, like a release review, takes a week. Since all of the projects will have recently engaged in a release review, there is no intellectual property review required. Really, all we need is PMC agreement that all of the projects are operating in accordance with the EDP and that the four criteria list above have been met and I can schedule the review.

Note that there are three EE4J projects that are missing project leads. This is an invalid state that needs to be addressed (we can't reasonably graduate these projects if they have no project lead).
  • Jakarta Annotations
  • Eclipse Implementation of JAXB
  • Eclipse OpenMQ
I need the PMC to make identifying project leads for these projects a priority, please.

Let me know if you need more help to understand what this involves or why it matters.

Wayne


On Tue, Sep 29, 2020 at 3:33 PM Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Greetings PMC.

Most of the EE4J projects are still in incubation. I believe that all of them have already engaged in successful releases and that the project teams are getting their legs with regard to the process.

Incubation is essentially a label that says that either the project content is unstable and/or that the project team is still learning the ropes. I don't believe that either of these things is true anymore.

I should probably take this opportunity to admit that I haven't been particularly assertive with regard to incubation branding requirements and what-not (incubating projects are required to indicate their status on their products), so most people probably have no idea what incubation is or why they should care.

With your approval, I'd like to just automatically add a graduation review to all of the forthcoming release reviews on the basis that all of the projects have mature content and their development teams know how to be successful with Eclipse Foundation processes.

Since these projects have been acting mature for some time, this change will have no real impact on the project teams. The primary difference will be that the incubation logo will be removed from the various PMI pages.

There's a bit more in the handbook.


As with everything, the PMC has a say in what constitutes preparedness for graduation. The PMC may choose, for example, to add a requirement that the contributed specification document be fully converted (I don't know the actual state of this). I am happy to help you work out your own graduation criteria.

Wayne

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Join us at our virtual event: EclipseCon 2020 - October 20-22



--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Join us at our virtual event: EclipseCon 2020 - October 20-22

Back to the top