You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kyuubi.apache.org by Kent Yao <ya...@apache.org> on 2022/03/09 08:23:19 UTC

[DISCUSS] Become A Committer of Apache Kyuubi

Hello PPMC and community,

In this thread, I want to discuss our committer requirements for
contributors that are willing to move from contributors to committers.

Hope to build a consensus with the following proposal.

===============================

# Become A Committer of Apache Kyuubi

Anyone being supportive of the community and working in any of the
CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
acronym from ASF to describe how we recognize your contributions not
only but code.

- **Co**mmunity - You can join us via our mailing list, issue
trackers, discussions page to interact with community members, and
share vision and knowledge
- **P**roject - a clear vision and consensus are needed
- **Do**cumentation - without it, the stuff remains only in the minds
of the authors
- **C**ode - discussion goes nowhere without code

Apache Kyuubi community strives to be meritocratic. Thus, once someone
has contributed sufficiently to any area of CoPDoC they can be a
candidate for committer-ship and at last, voted in as a Kyuubi
committer. Being an Apache Kyuubi committer does not necessarily mean
you must commit code with your commit privilege to the codebase; it
means you are committed to the Kyuubi project and are productively
contributing to our community's success.

## Committer Requirements:

There are no strict rules for becoming a committer or PMC member.
Candidates for new committers are typically people that are active
contributors and community members. Anyway, if the rules can be
clarified a little bit, it can somehow clear the doubts in the minds
of contributors and make the community more transparent, reasonable,
and fair.

### Continuous contributions

Committer candidates should have a decent amount of continuous
engagements and contributions (fixing bugs, adding new features,
writing documentation, maintaining issues boards, or answering
community questions) to Kyuubi either by contributing to the codebase
of main or website GitHub repositories.
- +3 months with light activity and engagement.
- +2 months of medium activity and engagement.
- +1 month with solid activity and engagement.

### Quality of contributions

- Well tested, well-designed, following Apache Kyuubi coding
standards, and simple patches.
- Well-organized and detailed user-oriented documentation.

### Community involvement

- Be active on the dev mailing list and help mentor newer contributors
and users.
- Be active on the issue tracker for project maintenance
- Be involved in the design road map discussions with a professional
and diplomatic approach even if there is a disagreement


===============================

Thank you for all your feedback and time. If there are no strong
objections, I will put this on our website.

BR,

Kent Yao

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Kent Yao <ya...@apache.org>.

Thanks All,


The doc has been updated on the official website[1]

Feedbacks are still welcome.

BR,

Kent Yao


[1] https://kyuubi.apache.org/become_committer.html



On 2022/03/14 07:57:37 Kent Yao wrote:
> Thanks, YiKun for the support and input.
> 
> 1. For specific activities which may belong to a certain area of
> CoPDoC, I guess we'd better put them
> in the CONTRIBUTING[1] guide not here. For example, diversity
> architecture support may need
> design and discussion being raised in mailing lists, code change via
> PRs, tech posts through
> blogs/conferences, documentations, e.t.c. It is inevitable that we
> will miss something if we try to make
> it as detailed as we can. This, on the contrary, can lead to some
> ambiguities and misunderstandings.
> 
> 2. The second suggestion may be similar to 'Promoting the project by
> writing articles or holding events.',
>  said Willem. And It will be great if we add this to the CONTRIBUTING guide.
> 
> 
> BR,
> 
> Kent Yao
> 
> [1] https://github.com/apache/incubator-kyuubi/blob/master/CONTRIBUTING.md
> 
> Yikun Jiang <yi...@gmail.com> 于2022年3月12日周六 16:46写道：
> >
> > Big no-binding +1 on this charter, I also think this is a good practice for
> > "community over the code".
> >
> > In addition, I think we can add some to encourage contributions in various
> > fields to make community better.
> >
> > -From tech view, we can encourage the improvement of specific fields, such
> > as diversity architecture (such as, x86 or arm), the deployment of
> > different OS, security improvement and so on, to make Kyuubi can expand
> > more application scenarios.
> >
> > -From community view, in addition to "you can join us via our mailing list,
> > issue trackers, discussions page to interact with community members, and
> > Share vision and knowledge", we might also encourage and help Kyuubi to
> > speak out in the outside world, including but not limited to development
> > related, such as share user story, best practices, join/organize the meetup.
> >
> > Regards,
> > Yikun
>

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Kent Yao <ya...@apache.org>.

Thanks, YiKun for the support and input.

1. For specific activities which may belong to a certain area of
CoPDoC, I guess we'd better put them
in the CONTRIBUTING[1] guide not here. For example, diversity
architecture support may need
design and discussion being raised in mailing lists, code change via
PRs, tech posts through
blogs/conferences, documentations, e.t.c. It is inevitable that we
will miss something if we try to make
it as detailed as we can. This, on the contrary, can lead to some
ambiguities and misunderstandings.

2. The second suggestion may be similar to 'Promoting the project by
writing articles or holding events.',
 said Willem. And It will be great if we add this to the CONTRIBUTING guide.


BR,

Kent Yao

[1] https://github.com/apache/incubator-kyuubi/blob/master/CONTRIBUTING.md

Yikun Jiang <yi...@gmail.com> 于2022年3月12日周六 16:46写道：
>
> Big no-binding +1 on this charter, I also think this is a good practice for
> "community over the code".
>
> In addition, I think we can add some to encourage contributions in various
> fields to make community better.
>
> -From tech view, we can encourage the improvement of specific fields, such
> as diversity architecture (such as, x86 or arm), the deployment of
> different OS, security improvement and so on, to make Kyuubi can expand
> more application scenarios.
>
> -From community view, in addition to "you can join us via our mailing list,
> issue trackers, discussions page to interact with community members, and
> Share vision and knowledge", we might also encourage and help Kyuubi to
> speak out in the outside world, including but not limited to development
> related, such as share user story, best practices, join/organize the meetup.
>
> Regards,
> Yikun

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Yikun Jiang <yi...@gmail.com>.

Big no-binding +1 on this charter, I also think this is a good practice for
"community over the code".

In addition, I think we can add some to encourage contributions in various
fields to make community better.

-From tech view, we can encourage the improvement of specific fields, such
as diversity architecture (such as, x86 or arm), the deployment of
different OS, security improvement and so on, to make Kyuubi can expand
more application scenarios.

-From community view, in addition to "you can join us via our mailing list,
issue trackers, discussions page to interact with community members, and
Share vision and knowledge", we might also encourage and help Kyuubi to
speak out in the outside world, including but not limited to development
related, such as share user story, best practices, join/organize the meetup.

Regards,
Yikun

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Kent Yao <ya...@apache.org>.

Hi Willem,

Thanks for the input. LGTM, I will address the comment.


BR,

Kent Yao

Willem Jiang <wi...@gmail.com> 于2022年3月10日周四 16:21写道：
>
> For the community involvement, I suggest we add a line:
>
> Promoting the project by writing articles or holding events.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
> On Wed, Mar 9, 2022 at 4:23 PM Kent Yao <ya...@apache.org> wrote:
> >
> > Hello PPMC and community,
> >
> > In this thread, I want to discuss our committer requirements for
> > contributors that are willing to move from contributors to committers.
> >
> > Hope to build a consensus with the following proposal.
> >
> > ===============================
> >
> > # Become A Committer of Apache Kyuubi
> >
> > Anyone being supportive of the community and working in any of the
> > CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> > acronym from ASF to describe how we recognize your contributions not
> > only but code.
> >
> > - **Co**mmunity - You can join us via our mailing list, issue
> > trackers, discussions page to interact with community members, and
> > share vision and knowledge
> > - **P**roject - a clear vision and consensus are needed
> > - **Do**cumentation - without it, the stuff remains only in the minds
> > of the authors
> > - **C**ode - discussion goes nowhere without code
> >
> > Apache Kyuubi community strives to be meritocratic. Thus, once someone
> > has contributed sufficiently to any area of CoPDoC they can be a
> > candidate for committer-ship and at last, voted in as a Kyuubi
> > committer. Being an Apache Kyuubi committer does not necessarily mean
> > you must commit code with your commit privilege to the codebase; it
> > means you are committed to the Kyuubi project and are productively
> > contributing to our community's success.
> >
> > ## Committer Requirements:
> >
> > There are no strict rules for becoming a committer or PMC member.
> > Candidates for new committers are typically people that are active
> > contributors and community members. Anyway, if the rules can be
> > clarified a little bit, it can somehow clear the doubts in the minds
> > of contributors and make the community more transparent, reasonable,
> > and fair.
> >
> > ### Continuous contributions
> >
> > Committer candidates should have a decent amount of continuous
> > engagements and contributions (fixing bugs, adding new features,
> > writing documentation, maintaining issues boards, or answering
> > community questions) to Kyuubi either by contributing to the codebase
> > of main or website GitHub repositories.
> > - +3 months with light activity and engagement.
> > - +2 months of medium activity and engagement.
> > - +1 month with solid activity and engagement.
> >
> > ### Quality of contributions
> >
> > - Well tested, well-designed, following Apache Kyuubi coding
> > standards, and simple patches.
> > - Well-organized and detailed user-oriented documentation.
> >
> > ### Community involvement
> >
> > - Be active on the dev mailing list and help mentor newer contributors
> > and users.
> > - Be active on the issue tracker for project maintenance
> > - Be involved in the design road map discussions with a professional
> > and diplomatic approach even if there is a disagreement
> >
> >
> > ===============================
> >
> > Thank you for all your feedback and time. If there are no strong
> > objections, I will put this on our website.
> >
> > BR,
> >
> > Kent Yao

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Willem Jiang <wi...@gmail.com>.

For the community involvement, I suggest we add a line:

Promoting the project by writing articles or holding events.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Wed, Mar 9, 2022 at 4:23 PM Kent Yao <ya...@apache.org> wrote:
>
> Hello PPMC and community,
>
> In this thread, I want to discuss our committer requirements for
> contributors that are willing to move from contributors to committers.
>
> Hope to build a consensus with the following proposal.
>
> ===============================
>
> # Become A Committer of Apache Kyuubi
>
> Anyone being supportive of the community and working in any of the
> CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> acronym from ASF to describe how we recognize your contributions not
> only but code.
>
> - **Co**mmunity - You can join us via our mailing list, issue
> trackers, discussions page to interact with community members, and
> share vision and knowledge
> - **P**roject - a clear vision and consensus are needed
> - **Do**cumentation - without it, the stuff remains only in the minds
> of the authors
> - **C**ode - discussion goes nowhere without code
>
> Apache Kyuubi community strives to be meritocratic. Thus, once someone
> has contributed sufficiently to any area of CoPDoC they can be a
> candidate for committer-ship and at last, voted in as a Kyuubi
> committer. Being an Apache Kyuubi committer does not necessarily mean
> you must commit code with your commit privilege to the codebase; it
> means you are committed to the Kyuubi project and are productively
> contributing to our community's success.
>
> ## Committer Requirements:
>
> There are no strict rules for becoming a committer or PMC member.
> Candidates for new committers are typically people that are active
> contributors and community members. Anyway, if the rules can be
> clarified a little bit, it can somehow clear the doubts in the minds
> of contributors and make the community more transparent, reasonable,
> and fair.
>
> ### Continuous contributions
>
> Committer candidates should have a decent amount of continuous
> engagements and contributions (fixing bugs, adding new features,
> writing documentation, maintaining issues boards, or answering
> community questions) to Kyuubi either by contributing to the codebase
> of main or website GitHub repositories.
> - +3 months with light activity and engagement.
> - +2 months of medium activity and engagement.
> - +1 month with solid activity and engagement.
>
> ### Quality of contributions
>
> - Well tested, well-designed, following Apache Kyuubi coding
> standards, and simple patches.
> - Well-organized and detailed user-oriented documentation.
>
> ### Community involvement
>
> - Be active on the dev mailing list and help mentor newer contributors
> and users.
> - Be active on the issue tracker for project maintenance
> - Be involved in the design road map discussions with a professional
> and diplomatic approach even if there is a disagreement
>
>
> ===============================
>
> Thank you for all your feedback and time. If there are no strong
> objections, I will put this on our website.
>
> BR,
>
> Kent Yao

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Kent Yao <ya...@apache.org>.

Fix typo

> The CoPDoC is an acronym from ASF to describe how we recognize your
contributions not only but code.

The CoPDoC is an acronym from ASF to describe how we recognize your
contributions not only *by* code


Kent Yao <ya...@apache.org> 于2022年3月9日周三 16:23写道：

> Hello PPMC and community,
>
> In this thread, I want to discuss our committer requirements for
> contributors that are willing to move from contributors to committers.
>
> Hope to build a consensus with the following proposal.
>
> ===============================
>
> # Become A Committer of Apache Kyuubi
>
> Anyone being supportive of the community and working in any of the
> CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> acronym from ASF to describe how we recognize your contributions not
> only but code.
>
> - **Co**mmunity - You can join us via our mailing list, issue
> trackers, discussions page to interact with community members, and
> share vision and knowledge
> - **P**roject - a clear vision and consensus are needed
> - **Do**cumentation - without it, the stuff remains only in the minds
> of the authors
> - **C**ode - discussion goes nowhere without code
>
> Apache Kyuubi community strives to be meritocratic. Thus, once someone
> has contributed sufficiently to any area of CoPDoC they can be a
> candidate for committer-ship and at last, voted in as a Kyuubi
> committer. Being an Apache Kyuubi committer does not necessarily mean
> you must commit code with your commit privilege to the codebase; it
> means you are committed to the Kyuubi project and are productively
> contributing to our community's success.
>
> ## Committer Requirements:
>
> There are no strict rules for becoming a committer or PMC member.
> Candidates for new committers are typically people that are active
> contributors and community members. Anyway, if the rules can be
> clarified a little bit, it can somehow clear the doubts in the minds
> of contributors and make the community more transparent, reasonable,
> and fair.
>
> ### Continuous contributions
>
> Committer candidates should have a decent amount of continuous
> engagements and contributions (fixing bugs, adding new features,
> writing documentation, maintaining issues boards, or answering
> community questions) to Kyuubi either by contributing to the codebase
> of main or website GitHub repositories.
> - +3 months with light activity and engagement.
> - +2 months of medium activity and engagement.
> - +1 month with solid activity and engagement.
>
> ### Quality of contributions
>
> - Well tested, well-designed, following Apache Kyuubi coding
> standards, and simple patches.
> - Well-organized and detailed user-oriented documentation.
>
> ### Community involvement
>
> - Be active on the dev mailing list and help mentor newer contributors
> and users.
> - Be active on the issue tracker for project maintenance
> - Be involved in the design road map discussions with a professional
> and diplomatic approach even if there is a disagreement
>
>
> ===============================
>
> Thank you for all your feedback and time. If there are no strong
> objections, I will put this on our website.
>
> BR,
>
> Kent Yao
>

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Kent Yao <ya...@apache.org>.

Thanks, Vino,

It is a good suggestion for giving stimuli to contributors.

Will make a full plan for incentives at [1] and discuss it with the
community later. Suggestions are welcome.

BR,

Kent Yao

[1] https://github.com/apache/incubator-kyuubi/blob/master/CONTRIBUTING.md#easter-eggs-for-contributors

Vino Yang <ya...@gmail.com> 于2022年3月10日周四 18:26写道：
>
> Hi Kent,
>
> >> And my only concern is, I don't know if it's reasonable to do this *before*
> nomination,
> ASF seems to have a strict process for Committer nomination, before the
> committer
> announcement in the dev list, many uncertain things need to reach consensus
> in advance in the private mailing list.
>
> Yes, your concern is reasonable. Let me share more information.
>
> Before nomination, we can recognize outstanding contributors and vote
> about sending appreciated emails in private ML.
> After voting passed, the appreciated mail would be sent.
>
> In Apache Hudi community, we apply this rule.
>
> Just FYI.
>
> Best,
> Vino
>
> Kent Yao <ya...@apache.org> 于2022年3月10日周四 11:02写道：
> >
> > Hi Vino，
> >
> > Your suggestion looks good to me.
> >
> > This is a very beneficial way to maintain good community and contributor
> > relations.
> > For code contributors, we are generally able to express our appreciation in
> > PRs.
> > Of course, periodically aggregating and syncing these appreciations to our
> > mailing
> > list will also be an incentive for other contributors. I plan to list
> > contributions from all
> > contributors in more detail in ASF's quarterly reports to show
> > appreciation. In particular,
> > for some non-code contributors, such as Jianding Zhou, who recently worked
> > with me
> > to design our website and helped organize several meetups, these
> > contributions which are
> > a bit harder to track than code contributions, deserve to be documented
> > with care.
> >
> > And my only concern is, I don't know if it's reasonable to do this *before*
> > nomination,
> > ASF seems to have a strict process for Committer nomination, before the
> > committer
> > announcement in the dev list, many uncertain things need to reach consensus
> > in advance in the private mailing list.
> >
> > BR,
> >
> > Kent Yao
> >
> >
> > 在 2022年3月9日星期三，Vino Yang <ya...@gmail.com> 写道：
> >
> > > Hi Kent,
> > >
> > > Thanks for driving this.
> > >
> > > One suggestion to chime in:
> > >
> > > Before nominating one contributor to be a committer,
> > >
> > > WDYT about sending appreciated email to the contributors who make
> > > outstanding contributions to give them more passion and energy.
> > >
> > > And let them know that their work are recognised and appreciated.
> > >
> > > Best,
> > > Vino
> > >
> > > Kent Yao <ya...@apache.org> 于2022年3月9日周三 20:24写道：
> > > >
> > > > Hi Pan,
> > > >
> > > > Thanks, this will be fixed
> > > >
> > > > Cheng Pan <pa...@gmail.com> 于2022年3月9日周三 19:28写道：
> > > > >
> > > > > Thanks Kent for driving this, overall looks good to me, one question,
> > > > > as Kyuubi is still in the podling phase, should we replace "PMC
> > > > > member" by "PPMC member"?
> > > > >
> > > > > Thanks,
> > > > > Cheng Pan
> > > > >
> > > > > On Wed, Mar 9, 2022 at 7:24 PM Nicholas Jiang <
> > > nicholasjiang@apache.org> wrote:
> > > > > >
> > > > > > Hi Kent,
> > > > > >
> > > > > >    About the contribution, does the contribution include the
> > > practical articles in the company and technical Q&A?
> > > > > >
> > > > > >    What's more, I have a question about the requirements for
> > > becoming a PMC of Apache Kyuubi. IMO, the requirements could be discussed
> > > in the same thread. Could you please provide the standard to become a PMC?
> > > > > >
> > > > > > Best
> > > > > > Nicholas.
> > > > > >
> > > > > > On 2022/03/09 10:44:28 Kent Yao wrote:
> > > > > > > Thanks, Paul for the feedback. Updated according to your comments
> > > > > > >
> > > > > > >
> > > > > > > ===============================
> > > > > > >
> > > > > > > # Become A Committer of Apache Kyuubi
> > > > > > >
> > > > > > > Anyone being supportive of the community and working in any of the
> > > > > > > CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is
> > > an
> > > > > > > acronym from ASF to describe how we recognize your contributions
> > > not
> > > > > > > only by code.
> > > > > > >
> > > > > > > - **Co**mmunity - You can join us via our mailing list, issue
> > > > > > > trackers, discussions page to interact with community members, and
> > > > > > > share vision and knowledge
> > > > > > > - **P**roject - a clear vision and consensus are needed
> > > > > > > - **Do**cumentation - without it, the stuff remains only in the
> > > minds
> > > > > > > of the authors
> > > > > > > - **C**ode - discussion goes nowhere without code
> > > > > > >
> > > > > > > Apache Kyuubi community strives to be meritocratic. Thus, once
> > > someone
> > > > > > > has contributed sufficiently to any area of CoPDoC they can be a
> > > > > > > candidate for committer-ship and at last voted in as a Kyuubi
> > > > > > > committer. Being an Apache Kyuubi committer does not necessarily
> > > mean
> > > > > > > you must commit code with your commit privilege to the codebase; it
> > > > > > > means you are committed to the Kyuubi project and are productively
> > > > > > > contributing to our community's success.
> > > > > > >
> > > > > > > ## Committer Requirements:
> > > > > > >
> > > > > > > There are no strict rules for becoming a committer or PMC member.
> > > > > > > Candidates for new committers are typically people that are active
> > > > > > > contributors and community members. Anyway, if the rules can be
> > > > > > > clarified a little bit, it can somehow clear the doubts in the
> > > minds
> > > > > > > of contributors and make the community more transparent,
> > > reasonable,
> > > > > > > and fair.
> > > > > > >
> > > > > > > ### Continuous contributions
> > > > > > >
> > > > > > > Committer candidates should have a decent amount of continuous
> > > > > > > engagements and contributions (fixing bugs, adding new features,
> > > > > > > writing documentation, maintaining issues boards, code review, or
> > > answering
> > > > > > > community questions) to Kyuubi either by contributing to the
> > > codebase
> > > > > > > of the main website or Kyuubi's GitHub repositories
> > > > > > >
> > > > > > > - +3 months with light activity and engagement.
> > > > > > > - +2 months of medium activity and engagement.
> > > > > > > - +1 month with solid activity and engagement.
> > > > > > >
> > > > > > > ### Quality of contributions
> > > > > > > - A solid general understanding of the project
> > > > > > > - Well tested, well-designed, following Apache Kyuubi coding
> > > > > > > standards, and simple patches.
> > > > > > > - Well-organized and detailed user-oriented documentation.
> > > > > > >
> > > > > > > ### Community involvement
> > > > > > >
> > > > > > > - Be active, courteous, and respectful on the dev mailing list and
> > > > > > > help mentor newer contributors
> > > > > > > and users.
> > > > > > > - Be active, courteous, and respectful on the issue tracker for
> > > > > > > project maintenance
> > > > > > > - Be active, courteous, and respectful for pull requests reviewing
> > > > > > > - Be involved in the design road map discussions with a
> > > professional
> > > > > > > and diplomatic approach even if there is a disagreement
> > > > > > >
> > > > > > >
> > > > > > > ===============================
> > > > > > >
> > > > > > >
> > > > > > > Paul Lam <pa...@gmail.com> 于2022年3月9日周三 18:16写道：
> > > > > > > >
> > > > > > > > Hi Kent,
> > > > > > > >
> > > > > > > > The commuter guide is very informative and LGTM in general.
> > > > > > > >
> > > > > > > > I see two minor possible improvements:
> > > > > > > >
> > > > > > > > 1. code review could be listed as one of the contributions
> > > > > > > > 2. “the codebase of main or website GitHub repositories" -> “the
> > > codebase of the main website or Kyuubi's GitHub repositories"
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > Paul Lam
> > > > > > > >
> > > > > > > > > 2022年3月9日 17:39，LuNing Wang <wa...@gmail.com> 写道：
> > > > > > > > >
> > > > > > > > > Hi, I second with all the requirements above mentioned. Best,
> > > LuNing Wang
> > > > > > > > > 王鲁宁
> > > > > > > > >
> > > > > > > > > Nicholas Jiang <ni...@apache.org> 于2022年3月9日周三
> > > 17:17写道：
> > > > > > > > >
> > > > > > > > >> Hi Kent,
> > > > > > > > >>
> > > > > > > > >>   Thanks for starting the discussion thread about committer
> > > requirements.
> > > > > > > > >> IMO, the community is more than code. The committer need to
> > > have much
> > > > > > > > >> contribution like code, document, review and feature design
> > > and have an
> > > > > > > > >> excellent knowledge of the centain module in Kyuubi. In
> > > general, the
> > > > > > > > >> requirements make sense to me. I agree with all the
> > > requirements above
> > > > > > > > >> mentioned.
> > > > > > > > >>
> > > > > > > > >> Best,
> > > > > > > > >> Nicholas Jiang
> > > > > > > > >>
> > > > > > > > >> On 2022/03/09 08:23:19 Kent Yao wrote:
> > > > > > > > >>> Hello PPMC and community,
> > > > > > > > >>>
> > > > > > > > >>> In this thread, I want to discuss our committer requirements
> > > for
> > > > > > > > >>> contributors that are willing to move from contributors to
> > > committers.
> > > > > > > > >>>
> > > > > > > > >>> Hope to build a consensus with the following proposal.
> > > > > > > > >>>
> > > > > > > > >>> ===============================
> > > > > > > > >>>
> > > > > > > > >>> # Become A Committer of Apache Kyuubi
> > > > > > > > >>>
> > > > > > > > >>> Anyone being supportive of the community and working in any
> > > of the
> > > > > > > > >>> CoPDoC areas can become an Apache Kyuubi committer. The
> > > CoPDoC is an
> > > > > > > > >>> acronym from ASF to describe how we recognize your
> > > contributions not
> > > > > > > > >>> only but code.
> > > > > > > > >>>
> > > > > > > > >>> - **Co**mmunity - You can join us via our mailing list, issue
> > > > > > > > >>> trackers, discussions page to interact with community
> > > members, and
> > > > > > > > >>> share vision and knowledge
> > > > > > > > >>> - **P**roject - a clear vision and consensus are needed
> > > > > > > > >>> - **Do**cumentation - without it, the stuff remains only in
> > > the minds
> > > > > > > > >>> of the authors
> > > > > > > > >>> - **C**ode - discussion goes nowhere without code
> > > > > > > > >>>
> > > > > > > > >>> Apache Kyuubi community strives to be meritocratic. Thus,
> > > once someone
> > > > > > > > >>> has contributed sufficiently to any area of CoPDoC they can
> > > be a
> > > > > > > > >>> candidate for committer-ship and at last, voted in as a
> > > Kyuubi
> > > > > > > > >>> committer. Being an Apache Kyuubi committer does not
> > > necessarily mean
> > > > > > > > >>> you must commit code with your commit privilege to the
> > > codebase; it
> > > > > > > > >>> means you are committed to the Kyuubi project and are
> > > productively
> > > > > > > > >>> contributing to our community's success.
> > > > > > > > >>>
> > > > > > > > >>> ## Committer Requirements:
> > > > > > > > >>>
> > > > > > > > >>> There are no strict rules for becoming a committer or PMC
> > > member.
> > > > > > > > >>> Candidates for new committers are typically people that are
> > > active
> > > > > > > > >>> contributors and community members. Anyway, if the rules can
> > > be
> > > > > > > > >>> clarified a little bit, it can somehow clear the doubts in
> > > the minds
> > > > > > > > >>> of contributors and make the community more transparent,
> > > reasonable,
> > > > > > > > >>> and fair.
> > > > > > > > >>>
> > > > > > > > >>> ### Continuous contributions
> > > > > > > > >>>
> > > > > > > > >>> Committer candidates should have a decent amount of
> > > continuous
> > > > > > > > >>> engagements and contributions (fixing bugs, adding new
> > > features,
> > > > > > > > >>> writing documentation, maintaining issues boards, or
> > > answering
> > > > > > > > >>> community questions) to Kyuubi either by contributing to the
> > > codebase
> > > > > > > > >>> of main or website GitHub repositories.
> > > > > > > > >>> - +3 months with light activity and engagement.
> > > > > > > > >>> - +2 months of medium activity and engagement.
> > > > > > > > >>> - +1 month with solid activity and engagement.
> > > > > > > > >>>
> > > > > > > > >>> ### Quality of contributions
> > > > > > > > >>>
> > > > > > > > >>> - Well tested, well-designed, following Apache Kyuubi coding
> > > > > > > > >>> standards, and simple patches.
> > > > > > > > >>> - Well-organized and detailed user-oriented documentation.
> > > > > > > > >>>
> > > > > > > > >>> ### Community involvement
> > > > > > > > >>>
> > > > > > > > >>> - Be active on the dev mailing list and help mentor newer
> > > contributors
> > > > > > > > >>> and users.
> > > > > > > > >>> - Be active on the issue tracker for project maintenance
> > > > > > > > >>> - Be involved in the design road map discussions with a
> > > professional
> > > > > > > > >>> and diplomatic approach even if there is a disagreement
> > > > > > > > >>>
> > > > > > > > >>>
> > > > > > > > >>> ===============================
> > > > > > > > >>>
> > > > > > > > >>> Thank you for all your feedback and time. If there are no
> > > strong
> > > > > > > > >>> objections, I will put this on our website.
> > > > > > > > >>>
> > > > > > > > >>> BR,
> > > > > > > > >>>
> > > > > > > > >>> Kent Yao
> > > > > > > > >>>
> > > > > > > > >>
> > > > > > > >
> > > > > > >
> > >

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Vino Yang <ya...@gmail.com>.

Hi Kent,

>> And my only concern is, I don't know if it's reasonable to do this *before*
nomination,
ASF seems to have a strict process for Committer nomination, before the
committer
announcement in the dev list, many uncertain things need to reach consensus
in advance in the private mailing list.

Yes, your concern is reasonable. Let me share more information.

Before nomination, we can recognize outstanding contributors and vote
about sending appreciated emails in private ML.
After voting passed, the appreciated mail would be sent.

In Apache Hudi community, we apply this rule.

Just FYI.

Best,
Vino

Kent Yao <ya...@apache.org> 于2022年3月10日周四 11:02写道：
>
> Hi Vino，
>
> Your suggestion looks good to me.
>
> This is a very beneficial way to maintain good community and contributor
> relations.
> For code contributors, we are generally able to express our appreciation in
> PRs.
> Of course, periodically aggregating and syncing these appreciations to our
> mailing
> list will also be an incentive for other contributors. I plan to list
> contributions from all
> contributors in more detail in ASF's quarterly reports to show
> appreciation. In particular,
> for some non-code contributors, such as Jianding Zhou, who recently worked
> with me
> to design our website and helped organize several meetups, these
> contributions which are
> a bit harder to track than code contributions, deserve to be documented
> with care.
>
> And my only concern is, I don't know if it's reasonable to do this *before*
> nomination,
> ASF seems to have a strict process for Committer nomination, before the
> committer
> announcement in the dev list, many uncertain things need to reach consensus
> in advance in the private mailing list.
>
> BR,
>
> Kent Yao
>
>
> 在 2022年3月9日星期三，Vino Yang <ya...@gmail.com> 写道：
>
> > Hi Kent,
> >
> > Thanks for driving this.
> >
> > One suggestion to chime in:
> >
> > Before nominating one contributor to be a committer,
> >
> > WDYT about sending appreciated email to the contributors who make
> > outstanding contributions to give them more passion and energy.
> >
> > And let them know that their work are recognised and appreciated.
> >
> > Best,
> > Vino
> >
> > Kent Yao <ya...@apache.org> 于2022年3月9日周三 20:24写道：
> > >
> > > Hi Pan,
> > >
> > > Thanks, this will be fixed
> > >
> > > Cheng Pan <pa...@gmail.com> 于2022年3月9日周三 19:28写道：
> > > >
> > > > Thanks Kent for driving this, overall looks good to me, one question,
> > > > as Kyuubi is still in the podling phase, should we replace "PMC
> > > > member" by "PPMC member"?
> > > >
> > > > Thanks,
> > > > Cheng Pan
> > > >
> > > > On Wed, Mar 9, 2022 at 7:24 PM Nicholas Jiang <
> > nicholasjiang@apache.org> wrote:
> > > > >
> > > > > Hi Kent,
> > > > >
> > > > >    About the contribution, does the contribution include the
> > practical articles in the company and technical Q&A?
> > > > >
> > > > >    What's more, I have a question about the requirements for
> > becoming a PMC of Apache Kyuubi. IMO, the requirements could be discussed
> > in the same thread. Could you please provide the standard to become a PMC?
> > > > >
> > > > > Best
> > > > > Nicholas.
> > > > >
> > > > > On 2022/03/09 10:44:28 Kent Yao wrote:
> > > > > > Thanks, Paul for the feedback. Updated according to your comments
> > > > > >
> > > > > >
> > > > > > ===============================
> > > > > >
> > > > > > # Become A Committer of Apache Kyuubi
> > > > > >
> > > > > > Anyone being supportive of the community and working in any of the
> > > > > > CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is
> > an
> > > > > > acronym from ASF to describe how we recognize your contributions
> > not
> > > > > > only by code.
> > > > > >
> > > > > > - **Co**mmunity - You can join us via our mailing list, issue
> > > > > > trackers, discussions page to interact with community members, and
> > > > > > share vision and knowledge
> > > > > > - **P**roject - a clear vision and consensus are needed
> > > > > > - **Do**cumentation - without it, the stuff remains only in the
> > minds
> > > > > > of the authors
> > > > > > - **C**ode - discussion goes nowhere without code
> > > > > >
> > > > > > Apache Kyuubi community strives to be meritocratic. Thus, once
> > someone
> > > > > > has contributed sufficiently to any area of CoPDoC they can be a
> > > > > > candidate for committer-ship and at last voted in as a Kyuubi
> > > > > > committer. Being an Apache Kyuubi committer does not necessarily
> > mean
> > > > > > you must commit code with your commit privilege to the codebase; it
> > > > > > means you are committed to the Kyuubi project and are productively
> > > > > > contributing to our community's success.
> > > > > >
> > > > > > ## Committer Requirements:
> > > > > >
> > > > > > There are no strict rules for becoming a committer or PMC member.
> > > > > > Candidates for new committers are typically people that are active
> > > > > > contributors and community members. Anyway, if the rules can be
> > > > > > clarified a little bit, it can somehow clear the doubts in the
> > minds
> > > > > > of contributors and make the community more transparent,
> > reasonable,
> > > > > > and fair.
> > > > > >
> > > > > > ### Continuous contributions
> > > > > >
> > > > > > Committer candidates should have a decent amount of continuous
> > > > > > engagements and contributions (fixing bugs, adding new features,
> > > > > > writing documentation, maintaining issues boards, code review, or
> > answering
> > > > > > community questions) to Kyuubi either by contributing to the
> > codebase
> > > > > > of the main website or Kyuubi's GitHub repositories
> > > > > >
> > > > > > - +3 months with light activity and engagement.
> > > > > > - +2 months of medium activity and engagement.
> > > > > > - +1 month with solid activity and engagement.
> > > > > >
> > > > > > ### Quality of contributions
> > > > > > - A solid general understanding of the project
> > > > > > - Well tested, well-designed, following Apache Kyuubi coding
> > > > > > standards, and simple patches.
> > > > > > - Well-organized and detailed user-oriented documentation.
> > > > > >
> > > > > > ### Community involvement
> > > > > >
> > > > > > - Be active, courteous, and respectful on the dev mailing list and
> > > > > > help mentor newer contributors
> > > > > > and users.
> > > > > > - Be active, courteous, and respectful on the issue tracker for
> > > > > > project maintenance
> > > > > > - Be active, courteous, and respectful for pull requests reviewing
> > > > > > - Be involved in the design road map discussions with a
> > professional
> > > > > > and diplomatic approach even if there is a disagreement
> > > > > >
> > > > > >
> > > > > > ===============================
> > > > > >
> > > > > >
> > > > > > Paul Lam <pa...@gmail.com> 于2022年3月9日周三 18:16写道：
> > > > > > >
> > > > > > > Hi Kent,
> > > > > > >
> > > > > > > The commuter guide is very informative and LGTM in general.
> > > > > > >
> > > > > > > I see two minor possible improvements:
> > > > > > >
> > > > > > > 1. code review could be listed as one of the contributions
> > > > > > > 2. “the codebase of main or website GitHub repositories" -> “the
> > codebase of the main website or Kyuubi's GitHub repositories"
> > > > > > >
> > > > > > > Best,
> > > > > > > Paul Lam
> > > > > > >
> > > > > > > > 2022年3月9日 17:39，LuNing Wang <wa...@gmail.com> 写道：
> > > > > > > >
> > > > > > > > Hi, I second with all the requirements above mentioned. Best,
> > LuNing Wang
> > > > > > > > 王鲁宁
> > > > > > > >
> > > > > > > > Nicholas Jiang <ni...@apache.org> 于2022年3月9日周三
> > 17:17写道：
> > > > > > > >
> > > > > > > >> Hi Kent,
> > > > > > > >>
> > > > > > > >>   Thanks for starting the discussion thread about committer
> > requirements.
> > > > > > > >> IMO, the community is more than code. The committer need to
> > have much
> > > > > > > >> contribution like code, document, review and feature design
> > and have an
> > > > > > > >> excellent knowledge of the centain module in Kyuubi. In
> > general, the
> > > > > > > >> requirements make sense to me. I agree with all the
> > requirements above
> > > > > > > >> mentioned.
> > > > > > > >>
> > > > > > > >> Best,
> > > > > > > >> Nicholas Jiang
> > > > > > > >>
> > > > > > > >> On 2022/03/09 08:23:19 Kent Yao wrote:
> > > > > > > >>> Hello PPMC and community,
> > > > > > > >>>
> > > > > > > >>> In this thread, I want to discuss our committer requirements
> > for
> > > > > > > >>> contributors that are willing to move from contributors to
> > committers.
> > > > > > > >>>
> > > > > > > >>> Hope to build a consensus with the following proposal.
> > > > > > > >>>
> > > > > > > >>> ===============================
> > > > > > > >>>
> > > > > > > >>> # Become A Committer of Apache Kyuubi
> > > > > > > >>>
> > > > > > > >>> Anyone being supportive of the community and working in any
> > of the
> > > > > > > >>> CoPDoC areas can become an Apache Kyuubi committer. The
> > CoPDoC is an
> > > > > > > >>> acronym from ASF to describe how we recognize your
> > contributions not
> > > > > > > >>> only but code.
> > > > > > > >>>
> > > > > > > >>> - **Co**mmunity - You can join us via our mailing list, issue
> > > > > > > >>> trackers, discussions page to interact with community
> > members, and
> > > > > > > >>> share vision and knowledge
> > > > > > > >>> - **P**roject - a clear vision and consensus are needed
> > > > > > > >>> - **Do**cumentation - without it, the stuff remains only in
> > the minds
> > > > > > > >>> of the authors
> > > > > > > >>> - **C**ode - discussion goes nowhere without code
> > > > > > > >>>
> > > > > > > >>> Apache Kyuubi community strives to be meritocratic. Thus,
> > once someone
> > > > > > > >>> has contributed sufficiently to any area of CoPDoC they can
> > be a
> > > > > > > >>> candidate for committer-ship and at last, voted in as a
> > Kyuubi
> > > > > > > >>> committer. Being an Apache Kyuubi committer does not
> > necessarily mean
> > > > > > > >>> you must commit code with your commit privilege to the
> > codebase; it
> > > > > > > >>> means you are committed to the Kyuubi project and are
> > productively
> > > > > > > >>> contributing to our community's success.
> > > > > > > >>>
> > > > > > > >>> ## Committer Requirements:
> > > > > > > >>>
> > > > > > > >>> There are no strict rules for becoming a committer or PMC
> > member.
> > > > > > > >>> Candidates for new committers are typically people that are
> > active
> > > > > > > >>> contributors and community members. Anyway, if the rules can
> > be
> > > > > > > >>> clarified a little bit, it can somehow clear the doubts in
> > the minds
> > > > > > > >>> of contributors and make the community more transparent,
> > reasonable,
> > > > > > > >>> and fair.
> > > > > > > >>>
> > > > > > > >>> ### Continuous contributions
> > > > > > > >>>
> > > > > > > >>> Committer candidates should have a decent amount of
> > continuous
> > > > > > > >>> engagements and contributions (fixing bugs, adding new
> > features,
> > > > > > > >>> writing documentation, maintaining issues boards, or
> > answering
> > > > > > > >>> community questions) to Kyuubi either by contributing to the
> > codebase
> > > > > > > >>> of main or website GitHub repositories.
> > > > > > > >>> - +3 months with light activity and engagement.
> > > > > > > >>> - +2 months of medium activity and engagement.
> > > > > > > >>> - +1 month with solid activity and engagement.
> > > > > > > >>>
> > > > > > > >>> ### Quality of contributions
> > > > > > > >>>
> > > > > > > >>> - Well tested, well-designed, following Apache Kyuubi coding
> > > > > > > >>> standards, and simple patches.
> > > > > > > >>> - Well-organized and detailed user-oriented documentation.
> > > > > > > >>>
> > > > > > > >>> ### Community involvement
> > > > > > > >>>
> > > > > > > >>> - Be active on the dev mailing list and help mentor newer
> > contributors
> > > > > > > >>> and users.
> > > > > > > >>> - Be active on the issue tracker for project maintenance
> > > > > > > >>> - Be involved in the design road map discussions with a
> > professional
> > > > > > > >>> and diplomatic approach even if there is a disagreement
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>> ===============================
> > > > > > > >>>
> > > > > > > >>> Thank you for all your feedback and time. If there are no
> > strong
> > > > > > > >>> objections, I will put this on our website.
> > > > > > > >>>
> > > > > > > >>> BR,
> > > > > > > >>>
> > > > > > > >>> Kent Yao
> > > > > > > >>>
> > > > > > > >>
> > > > > > >
> > > > > >
> >

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Kent Yao <ya...@apache.org>.

Hi Vino，

Your suggestion looks good to me.

This is a very beneficial way to maintain good community and contributor
relations.
For code contributors, we are generally able to express our appreciation in
PRs.
Of course, periodically aggregating and syncing these appreciations to our
mailing
list will also be an incentive for other contributors. I plan to list
contributions from all
contributors in more detail in ASF's quarterly reports to show
appreciation. In particular,
for some non-code contributors, such as Jianding Zhou, who recently worked
with me
to design our website and helped organize several meetups, these
contributions which are
a bit harder to track than code contributions, deserve to be documented
with care.

And my only concern is, I don't know if it's reasonable to do this *before*
nomination,
ASF seems to have a strict process for Committer nomination, before the
committer
announcement in the dev list, many uncertain things need to reach consensus
in advance in the private mailing list.

BR,

Kent Yao


在 2022年3月9日星期三，Vino Yang <ya...@gmail.com> 写道：

> Hi Kent,
>
> Thanks for driving this.
>
> One suggestion to chime in:
>
> Before nominating one contributor to be a committer,
>
> WDYT about sending appreciated email to the contributors who make
> outstanding contributions to give them more passion and energy.
>
> And let them know that their work are recognised and appreciated.
>
> Best,
> Vino
>
> Kent Yao <ya...@apache.org> 于2022年3月9日周三 20:24写道：
> >
> > Hi Pan,
> >
> > Thanks, this will be fixed
> >
> > Cheng Pan <pa...@gmail.com> 于2022年3月9日周三 19:28写道：
> > >
> > > Thanks Kent for driving this, overall looks good to me, one question,
> > > as Kyuubi is still in the podling phase, should we replace "PMC
> > > member" by "PPMC member"?
> > >
> > > Thanks,
> > > Cheng Pan
> > >
> > > On Wed, Mar 9, 2022 at 7:24 PM Nicholas Jiang <
> nicholasjiang@apache.org> wrote:
> > > >
> > > > Hi Kent,
> > > >
> > > >    About the contribution, does the contribution include the
> practical articles in the company and technical Q&A?
> > > >
> > > >    What's more, I have a question about the requirements for
> becoming a PMC of Apache Kyuubi. IMO, the requirements could be discussed
> in the same thread. Could you please provide the standard to become a PMC?
> > > >
> > > > Best
> > > > Nicholas.
> > > >
> > > > On 2022/03/09 10:44:28 Kent Yao wrote:
> > > > > Thanks, Paul for the feedback. Updated according to your comments
> > > > >
> > > > >
> > > > > ===============================
> > > > >
> > > > > # Become A Committer of Apache Kyuubi
> > > > >
> > > > > Anyone being supportive of the community and working in any of the
> > > > > CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is
> an
> > > > > acronym from ASF to describe how we recognize your contributions
> not
> > > > > only by code.
> > > > >
> > > > > - **Co**mmunity - You can join us via our mailing list, issue
> > > > > trackers, discussions page to interact with community members, and
> > > > > share vision and knowledge
> > > > > - **P**roject - a clear vision and consensus are needed
> > > > > - **Do**cumentation - without it, the stuff remains only in the
> minds
> > > > > of the authors
> > > > > - **C**ode - discussion goes nowhere without code
> > > > >
> > > > > Apache Kyuubi community strives to be meritocratic. Thus, once
> someone
> > > > > has contributed sufficiently to any area of CoPDoC they can be a
> > > > > candidate for committer-ship and at last voted in as a Kyuubi
> > > > > committer. Being an Apache Kyuubi committer does not necessarily
> mean
> > > > > you must commit code with your commit privilege to the codebase; it
> > > > > means you are committed to the Kyuubi project and are productively
> > > > > contributing to our community's success.
> > > > >
> > > > > ## Committer Requirements:
> > > > >
> > > > > There are no strict rules for becoming a committer or PMC member.
> > > > > Candidates for new committers are typically people that are active
> > > > > contributors and community members. Anyway, if the rules can be
> > > > > clarified a little bit, it can somehow clear the doubts in the
> minds
> > > > > of contributors and make the community more transparent,
> reasonable,
> > > > > and fair.
> > > > >
> > > > > ### Continuous contributions
> > > > >
> > > > > Committer candidates should have a decent amount of continuous
> > > > > engagements and contributions (fixing bugs, adding new features,
> > > > > writing documentation, maintaining issues boards, code review, or
> answering
> > > > > community questions) to Kyuubi either by contributing to the
> codebase
> > > > > of the main website or Kyuubi's GitHub repositories
> > > > >
> > > > > - +3 months with light activity and engagement.
> > > > > - +2 months of medium activity and engagement.
> > > > > - +1 month with solid activity and engagement.
> > > > >
> > > > > ### Quality of contributions
> > > > > - A solid general understanding of the project
> > > > > - Well tested, well-designed, following Apache Kyuubi coding
> > > > > standards, and simple patches.
> > > > > - Well-organized and detailed user-oriented documentation.
> > > > >
> > > > > ### Community involvement
> > > > >
> > > > > - Be active, courteous, and respectful on the dev mailing list and
> > > > > help mentor newer contributors
> > > > > and users.
> > > > > - Be active, courteous, and respectful on the issue tracker for
> > > > > project maintenance
> > > > > - Be active, courteous, and respectful for pull requests reviewing
> > > > > - Be involved in the design road map discussions with a
> professional
> > > > > and diplomatic approach even if there is a disagreement
> > > > >
> > > > >
> > > > > ===============================
> > > > >
> > > > >
> > > > > Paul Lam <pa...@gmail.com> 于2022年3月9日周三 18:16写道：
> > > > > >
> > > > > > Hi Kent,
> > > > > >
> > > > > > The commuter guide is very informative and LGTM in general.
> > > > > >
> > > > > > I see two minor possible improvements:
> > > > > >
> > > > > > 1. code review could be listed as one of the contributions
> > > > > > 2. “the codebase of main or website GitHub repositories" -> “the
> codebase of the main website or Kyuubi's GitHub repositories"
> > > > > >
> > > > > > Best,
> > > > > > Paul Lam
> > > > > >
> > > > > > > 2022年3月9日 17:39，LuNing Wang <wa...@gmail.com> 写道：
> > > > > > >
> > > > > > > Hi, I second with all the requirements above mentioned. Best,
> LuNing Wang
> > > > > > > 王鲁宁
> > > > > > >
> > > > > > > Nicholas Jiang <ni...@apache.org> 于2022年3月9日周三
> 17:17写道：
> > > > > > >
> > > > > > >> Hi Kent,
> > > > > > >>
> > > > > > >>   Thanks for starting the discussion thread about committer
> requirements.
> > > > > > >> IMO, the community is more than code. The committer need to
> have much
> > > > > > >> contribution like code, document, review and feature design
> and have an
> > > > > > >> excellent knowledge of the centain module in Kyuubi. In
> general, the
> > > > > > >> requirements make sense to me. I agree with all the
> requirements above
> > > > > > >> mentioned.
> > > > > > >>
> > > > > > >> Best,
> > > > > > >> Nicholas Jiang
> > > > > > >>
> > > > > > >> On 2022/03/09 08:23:19 Kent Yao wrote:
> > > > > > >>> Hello PPMC and community,
> > > > > > >>>
> > > > > > >>> In this thread, I want to discuss our committer requirements
> for
> > > > > > >>> contributors that are willing to move from contributors to
> committers.
> > > > > > >>>
> > > > > > >>> Hope to build a consensus with the following proposal.
> > > > > > >>>
> > > > > > >>> ===============================
> > > > > > >>>
> > > > > > >>> # Become A Committer of Apache Kyuubi
> > > > > > >>>
> > > > > > >>> Anyone being supportive of the community and working in any
> of the
> > > > > > >>> CoPDoC areas can become an Apache Kyuubi committer. The
> CoPDoC is an
> > > > > > >>> acronym from ASF to describe how we recognize your
> contributions not
> > > > > > >>> only but code.
> > > > > > >>>
> > > > > > >>> - **Co**mmunity - You can join us via our mailing list, issue
> > > > > > >>> trackers, discussions page to interact with community
> members, and
> > > > > > >>> share vision and knowledge
> > > > > > >>> - **P**roject - a clear vision and consensus are needed
> > > > > > >>> - **Do**cumentation - without it, the stuff remains only in
> the minds
> > > > > > >>> of the authors
> > > > > > >>> - **C**ode - discussion goes nowhere without code
> > > > > > >>>
> > > > > > >>> Apache Kyuubi community strives to be meritocratic. Thus,
> once someone
> > > > > > >>> has contributed sufficiently to any area of CoPDoC they can
> be a
> > > > > > >>> candidate for committer-ship and at last, voted in as a
> Kyuubi
> > > > > > >>> committer. Being an Apache Kyuubi committer does not
> necessarily mean
> > > > > > >>> you must commit code with your commit privilege to the
> codebase; it
> > > > > > >>> means you are committed to the Kyuubi project and are
> productively
> > > > > > >>> contributing to our community's success.
> > > > > > >>>
> > > > > > >>> ## Committer Requirements:
> > > > > > >>>
> > > > > > >>> There are no strict rules for becoming a committer or PMC
> member.
> > > > > > >>> Candidates for new committers are typically people that are
> active
> > > > > > >>> contributors and community members. Anyway, if the rules can
> be
> > > > > > >>> clarified a little bit, it can somehow clear the doubts in
> the minds
> > > > > > >>> of contributors and make the community more transparent,
> reasonable,
> > > > > > >>> and fair.
> > > > > > >>>
> > > > > > >>> ### Continuous contributions
> > > > > > >>>
> > > > > > >>> Committer candidates should have a decent amount of
> continuous
> > > > > > >>> engagements and contributions (fixing bugs, adding new
> features,
> > > > > > >>> writing documentation, maintaining issues boards, or
> answering
> > > > > > >>> community questions) to Kyuubi either by contributing to the
> codebase
> > > > > > >>> of main or website GitHub repositories.
> > > > > > >>> - +3 months with light activity and engagement.
> > > > > > >>> - +2 months of medium activity and engagement.
> > > > > > >>> - +1 month with solid activity and engagement.
> > > > > > >>>
> > > > > > >>> ### Quality of contributions
> > > > > > >>>
> > > > > > >>> - Well tested, well-designed, following Apache Kyuubi coding
> > > > > > >>> standards, and simple patches.
> > > > > > >>> - Well-organized and detailed user-oriented documentation.
> > > > > > >>>
> > > > > > >>> ### Community involvement
> > > > > > >>>
> > > > > > >>> - Be active on the dev mailing list and help mentor newer
> contributors
> > > > > > >>> and users.
> > > > > > >>> - Be active on the issue tracker for project maintenance
> > > > > > >>> - Be involved in the design road map discussions with a
> professional
> > > > > > >>> and diplomatic approach even if there is a disagreement
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> ===============================
> > > > > > >>>
> > > > > > >>> Thank you for all your feedback and time. If there are no
> strong
> > > > > > >>> objections, I will put this on our website.
> > > > > > >>>
> > > > > > >>> BR,
> > > > > > >>>
> > > > > > >>> Kent Yao
> > > > > > >>>
> > > > > > >>
> > > > > >
> > > > >
>

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Vino Yang <ya...@gmail.com>.

Hi Kent,

Thanks for driving this.

One suggestion to chime in:

Before nominating one contributor to be a committer,

WDYT about sending appreciated email to the contributors who make
outstanding contributions to give them more passion and energy.

And let them know that their work are recognised and appreciated.

Best,
Vino

Kent Yao <ya...@apache.org> 于2022年3月9日周三 20:24写道：
>
> Hi Pan,
>
> Thanks, this will be fixed
>
> Cheng Pan <pa...@gmail.com> 于2022年3月9日周三 19:28写道：
> >
> > Thanks Kent for driving this, overall looks good to me, one question,
> > as Kyuubi is still in the podling phase, should we replace "PMC
> > member" by "PPMC member"?
> >
> > Thanks,
> > Cheng Pan
> >
> > On Wed, Mar 9, 2022 at 7:24 PM Nicholas Jiang <ni...@apache.org> wrote:
> > >
> > > Hi Kent,
> > >
> > >    About the contribution, does the contribution include the practical articles in the company and technical Q&A?
> > >
> > >    What's more, I have a question about the requirements for becoming a PMC of Apache Kyuubi. IMO, the requirements could be discussed in the same thread. Could you please provide the standard to become a PMC?
> > >
> > > Best
> > > Nicholas.
> > >
> > > On 2022/03/09 10:44:28 Kent Yao wrote:
> > > > Thanks, Paul for the feedback. Updated according to your comments
> > > >
> > > >
> > > > ===============================
> > > >
> > > > # Become A Committer of Apache Kyuubi
> > > >
> > > > Anyone being supportive of the community and working in any of the
> > > > CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> > > > acronym from ASF to describe how we recognize your contributions not
> > > > only by code.
> > > >
> > > > - **Co**mmunity - You can join us via our mailing list, issue
> > > > trackers, discussions page to interact with community members, and
> > > > share vision and knowledge
> > > > - **P**roject - a clear vision and consensus are needed
> > > > - **Do**cumentation - without it, the stuff remains only in the minds
> > > > of the authors
> > > > - **C**ode - discussion goes nowhere without code
> > > >
> > > > Apache Kyuubi community strives to be meritocratic. Thus, once someone
> > > > has contributed sufficiently to any area of CoPDoC they can be a
> > > > candidate for committer-ship and at last voted in as a Kyuubi
> > > > committer. Being an Apache Kyuubi committer does not necessarily mean
> > > > you must commit code with your commit privilege to the codebase; it
> > > > means you are committed to the Kyuubi project and are productively
> > > > contributing to our community's success.
> > > >
> > > > ## Committer Requirements:
> > > >
> > > > There are no strict rules for becoming a committer or PMC member.
> > > > Candidates for new committers are typically people that are active
> > > > contributors and community members. Anyway, if the rules can be
> > > > clarified a little bit, it can somehow clear the doubts in the minds
> > > > of contributors and make the community more transparent, reasonable,
> > > > and fair.
> > > >
> > > > ### Continuous contributions
> > > >
> > > > Committer candidates should have a decent amount of continuous
> > > > engagements and contributions (fixing bugs, adding new features,
> > > > writing documentation, maintaining issues boards, code review, or answering
> > > > community questions) to Kyuubi either by contributing to the codebase
> > > > of the main website or Kyuubi's GitHub repositories
> > > >
> > > > - +3 months with light activity and engagement.
> > > > - +2 months of medium activity and engagement.
> > > > - +1 month with solid activity and engagement.
> > > >
> > > > ### Quality of contributions
> > > > - A solid general understanding of the project
> > > > - Well tested, well-designed, following Apache Kyuubi coding
> > > > standards, and simple patches.
> > > > - Well-organized and detailed user-oriented documentation.
> > > >
> > > > ### Community involvement
> > > >
> > > > - Be active, courteous, and respectful on the dev mailing list and
> > > > help mentor newer contributors
> > > > and users.
> > > > - Be active, courteous, and respectful on the issue tracker for
> > > > project maintenance
> > > > - Be active, courteous, and respectful for pull requests reviewing
> > > > - Be involved in the design road map discussions with a professional
> > > > and diplomatic approach even if there is a disagreement
> > > >
> > > >
> > > > ===============================
> > > >
> > > >
> > > > Paul Lam <pa...@gmail.com> 于2022年3月9日周三 18:16写道：
> > > > >
> > > > > Hi Kent,
> > > > >
> > > > > The commuter guide is very informative and LGTM in general.
> > > > >
> > > > > I see two minor possible improvements:
> > > > >
> > > > > 1. code review could be listed as one of the contributions
> > > > > 2. “the codebase of main or website GitHub repositories" -> “the codebase of the main website or Kyuubi's GitHub repositories"
> > > > >
> > > > > Best,
> > > > > Paul Lam
> > > > >
> > > > > > 2022年3月9日 17:39，LuNing Wang <wa...@gmail.com> 写道：
> > > > > >
> > > > > > Hi, I second with all the requirements above mentioned. Best, LuNing Wang
> > > > > > 王鲁宁
> > > > > >
> > > > > > Nicholas Jiang <ni...@apache.org> 于2022年3月9日周三 17:17写道：
> > > > > >
> > > > > >> Hi Kent,
> > > > > >>
> > > > > >>   Thanks for starting the discussion thread about committer requirements.
> > > > > >> IMO, the community is more than code. The committer need to have much
> > > > > >> contribution like code, document, review and feature design and have an
> > > > > >> excellent knowledge of the centain module in Kyuubi. In general, the
> > > > > >> requirements make sense to me. I agree with all the requirements above
> > > > > >> mentioned.
> > > > > >>
> > > > > >> Best,
> > > > > >> Nicholas Jiang
> > > > > >>
> > > > > >> On 2022/03/09 08:23:19 Kent Yao wrote:
> > > > > >>> Hello PPMC and community,
> > > > > >>>
> > > > > >>> In this thread, I want to discuss our committer requirements for
> > > > > >>> contributors that are willing to move from contributors to committers.
> > > > > >>>
> > > > > >>> Hope to build a consensus with the following proposal.
> > > > > >>>
> > > > > >>> ===============================
> > > > > >>>
> > > > > >>> # Become A Committer of Apache Kyuubi
> > > > > >>>
> > > > > >>> Anyone being supportive of the community and working in any of the
> > > > > >>> CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> > > > > >>> acronym from ASF to describe how we recognize your contributions not
> > > > > >>> only but code.
> > > > > >>>
> > > > > >>> - **Co**mmunity - You can join us via our mailing list, issue
> > > > > >>> trackers, discussions page to interact with community members, and
> > > > > >>> share vision and knowledge
> > > > > >>> - **P**roject - a clear vision and consensus are needed
> > > > > >>> - **Do**cumentation - without it, the stuff remains only in the minds
> > > > > >>> of the authors
> > > > > >>> - **C**ode - discussion goes nowhere without code
> > > > > >>>
> > > > > >>> Apache Kyuubi community strives to be meritocratic. Thus, once someone
> > > > > >>> has contributed sufficiently to any area of CoPDoC they can be a
> > > > > >>> candidate for committer-ship and at last, voted in as a Kyuubi
> > > > > >>> committer. Being an Apache Kyuubi committer does not necessarily mean
> > > > > >>> you must commit code with your commit privilege to the codebase; it
> > > > > >>> means you are committed to the Kyuubi project and are productively
> > > > > >>> contributing to our community's success.
> > > > > >>>
> > > > > >>> ## Committer Requirements:
> > > > > >>>
> > > > > >>> There are no strict rules for becoming a committer or PMC member.
> > > > > >>> Candidates for new committers are typically people that are active
> > > > > >>> contributors and community members. Anyway, if the rules can be
> > > > > >>> clarified a little bit, it can somehow clear the doubts in the minds
> > > > > >>> of contributors and make the community more transparent, reasonable,
> > > > > >>> and fair.
> > > > > >>>
> > > > > >>> ### Continuous contributions
> > > > > >>>
> > > > > >>> Committer candidates should have a decent amount of continuous
> > > > > >>> engagements and contributions (fixing bugs, adding new features,
> > > > > >>> writing documentation, maintaining issues boards, or answering
> > > > > >>> community questions) to Kyuubi either by contributing to the codebase
> > > > > >>> of main or website GitHub repositories.
> > > > > >>> - +3 months with light activity and engagement.
> > > > > >>> - +2 months of medium activity and engagement.
> > > > > >>> - +1 month with solid activity and engagement.
> > > > > >>>
> > > > > >>> ### Quality of contributions
> > > > > >>>
> > > > > >>> - Well tested, well-designed, following Apache Kyuubi coding
> > > > > >>> standards, and simple patches.
> > > > > >>> - Well-organized and detailed user-oriented documentation.
> > > > > >>>
> > > > > >>> ### Community involvement
> > > > > >>>
> > > > > >>> - Be active on the dev mailing list and help mentor newer contributors
> > > > > >>> and users.
> > > > > >>> - Be active on the issue tracker for project maintenance
> > > > > >>> - Be involved in the design road map discussions with a professional
> > > > > >>> and diplomatic approach even if there is a disagreement
> > > > > >>>
> > > > > >>>
> > > > > >>> ===============================
> > > > > >>>
> > > > > >>> Thank you for all your feedback and time. If there are no strong
> > > > > >>> objections, I will put this on our website.
> > > > > >>>
> > > > > >>> BR,
> > > > > >>>
> > > > > >>> Kent Yao
> > > > > >>>
> > > > > >>
> > > > >
> > > >

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Kent Yao <ya...@apache.org>.

Hi Pan,

Thanks, this will be fixed

Cheng Pan <pa...@gmail.com> 于2022年3月9日周三 19:28写道：
>
> Thanks Kent for driving this, overall looks good to me, one question,
> as Kyuubi is still in the podling phase, should we replace "PMC
> member" by "PPMC member"?
>
> Thanks,
> Cheng Pan
>
> On Wed, Mar 9, 2022 at 7:24 PM Nicholas Jiang <ni...@apache.org> wrote:
> >
> > Hi Kent,
> >
> >    About the contribution, does the contribution include the practical articles in the company and technical Q&A?
> >
> >    What's more, I have a question about the requirements for becoming a PMC of Apache Kyuubi. IMO, the requirements could be discussed in the same thread. Could you please provide the standard to become a PMC?
> >
> > Best
> > Nicholas.
> >
> > On 2022/03/09 10:44:28 Kent Yao wrote:
> > > Thanks, Paul for the feedback. Updated according to your comments
> > >
> > >
> > > ===============================
> > >
> > > # Become A Committer of Apache Kyuubi
> > >
> > > Anyone being supportive of the community and working in any of the
> > > CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> > > acronym from ASF to describe how we recognize your contributions not
> > > only by code.
> > >
> > > - **Co**mmunity - You can join us via our mailing list, issue
> > > trackers, discussions page to interact with community members, and
> > > share vision and knowledge
> > > - **P**roject - a clear vision and consensus are needed
> > > - **Do**cumentation - without it, the stuff remains only in the minds
> > > of the authors
> > > - **C**ode - discussion goes nowhere without code
> > >
> > > Apache Kyuubi community strives to be meritocratic. Thus, once someone
> > > has contributed sufficiently to any area of CoPDoC they can be a
> > > candidate for committer-ship and at last voted in as a Kyuubi
> > > committer. Being an Apache Kyuubi committer does not necessarily mean
> > > you must commit code with your commit privilege to the codebase; it
> > > means you are committed to the Kyuubi project and are productively
> > > contributing to our community's success.
> > >
> > > ## Committer Requirements:
> > >
> > > There are no strict rules for becoming a committer or PMC member.
> > > Candidates for new committers are typically people that are active
> > > contributors and community members. Anyway, if the rules can be
> > > clarified a little bit, it can somehow clear the doubts in the minds
> > > of contributors and make the community more transparent, reasonable,
> > > and fair.
> > >
> > > ### Continuous contributions
> > >
> > > Committer candidates should have a decent amount of continuous
> > > engagements and contributions (fixing bugs, adding new features,
> > > writing documentation, maintaining issues boards, code review, or answering
> > > community questions) to Kyuubi either by contributing to the codebase
> > > of the main website or Kyuubi's GitHub repositories
> > >
> > > - +3 months with light activity and engagement.
> > > - +2 months of medium activity and engagement.
> > > - +1 month with solid activity and engagement.
> > >
> > > ### Quality of contributions
> > > - A solid general understanding of the project
> > > - Well tested, well-designed, following Apache Kyuubi coding
> > > standards, and simple patches.
> > > - Well-organized and detailed user-oriented documentation.
> > >
> > > ### Community involvement
> > >
> > > - Be active, courteous, and respectful on the dev mailing list and
> > > help mentor newer contributors
> > > and users.
> > > - Be active, courteous, and respectful on the issue tracker for
> > > project maintenance
> > > - Be active, courteous, and respectful for pull requests reviewing
> > > - Be involved in the design road map discussions with a professional
> > > and diplomatic approach even if there is a disagreement
> > >
> > >
> > > ===============================
> > >
> > >
> > > Paul Lam <pa...@gmail.com> 于2022年3月9日周三 18:16写道：
> > > >
> > > > Hi Kent,
> > > >
> > > > The commuter guide is very informative and LGTM in general.
> > > >
> > > > I see two minor possible improvements:
> > > >
> > > > 1. code review could be listed as one of the contributions
> > > > 2. “the codebase of main or website GitHub repositories" -> “the codebase of the main website or Kyuubi's GitHub repositories"
> > > >
> > > > Best,
> > > > Paul Lam
> > > >
> > > > > 2022年3月9日 17:39，LuNing Wang <wa...@gmail.com> 写道：
> > > > >
> > > > > Hi, I second with all the requirements above mentioned. Best, LuNing Wang
> > > > > 王鲁宁
> > > > >
> > > > > Nicholas Jiang <ni...@apache.org> 于2022年3月9日周三 17:17写道：
> > > > >
> > > > >> Hi Kent,
> > > > >>
> > > > >>   Thanks for starting the discussion thread about committer requirements.
> > > > >> IMO, the community is more than code. The committer need to have much
> > > > >> contribution like code, document, review and feature design and have an
> > > > >> excellent knowledge of the centain module in Kyuubi. In general, the
> > > > >> requirements make sense to me. I agree with all the requirements above
> > > > >> mentioned.
> > > > >>
> > > > >> Best,
> > > > >> Nicholas Jiang
> > > > >>
> > > > >> On 2022/03/09 08:23:19 Kent Yao wrote:
> > > > >>> Hello PPMC and community,
> > > > >>>
> > > > >>> In this thread, I want to discuss our committer requirements for
> > > > >>> contributors that are willing to move from contributors to committers.
> > > > >>>
> > > > >>> Hope to build a consensus with the following proposal.
> > > > >>>
> > > > >>> ===============================
> > > > >>>
> > > > >>> # Become A Committer of Apache Kyuubi
> > > > >>>
> > > > >>> Anyone being supportive of the community and working in any of the
> > > > >>> CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> > > > >>> acronym from ASF to describe how we recognize your contributions not
> > > > >>> only but code.
> > > > >>>
> > > > >>> - **Co**mmunity - You can join us via our mailing list, issue
> > > > >>> trackers, discussions page to interact with community members, and
> > > > >>> share vision and knowledge
> > > > >>> - **P**roject - a clear vision and consensus are needed
> > > > >>> - **Do**cumentation - without it, the stuff remains only in the minds
> > > > >>> of the authors
> > > > >>> - **C**ode - discussion goes nowhere without code
> > > > >>>
> > > > >>> Apache Kyuubi community strives to be meritocratic. Thus, once someone
> > > > >>> has contributed sufficiently to any area of CoPDoC they can be a
> > > > >>> candidate for committer-ship and at last, voted in as a Kyuubi
> > > > >>> committer. Being an Apache Kyuubi committer does not necessarily mean
> > > > >>> you must commit code with your commit privilege to the codebase; it
> > > > >>> means you are committed to the Kyuubi project and are productively
> > > > >>> contributing to our community's success.
> > > > >>>
> > > > >>> ## Committer Requirements:
> > > > >>>
> > > > >>> There are no strict rules for becoming a committer or PMC member.
> > > > >>> Candidates for new committers are typically people that are active
> > > > >>> contributors and community members. Anyway, if the rules can be
> > > > >>> clarified a little bit, it can somehow clear the doubts in the minds
> > > > >>> of contributors and make the community more transparent, reasonable,
> > > > >>> and fair.
> > > > >>>
> > > > >>> ### Continuous contributions
> > > > >>>
> > > > >>> Committer candidates should have a decent amount of continuous
> > > > >>> engagements and contributions (fixing bugs, adding new features,
> > > > >>> writing documentation, maintaining issues boards, or answering
> > > > >>> community questions) to Kyuubi either by contributing to the codebase
> > > > >>> of main or website GitHub repositories.
> > > > >>> - +3 months with light activity and engagement.
> > > > >>> - +2 months of medium activity and engagement.
> > > > >>> - +1 month with solid activity and engagement.
> > > > >>>
> > > > >>> ### Quality of contributions
> > > > >>>
> > > > >>> - Well tested, well-designed, following Apache Kyuubi coding
> > > > >>> standards, and simple patches.
> > > > >>> - Well-organized and detailed user-oriented documentation.
> > > > >>>
> > > > >>> ### Community involvement
> > > > >>>
> > > > >>> - Be active on the dev mailing list and help mentor newer contributors
> > > > >>> and users.
> > > > >>> - Be active on the issue tracker for project maintenance
> > > > >>> - Be involved in the design road map discussions with a professional
> > > > >>> and diplomatic approach even if there is a disagreement
> > > > >>>
> > > > >>>
> > > > >>> ===============================
> > > > >>>
> > > > >>> Thank you for all your feedback and time. If there are no strong
> > > > >>> objections, I will put this on our website.
> > > > >>>
> > > > >>> BR,
> > > > >>>
> > > > >>> Kent Yao
> > > > >>>
> > > > >>
> > > >
> > >

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Kent Yao <ya...@apache.org>.

 Hi Nicholas,

Thanks for pointing those out.

The section here ' Become A Committer of Apache Kyuubi' is one part
that I raised in this thread for a community consensus.

 The full-page on our website will cover all Apache Roles. It will include

- Become A User of Apache Kyuubi
- Become A Contributor of Apache Kyuubi
- Become A Committer of Apache Kyuubi
- Become A PPMC of Apache Kyuubi
- Become A Member of Apache Kyuubi


The contributions will be mainly detailed in the section `Become A
Contributor of Apache Kyuubi`,
We'll try to list them as thoroughly as we can, but not exhaustive.

About the requirements for being a committer, as I described above,
they are not strict rules that we shall follow blindly
, but general instructions help us to reduce our differences and
doubts to some extent.

Also for PPMC, committers may also be invited to be part of PPMC,
ensuring the project’s vitality if they are willing to
help the community grow after becoming a committer. All the rules
listed, I think, still apply not strictly.

BR,

Kent Yao

Cheng Pan <pa...@gmail.com> 于2022年3月9日周三 19:28写道：
>
> Thanks Kent for driving this, overall looks good to me, one question,
> as Kyuubi is still in the podling phase, should we replace "PMC
> member" by "PPMC member"?
>
> Thanks,
> Cheng Pan
>
> On Wed, Mar 9, 2022 at 7:24 PM Nicholas Jiang <ni...@apache.org> wrote:
> >
> > Hi Kent,
> >
> >    About the contribution, does the contribution include the practical articles in the company and technical Q&A?
> >
> >    What's more, I have a question about the requirements for becoming a PMC of Apache Kyuubi. IMO, the requirements could be discussed in the same thread. Could you please provide the standard to become a PMC?
> >
> > Best
> > Nicholas.
> >
> > On 2022/03/09 10:44:28 Kent Yao wrote:
> > > Thanks, Paul for the feedback. Updated according to your comments
> > >
> > >
> > > ===============================
> > >
> > > # Become A Committer of Apache Kyuubi
> > >
> > > Anyone being supportive of the community and working in any of the
> > > CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> > > acronym from ASF to describe how we recognize your contributions not
> > > only by code.
> > >
> > > - **Co**mmunity - You can join us via our mailing list, issue
> > > trackers, discussions page to interact with community members, and
> > > share vision and knowledge
> > > - **P**roject - a clear vision and consensus are needed
> > > - **Do**cumentation - without it, the stuff remains only in the minds
> > > of the authors
> > > - **C**ode - discussion goes nowhere without code
> > >
> > > Apache Kyuubi community strives to be meritocratic. Thus, once someone
> > > has contributed sufficiently to any area of CoPDoC they can be a
> > > candidate for committer-ship and at last voted in as a Kyuubi
> > > committer. Being an Apache Kyuubi committer does not necessarily mean
> > > you must commit code with your commit privilege to the codebase; it
> > > means you are committed to the Kyuubi project and are productively
> > > contributing to our community's success.
> > >
> > > ## Committer Requirements:
> > >
> > > There are no strict rules for becoming a committer or PMC member.
> > > Candidates for new committers are typically people that are active
> > > contributors and community members. Anyway, if the rules can be
> > > clarified a little bit, it can somehow clear the doubts in the minds
> > > of contributors and make the community more transparent, reasonable,
> > > and fair.
> > >
> > > ### Continuous contributions
> > >
> > > Committer candidates should have a decent amount of continuous
> > > engagements and contributions (fixing bugs, adding new features,
> > > writing documentation, maintaining issues boards, code review, or answering
> > > community questions) to Kyuubi either by contributing to the codebase
> > > of the main website or Kyuubi's GitHub repositories
> > >
> > > - +3 months with light activity and engagement.
> > > - +2 months of medium activity and engagement.
> > > - +1 month with solid activity and engagement.
> > >
> > > ### Quality of contributions
> > > - A solid general understanding of the project
> > > - Well tested, well-designed, following Apache Kyuubi coding
> > > standards, and simple patches.
> > > - Well-organized and detailed user-oriented documentation.
> > >
> > > ### Community involvement
> > >
> > > - Be active, courteous, and respectful on the dev mailing list and
> > > help mentor newer contributors
> > > and users.
> > > - Be active, courteous, and respectful on the issue tracker for
> > > project maintenance
> > > - Be active, courteous, and respectful for pull requests reviewing
> > > - Be involved in the design road map discussions with a professional
> > > and diplomatic approach even if there is a disagreement
> > >
> > >
> > > ===============================
> > >
> > >
> > > Paul Lam <pa...@gmail.com> 于2022年3月9日周三 18:16写道：
> > > >
> > > > Hi Kent,
> > > >
> > > > The commuter guide is very informative and LGTM in general.
> > > >
> > > > I see two minor possible improvements:
> > > >
> > > > 1. code review could be listed as one of the contributions
> > > > 2. “the codebase of main or website GitHub repositories" -> “the codebase of the main website or Kyuubi's GitHub repositories"
> > > >
> > > > Best,
> > > > Paul Lam
> > > >
> > > > > 2022年3月9日 17:39，LuNing Wang <wa...@gmail.com> 写道：
> > > > >
> > > > > Hi, I second with all the requirements above mentioned. Best, LuNing Wang
> > > > > 王鲁宁
> > > > >
> > > > > Nicholas Jiang <ni...@apache.org> 于2022年3月9日周三 17:17写道：
> > > > >
> > > > >> Hi Kent,
> > > > >>
> > > > >>   Thanks for starting the discussion thread about committer requirements.
> > > > >> IMO, the community is more than code. The committer need to have much
> > > > >> contribution like code, document, review and feature design and have an
> > > > >> excellent knowledge of the centain module in Kyuubi. In general, the
> > > > >> requirements make sense to me. I agree with all the requirements above
> > > > >> mentioned.
> > > > >>
> > > > >> Best,
> > > > >> Nicholas Jiang
> > > > >>
> > > > >> On 2022/03/09 08:23:19 Kent Yao wrote:
> > > > >>> Hello PPMC and community,
> > > > >>>
> > > > >>> In this thread, I want to discuss our committer requirements for
> > > > >>> contributors that are willing to move from contributors to committers.
> > > > >>>
> > > > >>> Hope to build a consensus with the following proposal.
> > > > >>>
> > > > >>> ===============================
> > > > >>>
> > > > >>> # Become A Committer of Apache Kyuubi
> > > > >>>
> > > > >>> Anyone being supportive of the community and working in any of the
> > > > >>> CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> > > > >>> acronym from ASF to describe how we recognize your contributions not
> > > > >>> only but code.
> > > > >>>
> > > > >>> - **Co**mmunity - You can join us via our mailing list, issue
> > > > >>> trackers, discussions page to interact with community members, and
> > > > >>> share vision and knowledge
> > > > >>> - **P**roject - a clear vision and consensus are needed
> > > > >>> - **Do**cumentation - without it, the stuff remains only in the minds
> > > > >>> of the authors
> > > > >>> - **C**ode - discussion goes nowhere without code
> > > > >>>
> > > > >>> Apache Kyuubi community strives to be meritocratic. Thus, once someone
> > > > >>> has contributed sufficiently to any area of CoPDoC they can be a
> > > > >>> candidate for committer-ship and at last, voted in as a Kyuubi
> > > > >>> committer. Being an Apache Kyuubi committer does not necessarily mean
> > > > >>> you must commit code with your commit privilege to the codebase; it
> > > > >>> means you are committed to the Kyuubi project and are productively
> > > > >>> contributing to our community's success.
> > > > >>>
> > > > >>> ## Committer Requirements:
> > > > >>>
> > > > >>> There are no strict rules for becoming a committer or PMC member.
> > > > >>> Candidates for new committers are typically people that are active
> > > > >>> contributors and community members. Anyway, if the rules can be
> > > > >>> clarified a little bit, it can somehow clear the doubts in the minds
> > > > >>> of contributors and make the community more transparent, reasonable,
> > > > >>> and fair.
> > > > >>>
> > > > >>> ### Continuous contributions
> > > > >>>
> > > > >>> Committer candidates should have a decent amount of continuous
> > > > >>> engagements and contributions (fixing bugs, adding new features,
> > > > >>> writing documentation, maintaining issues boards, or answering
> > > > >>> community questions) to Kyuubi either by contributing to the codebase
> > > > >>> of main or website GitHub repositories.
> > > > >>> - +3 months with light activity and engagement.
> > > > >>> - +2 months of medium activity and engagement.
> > > > >>> - +1 month with solid activity and engagement.
> > > > >>>
> > > > >>> ### Quality of contributions
> > > > >>>
> > > > >>> - Well tested, well-designed, following Apache Kyuubi coding
> > > > >>> standards, and simple patches.
> > > > >>> - Well-organized and detailed user-oriented documentation.
> > > > >>>
> > > > >>> ### Community involvement
> > > > >>>
> > > > >>> - Be active on the dev mailing list and help mentor newer contributors
> > > > >>> and users.
> > > > >>> - Be active on the issue tracker for project maintenance
> > > > >>> - Be involved in the design road map discussions with a professional
> > > > >>> and diplomatic approach even if there is a disagreement
> > > > >>>
> > > > >>>
> > > > >>> ===============================
> > > > >>>
> > > > >>> Thank you for all your feedback and time. If there are no strong
> > > > >>> objections, I will put this on our website.
> > > > >>>
> > > > >>> BR,
> > > > >>>
> > > > >>> Kent Yao
> > > > >>>
> > > > >>
> > > >
> > >

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Cheng Pan <pa...@gmail.com>.

Thanks Kent for driving this, overall looks good to me, one question,
as Kyuubi is still in the podling phase, should we replace "PMC
member" by "PPMC member"?

Thanks,
Cheng Pan

On Wed, Mar 9, 2022 at 7:24 PM Nicholas Jiang <ni...@apache.org> wrote:
>
> Hi Kent,
>
>    About the contribution, does the contribution include the practical articles in the company and technical Q&A?
>
>    What's more, I have a question about the requirements for becoming a PMC of Apache Kyuubi. IMO, the requirements could be discussed in the same thread. Could you please provide the standard to become a PMC?
>
> Best
> Nicholas.
>
> On 2022/03/09 10:44:28 Kent Yao wrote:
> > Thanks, Paul for the feedback. Updated according to your comments
> >
> >
> > ===============================
> >
> > # Become A Committer of Apache Kyuubi
> >
> > Anyone being supportive of the community and working in any of the
> > CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> > acronym from ASF to describe how we recognize your contributions not
> > only by code.
> >
> > - **Co**mmunity - You can join us via our mailing list, issue
> > trackers, discussions page to interact with community members, and
> > share vision and knowledge
> > - **P**roject - a clear vision and consensus are needed
> > - **Do**cumentation - without it, the stuff remains only in the minds
> > of the authors
> > - **C**ode - discussion goes nowhere without code
> >
> > Apache Kyuubi community strives to be meritocratic. Thus, once someone
> > has contributed sufficiently to any area of CoPDoC they can be a
> > candidate for committer-ship and at last voted in as a Kyuubi
> > committer. Being an Apache Kyuubi committer does not necessarily mean
> > you must commit code with your commit privilege to the codebase; it
> > means you are committed to the Kyuubi project and are productively
> > contributing to our community's success.
> >
> > ## Committer Requirements:
> >
> > There are no strict rules for becoming a committer or PMC member.
> > Candidates for new committers are typically people that are active
> > contributors and community members. Anyway, if the rules can be
> > clarified a little bit, it can somehow clear the doubts in the minds
> > of contributors and make the community more transparent, reasonable,
> > and fair.
> >
> > ### Continuous contributions
> >
> > Committer candidates should have a decent amount of continuous
> > engagements and contributions (fixing bugs, adding new features,
> > writing documentation, maintaining issues boards, code review, or answering
> > community questions) to Kyuubi either by contributing to the codebase
> > of the main website or Kyuubi's GitHub repositories
> >
> > - +3 months with light activity and engagement.
> > - +2 months of medium activity and engagement.
> > - +1 month with solid activity and engagement.
> >
> > ### Quality of contributions
> > - A solid general understanding of the project
> > - Well tested, well-designed, following Apache Kyuubi coding
> > standards, and simple patches.
> > - Well-organized and detailed user-oriented documentation.
> >
> > ### Community involvement
> >
> > - Be active, courteous, and respectful on the dev mailing list and
> > help mentor newer contributors
> > and users.
> > - Be active, courteous, and respectful on the issue tracker for
> > project maintenance
> > - Be active, courteous, and respectful for pull requests reviewing
> > - Be involved in the design road map discussions with a professional
> > and diplomatic approach even if there is a disagreement
> >
> >
> > ===============================
> >
> >
> > Paul Lam <pa...@gmail.com> 于2022年3月9日周三 18:16写道：
> > >
> > > Hi Kent,
> > >
> > > The commuter guide is very informative and LGTM in general.
> > >
> > > I see two minor possible improvements:
> > >
> > > 1. code review could be listed as one of the contributions
> > > 2. “the codebase of main or website GitHub repositories" -> “the codebase of the main website or Kyuubi's GitHub repositories"
> > >
> > > Best,
> > > Paul Lam
> > >
> > > > 2022年3月9日 17:39，LuNing Wang <wa...@gmail.com> 写道：
> > > >
> > > > Hi, I second with all the requirements above mentioned. Best, LuNing Wang
> > > > 王鲁宁
> > > >
> > > > Nicholas Jiang <ni...@apache.org> 于2022年3月9日周三 17:17写道：
> > > >
> > > >> Hi Kent,
> > > >>
> > > >>   Thanks for starting the discussion thread about committer requirements.
> > > >> IMO, the community is more than code. The committer need to have much
> > > >> contribution like code, document, review and feature design and have an
> > > >> excellent knowledge of the centain module in Kyuubi. In general, the
> > > >> requirements make sense to me. I agree with all the requirements above
> > > >> mentioned.
> > > >>
> > > >> Best,
> > > >> Nicholas Jiang
> > > >>
> > > >> On 2022/03/09 08:23:19 Kent Yao wrote:
> > > >>> Hello PPMC and community,
> > > >>>
> > > >>> In this thread, I want to discuss our committer requirements for
> > > >>> contributors that are willing to move from contributors to committers.
> > > >>>
> > > >>> Hope to build a consensus with the following proposal.
> > > >>>
> > > >>> ===============================
> > > >>>
> > > >>> # Become A Committer of Apache Kyuubi
> > > >>>
> > > >>> Anyone being supportive of the community and working in any of the
> > > >>> CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> > > >>> acronym from ASF to describe how we recognize your contributions not
> > > >>> only but code.
> > > >>>
> > > >>> - **Co**mmunity - You can join us via our mailing list, issue
> > > >>> trackers, discussions page to interact with community members, and
> > > >>> share vision and knowledge
> > > >>> - **P**roject - a clear vision and consensus are needed
> > > >>> - **Do**cumentation - without it, the stuff remains only in the minds
> > > >>> of the authors
> > > >>> - **C**ode - discussion goes nowhere without code
> > > >>>
> > > >>> Apache Kyuubi community strives to be meritocratic. Thus, once someone
> > > >>> has contributed sufficiently to any area of CoPDoC they can be a
> > > >>> candidate for committer-ship and at last, voted in as a Kyuubi
> > > >>> committer. Being an Apache Kyuubi committer does not necessarily mean
> > > >>> you must commit code with your commit privilege to the codebase; it
> > > >>> means you are committed to the Kyuubi project and are productively
> > > >>> contributing to our community's success.
> > > >>>
> > > >>> ## Committer Requirements:
> > > >>>
> > > >>> There are no strict rules for becoming a committer or PMC member.
> > > >>> Candidates for new committers are typically people that are active
> > > >>> contributors and community members. Anyway, if the rules can be
> > > >>> clarified a little bit, it can somehow clear the doubts in the minds
> > > >>> of contributors and make the community more transparent, reasonable,
> > > >>> and fair.
> > > >>>
> > > >>> ### Continuous contributions
> > > >>>
> > > >>> Committer candidates should have a decent amount of continuous
> > > >>> engagements and contributions (fixing bugs, adding new features,
> > > >>> writing documentation, maintaining issues boards, or answering
> > > >>> community questions) to Kyuubi either by contributing to the codebase
> > > >>> of main or website GitHub repositories.
> > > >>> - +3 months with light activity and engagement.
> > > >>> - +2 months of medium activity and engagement.
> > > >>> - +1 month with solid activity and engagement.
> > > >>>
> > > >>> ### Quality of contributions
> > > >>>
> > > >>> - Well tested, well-designed, following Apache Kyuubi coding
> > > >>> standards, and simple patches.
> > > >>> - Well-organized and detailed user-oriented documentation.
> > > >>>
> > > >>> ### Community involvement
> > > >>>
> > > >>> - Be active on the dev mailing list and help mentor newer contributors
> > > >>> and users.
> > > >>> - Be active on the issue tracker for project maintenance
> > > >>> - Be involved in the design road map discussions with a professional
> > > >>> and diplomatic approach even if there is a disagreement
> > > >>>
> > > >>>
> > > >>> ===============================
> > > >>>
> > > >>> Thank you for all your feedback and time. If there are no strong
> > > >>> objections, I will put this on our website.
> > > >>>
> > > >>> BR,
> > > >>>
> > > >>> Kent Yao
> > > >>>
> > > >>
> > >
> >

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Nicholas Jiang <ni...@apache.org>.

Hi Kent,
    
   About the contribution, does the contribution include the practical articles in the company and technical Q&A?   

   What's more, I have a question about the requirements for becoming a PMC of Apache Kyuubi. IMO, the requirements could be discussed in the same thread. Could you please provide the standard to become a PMC?

Best
Nicholas.

On 2022/03/09 10:44:28 Kent Yao wrote:
> Thanks, Paul for the feedback. Updated according to your comments
> 
> 
> ===============================
> 
> # Become A Committer of Apache Kyuubi
> 
> Anyone being supportive of the community and working in any of the
> CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> acronym from ASF to describe how we recognize your contributions not
> only by code.
> 
> - **Co**mmunity - You can join us via our mailing list, issue
> trackers, discussions page to interact with community members, and
> share vision and knowledge
> - **P**roject - a clear vision and consensus are needed
> - **Do**cumentation - without it, the stuff remains only in the minds
> of the authors
> - **C**ode - discussion goes nowhere without code
> 
> Apache Kyuubi community strives to be meritocratic. Thus, once someone
> has contributed sufficiently to any area of CoPDoC they can be a
> candidate for committer-ship and at last voted in as a Kyuubi
> committer. Being an Apache Kyuubi committer does not necessarily mean
> you must commit code with your commit privilege to the codebase; it
> means you are committed to the Kyuubi project and are productively
> contributing to our community's success.
> 
> ## Committer Requirements:
> 
> There are no strict rules for becoming a committer or PMC member.
> Candidates for new committers are typically people that are active
> contributors and community members. Anyway, if the rules can be
> clarified a little bit, it can somehow clear the doubts in the minds
> of contributors and make the community more transparent, reasonable,
> and fair.
> 
> ### Continuous contributions
> 
> Committer candidates should have a decent amount of continuous
> engagements and contributions (fixing bugs, adding new features,
> writing documentation, maintaining issues boards, code review, or answering
> community questions) to Kyuubi either by contributing to the codebase
> of the main website or Kyuubi's GitHub repositories
> 
> - +3 months with light activity and engagement.
> - +2 months of medium activity and engagement.
> - +1 month with solid activity and engagement.
> 
> ### Quality of contributions
> - A solid general understanding of the project
> - Well tested, well-designed, following Apache Kyuubi coding
> standards, and simple patches.
> - Well-organized and detailed user-oriented documentation.
> 
> ### Community involvement
> 
> - Be active, courteous, and respectful on the dev mailing list and
> help mentor newer contributors
> and users.
> - Be active, courteous, and respectful on the issue tracker for
> project maintenance
> - Be active, courteous, and respectful for pull requests reviewing
> - Be involved in the design road map discussions with a professional
> and diplomatic approach even if there is a disagreement
> 
> 
> ===============================
> 
> 
> Paul Lam <pa...@gmail.com> 于2022年3月9日周三 18:16写道：
> >
> > Hi Kent,
> >
> > The commuter guide is very informative and LGTM in general.
> >
> > I see two minor possible improvements:
> >
> > 1. code review could be listed as one of the contributions
> > 2. “the codebase of main or website GitHub repositories" -> “the codebase of the main website or Kyuubi's GitHub repositories"
> >
> > Best,
> > Paul Lam
> >
> > > 2022年3月9日 17:39，LuNing Wang <wa...@gmail.com> 写道：
> > >
> > > Hi, I second with all the requirements above mentioned. Best, LuNing Wang
> > > 王鲁宁
> > >
> > > Nicholas Jiang <ni...@apache.org> 于2022年3月9日周三 17:17写道：
> > >
> > >> Hi Kent,
> > >>
> > >>   Thanks for starting the discussion thread about committer requirements.
> > >> IMO, the community is more than code. The committer need to have much
> > >> contribution like code, document, review and feature design and have an
> > >> excellent knowledge of the centain module in Kyuubi. In general, the
> > >> requirements make sense to me. I agree with all the requirements above
> > >> mentioned.
> > >>
> > >> Best,
> > >> Nicholas Jiang
> > >>
> > >> On 2022/03/09 08:23:19 Kent Yao wrote:
> > >>> Hello PPMC and community,
> > >>>
> > >>> In this thread, I want to discuss our committer requirements for
> > >>> contributors that are willing to move from contributors to committers.
> > >>>
> > >>> Hope to build a consensus with the following proposal.
> > >>>
> > >>> ===============================
> > >>>
> > >>> # Become A Committer of Apache Kyuubi
> > >>>
> > >>> Anyone being supportive of the community and working in any of the
> > >>> CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> > >>> acronym from ASF to describe how we recognize your contributions not
> > >>> only but code.
> > >>>
> > >>> - **Co**mmunity - You can join us via our mailing list, issue
> > >>> trackers, discussions page to interact with community members, and
> > >>> share vision and knowledge
> > >>> - **P**roject - a clear vision and consensus are needed
> > >>> - **Do**cumentation - without it, the stuff remains only in the minds
> > >>> of the authors
> > >>> - **C**ode - discussion goes nowhere without code
> > >>>
> > >>> Apache Kyuubi community strives to be meritocratic. Thus, once someone
> > >>> has contributed sufficiently to any area of CoPDoC they can be a
> > >>> candidate for committer-ship and at last, voted in as a Kyuubi
> > >>> committer. Being an Apache Kyuubi committer does not necessarily mean
> > >>> you must commit code with your commit privilege to the codebase; it
> > >>> means you are committed to the Kyuubi project and are productively
> > >>> contributing to our community's success.
> > >>>
> > >>> ## Committer Requirements:
> > >>>
> > >>> There are no strict rules for becoming a committer or PMC member.
> > >>> Candidates for new committers are typically people that are active
> > >>> contributors and community members. Anyway, if the rules can be
> > >>> clarified a little bit, it can somehow clear the doubts in the minds
> > >>> of contributors and make the community more transparent, reasonable,
> > >>> and fair.
> > >>>
> > >>> ### Continuous contributions
> > >>>
> > >>> Committer candidates should have a decent amount of continuous
> > >>> engagements and contributions (fixing bugs, adding new features,
> > >>> writing documentation, maintaining issues boards, or answering
> > >>> community questions) to Kyuubi either by contributing to the codebase
> > >>> of main or website GitHub repositories.
> > >>> - +3 months with light activity and engagement.
> > >>> - +2 months of medium activity and engagement.
> > >>> - +1 month with solid activity and engagement.
> > >>>
> > >>> ### Quality of contributions
> > >>>
> > >>> - Well tested, well-designed, following Apache Kyuubi coding
> > >>> standards, and simple patches.
> > >>> - Well-organized and detailed user-oriented documentation.
> > >>>
> > >>> ### Community involvement
> > >>>
> > >>> - Be active on the dev mailing list and help mentor newer contributors
> > >>> and users.
> > >>> - Be active on the issue tracker for project maintenance
> > >>> - Be involved in the design road map discussions with a professional
> > >>> and diplomatic approach even if there is a disagreement
> > >>>
> > >>>
> > >>> ===============================
> > >>>
> > >>> Thank you for all your feedback and time. If there are no strong
> > >>> objections, I will put this on our website.
> > >>>
> > >>> BR,
> > >>>
> > >>> Kent Yao
> > >>>
> > >>
> >
>

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Kent Yao <ya...@apache.org>.

Thanks, Paul for the feedback. Updated according to your comments


===============================

# Become A Committer of Apache Kyuubi

Anyone being supportive of the community and working in any of the
CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
acronym from ASF to describe how we recognize your contributions not
only by code.

- **Co**mmunity - You can join us via our mailing list, issue
trackers, discussions page to interact with community members, and
share vision and knowledge
- **P**roject - a clear vision and consensus are needed
- **Do**cumentation - without it, the stuff remains only in the minds
of the authors
- **C**ode - discussion goes nowhere without code

Apache Kyuubi community strives to be meritocratic. Thus, once someone
has contributed sufficiently to any area of CoPDoC they can be a
candidate for committer-ship and at last voted in as a Kyuubi
committer. Being an Apache Kyuubi committer does not necessarily mean
you must commit code with your commit privilege to the codebase; it
means you are committed to the Kyuubi project and are productively
contributing to our community's success.

## Committer Requirements:

There are no strict rules for becoming a committer or PMC member.
Candidates for new committers are typically people that are active
contributors and community members. Anyway, if the rules can be
clarified a little bit, it can somehow clear the doubts in the minds
of contributors and make the community more transparent, reasonable,
and fair.

### Continuous contributions

Committer candidates should have a decent amount of continuous
engagements and contributions (fixing bugs, adding new features,
writing documentation, maintaining issues boards, code review, or answering
community questions) to Kyuubi either by contributing to the codebase
of the main website or Kyuubi's GitHub repositories

- +3 months with light activity and engagement.
- +2 months of medium activity and engagement.
- +1 month with solid activity and engagement.

### Quality of contributions
- A solid general understanding of the project
- Well tested, well-designed, following Apache Kyuubi coding
standards, and simple patches.
- Well-organized and detailed user-oriented documentation.

### Community involvement

- Be active, courteous, and respectful on the dev mailing list and
help mentor newer contributors
and users.
- Be active, courteous, and respectful on the issue tracker for
project maintenance
- Be active, courteous, and respectful for pull requests reviewing
- Be involved in the design road map discussions with a professional
and diplomatic approach even if there is a disagreement


===============================


Paul Lam <pa...@gmail.com> 于2022年3月9日周三 18:16写道：
>
> Hi Kent,
>
> The commuter guide is very informative and LGTM in general.
>
> I see two minor possible improvements:
>
> 1. code review could be listed as one of the contributions
> 2. “the codebase of main or website GitHub repositories" -> “the codebase of the main website or Kyuubi's GitHub repositories"
>
> Best,
> Paul Lam
>
> > 2022年3月9日 17:39，LuNing Wang <wa...@gmail.com> 写道：
> >
> > Hi, I second with all the requirements above mentioned. Best, LuNing Wang
> > 王鲁宁
> >
> > Nicholas Jiang <ni...@apache.org> 于2022年3月9日周三 17:17写道：
> >
> >> Hi Kent,
> >>
> >>   Thanks for starting the discussion thread about committer requirements.
> >> IMO, the community is more than code. The committer need to have much
> >> contribution like code, document, review and feature design and have an
> >> excellent knowledge of the centain module in Kyuubi. In general, the
> >> requirements make sense to me. I agree with all the requirements above
> >> mentioned.
> >>
> >> Best,
> >> Nicholas Jiang
> >>
> >> On 2022/03/09 08:23:19 Kent Yao wrote:
> >>> Hello PPMC and community,
> >>>
> >>> In this thread, I want to discuss our committer requirements for
> >>> contributors that are willing to move from contributors to committers.
> >>>
> >>> Hope to build a consensus with the following proposal.
> >>>
> >>> ===============================
> >>>
> >>> # Become A Committer of Apache Kyuubi
> >>>
> >>> Anyone being supportive of the community and working in any of the
> >>> CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> >>> acronym from ASF to describe how we recognize your contributions not
> >>> only but code.
> >>>
> >>> - **Co**mmunity - You can join us via our mailing list, issue
> >>> trackers, discussions page to interact with community members, and
> >>> share vision and knowledge
> >>> - **P**roject - a clear vision and consensus are needed
> >>> - **Do**cumentation - without it, the stuff remains only in the minds
> >>> of the authors
> >>> - **C**ode - discussion goes nowhere without code
> >>>
> >>> Apache Kyuubi community strives to be meritocratic. Thus, once someone
> >>> has contributed sufficiently to any area of CoPDoC they can be a
> >>> candidate for committer-ship and at last, voted in as a Kyuubi
> >>> committer. Being an Apache Kyuubi committer does not necessarily mean
> >>> you must commit code with your commit privilege to the codebase; it
> >>> means you are committed to the Kyuubi project and are productively
> >>> contributing to our community's success.
> >>>
> >>> ## Committer Requirements:
> >>>
> >>> There are no strict rules for becoming a committer or PMC member.
> >>> Candidates for new committers are typically people that are active
> >>> contributors and community members. Anyway, if the rules can be
> >>> clarified a little bit, it can somehow clear the doubts in the minds
> >>> of contributors and make the community more transparent, reasonable,
> >>> and fair.
> >>>
> >>> ### Continuous contributions
> >>>
> >>> Committer candidates should have a decent amount of continuous
> >>> engagements and contributions (fixing bugs, adding new features,
> >>> writing documentation, maintaining issues boards, or answering
> >>> community questions) to Kyuubi either by contributing to the codebase
> >>> of main or website GitHub repositories.
> >>> - +3 months with light activity and engagement.
> >>> - +2 months of medium activity and engagement.
> >>> - +1 month with solid activity and engagement.
> >>>
> >>> ### Quality of contributions
> >>>
> >>> - Well tested, well-designed, following Apache Kyuubi coding
> >>> standards, and simple patches.
> >>> - Well-organized and detailed user-oriented documentation.
> >>>
> >>> ### Community involvement
> >>>
> >>> - Be active on the dev mailing list and help mentor newer contributors
> >>> and users.
> >>> - Be active on the issue tracker for project maintenance
> >>> - Be involved in the design road map discussions with a professional
> >>> and diplomatic approach even if there is a disagreement
> >>>
> >>>
> >>> ===============================
> >>>
> >>> Thank you for all your feedback and time. If there are no strong
> >>> objections, I will put this on our website.
> >>>
> >>> BR,
> >>>
> >>> Kent Yao
> >>>
> >>
>

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Paul Lam <pa...@gmail.com>.

Hi Kent,

The commuter guide is very informative and LGTM in general.

I see two minor possible improvements:

1. code review could be listed as one of the contributions
2. “the codebase of main or website GitHub repositories" -> “the codebase of the main website or Kyuubi's GitHub repositories"

Best,
Paul Lam

> 2022年3月9日 17:39，LuNing Wang <wa...@gmail.com> 写道：
> 
> Hi, I second with all the requirements above mentioned. Best, LuNing Wang
> 王鲁宁
> 
> Nicholas Jiang <ni...@apache.org> 于2022年3月9日周三 17:17写道：
> 
>> Hi Kent,
>> 
>>   Thanks for starting the discussion thread about committer requirements.
>> IMO, the community is more than code. The committer need to have much
>> contribution like code, document, review and feature design and have an
>> excellent knowledge of the centain module in Kyuubi. In general, the
>> requirements make sense to me. I agree with all the requirements above
>> mentioned.
>> 
>> Best,
>> Nicholas Jiang
>> 
>> On 2022/03/09 08:23:19 Kent Yao wrote:
>>> Hello PPMC and community,
>>> 
>>> In this thread, I want to discuss our committer requirements for
>>> contributors that are willing to move from contributors to committers.
>>> 
>>> Hope to build a consensus with the following proposal.
>>> 
>>> ===============================
>>> 
>>> # Become A Committer of Apache Kyuubi
>>> 
>>> Anyone being supportive of the community and working in any of the
>>> CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
>>> acronym from ASF to describe how we recognize your contributions not
>>> only but code.
>>> 
>>> - **Co**mmunity - You can join us via our mailing list, issue
>>> trackers, discussions page to interact with community members, and
>>> share vision and knowledge
>>> - **P**roject - a clear vision and consensus are needed
>>> - **Do**cumentation - without it, the stuff remains only in the minds
>>> of the authors
>>> - **C**ode - discussion goes nowhere without code
>>> 
>>> Apache Kyuubi community strives to be meritocratic. Thus, once someone
>>> has contributed sufficiently to any area of CoPDoC they can be a
>>> candidate for committer-ship and at last, voted in as a Kyuubi
>>> committer. Being an Apache Kyuubi committer does not necessarily mean
>>> you must commit code with your commit privilege to the codebase; it
>>> means you are committed to the Kyuubi project and are productively
>>> contributing to our community's success.
>>> 
>>> ## Committer Requirements:
>>> 
>>> There are no strict rules for becoming a committer or PMC member.
>>> Candidates for new committers are typically people that are active
>>> contributors and community members. Anyway, if the rules can be
>>> clarified a little bit, it can somehow clear the doubts in the minds
>>> of contributors and make the community more transparent, reasonable,
>>> and fair.
>>> 
>>> ### Continuous contributions
>>> 
>>> Committer candidates should have a decent amount of continuous
>>> engagements and contributions (fixing bugs, adding new features,
>>> writing documentation, maintaining issues boards, or answering
>>> community questions) to Kyuubi either by contributing to the codebase
>>> of main or website GitHub repositories.
>>> - +3 months with light activity and engagement.
>>> - +2 months of medium activity and engagement.
>>> - +1 month with solid activity and engagement.
>>> 
>>> ### Quality of contributions
>>> 
>>> - Well tested, well-designed, following Apache Kyuubi coding
>>> standards, and simple patches.
>>> - Well-organized and detailed user-oriented documentation.
>>> 
>>> ### Community involvement
>>> 
>>> - Be active on the dev mailing list and help mentor newer contributors
>>> and users.
>>> - Be active on the issue tracker for project maintenance
>>> - Be involved in the design road map discussions with a professional
>>> and diplomatic approach even if there is a disagreement
>>> 
>>> 
>>> ===============================
>>> 
>>> Thank you for all your feedback and time. If there are no strong
>>> objections, I will put this on our website.
>>> 
>>> BR,
>>> 
>>> Kent Yao
>>> 
>>

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by XiDuo You <ul...@gmail.com>.

+1

thank you

LuNing Wang <wa...@gmail.com> 于2022年3月9日周三 17:40写道：
>
> Hi, I second with all the requirements above mentioned. Best, LuNing Wang
> 王鲁宁
>
> Nicholas Jiang <ni...@apache.org> 于2022年3月9日周三 17:17写道：
>
> > Hi Kent,
> >
> >    Thanks for starting the discussion thread about committer requirements.
> > IMO, the community is more than code. The committer need to have much
> > contribution like code, document, review and feature design and have an
> > excellent knowledge of the centain module in Kyuubi. In general, the
> > requirements make sense to me. I agree with all the requirements above
> > mentioned.
> >
> > Best,
> > Nicholas Jiang
> >
> > On 2022/03/09 08:23:19 Kent Yao wrote:
> > > Hello PPMC and community,
> > >
> > > In this thread, I want to discuss our committer requirements for
> > > contributors that are willing to move from contributors to committers.
> > >
> > > Hope to build a consensus with the following proposal.
> > >
> > > ===============================
> > >
> > > # Become A Committer of Apache Kyuubi
> > >
> > > Anyone being supportive of the community and working in any of the
> > > CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> > > acronym from ASF to describe how we recognize your contributions not
> > > only but code.
> > >
> > > - **Co**mmunity - You can join us via our mailing list, issue
> > > trackers, discussions page to interact with community members, and
> > > share vision and knowledge
> > > - **P**roject - a clear vision and consensus are needed
> > > - **Do**cumentation - without it, the stuff remains only in the minds
> > > of the authors
> > > - **C**ode - discussion goes nowhere without code
> > >
> > > Apache Kyuubi community strives to be meritocratic. Thus, once someone
> > > has contributed sufficiently to any area of CoPDoC they can be a
> > > candidate for committer-ship and at last, voted in as a Kyuubi
> > > committer. Being an Apache Kyuubi committer does not necessarily mean
> > > you must commit code with your commit privilege to the codebase; it
> > > means you are committed to the Kyuubi project and are productively
> > > contributing to our community's success.
> > >
> > > ## Committer Requirements:
> > >
> > > There are no strict rules for becoming a committer or PMC member.
> > > Candidates for new committers are typically people that are active
> > > contributors and community members. Anyway, if the rules can be
> > > clarified a little bit, it can somehow clear the doubts in the minds
> > > of contributors and make the community more transparent, reasonable,
> > > and fair.
> > >
> > > ### Continuous contributions
> > >
> > > Committer candidates should have a decent amount of continuous
> > > engagements and contributions (fixing bugs, adding new features,
> > > writing documentation, maintaining issues boards, or answering
> > > community questions) to Kyuubi either by contributing to the codebase
> > > of main or website GitHub repositories.
> > > - +3 months with light activity and engagement.
> > > - +2 months of medium activity and engagement.
> > > - +1 month with solid activity and engagement.
> > >
> > > ### Quality of contributions
> > >
> > > - Well tested, well-designed, following Apache Kyuubi coding
> > > standards, and simple patches.
> > > - Well-organized and detailed user-oriented documentation.
> > >
> > > ### Community involvement
> > >
> > > - Be active on the dev mailing list and help mentor newer contributors
> > > and users.
> > > - Be active on the issue tracker for project maintenance
> > > - Be involved in the design road map discussions with a professional
> > > and diplomatic approach even if there is a disagreement
> > >
> > >
> > > ===============================
> > >
> > > Thank you for all your feedback and time. If there are no strong
> > > objections, I will put this on our website.
> > >
> > > BR,
> > >
> > > Kent Yao
> > >
> >

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by LuNing Wang <wa...@gmail.com>.

Hi, I second with all the requirements above mentioned. Best, LuNing Wang
王鲁宁

Nicholas Jiang <ni...@apache.org> 于2022年3月9日周三 17:17写道：

> Hi Kent,
>
>    Thanks for starting the discussion thread about committer requirements.
> IMO, the community is more than code. The committer need to have much
> contribution like code, document, review and feature design and have an
> excellent knowledge of the centain module in Kyuubi. In general, the
> requirements make sense to me. I agree with all the requirements above
> mentioned.
>
> Best,
> Nicholas Jiang
>
> On 2022/03/09 08:23:19 Kent Yao wrote:
> > Hello PPMC and community,
> >
> > In this thread, I want to discuss our committer requirements for
> > contributors that are willing to move from contributors to committers.
> >
> > Hope to build a consensus with the following proposal.
> >
> > ===============================
> >
> > # Become A Committer of Apache Kyuubi
> >
> > Anyone being supportive of the community and working in any of the
> > CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> > acronym from ASF to describe how we recognize your contributions not
> > only but code.
> >
> > - **Co**mmunity - You can join us via our mailing list, issue
> > trackers, discussions page to interact with community members, and
> > share vision and knowledge
> > - **P**roject - a clear vision and consensus are needed
> > - **Do**cumentation - without it, the stuff remains only in the minds
> > of the authors
> > - **C**ode - discussion goes nowhere without code
> >
> > Apache Kyuubi community strives to be meritocratic. Thus, once someone
> > has contributed sufficiently to any area of CoPDoC they can be a
> > candidate for committer-ship and at last, voted in as a Kyuubi
> > committer. Being an Apache Kyuubi committer does not necessarily mean
> > you must commit code with your commit privilege to the codebase; it
> > means you are committed to the Kyuubi project and are productively
> > contributing to our community's success.
> >
> > ## Committer Requirements:
> >
> > There are no strict rules for becoming a committer or PMC member.
> > Candidates for new committers are typically people that are active
> > contributors and community members. Anyway, if the rules can be
> > clarified a little bit, it can somehow clear the doubts in the minds
> > of contributors and make the community more transparent, reasonable,
> > and fair.
> >
> > ### Continuous contributions
> >
> > Committer candidates should have a decent amount of continuous
> > engagements and contributions (fixing bugs, adding new features,
> > writing documentation, maintaining issues boards, or answering
> > community questions) to Kyuubi either by contributing to the codebase
> > of main or website GitHub repositories.
> > - +3 months with light activity and engagement.
> > - +2 months of medium activity and engagement.
> > - +1 month with solid activity and engagement.
> >
> > ### Quality of contributions
> >
> > - Well tested, well-designed, following Apache Kyuubi coding
> > standards, and simple patches.
> > - Well-organized and detailed user-oriented documentation.
> >
> > ### Community involvement
> >
> > - Be active on the dev mailing list and help mentor newer contributors
> > and users.
> > - Be active on the issue tracker for project maintenance
> > - Be involved in the design road map discussions with a professional
> > and diplomatic approach even if there is a disagreement
> >
> >
> > ===============================
> >
> > Thank you for all your feedback and time. If there are no strong
> > objections, I will put this on our website.
> >
> > BR,
> >
> > Kent Yao
> >
>

Re: [DISCUSS] Become A Committer of Apache Kyuubi

Posted by Nicholas Jiang <ni...@apache.org>.

Hi Kent,

   Thanks for starting the discussion thread about committer requirements. IMO, the community is more than code. The committer need to have much contribution like code, document, review and feature design and have an excellent knowledge of the centain module in Kyuubi. In general, the requirements make sense to me. I agree with all the requirements above mentioned.

Best,
Nicholas Jiang

On 2022/03/09 08:23:19 Kent Yao wrote:
> Hello PPMC and community,
> 
> In this thread, I want to discuss our committer requirements for
> contributors that are willing to move from contributors to committers.
> 
> Hope to build a consensus with the following proposal.
> 
> ===============================
> 
> # Become A Committer of Apache Kyuubi
> 
> Anyone being supportive of the community and working in any of the
> CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
> acronym from ASF to describe how we recognize your contributions not
> only but code.
> 
> - **Co**mmunity - You can join us via our mailing list, issue
> trackers, discussions page to interact with community members, and
> share vision and knowledge
> - **P**roject - a clear vision and consensus are needed
> - **Do**cumentation - without it, the stuff remains only in the minds
> of the authors
> - **C**ode - discussion goes nowhere without code
> 
> Apache Kyuubi community strives to be meritocratic. Thus, once someone
> has contributed sufficiently to any area of CoPDoC they can be a
> candidate for committer-ship and at last, voted in as a Kyuubi
> committer. Being an Apache Kyuubi committer does not necessarily mean
> you must commit code with your commit privilege to the codebase; it
> means you are committed to the Kyuubi project and are productively
> contributing to our community's success.
> 
> ## Committer Requirements:
> 
> There are no strict rules for becoming a committer or PMC member.
> Candidates for new committers are typically people that are active
> contributors and community members. Anyway, if the rules can be
> clarified a little bit, it can somehow clear the doubts in the minds
> of contributors and make the community more transparent, reasonable,
> and fair.
> 
> ### Continuous contributions
> 
> Committer candidates should have a decent amount of continuous
> engagements and contributions (fixing bugs, adding new features,
> writing documentation, maintaining issues boards, or answering
> community questions) to Kyuubi either by contributing to the codebase
> of main or website GitHub repositories.
> - +3 months with light activity and engagement.
> - +2 months of medium activity and engagement.
> - +1 month with solid activity and engagement.
> 
> ### Quality of contributions
> 
> - Well tested, well-designed, following Apache Kyuubi coding
> standards, and simple patches.
> - Well-organized and detailed user-oriented documentation.
> 
> ### Community involvement
> 
> - Be active on the dev mailing list and help mentor newer contributors
> and users.
> - Be active on the issue tracker for project maintenance
> - Be involved in the design road map discussions with a professional
> and diplomatic approach even if there is a disagreement
> 
> 
> ===============================
> 
> Thank you for all your feedback and time. If there are no strong
> objections, I will put this on our website.
> 
> BR,
> 
> Kent Yao
>