>From Mark's description, it looks quite a big challenge to me. In the past, I focus more on driving this project forward from the perspective of technique which apparent interests me very much. The most benefit I received from this incubating practice is that I have truly believed 'community over code'. I'd like to give it a try if the board accepts the proposal, and hope to contribute more by wearing this 'admin' hat.
Regards, -Ian. On Fri, Apr 5, 2019 at 11:42 PM Huxing Zhang <[email protected]> wrote: > Hi, > > > On Fri, Apr 5, 2019 at 5:42 PM Mark Thomas <[email protected]> wrote: > > > > On 04/04/2019 03:26, Huxing Zhang wrote: > > > Hi All, > > > > > > According to [1], in the "Preparing a Charter" section, we need to > > > decide PMC chair. > > > > Just to nitpick here. > > > > The PMC does not decide on who is the chair. The board does. > > > > The PMC makes a recommendation to the board as to who should be > > appointed the PMC chair. The board nearly always accepts that > > recommendation. > > Understand, what I mean is to decide the recommendation :-) > > > > > > This is previously discussed on the "[DISCUSS] Graduate Apache > > > Dubbo(incubating) as a Top Level Project" thread, but it looks like it > > > is easily ignored. Therefore I am starting a dedicated thread to > > > discuss this. > > > > > > I personally am suggesting Ian Luo as PMC chair. Ian is leading the > > > Dubbo project, and has rich experience in RPC/service framework. I > > > think he is the best candidate. > > > > Leading is a word that always makes me nervous around ASF projects. > > By saying leading, I mean to say skills like technical foresight, > sophisticated understanding of the architecture and underlying > implementation, and etc. to drive the project forward. > I think every project/community will have one or more folk like this. > I do not mean to say one has more power over others. In Apache, all > the PMC members are equal. > > > > > The role of PMC chair is an unusual one. PMC chairs are officers of the > > foundation and, as such, have quite a lot of authority. However, if they > > ever need to use that authority then it usually means things have gone > > very badly wrong. > > Just adding some more information about what PMC chair is, and what it > the responsibility. > > PMC CHAIR > The Chair of a Project Management Committee (PMC) is appointed by the > Board from the PMC Members. The PMC as a whole is the entity that > controls and leads the project. The Chair is the interface between the > Board and the Project. PMC Chairs have specific duties[1][2], which is > briefly described here: > - SUBSCRIBE TO THE BOARD@ MAILING LIST > - REVIEW BOARD MEETING MINUTES ABOUT THEIR PROJECT > - ENSURE THE PROJECT'S QUARTERLY BOARD REPORT IS SUBMITTED > - ENSURE NEW COMMITTER REQUESTS ARE MADE > - SEND NOTICES AND FOLLOWUP WHEN ADDING NEW PMC MEMBERS > - MAINTAIN ASF RECORDS ON THE PMC ROSTER > > [1] http://www.apache.org/dev/pmc.html#chair > [2] > https://svn.apache.org/repos/private/foundation/officers/advice-for-new-pmc-chairs.txt > > > > > If everything is working as it should, the role of PMC chair is mostly > > an admin role. Applying for new accounts, writing quarterly reports, etc. > > > > The most important part of a PMC chair's role is to write quarterly > > reports for the board that *accurately* describe the current state of > > the project community. Note: not the technical state of the project, but > > the state of the project community. I'd strongly recommend reading > > through the minutes of the last few board meetings to get an idea of > > what makes a good project report in the eyes of the board. > > I have added the link here[3] so that the community can take a look. > > [3] > http://www.apache.org/foundation/records/minutes/2019/board_minutes_2019_02_20.txt > > > > > Mark > > > > -- > Best Regards！ > Huxing >
