Thanks Dave for asking the question in bigger forum. As mentioned, for the draft, I just followed the text suggested by the whimsy tool, which I've seen included in multiple recent resolutions.
My understanding of that paragraph is that "once the PMC is formed one of its first tasks would be to figure out what it wants to do with respect to bylaws, whether to adopt standard ASF bylaws or have a modified version discussed and voted by PMC". If the consensus is to leave this paragraph out of the draft, we can certainly remove from draft. To comment on Taylor's question: >> Does the Pulsar PPMC feel the need to adopt bylaws (it’s not required), or are the Apache defaults acceptable? >> One option is to simply not have bylaws, which means you would simply adhere to [1] and [2], and put any clarifications in a contributors’ guide (which you’ve done). I am personally fine with Apache defaults, though I find it useful to have (like many projects do) a page with explicit ByLaws, with details on what is the process for different "actions" (eg: code changes, releases, committer). One such example, that I'm familiar with is BookKeeper ( http://bookkeeper.apache.org/project/bylaws/). Matteo On Sun, Sep 2, 2018 at 9:32 AM Dave Fisher <dave2w...@comcast.net> wrote: > Hi - > > I’m bringing Taylor’s comment to general@incubator so that we can get > consensus to get the whimsy tool changed. > > Regards, > Dave > > > On Sep 2, 2018, at 8:33 AM, Jim Jagielski <j...@jagunet.com> wrote: > > > > I would agree. I think that we should NOT add anything about PMC > specific bylaws in our resolution. I would even go so far as to vote -1 on > the resolution with that clause included. > > > >> On Aug 31, 2018, at 4:16 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote: > >> > >> I would like to stay on as well. > >> > >> Quick question: > >> > >>> RESOLVED, that the initial Apache Pulsar PMC be and hereby is tasked > >>> with the creation of a set of bylaws intended to encourage open > >>> development and increased participation in the Apache Pulsar Project; > >>> and be it further > >> > >> Does the Pulsar PPMC feel the need to adopt bylaws (it’s not required), > or are the Apache defaults acceptable? > >> > >> One option is to simply not have bylaws, which means you would simply > adhere to [1] and [2], and put any clarifications in a contributors’ guide > (which you’ve done). > >> > >> -Taylor > >> > >> [1] http://www.apache.org/foundation/voting.html < > http://www.apache.org/foundation/voting.html> > >> [2] http://www.apache.org/dev/pmc.html < > http://www.apache.org/dev/pmc.html> > >> > >>> On Aug 31, 2018, at 12:43 PM, Matteo Merli <mme...@apache.org <mailto: > mme...@apache.org>> wrote: > >>> > >>> I have prepared the draft for the graduation resolution using the > >>> Whimsy tool (https://whimsy.apache.org/roster/ppmc/pulsar < > https://whimsy.apache.org/roster/ppmc/pulsar>). > >>> > >>> Maturity model self-assessment is at > >>> > https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar > < > https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar > > > >>> Contributing to Pulsar page is now available at > >>> http://pulsar.incubator.apache.org/contributing/ > >>> > >>> Notes: > >>> > >>> * I'm proposing myself as initial PMC chair -- Please comment if > >>> community is onboard with this or propose other persons as well > >>> > >>> * This draft includes all existing PPMC members and mentors into the > new PMC. > >>> > >>> - For all: please indicate if you want to keep being part of the > >>> PMC or if you prefer to be removed. > >>> > >>> > >>> ---------------------------------------- > >>> > >>> Establish the Apache Pulsar Project > >>> > >>> WHEREAS, the Board of Directors deems it to be in the best interests of > >>> the Foundation and consistent with the Foundation's purpose to > establish > >>> a Project Management Committee charged with the creation and > maintenance > >>> of open-source software, for distribution at no charge to the public, > >>> related to a highly scalable, low latency messaging platform running on > >>> commodity hardware. It provides simple pub-sub and queue semantics over > >>> topics, lightweight compute framework, automatic cursor management for > >>> subscribers, and cross-datacenter replication. > >>> > >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > >>> (PMC), to be known as the "Apache Pulsar Project", be and hereby is > >>> established pursuant to Bylaws of the Foundation; and be it further > >>> > >>> RESOLVED, that the Apache Pulsar Project be and hereby is responsible > >>> for the creation and maintenance of software related to a highly > >>> scalable, low latency messaging platform running on commodity hardware. > >>> It provides simple pub-sub and queue semantics over topics, lightweight > >>> compute framework, automatic cursor management for subscribers, and > >>> cross-datacenter replication; and be it further > >>> > >>> RESOLVED, that the office of "Vice President, Apache Pulsar" be and > >>> hereby is created, the person holding such office to serve at the > >>> direction of the Board of Directors as the chair of the Apache Pulsar > >>> Project, and to have primary responsibility for management of the > >>> projects within the scope of responsibility of the Apache Pulsar > >>> Project; and be it further > >>> > >>> RESOLVED, that the persons listed immediately below be and hereby are > >>> appointed to serve as the initial members of the Apache Pulsar Project: > >>> > >>> * Boyang Jerry Peng <jerryp...@apache.org> > >>> * Brad McMillen <bra...@apache.org> > >>> * David Fisher <w...@apache.org> > >>> * Francis Christopher Liu <tof...@apache.org> > >>> * Hiroyuki Sakai <hrsa...@apache.org> > >>> * Ivan Brendan Kelly <iv...@apache.org> > >>> * Jai Asher <j...@apache.org> > >>> * Jia Zhai <zhai...@apache.org> > >>> * Jim Jagielski <j...@apache.org> > >>> * Joe Francis <j...@apache.org> > >>> * Ludwig Pummer <ludw...@apache.org> > >>> * Masahiro Sakamoto <massa...@apache.org> > >>> * Masakazu Kitajo <mas...@apache.org> > >>> * Matteo Merli <mme...@apache.org> > >>> * Nozomi Kurihara <nkuri...@apache.org> > >>> * P. Taylor Goetz <ptgo...@apache.org> > >>> * Rajan Dhabalia <rdhaba...@apache.org> > >>> * Sahaya Andrews <andr...@apache.org> > >>> * Sanjeev Kulkarni <sanjee...@apache.org> > >>> * Sebastián Schepens <sschep...@apache.org> > >>> * Siddharth Boobna <sboo...@apache.org> > >>> * Sijie Guo <si...@apache.org> > >>> * Yuki Shiga <yush...@apache.org> > >>> > >>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed > >>> to the office of Vice President, Apache Pulsar, to serve in accordance > >>> with and subject to the direction of the Board of Directors and the > >>> Bylaws of the Foundation until death, resignation, retirement, removal > >>> or disqualification, or until a successor is appointed; and be it > >>> further > >>> > >>> RESOLVED, that the initial Apache Pulsar PMC be and hereby is tasked > >>> with the creation of a set of bylaws intended to encourage open > >>> development and increased participation in the Apache Pulsar Project; > >>> and be it further > >>> > >>> RESOLVED, that the Apache Pulsar Project be and hereby is tasked with > >>> the migration and rationalization of the Apache Incubator Pulsar > >>> podling; and be it further > >>> > >>> RESOLVED, that all responsibilities pertaining to the Apache Incubator > >>> Pulsar podling encumbered upon the Apache Incubator PMC are hereafter > >>> discharged. > >>> > >>> ---------------------------------------- > >>> > >>> > >>> -- > >>> Matteo Merli > >>> <mme...@apache.org> > >>> -- > >>> Matteo Merli > >>> <mme...@apache.org> > >> > > > > -- Matteo Merli <mme...@apache.org>
