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 <paullin3...@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 <wang4lun...@gmail.com> 写道：
> > >
> > > Hi, I second with all the requirements above mentioned. Best, LuNing Wang
> > > 王鲁宁
> > >
> > > Nicholas Jiang <nicholasji...@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
> > >>>
> > >>
> >
>
