I can statistics some data for all PPMCs and committers, which can
include count of mails, issues, pull requests, code addition and deletion
after we goto incubator, and can statistics last contribution time, does
the statistics enough?

------------------

Liang Zhang (John)
Apache ShardingSphere & Dubbo


zhangli...@apache.org <zhangli...@apache.org> 于2020年2月6日周四 上午1:59写道:

> Before I list all PPMCs and committers, we need to discuss the rule of how
> to define `inactive` PPMC.
>
> The rules maybe:
>
>   - Stop contribution after ShardingSphere goto incubator.
>   - Rare contribution after ShardingSphere goto incubator. We need to
> define how to define `rare` too.
>   - Stop contribution during past period until now. The definition of
> `during past period` maybe one year or half year.
>
> If we decide follow these rules, we may let these PPMCs as committers.
>
> And do we need to discuss the rules to upgrade committers to PMC?
>
> Any suggestions?
>
> ------------------
>
> Liang Zhang (John)
> Apache ShardingSphere & Dubbo
>
>
> Sheng Wu <wu.sheng.841...@gmail.com> 于2020年2月5日周三 下午9:28写道:
>
>> Zonglei Dong <dongzong...@apache.org> 于2020年2月5日周三 下午9:19写道:
>>
>> > Hi Sheng, Liang,
>> >
>> >
>> > As a committer, I want to take on greater responsibility, make more
>> > contribution to ShardingSphere and take better practice for Apache Way
>> in
>> > the future.
>> >
>> >
>> > I understand some permissions only for PMC(or PPMC), e.g release new
>> > version, Does there are any difference between PMC and committer?
>> >
>>
>> For release, the committer is enough to go for a release, you just need
>> PMC's vote to make release official.
>>
>> As an active PMC member should
>> 1. Watching the project to follow the Apache way
>> 2. Watching the branding issue, and work on the issues if find it(such as
>> talk with other committer/contributor or 3rd party)
>> 3. Find and promote new committer and PMC member
>> For more, read https://www.apache.org/dev/pmc.html
>>
>> Also, in the Apache, we don't(also shouldn't) require people always
>> active.
>> You could do these in part-time, or when you have time.
>>
>>
>>
>> >
>> >
>> > Thanks.
>> > Best wishes.
>> >
>> >
>> > Zonglei Dong
>> > Apache ShardingSphere
>> >
>> >
>> > On 02/5/2020 20:34,Sheng Wu<wu.sheng.841...@gmail.com> wrote:
>> > I had the impression that inactive PPMC will be excluded to become PMC.
>> > ALL in or not?
>> >
>> > Do you have the list? I think if some of them stop contributing to the
>> > project after joining the incubator, I could exclude those.
>> >
>> > I nominate myself as project VP because my responsibility is monthly
>> > report
>> > to incubator, and I will in charge of to report to ASF in future.
>> >
>> > +1
>> >
>> > I would like to keep all PPMC members to PMC, and keep all current
>> > committers as committers too.
>> >
>> > Personally, I prefer to move all committers to PMC. I trust they will
>> > follow the more experienced PMC's suggestions and they wouldn't break
>> the
>> > ASF rules intentionally.
>> >
>> > To All committer(but not PMC)
>> > What do you think? I would like to support their own decision.
>> >
>> >
>> > Sheng Wu 吴晟
>> > Twitter, wusheng1108
>> >
>> >
>> > Juan Pan <panj...@apache.org> 于2020年2月5日周三 下午6:55写道:
>> >
>> > I would like to keep all PPMC members to PMC, and keep all current
>> > committers as committers too.
>> >
>> >
>> > I had the impression that inactive PPMC will be excluded to become PMC.
>> > ALL in or not?
>> >
>> >
>> > Juan Pan (Trista)
>> >
>> > Senior DBA & PPMC of Apache ShardingSphere(Incubating)
>> > E-mail: panj...@apache.org
>> >
>> >
>> >
>> >
>> > On 02/5/2020 17:38,zhangli...@apache.org<zhangli...@apache.org> wrote:
>> > I want discuss about project VP, PMC and committer list after
>> graduation.
>> > I would like to keep all PPMC members to PMC, and keep all current
>> > committers as committers too.
>> > The almost committers are new guys for ShardingSphere, they may need
>> more
>> > experiences for open source community governance, we can vote
>> committers to
>> > PMC one by one after graduation.
>> > I nominate myself as project VP because my responsibility is monthly
>> report
>> > to incubator, and I will in charge of to report to ASF in future.
>> >
>> > Any suggestion?
>> > ------------------
>> >
>> > Liang Zhang (John)
>> > Apache ShardingSphere & Dubbo
>> >
>> >
>> > zhangli...@apache.org <zhangli...@apache.org> 于2020年1月20日周一 下午3:26写道:
>> >
>> > Got it, it means those threads are not block for our graduation, and
>> > could be done anytime.
>> >
>> > Yes
>> >
>> > ------------------
>> >
>> > Liang Zhang (John)
>> > Apache ShardingSphere & Dubbo
>> >
>> >
>> > Juan Pan <panj...@apache.org> 于2020年1月20日周一 上午10:14写道:
>> >
>> > Got it, it means those threads are not block for our graduation, and
>> > could be done anytime.
>> >
>> >
>> > Juan Pan (Trista)
>> >
>> > Senior DBA & PPMC of Apache ShardingSphere(Incubating)
>> > E-mail: panj...@apache.org
>> >
>> >
>> >
>> >
>> > On 01/19/2020 10:37,Sheng Wu<wu.sheng.841...@gmail.com> wrote:
>> > As far as those docs and examples already in the Apache repos, I think
>> > those are irrelavent.
>> >
>> > Sheng Wu 吴晟
>> > Twitter, wusheng1108
>> >
>> >
>> > Juan Pan <panj...@apache.org> 于2020年1月19日周日 上午10:30写道:
>> >
>> > +1 Agreeing to put graduation into our upcoming agenda. BTW, do you
>> think
>> > we need  finish the work discussed in other thread, like moving doc and
>> > example repos to ShardingSphere repo?
>> >
>> >
>> > Juan Pan (Trista)
>> >
>> > Senior DBA & PPMC of Apache ShardingSphere(Incubating)
>> > E-mail: panj...@apache.org
>> >
>> >
>> >
>> >
>> > On 01/17/2020 23:39,zhangli...@apache.org<zhangli...@apache.org> wrote:
>> > I list remain issues here:
>> >
>> > 1. Remove author information in java code, copyright should belong to
>> ASF.
>> > 2. Some remain codes[1] still using the old package name
>> > `io.shardingsphere`, we plan to rename them as `io.opensharding`.
>> > <https://github.com/OpenSharding>3. Let the major contributors to sign
>> > ICLA
>> > if they haven't singed yet.
>> >
>> > Please complement the list if I missing anything.
>> >
>> > [1] https://github.com/OpenSharding
>> >
>> > ------------------
>> >
>> > Liang Zhang (John)
>> > Apache ShardingSphere & Dubbo
>> >
>> >
>> > Sheng Wu <wu.sheng.841...@gmail.com> 于2020年1月17日周五 下午6:01写道:
>> >
>> > From my perspective, we should. Like I said in another thread.
>> > I think we should be ready to consider and filter whether we have left
>> any
>> > issue before graduation.
>> >
>> > Sheng Wu 吴晟
>> > Twitter, wusheng1108
>> >
>> >
>> > zhangli...@apache.org <zhangli...@apache.org> 于2020年1月17日周五 下午3:10写道:
>> >
>> > Hello community,
>> >
>> >
>> > I'd like to talk about graduation as TLP for Apache
>> > ShardingSphere(Incubator).
>> >
>> >
>> > We were open source at 16th Jan 2016, and entered into ASF incubator in
>> > 10th Nov 2018. During the past period in incubator, our community grow
>> up
>> > quickly.
>> >
>> >
>> > I summarize some data below:
>> >
>> >
>> > - There are 1301 emails sent by 159 people in dev mailing-list excepted
>> > GitBox forwarded;
>> >
>> > - 2539 Issues created during ASF incubating, 2468 Issues resolved during
>> > ASF incubating;
>> >
>> > - 1073 PRs created during ASF incubating, 918 PRs merged during ASF
>> > incubating;
>> >
>> > - There are 89 contributors for now;
>> >
>> > - There are 4 versions released successfully conformant to Apache
>> release
>> > policy by 3 release managers;
>> >
>> > - There are 2 new PPMCs and 8 new committers were invited to join the
>> > community.
>> >
>> >
>> > We had already finished the Podling Maturity Assessment for
>> > ShardingSphere[1], the 34 items are all passed.
>> >
>> >
>> > We had resolved all branding issues which include Logo, GitHub repo,
>> > document, website and DockerHub image.
>> >
>> >
>> >
>> > Can we talk about when will start to consider about graduate?
>> >
>> >
>> > [1]
>> > https://github.com/apache/incubator-shardingsphere/blob/dev/MATURITY.md
>> >
>> >
>> > ------------------
>> >
>> >
>> > Liang Zhang (John)
>> >
>> > Apache ShardingSphere & Dubbo
>> >
>> >
>> >
>> >
>> >
>> >
>>
>

Reply via email to