[Bug 481702] [EDP] Rework the section regarding the Architecture Council

Bugzilla Link	481702
Status	NEW
Importance	P3 normal
Reported	Nov 09, 2015 05:32 EDT
Modified	Oct 15, 2020 16:20 EDT

Description

Copied from Bug 418208 Comment 4:

The bylaws are pretty clear regarding how one becomes a member of the AC. I'd like to remove that bit from the document completely. We don't include any of this sort of discussion for the Planning Council.

ie. scratch this:

--
Membership in the Architecture Council is per the bylaws through strategic membership, PMCs, and by appointment.\

Further, I don't think that much of the rest of the text is necessary. The bylaws state that the executive director (ED) can appoint members. I'm thinking that the nature of the relationship between the AC and the ED with regard to appointing new members is really between the AC and the ED and doesn't need to be in this document.

I believe the bylaws also reasonably imply that an appointed member can also be retired at the discretion of the ED, so again, how this is implemented is really a matter between the AC and ED.

I think that we can just scratch the entire rest of the section:

--
The Architecture Council will, at least annually, recommend to the EMO(ED), Eclipse Members who have sufficient experience, wisdom, and time to be appointed to the Architecture Council and serve as mentors. Election as a mentor is a highly visible confirmation of the Eclipse community's respect for the candidate's technical vision, good judgement, software development skills, past and future contributions to Eclipse. It is a role that should be neither given nor taken lightly. Appointed members of the Architecture Council are appointed to two year renewable terms.\

I quite like the description of the qualities of a member/mentor (though the use of the term "mentor" feels incorrect) and think that we should use that somewhere; perhaps it fits on the AC landing page in the wiki.

This leaves us with just this text:

--
The Architecture Council is responsible for (i) monitoring, guiding, and influencing the software architectures used by projects, (ii) new project mentoring, and (iii) maintaining and revising the Eclipse Development Process.\

Thoughts?