Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] Eclipse Foundation Development Process 2023 Update

On Jun 28, 2023, at 04:21, Emily Jiang via eclipse.org-architecture-council <eclipse.org-architecture-council@xxxxxxxxxxx> wrote:

My apologies for not looking at the draft earlier. I took a look at the draft and have a few comments:
1. It seems all info under the Reserved section was deleted. Do we still need to keep the empty Heading "Reserved"?


We generally keep "Reserved" to avoid a re-numbering exercise in the doc.


2. The sentence under

4.2 Code and Resources


"Projects should work with their PMCs and the EMO to request exceptions to this rule, and with their mentors and PMC if there are questions regarding the use of the namespace."

Does this mean there is no exception process? All projects must use their given namespace. With this, we will not be able to move a spec from one working group such as MicroProfile to Jakarta without the namespace changes.

The first part of the sentence indicates that there is an exception process: "Projects should work with their PMCs and the EMO to request exceptions to this rule". Does that work for you?

New Project Proposals are required to have at least one mentor. Mentors must be members of the Architecture Council. The mentors must be listed in the proposal. Mentors are required to monitor and advise the new Project during its Incubation Phase; they are released from that duty once the Project graduates to the Mature Phase.

What does this mean after the deletion? New projects no longer need mentors or they no longer need mentors from the Architecture Council?

Yes. New projects will no longer need mentors from the AC. 

-Gunnar

Back to the top