Thanks Roman for thoughtful guidance. If it is not a big problem and PPMC agrees, I'd like to nominate myself.
About the duty of Chair, in addition to Roman's summary, I've read some documents [1] [2] and they're really helpful to understand what it is. Regarding Chair selection policy, Chair of a project can be changed at anytime when a PMC wishes [3]. With the understanding of this flexibility of changing Chair, i believe PMC will always try to find a right person for the best community interest. And I wish we continue to grow and get more experience as a TLP and see what is the best policy for us. Thanks, moon [1] http://www.apache.org/dev/pmc.html#chair [2] http://www.apache.org/foundation/how-it-works.html#pmc [3] http://www.apache.org/dev/pmc.html#newchair On Thu, Apr 7, 2016 at 10:40 AM Roman Shaposhnik <ro...@shaposhnik.org> wrote: > This looks good to me. Still I think you need to decide on a Chair. > You will definitely have to do that before the vote goes to IPMC > and it is a good practice for community to vote on a complete > resolution rather than a part of it. > > A few things that you probably know already, but I find useful > to re-iterate: > 1. a Chair is by and large a just a guy on the hook to be communicating > with the board about the status of the project. Sort of like mentors, > who > may be clueless about your technology were helping you get the gist > of the Apache Way. > > 2. a good idea is for the community to consider a rotating chair > policy where every X months a question of -- who would volunteer > to be a new chair -- gets asked. Doesn't mean that the current > chair can't self-nominate and continue to server, of course -- it just > provides a nice forcing function for that discussion to come up. E.g.: > http://markmail.org/thread/4nadptmwrb3nqqd4 > > Other than that -- perhaps we can start with nominations (self-nominations > are always encouraged) and if there's more than one candidate we can > do a vote. > > Thanks, > Roman. > > On Wed, Apr 6, 2016 at 6:16 PM, moon soo Lee <m...@apache.org> wrote: > > Hi > > > > Thanks Henry and Roman for the advice. > > > > I have created a draft > > > https://cwiki.apache.org/confluence/display/ZEPPELIN/Board+resolution+%28DRAFT%29+for+the+graduation > . > > Please take a look. > > > > In the draft, > > > > Project description and scope follows description in incubation status > page > > [1]. > > Includes all Committers listed in incubation status page [2] as TLP's PMC > > members. > > Choosing the chair need to be done. > > > > Thanks, > > moon > > > > [1] http://incubator.apache.org/projects/zeppelin.html#Description > > [2] http://incubator.apache.org/projects/zeppelin.html#Project+info > > > > > > > > On Thu, Apr 7, 2016 at 9:23 AM Roman Shaposhnik <ro...@shaposhnik.org> > > wrote: > > > >> On Wed, Apr 6, 2016 at 7:18 AM, Henry Saputra <henry.sapu...@gmail.com> > >> wrote: > >> > Hi Moon, > >> > > >> > Actually we should add proposed board resolution [1] in the Vote > thread > >> > which include choosing the chair. > >> > > >> > [1] http://incubator.apache.org/guides/graduation.html#toplevel > >> > >> That's a really good advice! Part of the graduation process is the > >> formation > >> and final approval of the TLP's PMC and the Chair. That should be part > >> of what the community votes on in my opinion. > >> > >> Thanks, > >> Roman. > >> >
