Podling Report Reminder - September 2018

[jmclean]

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 19 September 2018, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, September 05).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://wiki.apache.org/incubator/September2018

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: [DRAFT] [UPDATED] Graduation resolution proposal

[P. Taylor Goetz]

+1

-Taylor

> On Sep 2, 2018, at 3:18 PM, Matteo Merli  wrote:
> 
> Updated the initial draft by removing paragraph on the "have a tasking for
> creating set of bylaws".
> 
> 
> 
> 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   
> * Brad McMillen   
> * David Fisher
> * Francis Christopher Liu 
> * Hiroyuki Sakai  
> * Ivan Brendan Kelly  
> * Jai Asher   
> * Jia Zhai
> * Jim Jagielski   
> * Joe Francis 
> * Ludwig Pummer   
> * Masahiro Sakamoto   
> * Masakazu Kitajo 
> * Matteo Merli
> * Nozomi Kurihara 
> * P. Taylor Goetz 
> * Rajan Dhabalia  
> * Sahaya Andrews  
> * Sanjeev Kulkarni
> * Sebastián Schepens  
> * Siddharth Boobna
> * Sijie Guo   
> * Yuki Shiga  
> 
> 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 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
> 

Re: [DRAFT] [UPDATED] Graduation resolution proposal

[Matteo Merli]

Sentence got cut when sending : (Updated the initial draft by removing
paragraph on "task to adopt a set of bylaws")

On Sun, Sep 2, 2018 at 12:22 PM Jim Jagielski  wrote:

> +1 (binding)! :)
>
> > On Sep 2, 2018, at 3:18 PM, Matteo Merli  wrote:
> >
> > Updated the initial draft by removing paragraph on the "have a tasking
> for
> > creating set of bylaws".
> >
> > 
> >
> > 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   
> > * Brad McMillen   
> > * David Fisher
> > * Francis Christopher Liu 
> > * Hiroyuki Sakai  
> > * Ivan Brendan Kelly  
> > * Jai Asher   
> > * Jia Zhai
> > * Jim Jagielski   
> > * Joe Francis 
> > * Ludwig Pummer   
> > * Masahiro Sakamoto   
> > * Masakazu Kitajo 
> > * Matteo Merli
> > * Nozomi Kurihara 
> > * P. Taylor Goetz 
> > * Rajan Dhabalia  
> > * Sahaya Andrews  
> > * Sanjeev Kulkarni
> > * Sebastián Schepens  
> > * Siddharth Boobna
> > * Sijie Guo   
> > * Yuki Shiga  
> >
> > 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 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
> > 
>
> --
Matteo Merli

Re: [DRAFT] [UPDATED] Graduation resolution proposal

[Jim Jagielski]

+1 (binding)! :)

> On Sep 2, 2018, at 3:18 PM, Matteo Merli  wrote:
> 
> Updated the initial draft by removing paragraph on the "have a tasking for
> creating set of bylaws".
> 
> 
> 
> 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   
> * Brad McMillen   
> * David Fisher
> * Francis Christopher Liu 
> * Hiroyuki Sakai  
> * Ivan Brendan Kelly  
> * Jai Asher   
> * Jia Zhai
> * Jim Jagielski   
> * Joe Francis 
> * Ludwig Pummer   
> * Masahiro Sakamoto   
> * Masakazu Kitajo 
> * Matteo Merli
> * Nozomi Kurihara 
> * P. Taylor Goetz 
> * Rajan Dhabalia  
> * Sahaya Andrews  
> * Sanjeev Kulkarni
> * Sebastián Schepens  
> * Siddharth Boobna
> * Sijie Guo   
> * Yuki Shiga  
> 
> 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 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
> 

Re: [DRAFT] [UPDATED] Graduation resolution proposal

[Matteo Merli]

Updated the initial draft by removing paragraph on the "have a tasking for
creating set of bylaws".



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   
 * Brad McMillen   
 * David Fisher
 * Francis Christopher Liu 
 * Hiroyuki Sakai  
 * Ivan Brendan Kelly  
 * Jai Asher   
 * Jia Zhai
 * Jim Jagielski   
 * Joe Francis 
 * Ludwig Pummer   
 * Masahiro Sakamoto   
 * Masakazu Kitajo 
 * Matteo Merli
 * Nozomi Kurihara 
 * P. Taylor Goetz 
 * Rajan Dhabalia  
 * Sahaya Andrews  
 * Sanjeev Kulkarni
 * Sebastián Schepens  
 * Siddharth Boobna
 * Sijie Guo   
 * Yuki Shiga  

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 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

Re: [DRAFT] Graduation resolution proposal

[Matteo Merli]

On Sun, Sep 2, 2018 at 11:59 AM Dave Fisher  wrote:

> Hi Matteo -
>
> The BookKeeper bylaws are a problem in that the PMC Emeritus process is
> not the Apache Way. Merit does not expire and numerous projects would be in
> trouble if those were the wide rules. It may not cause trouble for a PMC in
> the future. Not now as everything is good, but sooner or latter it may
> become grounds for trouble in the community. This is a foundation wide
> governance issue. IHMO - It is a bug in Whimsy. Which is why I brought it
> where I did. As such keep in mind that Jim has a very valid point. He is a
> Founder of the ASF and until this year had continually served as a Board
> member and/or Officer every year.
>
> Let’s remove the clause from the Resolution.
>

+1 -- I'll update draft

 Willing to discuss it with Sijie and Ivan on those lists.>
>

I didn't want to bring trouble also on BookKeeper :)


-- 
Matteo Merli

Re: Slack

[Matteo Merli]

On Fri, Aug 31, 2018 at 7:16 PM Dave Fisher  wrote:

> Hi -
>
> Regarding Slack. Is this a free account? Who on the PPMC has control?
>

Yes, the account is free. I created it initially and most people from the
PPMC have admin status on the instance. You Dave are also marked as admin.
Back when we started I was adding everyone from PPMC when registered to
Slack.

If there's anyone missing, any other "admin" can promote other regular
users into "admins" as well.


> Matteo - how do you run the daily script to send a digest of Slack
> conversations to dev@?
>

Currently, is running as a cron job from a private EC2 instance. I
initially tried to run it from ASF Jenkins but I had issues with the couple
of Python dependencies that the script needs. I guess, it might be a good
idea to run the script from a Docker image, so that it becomes easier to
run on Jenkins.

Script is still at https://github.com/merlimat/slack-email-digest

Matteo


>
> Regards,
> Dave
>
> Sent from my iPhone
>
-- 
Matteo Merli

Re: [DRAFT] Graduation resolution proposal

[Dave Fisher]

Hi Matteo -

The BookKeeper bylaws are a problem in that the PMC Emeritus process is not the 
Apache Way. Merit does not expire and numerous projects would be in trouble if 
those were the wide rules. It may not cause trouble for a PMC in the future. 
Not now as everything is good, but sooner or latter it may become grounds for 
trouble in the community. This is a foundation wide governance issue. IHMO - It 
is a bug in Whimsy. Which is why I brought it where I did. As such keep in mind 
that Jim has a very valid point. He is a Founder of the ASF and until this year 
had continually served as a Board member and/or Officer every year.

Let’s remove the clause from the Resolution.

A contribution guide can cover many of the points you find useful, but some of 
these bylaws are in conflict with the overall understanding of the Apache Way. 
Particularly about the PMC. If you become the VP of Pulsar you will see the 
large threads on board@ that discuss these and similar issues.



Regards,
Dave

> On Sep 2, 2018, at 11:10 AM, Matteo Merli  wrote:
> 
> 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  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  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  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>> 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
>> es

Re: [DRAFT] Graduation resolution proposal

[Matteo Merli]

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  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  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  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>> 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 Preside

Re: [DRAFT] Graduation resolution proposal

[Dave Fisher]

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  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  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 
>> 
>> [2] http://www.apache.org/dev/pmc.html 
>> 
>>> On Aug 31, 2018, at 12:43 PM, Matteo Merli >> > wrote:
>>> 
>>> I have prepared the draft for the graduation resolution using the
>>> Whimsy tool (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
>>>  
>>> 
>>> 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   
>>> * Brad McMillen   
>>> * David Fisher
>>> * Francis Christopher Liu 
>>> * Hiroyuki Sakai  
>>> * Ivan Brendan Kelly  
>>> * Jai Asher   
>>> * Jia Zhai
>>> * Jim Jagielski   
>>> * Joe Francis 
>>> * Ludwig Pummer   
>>> * Masahiro Sakamoto   
>>> * Masakazu Kitajo 
>>> * Matteo Merli
>>> * Nozomi Kurihara 
>>> * P. Taylor Goetz 
>>> * Rajan Dhabalia  
>>> * Sahaya Andrews  
>>> * Sanjeev Kulkarni
>>> * Sebastián Schepens  
>>> * Siddharth Boobna
>>> * Sijie Guo   
>>> * Yuki Shiga  
>>> 
>>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed
>>> to the office of Vice President, Apache Pulsar, to serve in accordance
>>>

Re: [DRAFT] Graduation resolution proposal

[Jim Jagielski]

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  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 
> 
> [2] http://www.apache.org/dev/pmc.html 
> 
>> On Aug 31, 2018, at 12:43 PM, Matteo Merli > > wrote:
>> 
>> I have prepared the draft for the graduation resolution using the
>> Whimsy tool (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
>>  
>> 
>> 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   
>> * Brad McMillen   
>> * David Fisher
>> * Francis Christopher Liu 
>> * Hiroyuki Sakai  
>> * Ivan Brendan Kelly  
>> * Jai Asher   
>> * Jia Zhai
>> * Jim Jagielski   
>> * Joe Francis 
>> * Ludwig Pummer   
>> * Masahiro Sakamoto   
>> * Masakazu Kitajo 
>> * Matteo Merli
>> * Nozomi Kurihara 
>> * P. Taylor Goetz 
>> * Rajan Dhabalia  
>> * Sahaya Andrews  
>> * Sanjeev Kulkarni
>> * Sebastián Schepens  
>> * Siddharth Boobna
>> * Sijie Guo   
>> * Yuki Shiga  
>> 
>> 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 c