You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apisix.apache.org by Zhiyuan Ju <ju...@apache.org> on 2022/04/08 10:12:44 UTC
[DISCUSS] What is really a Good first issue?
Hi, folks,
This question is benevolent and wise, and there is no uniform standard to
measure. The reason for the question is that I found only a few good first
issues when I looked through all the subproject[1] issues of the Apache
APISIX community.
Last year, Ruofei Zhao helped to build the Good first issue page[2], and
you will find that:
1. There have 11 issues with the Good first issue label in the
apache/apisix repo,
2. There have four issues in the apache/apisix-dashboard repo
3. There have 0 or few good first issues in other repos.
Maybe we don't have many good first issues currently, but I'd like to know
if we should have a clear scope for the Good first issues in Apache APISIX
projects? What's the good first issue that our community needs?
Here's my proposal for different levels of contributors:
1. Newbie
1.1 Description: People who have never been exposed to programming and have
no knowledge of the project but wish to be involved in an open source
project/community.
1.2 Cases: i18n, Documentation typo fix.
2. Beginner
2.1 Description: Programming experience (at any level of depth), but no
background in the knowledge required for API gateways (technology: Nginx,
OpenResty, etc.; knowledge: what is API gateway?)
2.2 Cases
2.2.1 Contribute independent features, i.e., issues that intersect less
with the core. e.g. apache/apisix plugins.
2.2.2 Contributing test coverage, e.g., Dashboard, Ingress Controller
project test writing.
2.2.3 Optimization of documentation, such as higher quality
internationalized documentation.
3. Familiar
3.1 Description: Experience with production use of API gateways (regardless
of usage) and unfamiliarity with Apache APISIX code/products, but can get
up to speed quickly.
3.2 Cases: Contribute valuable features and try to fix non-urgent bugs
(giving each other some patience).
4. Advanced
4.1 Description: Active participants in the project know what they are
doing and why.
5.2 Cases: No restrictions, but tends to lead to becoming a community KOL,
contributing more valuable features.
After discussing and confirming the proposal, I hope we can pick out the
practical issues for contributors based on the recommendation.
Kindly share your opinion~
[1] https://github.com/apache/?q=apisix-&type=all&language=&sort=
[2] https://apisix.apache.org/contribute/
Best Regards!
@ Zhiyuan Ju <https://github.com/juzhiyuan>
Re: [DISCUSS] What is really a Good first issue?
Posted by Anita Ihuman <an...@api7.ai>.
I think using this level of grading issues is great.
On Fri, Apr 8, 2022 at 11:13 AM Zhiyuan Ju <ju...@apache.org> wrote:
> Hi, folks,
>
> This question is benevolent and wise, and there is no uniform standard to
> measure. The reason for the question is that I found only a few good first
> issues when I looked through all the subproject[1] issues of the Apache
> APISIX community.
>
>
> Last year, Ruofei Zhao helped to build the Good first issue page[2], and
> you will find that:
>
>
> 1. There have 11 issues with the Good first issue label in the
> apache/apisix repo,
>
> 2. There have four issues in the apache/apisix-dashboard repo
>
> 3. There have 0 or few good first issues in other repos.
>
>
> Maybe we don't have many good first issues currently, but I'd like to know
> if we should have a clear scope for the Good first issues in Apache APISIX
> projects? What's the good first issue that our community needs?
>
>
> Here's my proposal for different levels of contributors:
>
>
> 1. Newbie
>
> 1.1 Description: People who have never been exposed to programming and have
> no knowledge of the project but wish to be involved in an open source
> project/community.
>
> 1.2 Cases: i18n, Documentation typo fix.
>
>
> 2. Beginner
>
> 2.1 Description: Programming experience (at any level of depth), but no
> background in the knowledge required for API gateways (technology: Nginx,
> OpenResty, etc.; knowledge: what is API gateway?)
>
> 2.2 Cases
>
> 2.2.1 Contribute independent features, i.e., issues that intersect less
> with the core. e.g. apache/apisix plugins.
>
> 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress Controller
> project test writing.
>
> 2.2.3 Optimization of documentation, such as higher quality
> internationalized documentation.
>
>
> 3. Familiar
>
> 3.1 Description: Experience with production use of API gateways (regardless
> of usage) and unfamiliarity with Apache APISIX code/products, but can get
> up to speed quickly.
>
> 3.2 Cases: Contribute valuable features and try to fix non-urgent bugs
> (giving each other some patience).
>
>
> 4. Advanced
>
> 4.1 Description: Active participants in the project know what they are
> doing and why.
>
> 5.2 Cases: No restrictions, but tends to lead to becoming a community KOL,
> contributing more valuable features.
>
>
> After discussing and confirming the proposal, I hope we can pick out the
> practical issues for contributors based on the recommendation.
>
>
> Kindly share your opinion~
>
> [1] https://github.com/apache/?q=apisix-&type=all&language=&sort=
> [2] https://apisix.apache.org/contribute/
>
> Best Regards!
> @ Zhiyuan Ju <https://github.com/juzhiyuan>
>
Re: [DISCUSS] What is really a Good first issue?
Posted by Chever John <ch...@gmail.com>.
Hi, Zhiyuan
I find that most of us are concerned about the need for making a quick
start or first issues. As a newbie, let me add some thoughts from other
perspectives.
I think a good first issue must be able to be completed. This means that
our maintainers can attempt to complete it before confirming that it can be
completed, for example as a bug or feat. I encountered a bug issue that
caused me to lose the confidence to continue contributing for a while.
I prefer to guide newbies in a progressive way to continue contributing to
the community, from newbie to beginner, familiar and advanced.
That is all my ideas. And I am looking forward your reply to talk about
this problem.
Best wish,
John Chever
On Apr 8, 2022 at 18:12:44, Zhiyuan Ju <ju...@apache.org> wrote:
> Hi, folks,
>
> This question is benevolent and wise, and there is no uniform standard to
> measure. The reason for the question is that I found only a few good first
> issues when I looked through all the subproject[1] issues of the Apache
> APISIX community.
>
>
> Last year, Ruofei Zhao helped to build the Good first issue page[2], and
> you will find that:
>
>
> 1. There have 11 issues with the Good first issue label in the
> apache/apisix repo,
>
> 2. There have four issues in the apache/apisix-dashboard repo
>
> 3. There have 0 or few good first issues in other repos.
>
>
> Maybe we don't have many good first issues currently, but I'd like to know
> if we should have a clear scope for the Good first issues in Apache APISIX
> projects? What's the good first issue that our community needs?
>
>
> Here's my proposal for different levels of contributors:
>
>
> 1. Newbie
>
> 1.1 Description: People who have never been exposed to programming and have
> no knowledge of the project but wish to be involved in an open source
> project/community.
>
> 1.2 Cases: i18n, Documentation typo fix.
>
>
> 2. Beginner
>
> 2.1 Description: Programming experience (at any level of depth), but no
> background in the knowledge required for API gateways (technology: Nginx,
> OpenResty, etc.; knowledge: what is API gateway?)
>
> 2.2 Cases
>
> 2.2.1 Contribute independent features, i.e., issues that intersect less
> with the core. e.g. apache/apisix plugins.
>
> 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress Controller
> project test writing.
>
> 2.2.3 Optimization of documentation, such as higher quality
> internationalized documentation.
>
>
> 3. Familiar
>
> 3.1 Description: Experience with production use of API gateways (regardless
> of usage) and unfamiliarity with Apache APISIX code/products, but can get
> up to speed quickly.
>
> 3.2 Cases: Contribute valuable features and try to fix non-urgent bugs
> (giving each other some patience).
>
>
> 4. Advanced
>
> 4.1 Description: Active participants in the project know what they are
> doing and why.
>
> 5.2 Cases: No restrictions, but tends to lead to becoming a community KOL,
> contributing more valuable features.
>
>
> After discussing and confirming the proposal, I hope we can pick out the
> practical issues for contributors based on the recommendation.
>
>
> Kindly share your opinion~
>
> [1] https://github.com/apache/?q=apisix-&type=all&language=&sort=
> [2] https://apisix.apache.org/contribute/
>
> Best Regards!
> @ Zhiyuan Ju <https://github.com/juzhiyuan>
>
Re: [DISCUSS] What is really a Good first issue?
Posted by Kwanhur Huang <hu...@163.com>.
Here[1] one guide help beginners to contribute to open source projects, I’m not sure if it’s helpful about this.
[1] https://firstcontributions.github.io/ <https://firstcontributions.github.io/>
Kwanhur Huang
TL;DR
> 2022年4月8日 下午6:12，Zhiyuan Ju <ju...@apache.org> 写道：
>
> Hi, folks,
>
> This question is benevolent and wise, and there is no uniform standard to
> measure. The reason for the question is that I found only a few good first
> issues when I looked through all the subproject[1] issues of the Apache
> APISIX community.
>
>
> Last year, Ruofei Zhao helped to build the Good first issue page[2], and
> you will find that:
>
>
> 1. There have 11 issues with the Good first issue label in the
> apache/apisix repo,
>
> 2. There have four issues in the apache/apisix-dashboard repo
>
> 3. There have 0 or few good first issues in other repos.
>
>
> Maybe we don't have many good first issues currently, but I'd like to know
> if we should have a clear scope for the Good first issues in Apache APISIX
> projects? What's the good first issue that our community needs?
>
>
> Here's my proposal for different levels of contributors:
>
>
> 1. Newbie
>
> 1.1 Description: People who have never been exposed to programming and have
> no knowledge of the project but wish to be involved in an open source
> project/community.
>
> 1.2 Cases: i18n, Documentation typo fix.
>
>
> 2. Beginner
>
> 2.1 Description: Programming experience (at any level of depth), but no
> background in the knowledge required for API gateways (technology: Nginx,
> OpenResty, etc.; knowledge: what is API gateway?)
>
> 2.2 Cases
>
> 2.2.1 Contribute independent features, i.e., issues that intersect less
> with the core. e.g. apache/apisix plugins.
>
> 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress Controller
> project test writing.
>
> 2.2.3 Optimization of documentation, such as higher quality
> internationalized documentation.
>
>
> 3. Familiar
>
> 3.1 Description: Experience with production use of API gateways (regardless
> of usage) and unfamiliarity with Apache APISIX code/products, but can get
> up to speed quickly.
>
> 3.2 Cases: Contribute valuable features and try to fix non-urgent bugs
> (giving each other some patience).
>
>
> 4. Advanced
>
> 4.1 Description: Active participants in the project know what they are
> doing and why.
>
> 5.2 Cases: No restrictions, but tends to lead to becoming a community KOL,
> contributing more valuable features.
>
>
> After discussing and confirming the proposal, I hope we can pick out the
> practical issues for contributors based on the recommendation.
>
>
> Kindly share your opinion~
>
> [1] https://github.com/apache/?q=apisix-&type=all&language=&sort=
> [2] https://apisix.apache.org/contribute/
>
> Best Regards!
> @ Zhiyuan Ju <https://github.com/juzhiyuan>
Re: [DISCUSS] What is really a Good first issue?
Posted by Anita Ihuman <an...@api7.ai>.
An onboarding team sounds like a good plan. So newbies can always request
for help at their convenience.
On Mon, Apr 11, 2022 at 5:50 PM Bobur Umurzokov <bo...@api7.ai> wrote:
> Hi Team,
>
> It is nice to read many opinions from you🙂
>
> > I prefer to guide newbies in a progressive way to continue contributing
> to
> the community, from newbie to beginner, familiar and advanced.
>
> Especially, I support the idea of having a step by step instructions for *a
> good first issue* when newbies and beginners would like to add their value
> to the open-source,
> at this point, they can easily follow the instruction without any
> hesitation considering that they do not have enough knowledge in the domain
> at the beginning.
>
> For example, I like that @Zhiyuan Ju <ju...@api7.ai> wrote down some
> guidelines on how to fix the specific issue
> https://github.com/apache/apisix-website/issues/1003
>
> Secondly, it is good to have a set of exercises prepared that new joiners
> can start to solve which gives background knowledge about APISIX with
> samples and tutorials.
>
> Thirdly, I vote for organizing a mentors group in APISIX. Let's say if
> there is a new contributor, we can assign a direct mentor or buddy who can
> help with onboarding, teaching,
> providing learning materials, working together to complete some tasks, and
> tracking daily how the newbie progressing during the first month. In this
> way, we can keep the encouragement of early starters interest in APISIX.
> Let's say one mentor can be responsible for up to 3 people. I can be the
> first volunteer. Nowadays, we are giving some workshops for the university
> students, it is great but once they reply with their ambition to contribute
> what's next? We do not have any plan to hold them longer.
>
> To be honest, if I were a student, I would think from the perspective of
> how I can get knowledge and experience that I can not obtain in the
> university. Of course, we are not a university or educational center but we
> are focusing on newbies and beginners so we need to take action
> accordingly.
>
> What do you think?
>
> Thanks!
>
> Kind regards,
> Bobur Umurzokov
>
Re: [DISCUSS] What is really a Good first issue?
Posted by Bobur Umurzokov <bo...@api7.ai>.
Hi Team,
It is nice to read many opinions from you🙂
> I prefer to guide newbies in a progressive way to continue contributing
to
the community, from newbie to beginner, familiar and advanced.
Especially, I support the idea of having a step by step instructions for *a
good first issue* when newbies and beginners would like to add their value
to the open-source,
at this point, they can easily follow the instruction without any
hesitation considering that they do not have enough knowledge in the domain
at the beginning.
For example, I like that @Zhiyuan Ju <ju...@api7.ai> wrote down some
guidelines on how to fix the specific issue
https://github.com/apache/apisix-website/issues/1003
Secondly, it is good to have a set of exercises prepared that new joiners
can start to solve which gives background knowledge about APISIX with
samples and tutorials.
Thirdly, I vote for organizing a mentors group in APISIX. Let's say if
there is a new contributor, we can assign a direct mentor or buddy who can
help with onboarding, teaching,
providing learning materials, working together to complete some tasks, and
tracking daily how the newbie progressing during the first month. In this
way, we can keep the encouragement of early starters interest in APISIX.
Let's say one mentor can be responsible for up to 3 people. I can be the
first volunteer. Nowadays, we are giving some workshops for the university
students, it is great but once they reply with their ambition to contribute
what's next? We do not have any plan to hold them longer.
To be honest, if I were a student, I would think from the perspective of
how I can get knowledge and experience that I can not obtain in the
university. Of course, we are not a university or educational center but we
are focusing on newbies and beginners so we need to take action
accordingly.
What do you think?
Thanks!
Kind regards,
Bobur Umurzokov
Re: [DISCUSS] What is really a Good first issue?
Posted by Tabah Baridule <ta...@gmail.com>.
This is great, ever since I join the community I have been reviewing PRs
and trying to get my first contributions mostly around documentation. So it
is great to have a standard. The "Good first issue" label is mostly used by
other projects as well like the "thegooddocsproject". I think it is a great
step to follow.
On Sat, Apr 9, 2022 at 6:40 AM Keer Liu <ke...@api7.ai> wrote:
> Glad to see there are already many discussions on how we can improve on
> Good first issues :)
> The Apache APISIX community will be hosting a series of new contributor
> workshops partnering with universities and communities globally in the
> following months. A great number of new contributors with great potential
> will be excited to try on and dig into the Good first issues! It is nice to
> see that people with various knowledge backgrounds can have something to
> contribute.
>
> On Sat, Apr 9, 2022 at 11:44 AM Ming Wen <we...@apache.org> wrote:
>
> > I don't think this is a standard practice.
> > The purpose of open source projects is to brainstorm ideas and lower the
> > bar for engineers to contribute.
> > As long as we uphold this goal and don't artificially create the illusion
> > of prosperity, I don't think there is a problem.
> >
> > Thanks,
> > Ming Wen, Apache APISIX PMC Chair
> > Twitter: _WenMing
> >
> >
> > Chao Zhang <to...@apache.org> 于2022年4月9日周六 10:57写道：
> >
> > > Hi Sheng,
> > >
> > > I'm curious about a better way to handle the documentation typo? The
> > > way I handle it is the same to Zhiyuan: creating a dedicated issue and
> > > adding the "Good First Issue" label.
> > >
> > > Best regards
> > > Chao Zhang
> > >
> > > https://github.com/tokers
> > >
> > > On Fri, Apr 8, 2022 at 8:26 PM Sheng Wu <wu...@gmail.com>
> > wrote:
> > > >
> > > > Documentation polish is fine. The argument is about posting doc typo
> > > issue
> > > > by official
> > > >
> > > > Sheng Wu 吴晟
> > > > Twitter, wusheng1108
> > > >
> > > >
> > > > Anita Ihuman <an...@api7.ai> 于2022年4月8日周五 20:16写道：
> > > >
> > > > > Often times, contributors focus on improving documentation or
> project
> > > > > UI(minor fixes) before digging into the core parts of the project.
> > > > > Personally I consider those kind of issues as beginner friendly
> > > > >
> > > > > On Fri, Apr 8, 2022 at 1:06 PM Sheng Wu <wu.sheng.841108@gmail.com
> >
> > > wrote:
> > > > >
> > > > > > > Documentation typo fix.
> > > > > >
> > > > > > This is really not a good thing as an official quick start or
> first
> > > > > issue.
> > > > > >
> > > > > > I am not sure whether you noticed an argument list on Twitter,
> > > > > > https://twitter.com/Manjusaka_Lee/status/1511267848735191042
> > > > > > Twitter is nothing relative to ASF, but I want you to know the
> risk
> > > of
> > > > > > other ppl's disagreements.
> > > > > >
> > > > > > Sheng Wu 吴晟
> > > > > > Twitter, wusheng1108
> > > > > >
> > > > > >
> > > > > > Zhiyuan Ju <ju...@apache.org> 于2022年4月8日周五 18:13写道：
> > > > > >
> > > > > > > Hi, folks,
> > > > > > >
> > > > > > > This question is benevolent and wise, and there is no uniform
> > > standard
> > > > > to
> > > > > > > measure. The reason for the question is that I found only a few
> > > good
> > > > > > first
> > > > > > > issues when I looked through all the subproject[1] issues of
> the
> > > Apache
> > > > > > > APISIX community.
> > > > > > >
> > > > > > >
> > > > > > > Last year, Ruofei Zhao helped to build the Good first issue
> > > page[2],
> > > > > and
> > > > > > > you will find that:
> > > > > > >
> > > > > > >
> > > > > > > 1. There have 11 issues with the Good first issue label in the
> > > > > > > apache/apisix repo,
> > > > > > >
> > > > > > > 2. There have four issues in the apache/apisix-dashboard repo
> > > > > > >
> > > > > > > 3. There have 0 or few good first issues in other repos.
> > > > > > >
> > > > > > >
> > > > > > > Maybe we don't have many good first issues currently, but I'd
> > like
> > > to
> > > > > > know
> > > > > > > if we should have a clear scope for the Good first issues in
> > Apache
> > > > > > APISIX
> > > > > > > projects? What's the good first issue that our community needs?
> > > > > > >
> > > > > > >
> > > > > > > Here's my proposal for different levels of contributors:
> > > > > > >
> > > > > > >
> > > > > > > 1. Newbie
> > > > > > >
> > > > > > > 1.1 Description: People who have never been exposed to
> > programming
> > > and
> > > > > > have
> > > > > > > no knowledge of the project but wish to be involved in an open
> > > source
> > > > > > > project/community.
> > > > > > >
> > > > > > > 1.2 Cases: i18n, Documentation typo fix.
> > > > > > >
> > > > > > >
> > > > > > > 2. Beginner
> > > > > > >
> > > > > > > 2.1 Description: Programming experience (at any level of
> depth),
> > > but no
> > > > > > > background in the knowledge required for API gateways
> > (technology:
> > > > > Nginx,
> > > > > > > OpenResty, etc.; knowledge: what is API gateway?)
> > > > > > >
> > > > > > > 2.2 Cases
> > > > > > >
> > > > > > > 2.2.1 Contribute independent features, i.e., issues that
> > intersect
> > > less
> > > > > > > with the core. e.g. apache/apisix plugins.
> > > > > > >
> > > > > > > 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress
> > > Controller
> > > > > > > project test writing.
> > > > > > >
> > > > > > > 2.2.3 Optimization of documentation, such as higher quality
> > > > > > > internationalized documentation.
> > > > > > >
> > > > > > >
> > > > > > > 3. Familiar
> > > > > > >
> > > > > > > 3.1 Description: Experience with production use of API gateways
> > > > > > (regardless
> > > > > > > of usage) and unfamiliarity with Apache APISIX code/products,
> but
> > > can
> > > > > get
> > > > > > > up to speed quickly.
> > > > > > >
> > > > > > > 3.2 Cases: Contribute valuable features and try to fix
> non-urgent
> > > bugs
> > > > > > > (giving each other some patience).
> > > > > > >
> > > > > > >
> > > > > > > 4. Advanced
> > > > > > >
> > > > > > > 4.1 Description: Active participants in the project know what
> > they
> > > are
> > > > > > > doing and why.
> > > > > > >
> > > > > > > 5.2 Cases: No restrictions, but tends to lead to becoming a
> > > community
> > > > > > KOL,
> > > > > > > contributing more valuable features.
> > > > > > >
> > > > > > >
> > > > > > > After discussing and confirming the proposal, I hope we can
> pick
> > > out
> > > > > the
> > > > > > > practical issues for contributors based on the recommendation.
> > > > > > >
> > > > > > >
> > > > > > > Kindly share your opinion~
> > > > > > >
> > > > > > > [1]
> > https://github.com/apache/?q=apisix-&type=all&language=&sort=
> > > > > > > [2] https://apisix.apache.org/contribute/
> > > > > > >
> > > > > > > Best Regards!
> > > > > > > @ Zhiyuan Ju <https://github.com/juzhiyuan>
> > > > > > >
> > > > > >
> > > > >
> > >
> >
>
>
> --
> *Keer Liu <https://www.linkedin.com/in/keerliu>*
> Head of Global Growth
>
Re: [DISCUSS] What is really a Good first issue?
Posted by Keer Liu <ke...@api7.ai>.
Glad to see there are already many discussions on how we can improve on
Good first issues :)
The Apache APISIX community will be hosting a series of new contributor
workshops partnering with universities and communities globally in the
following months. A great number of new contributors with great potential
will be excited to try on and dig into the Good first issues! It is nice to
see that people with various knowledge backgrounds can have something to
contribute.
On Sat, Apr 9, 2022 at 11:44 AM Ming Wen <we...@apache.org> wrote:
> I don't think this is a standard practice.
> The purpose of open source projects is to brainstorm ideas and lower the
> bar for engineers to contribute.
> As long as we uphold this goal and don't artificially create the illusion
> of prosperity, I don't think there is a problem.
>
> Thanks,
> Ming Wen, Apache APISIX PMC Chair
> Twitter: _WenMing
>
>
> Chao Zhang <to...@apache.org> 于2022年4月9日周六 10:57写道：
>
> > Hi Sheng,
> >
> > I'm curious about a better way to handle the documentation typo? The
> > way I handle it is the same to Zhiyuan: creating a dedicated issue and
> > adding the "Good First Issue" label.
> >
> > Best regards
> > Chao Zhang
> >
> > https://github.com/tokers
> >
> > On Fri, Apr 8, 2022 at 8:26 PM Sheng Wu <wu...@gmail.com>
> wrote:
> > >
> > > Documentation polish is fine. The argument is about posting doc typo
> > issue
> > > by official
> > >
> > > Sheng Wu 吴晟
> > > Twitter, wusheng1108
> > >
> > >
> > > Anita Ihuman <an...@api7.ai> 于2022年4月8日周五 20:16写道：
> > >
> > > > Often times, contributors focus on improving documentation or project
> > > > UI(minor fixes) before digging into the core parts of the project.
> > > > Personally I consider those kind of issues as beginner friendly
> > > >
> > > > On Fri, Apr 8, 2022 at 1:06 PM Sheng Wu <wu...@gmail.com>
> > wrote:
> > > >
> > > > > > Documentation typo fix.
> > > > >
> > > > > This is really not a good thing as an official quick start or first
> > > > issue.
> > > > >
> > > > > I am not sure whether you noticed an argument list on Twitter,
> > > > > https://twitter.com/Manjusaka_Lee/status/1511267848735191042
> > > > > Twitter is nothing relative to ASF, but I want you to know the risk
> > of
> > > > > other ppl's disagreements.
> > > > >
> > > > > Sheng Wu 吴晟
> > > > > Twitter, wusheng1108
> > > > >
> > > > >
> > > > > Zhiyuan Ju <ju...@apache.org> 于2022年4月8日周五 18:13写道：
> > > > >
> > > > > > Hi, folks,
> > > > > >
> > > > > > This question is benevolent and wise, and there is no uniform
> > standard
> > > > to
> > > > > > measure. The reason for the question is that I found only a few
> > good
> > > > > first
> > > > > > issues when I looked through all the subproject[1] issues of the
> > Apache
> > > > > > APISIX community.
> > > > > >
> > > > > >
> > > > > > Last year, Ruofei Zhao helped to build the Good first issue
> > page[2],
> > > > and
> > > > > > you will find that:
> > > > > >
> > > > > >
> > > > > > 1. There have 11 issues with the Good first issue label in the
> > > > > > apache/apisix repo,
> > > > > >
> > > > > > 2. There have four issues in the apache/apisix-dashboard repo
> > > > > >
> > > > > > 3. There have 0 or few good first issues in other repos.
> > > > > >
> > > > > >
> > > > > > Maybe we don't have many good first issues currently, but I'd
> like
> > to
> > > > > know
> > > > > > if we should have a clear scope for the Good first issues in
> Apache
> > > > > APISIX
> > > > > > projects? What's the good first issue that our community needs?
> > > > > >
> > > > > >
> > > > > > Here's my proposal for different levels of contributors:
> > > > > >
> > > > > >
> > > > > > 1. Newbie
> > > > > >
> > > > > > 1.1 Description: People who have never been exposed to
> programming
> > and
> > > > > have
> > > > > > no knowledge of the project but wish to be involved in an open
> > source
> > > > > > project/community.
> > > > > >
> > > > > > 1.2 Cases: i18n, Documentation typo fix.
> > > > > >
> > > > > >
> > > > > > 2. Beginner
> > > > > >
> > > > > > 2.1 Description: Programming experience (at any level of depth),
> > but no
> > > > > > background in the knowledge required for API gateways
> (technology:
> > > > Nginx,
> > > > > > OpenResty, etc.; knowledge: what is API gateway?)
> > > > > >
> > > > > > 2.2 Cases
> > > > > >
> > > > > > 2.2.1 Contribute independent features, i.e., issues that
> intersect
> > less
> > > > > > with the core. e.g. apache/apisix plugins.
> > > > > >
> > > > > > 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress
> > Controller
> > > > > > project test writing.
> > > > > >
> > > > > > 2.2.3 Optimization of documentation, such as higher quality
> > > > > > internationalized documentation.
> > > > > >
> > > > > >
> > > > > > 3. Familiar
> > > > > >
> > > > > > 3.1 Description: Experience with production use of API gateways
> > > > > (regardless
> > > > > > of usage) and unfamiliarity with Apache APISIX code/products, but
> > can
> > > > get
> > > > > > up to speed quickly.
> > > > > >
> > > > > > 3.2 Cases: Contribute valuable features and try to fix non-urgent
> > bugs
> > > > > > (giving each other some patience).
> > > > > >
> > > > > >
> > > > > > 4. Advanced
> > > > > >
> > > > > > 4.1 Description: Active participants in the project know what
> they
> > are
> > > > > > doing and why.
> > > > > >
> > > > > > 5.2 Cases: No restrictions, but tends to lead to becoming a
> > community
> > > > > KOL,
> > > > > > contributing more valuable features.
> > > > > >
> > > > > >
> > > > > > After discussing and confirming the proposal, I hope we can pick
> > out
> > > > the
> > > > > > practical issues for contributors based on the recommendation.
> > > > > >
> > > > > >
> > > > > > Kindly share your opinion~
> > > > > >
> > > > > > [1]
> https://github.com/apache/?q=apisix-&type=all&language=&sort=
> > > > > > [2] https://apisix.apache.org/contribute/
> > > > > >
> > > > > > Best Regards!
> > > > > > @ Zhiyuan Ju <https://github.com/juzhiyuan>
> > > > > >
> > > > >
> > > >
> >
>
--
*Keer Liu <https://www.linkedin.com/in/keerliu>*
Head of Global Growth
Re: [DISCUSS] What is really a Good first issue?
Posted by Ming Wen <we...@apache.org>.
I don't think this is a standard practice.
The purpose of open source projects is to brainstorm ideas and lower the
bar for engineers to contribute.
As long as we uphold this goal and don't artificially create the illusion
of prosperity, I don't think there is a problem.
Thanks,
Ming Wen, Apache APISIX PMC Chair
Twitter: _WenMing
Chao Zhang <to...@apache.org> 于2022年4月9日周六 10:57写道：
> Hi Sheng,
>
> I'm curious about a better way to handle the documentation typo? The
> way I handle it is the same to Zhiyuan: creating a dedicated issue and
> adding the "Good First Issue" label.
>
> Best regards
> Chao Zhang
>
> https://github.com/tokers
>
> On Fri, Apr 8, 2022 at 8:26 PM Sheng Wu <wu...@gmail.com> wrote:
> >
> > Documentation polish is fine. The argument is about posting doc typo
> issue
> > by official
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> >
> > Anita Ihuman <an...@api7.ai> 于2022年4月8日周五 20:16写道：
> >
> > > Often times, contributors focus on improving documentation or project
> > > UI(minor fixes) before digging into the core parts of the project.
> > > Personally I consider those kind of issues as beginner friendly
> > >
> > > On Fri, Apr 8, 2022 at 1:06 PM Sheng Wu <wu...@gmail.com>
> wrote:
> > >
> > > > > Documentation typo fix.
> > > >
> > > > This is really not a good thing as an official quick start or first
> > > issue.
> > > >
> > > > I am not sure whether you noticed an argument list on Twitter,
> > > > https://twitter.com/Manjusaka_Lee/status/1511267848735191042
> > > > Twitter is nothing relative to ASF, but I want you to know the risk
> of
> > > > other ppl's disagreements.
> > > >
> > > > Sheng Wu 吴晟
> > > > Twitter, wusheng1108
> > > >
> > > >
> > > > Zhiyuan Ju <ju...@apache.org> 于2022年4月8日周五 18:13写道：
> > > >
> > > > > Hi, folks,
> > > > >
> > > > > This question is benevolent and wise, and there is no uniform
> standard
> > > to
> > > > > measure. The reason for the question is that I found only a few
> good
> > > > first
> > > > > issues when I looked through all the subproject[1] issues of the
> Apache
> > > > > APISIX community.
> > > > >
> > > > >
> > > > > Last year, Ruofei Zhao helped to build the Good first issue
> page[2],
> > > and
> > > > > you will find that:
> > > > >
> > > > >
> > > > > 1. There have 11 issues with the Good first issue label in the
> > > > > apache/apisix repo,
> > > > >
> > > > > 2. There have four issues in the apache/apisix-dashboard repo
> > > > >
> > > > > 3. There have 0 or few good first issues in other repos.
> > > > >
> > > > >
> > > > > Maybe we don't have many good first issues currently, but I'd like
> to
> > > > know
> > > > > if we should have a clear scope for the Good first issues in Apache
> > > > APISIX
> > > > > projects? What's the good first issue that our community needs?
> > > > >
> > > > >
> > > > > Here's my proposal for different levels of contributors:
> > > > >
> > > > >
> > > > > 1. Newbie
> > > > >
> > > > > 1.1 Description: People who have never been exposed to programming
> and
> > > > have
> > > > > no knowledge of the project but wish to be involved in an open
> source
> > > > > project/community.
> > > > >
> > > > > 1.2 Cases: i18n, Documentation typo fix.
> > > > >
> > > > >
> > > > > 2. Beginner
> > > > >
> > > > > 2.1 Description: Programming experience (at any level of depth),
> but no
> > > > > background in the knowledge required for API gateways (technology:
> > > Nginx,
> > > > > OpenResty, etc.; knowledge: what is API gateway?)
> > > > >
> > > > > 2.2 Cases
> > > > >
> > > > > 2.2.1 Contribute independent features, i.e., issues that intersect
> less
> > > > > with the core. e.g. apache/apisix plugins.
> > > > >
> > > > > 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress
> Controller
> > > > > project test writing.
> > > > >
> > > > > 2.2.3 Optimization of documentation, such as higher quality
> > > > > internationalized documentation.
> > > > >
> > > > >
> > > > > 3. Familiar
> > > > >
> > > > > 3.1 Description: Experience with production use of API gateways
> > > > (regardless
> > > > > of usage) and unfamiliarity with Apache APISIX code/products, but
> can
> > > get
> > > > > up to speed quickly.
> > > > >
> > > > > 3.2 Cases: Contribute valuable features and try to fix non-urgent
> bugs
> > > > > (giving each other some patience).
> > > > >
> > > > >
> > > > > 4. Advanced
> > > > >
> > > > > 4.1 Description: Active participants in the project know what they
> are
> > > > > doing and why.
> > > > >
> > > > > 5.2 Cases: No restrictions, but tends to lead to becoming a
> community
> > > > KOL,
> > > > > contributing more valuable features.
> > > > >
> > > > >
> > > > > After discussing and confirming the proposal, I hope we can pick
> out
> > > the
> > > > > practical issues for contributors based on the recommendation.
> > > > >
> > > > >
> > > > > Kindly share your opinion~
> > > > >
> > > > > [1] https://github.com/apache/?q=apisix-&type=all&language=&sort=
> > > > > [2] https://apisix.apache.org/contribute/
> > > > >
> > > > > Best Regards!
> > > > > @ Zhiyuan Ju <https://github.com/juzhiyuan>
> > > > >
> > > >
> > >
>
Re: [DISCUSS] What is really a Good first issue?
Posted by Chao Zhang <to...@apache.org>.
Hi Sheng,
I'm curious about a better way to handle the documentation typo? The
way I handle it is the same to Zhiyuan: creating a dedicated issue and
adding the "Good First Issue" label.
Best regards
Chao Zhang
https://github.com/tokers
On Fri, Apr 8, 2022 at 8:26 PM Sheng Wu <wu...@gmail.com> wrote:
>
> Documentation polish is fine. The argument is about posting doc typo issue
> by official
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
> Anita Ihuman <an...@api7.ai> 于2022年4月8日周五 20:16写道：
>
> > Often times, contributors focus on improving documentation or project
> > UI(minor fixes) before digging into the core parts of the project.
> > Personally I consider those kind of issues as beginner friendly
> >
> > On Fri, Apr 8, 2022 at 1:06 PM Sheng Wu <wu...@gmail.com> wrote:
> >
> > > > Documentation typo fix.
> > >
> > > This is really not a good thing as an official quick start or first
> > issue.
> > >
> > > I am not sure whether you noticed an argument list on Twitter,
> > > https://twitter.com/Manjusaka_Lee/status/1511267848735191042
> > > Twitter is nothing relative to ASF, but I want you to know the risk of
> > > other ppl's disagreements.
> > >
> > > Sheng Wu 吴晟
> > > Twitter, wusheng1108
> > >
> > >
> > > Zhiyuan Ju <ju...@apache.org> 于2022年4月8日周五 18:13写道：
> > >
> > > > Hi, folks,
> > > >
> > > > This question is benevolent and wise, and there is no uniform standard
> > to
> > > > measure. The reason for the question is that I found only a few good
> > > first
> > > > issues when I looked through all the subproject[1] issues of the Apache
> > > > APISIX community.
> > > >
> > > >
> > > > Last year, Ruofei Zhao helped to build the Good first issue page[2],
> > and
> > > > you will find that:
> > > >
> > > >
> > > > 1. There have 11 issues with the Good first issue label in the
> > > > apache/apisix repo,
> > > >
> > > > 2. There have four issues in the apache/apisix-dashboard repo
> > > >
> > > > 3. There have 0 or few good first issues in other repos.
> > > >
> > > >
> > > > Maybe we don't have many good first issues currently, but I'd like to
> > > know
> > > > if we should have a clear scope for the Good first issues in Apache
> > > APISIX
> > > > projects? What's the good first issue that our community needs?
> > > >
> > > >
> > > > Here's my proposal for different levels of contributors:
> > > >
> > > >
> > > > 1. Newbie
> > > >
> > > > 1.1 Description: People who have never been exposed to programming and
> > > have
> > > > no knowledge of the project but wish to be involved in an open source
> > > > project/community.
> > > >
> > > > 1.2 Cases: i18n, Documentation typo fix.
> > > >
> > > >
> > > > 2. Beginner
> > > >
> > > > 2.1 Description: Programming experience (at any level of depth), but no
> > > > background in the knowledge required for API gateways (technology:
> > Nginx,
> > > > OpenResty, etc.; knowledge: what is API gateway?)
> > > >
> > > > 2.2 Cases
> > > >
> > > > 2.2.1 Contribute independent features, i.e., issues that intersect less
> > > > with the core. e.g. apache/apisix plugins.
> > > >
> > > > 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress Controller
> > > > project test writing.
> > > >
> > > > 2.2.3 Optimization of documentation, such as higher quality
> > > > internationalized documentation.
> > > >
> > > >
> > > > 3. Familiar
> > > >
> > > > 3.1 Description: Experience with production use of API gateways
> > > (regardless
> > > > of usage) and unfamiliarity with Apache APISIX code/products, but can
> > get
> > > > up to speed quickly.
> > > >
> > > > 3.2 Cases: Contribute valuable features and try to fix non-urgent bugs
> > > > (giving each other some patience).
> > > >
> > > >
> > > > 4. Advanced
> > > >
> > > > 4.1 Description: Active participants in the project know what they are
> > > > doing and why.
> > > >
> > > > 5.2 Cases: No restrictions, but tends to lead to becoming a community
> > > KOL,
> > > > contributing more valuable features.
> > > >
> > > >
> > > > After discussing and confirming the proposal, I hope we can pick out
> > the
> > > > practical issues for contributors based on the recommendation.
> > > >
> > > >
> > > > Kindly share your opinion~
> > > >
> > > > [1] https://github.com/apache/?q=apisix-&type=all&language=&sort=
> > > > [2] https://apisix.apache.org/contribute/
> > > >
> > > > Best Regards!
> > > > @ Zhiyuan Ju <https://github.com/juzhiyuan>
> > > >
> > >
> >
Re: [DISCUSS] What is really a Good first issue?
Posted by Baoyuan <ba...@gmail.com>.
Before an issue is marked as a good first issue, we should make sure that
the issue is meaningful and that it makes the project better.
Don't intentionally create issues just to create some good first issue.
Anita Ihuman <an...@api7.ai> 于2022年4月10日周日 23:36写道：
> How about an onboarding call for newcomers. Either once every week, or
> once/twice a month.
>
> On Sun, Apr 10, 2022 at 3:30 PM Willem Jiang <wi...@gmail.com>
> wrote:
>
> > Good first issue just gives the contributor a way to pick the lower
> > food, we need to do more in exchange for a long time contribution.
> > Beside fixing the typoes，I think we need to spend some time helping
> > the user onboarding.
> > Writing documents of contribution guid, providing mentoring help for
> > the newbees.
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Fri, Apr 8, 2022 at 10:12 PM Zhiyuan Ju <ju...@apache.org> wrote:
> > >
> > > Hi, Sheng and Anita,
> > >
> > > Thanks for your reply :)
> > >
> > > > The argument is about posting doc typo issue
> > > by official
> > >
> > > 1. Since I involved in the Apache APISIX Community in 2019, the
> community
> > > never created typos purposely and then created an issue with a Good
> first
> > > issue label AFAIK.
> > >
> > > 2. Usually, when I notice some typos or content that could be improved
> by
> > > chance, I will create an issue to track it. I could fix it directly but
> > > personally, I will tag a Good first issue because I think it’s easy for
> > > contributors to fix.
> > >
> > > 3. I’m not sure what kind of issues for our contributions who have
> > > different experience, that’s why I send this email to collect feedback
> > and
> > > opinions. <3
> > >
> > > Sheng Wu <wu...@gmail.com>于2022年4月8日 周五20:26写道：
> > >
> > > > Documentation polish is fine. The argument is about posting doc typo
> > issue
> > > > by official
> > > >
> > > > Sheng Wu 吴晟
> > > > Twitter, wusheng1108
> > > >
> > > >
> > > > Anita Ihuman <an...@api7.ai> 于2022年4月8日周五 20:16写道：
> > > >
> > > > > Often times, contributors focus on improving documentation or
> project
> > > > > UI(minor fixes) before digging into the core parts of the project.
> > > > > Personally I consider those kind of issues as beginner friendly
> > > > >
> > > > > On Fri, Apr 8, 2022 at 1:06 PM Sheng Wu <wu.sheng.841108@gmail.com
> >
> > > > wrote:
> > > > >
> > > > > > > Documentation typo fix.
> > > > > >
> > > > > > This is really not a good thing as an official quick start or
> first
> > > > > issue.
> > > > > >
> > > > > > I am not sure whether you noticed an argument list on Twitter,
> > > > > > https://twitter.com/Manjusaka_Lee/status/1511267848735191042
> > > > > > Twitter is nothing relative to ASF, but I want you to know the
> > risk of
> > > > > > other ppl's disagreements.
> > > > > >
> > > > > > Sheng Wu 吴晟
> > > > > > Twitter, wusheng1108
> > > > > >
> > > > > >
> > > > > > Zhiyuan Ju <ju...@apache.org> 于2022年4月8日周五 18:13写道：
> > > > > >
> > > > > > > Hi, folks,
> > > > > > >
> > > > > > > This question is benevolent and wise, and there is no uniform
> > > > standard
> > > > > to
> > > > > > > measure. The reason for the question is that I found only a few
> > good
> > > > > > first
> > > > > > > issues when I looked through all the subproject[1] issues of
> the
> > > > Apache
> > > > > > > APISIX community.
> > > > > > >
> > > > > > >
> > > > > > > Last year, Ruofei Zhao helped to build the Good first issue
> > page[2],
> > > > > and
> > > > > > > you will find that:
> > > > > > >
> > > > > > >
> > > > > > > 1. There have 11 issues with the Good first issue label in the
> > > > > > > apache/apisix repo,
> > > > > > >
> > > > > > > 2. There have four issues in the apache/apisix-dashboard repo
> > > > > > >
> > > > > > > 3. There have 0 or few good first issues in other repos.
> > > > > > >
> > > > > > >
> > > > > > > Maybe we don't have many good first issues currently, but I'd
> > like to
> > > > > > know
> > > > > > > if we should have a clear scope for the Good first issues in
> > Apache
> > > > > > APISIX
> > > > > > > projects? What's the good first issue that our community needs?
> > > > > > >
> > > > > > >
> > > > > > > Here's my proposal for different levels of contributors:
> > > > > > >
> > > > > > >
> > > > > > > 1. Newbie
> > > > > > >
> > > > > > > 1.1 Description: People who have never been exposed to
> > programming
> > > > and
> > > > > > have
> > > > > > > no knowledge of the project but wish to be involved in an open
> > source
> > > > > > > project/community.
> > > > > > >
> > > > > > > 1.2 Cases: i18n, Documentation typo fix.
> > > > > > >
> > > > > > >
> > > > > > > 2. Beginner
> > > > > > >
> > > > > > > 2.1 Description: Programming experience (at any level of
> depth),
> > but
> > > > no
> > > > > > > background in the knowledge required for API gateways
> > (technology:
> > > > > Nginx,
> > > > > > > OpenResty, etc.; knowledge: what is API gateway?)
> > > > > > >
> > > > > > > 2.2 Cases
> > > > > > >
> > > > > > > 2.2.1 Contribute independent features, i.e., issues that
> > intersect
> > > > less
> > > > > > > with the core. e.g. apache/apisix plugins.
> > > > > > >
> > > > > > > 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress
> > Controller
> > > > > > > project test writing.
> > > > > > >
> > > > > > > 2.2.3 Optimization of documentation, such as higher quality
> > > > > > > internationalized documentation.
> > > > > > >
> > > > > > >
> > > > > > > 3. Familiar
> > > > > > >
> > > > > > > 3.1 Description: Experience with production use of API gateways
> > > > > > (regardless
> > > > > > > of usage) and unfamiliarity with Apache APISIX code/products,
> > but can
> > > > > get
> > > > > > > up to speed quickly.
> > > > > > >
> > > > > > > 3.2 Cases: Contribute valuable features and try to fix
> non-urgent
> > > > bugs
> > > > > > > (giving each other some patience).
> > > > > > >
> > > > > > >
> > > > > > > 4. Advanced
> > > > > > >
> > > > > > > 4.1 Description: Active participants in the project know what
> > they
> > > > are
> > > > > > > doing and why.
> > > > > > >
> > > > > > > 5.2 Cases: No restrictions, but tends to lead to becoming a
> > community
> > > > > > KOL,
> > > > > > > contributing more valuable features.
> > > > > > >
> > > > > > >
> > > > > > > After discussing and confirming the proposal, I hope we can
> pick
> > out
> > > > > the
> > > > > > > practical issues for contributors based on the recommendation.
> > > > > > >
> > > > > > >
> > > > > > > Kindly share your opinion~
> > > > > > >
> > > > > > > [1]
> > https://github.com/apache/?q=apisix-&type=all&language=&sort=
> > > > > > > [2] https://apisix.apache.org/contribute/
> > > > > > >
> > > > > > > Best Regards!
> > > > > > > @ Zhiyuan Ju <https://github.com/juzhiyuan>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > --
> > > 来自 琚致远
> >
>
Re: [DISCUSS] What is really a Good first issue?
Posted by Anita Ihuman <an...@api7.ai>.
How about an onboarding call for newcomers. Either once every week, or
once/twice a month.
On Sun, Apr 10, 2022 at 3:30 PM Willem Jiang <wi...@gmail.com> wrote:
> Good first issue just gives the contributor a way to pick the lower
> food, we need to do more in exchange for a long time contribution.
> Beside fixing the typoes，I think we need to spend some time helping
> the user onboarding.
> Writing documents of contribution guid, providing mentoring help for
> the newbees.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Apr 8, 2022 at 10:12 PM Zhiyuan Ju <ju...@apache.org> wrote:
> >
> > Hi, Sheng and Anita,
> >
> > Thanks for your reply :)
> >
> > > The argument is about posting doc typo issue
> > by official
> >
> > 1. Since I involved in the Apache APISIX Community in 2019, the community
> > never created typos purposely and then created an issue with a Good first
> > issue label AFAIK.
> >
> > 2. Usually, when I notice some typos or content that could be improved by
> > chance, I will create an issue to track it. I could fix it directly but
> > personally, I will tag a Good first issue because I think it’s easy for
> > contributors to fix.
> >
> > 3. I’m not sure what kind of issues for our contributions who have
> > different experience, that’s why I send this email to collect feedback
> and
> > opinions. <3
> >
> > Sheng Wu <wu...@gmail.com>于2022年4月8日 周五20:26写道：
> >
> > > Documentation polish is fine. The argument is about posting doc typo
> issue
> > > by official
> > >
> > > Sheng Wu 吴晟
> > > Twitter, wusheng1108
> > >
> > >
> > > Anita Ihuman <an...@api7.ai> 于2022年4月8日周五 20:16写道：
> > >
> > > > Often times, contributors focus on improving documentation or project
> > > > UI(minor fixes) before digging into the core parts of the project.
> > > > Personally I consider those kind of issues as beginner friendly
> > > >
> > > > On Fri, Apr 8, 2022 at 1:06 PM Sheng Wu <wu...@gmail.com>
> > > wrote:
> > > >
> > > > > > Documentation typo fix.
> > > > >
> > > > > This is really not a good thing as an official quick start or first
> > > > issue.
> > > > >
> > > > > I am not sure whether you noticed an argument list on Twitter,
> > > > > https://twitter.com/Manjusaka_Lee/status/1511267848735191042
> > > > > Twitter is nothing relative to ASF, but I want you to know the
> risk of
> > > > > other ppl's disagreements.
> > > > >
> > > > > Sheng Wu 吴晟
> > > > > Twitter, wusheng1108
> > > > >
> > > > >
> > > > > Zhiyuan Ju <ju...@apache.org> 于2022年4月8日周五 18:13写道：
> > > > >
> > > > > > Hi, folks,
> > > > > >
> > > > > > This question is benevolent and wise, and there is no uniform
> > > standard
> > > > to
> > > > > > measure. The reason for the question is that I found only a few
> good
> > > > > first
> > > > > > issues when I looked through all the subproject[1] issues of the
> > > Apache
> > > > > > APISIX community.
> > > > > >
> > > > > >
> > > > > > Last year, Ruofei Zhao helped to build the Good first issue
> page[2],
> > > > and
> > > > > > you will find that:
> > > > > >
> > > > > >
> > > > > > 1. There have 11 issues with the Good first issue label in the
> > > > > > apache/apisix repo,
> > > > > >
> > > > > > 2. There have four issues in the apache/apisix-dashboard repo
> > > > > >
> > > > > > 3. There have 0 or few good first issues in other repos.
> > > > > >
> > > > > >
> > > > > > Maybe we don't have many good first issues currently, but I'd
> like to
> > > > > know
> > > > > > if we should have a clear scope for the Good first issues in
> Apache
> > > > > APISIX
> > > > > > projects? What's the good first issue that our community needs?
> > > > > >
> > > > > >
> > > > > > Here's my proposal for different levels of contributors:
> > > > > >
> > > > > >
> > > > > > 1. Newbie
> > > > > >
> > > > > > 1.1 Description: People who have never been exposed to
> programming
> > > and
> > > > > have
> > > > > > no knowledge of the project but wish to be involved in an open
> source
> > > > > > project/community.
> > > > > >
> > > > > > 1.2 Cases: i18n, Documentation typo fix.
> > > > > >
> > > > > >
> > > > > > 2. Beginner
> > > > > >
> > > > > > 2.1 Description: Programming experience (at any level of depth),
> but
> > > no
> > > > > > background in the knowledge required for API gateways
> (technology:
> > > > Nginx,
> > > > > > OpenResty, etc.; knowledge: what is API gateway?)
> > > > > >
> > > > > > 2.2 Cases
> > > > > >
> > > > > > 2.2.1 Contribute independent features, i.e., issues that
> intersect
> > > less
> > > > > > with the core. e.g. apache/apisix plugins.
> > > > > >
> > > > > > 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress
> Controller
> > > > > > project test writing.
> > > > > >
> > > > > > 2.2.3 Optimization of documentation, such as higher quality
> > > > > > internationalized documentation.
> > > > > >
> > > > > >
> > > > > > 3. Familiar
> > > > > >
> > > > > > 3.1 Description: Experience with production use of API gateways
> > > > > (regardless
> > > > > > of usage) and unfamiliarity with Apache APISIX code/products,
> but can
> > > > get
> > > > > > up to speed quickly.
> > > > > >
> > > > > > 3.2 Cases: Contribute valuable features and try to fix non-urgent
> > > bugs
> > > > > > (giving each other some patience).
> > > > > >
> > > > > >
> > > > > > 4. Advanced
> > > > > >
> > > > > > 4.1 Description: Active participants in the project know what
> they
> > > are
> > > > > > doing and why.
> > > > > >
> > > > > > 5.2 Cases: No restrictions, but tends to lead to becoming a
> community
> > > > > KOL,
> > > > > > contributing more valuable features.
> > > > > >
> > > > > >
> > > > > > After discussing and confirming the proposal, I hope we can pick
> out
> > > > the
> > > > > > practical issues for contributors based on the recommendation.
> > > > > >
> > > > > >
> > > > > > Kindly share your opinion~
> > > > > >
> > > > > > [1]
> https://github.com/apache/?q=apisix-&type=all&language=&sort=
> > > > > > [2] https://apisix.apache.org/contribute/
> > > > > >
> > > > > > Best Regards!
> > > > > > @ Zhiyuan Ju <https://github.com/juzhiyuan>
> > > > > >
> > > > >
> > > >
> > >
> > --
> > 来自 琚致远
>
Re: [DISCUSS] What is really a Good first issue?
Posted by Willem Jiang <wi...@gmail.com>.
Good first issue just gives the contributor a way to pick the lower
food, we need to do more in exchange for a long time contribution.
Beside fixing the typoes，I think we need to spend some time helping
the user onboarding.
Writing documents of contribution guid, providing mentoring help for
the newbees.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Apr 8, 2022 at 10:12 PM Zhiyuan Ju <ju...@apache.org> wrote:
>
> Hi, Sheng and Anita,
>
> Thanks for your reply :)
>
> > The argument is about posting doc typo issue
> by official
>
> 1. Since I involved in the Apache APISIX Community in 2019, the community
> never created typos purposely and then created an issue with a Good first
> issue label AFAIK.
>
> 2. Usually, when I notice some typos or content that could be improved by
> chance, I will create an issue to track it. I could fix it directly but
> personally, I will tag a Good first issue because I think it’s easy for
> contributors to fix.
>
> 3. I’m not sure what kind of issues for our contributions who have
> different experience, that’s why I send this email to collect feedback and
> opinions. <3
>
> Sheng Wu <wu...@gmail.com>于2022年4月8日 周五20:26写道：
>
> > Documentation polish is fine. The argument is about posting doc typo issue
> > by official
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> >
> > Anita Ihuman <an...@api7.ai> 于2022年4月8日周五 20:16写道：
> >
> > > Often times, contributors focus on improving documentation or project
> > > UI(minor fixes) before digging into the core parts of the project.
> > > Personally I consider those kind of issues as beginner friendly
> > >
> > > On Fri, Apr 8, 2022 at 1:06 PM Sheng Wu <wu...@gmail.com>
> > wrote:
> > >
> > > > > Documentation typo fix.
> > > >
> > > > This is really not a good thing as an official quick start or first
> > > issue.
> > > >
> > > > I am not sure whether you noticed an argument list on Twitter,
> > > > https://twitter.com/Manjusaka_Lee/status/1511267848735191042
> > > > Twitter is nothing relative to ASF, but I want you to know the risk of
> > > > other ppl's disagreements.
> > > >
> > > > Sheng Wu 吴晟
> > > > Twitter, wusheng1108
> > > >
> > > >
> > > > Zhiyuan Ju <ju...@apache.org> 于2022年4月8日周五 18:13写道：
> > > >
> > > > > Hi, folks,
> > > > >
> > > > > This question is benevolent and wise, and there is no uniform
> > standard
> > > to
> > > > > measure. The reason for the question is that I found only a few good
> > > > first
> > > > > issues when I looked through all the subproject[1] issues of the
> > Apache
> > > > > APISIX community.
> > > > >
> > > > >
> > > > > Last year, Ruofei Zhao helped to build the Good first issue page[2],
> > > and
> > > > > you will find that:
> > > > >
> > > > >
> > > > > 1. There have 11 issues with the Good first issue label in the
> > > > > apache/apisix repo,
> > > > >
> > > > > 2. There have four issues in the apache/apisix-dashboard repo
> > > > >
> > > > > 3. There have 0 or few good first issues in other repos.
> > > > >
> > > > >
> > > > > Maybe we don't have many good first issues currently, but I'd like to
> > > > know
> > > > > if we should have a clear scope for the Good first issues in Apache
> > > > APISIX
> > > > > projects? What's the good first issue that our community needs?
> > > > >
> > > > >
> > > > > Here's my proposal for different levels of contributors:
> > > > >
> > > > >
> > > > > 1. Newbie
> > > > >
> > > > > 1.1 Description: People who have never been exposed to programming
> > and
> > > > have
> > > > > no knowledge of the project but wish to be involved in an open source
> > > > > project/community.
> > > > >
> > > > > 1.2 Cases: i18n, Documentation typo fix.
> > > > >
> > > > >
> > > > > 2. Beginner
> > > > >
> > > > > 2.1 Description: Programming experience (at any level of depth), but
> > no
> > > > > background in the knowledge required for API gateways (technology:
> > > Nginx,
> > > > > OpenResty, etc.; knowledge: what is API gateway?)
> > > > >
> > > > > 2.2 Cases
> > > > >
> > > > > 2.2.1 Contribute independent features, i.e., issues that intersect
> > less
> > > > > with the core. e.g. apache/apisix plugins.
> > > > >
> > > > > 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress Controller
> > > > > project test writing.
> > > > >
> > > > > 2.2.3 Optimization of documentation, such as higher quality
> > > > > internationalized documentation.
> > > > >
> > > > >
> > > > > 3. Familiar
> > > > >
> > > > > 3.1 Description: Experience with production use of API gateways
> > > > (regardless
> > > > > of usage) and unfamiliarity with Apache APISIX code/products, but can
> > > get
> > > > > up to speed quickly.
> > > > >
> > > > > 3.2 Cases: Contribute valuable features and try to fix non-urgent
> > bugs
> > > > > (giving each other some patience).
> > > > >
> > > > >
> > > > > 4. Advanced
> > > > >
> > > > > 4.1 Description: Active participants in the project know what they
> > are
> > > > > doing and why.
> > > > >
> > > > > 5.2 Cases: No restrictions, but tends to lead to becoming a community
> > > > KOL,
> > > > > contributing more valuable features.
> > > > >
> > > > >
> > > > > After discussing and confirming the proposal, I hope we can pick out
> > > the
> > > > > practical issues for contributors based on the recommendation.
> > > > >
> > > > >
> > > > > Kindly share your opinion~
> > > > >
> > > > > [1] https://github.com/apache/?q=apisix-&type=all&language=&sort=
> > > > > [2] https://apisix.apache.org/contribute/
> > > > >
> > > > > Best Regards!
> > > > > @ Zhiyuan Ju <https://github.com/juzhiyuan>
> > > > >
> > > >
> > >
> >
> --
> 来自 琚致远
Re: [DISCUSS] What is really a Good first issue?
Posted by Zhiyuan Ju <ju...@apache.org>.
Hi, Sheng and Anita,
Thanks for your reply :)
> The argument is about posting doc typo issue
by official
1. Since I involved in the Apache APISIX Community in 2019, the community
never created typos purposely and then created an issue with a Good first
issue label AFAIK.
2. Usually, when I notice some typos or content that could be improved by
chance, I will create an issue to track it. I could fix it directly but
personally, I will tag a Good first issue because I think it’s easy for
contributors to fix.
3. I’m not sure what kind of issues for our contributions who have
different experience, that’s why I send this email to collect feedback and
opinions. <3
Sheng Wu <wu...@gmail.com>于2022年4月8日 周五20:26写道：
> Documentation polish is fine. The argument is about posting doc typo issue
> by official
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
> Anita Ihuman <an...@api7.ai> 于2022年4月8日周五 20:16写道：
>
> > Often times, contributors focus on improving documentation or project
> > UI(minor fixes) before digging into the core parts of the project.
> > Personally I consider those kind of issues as beginner friendly
> >
> > On Fri, Apr 8, 2022 at 1:06 PM Sheng Wu <wu...@gmail.com>
> wrote:
> >
> > > > Documentation typo fix.
> > >
> > > This is really not a good thing as an official quick start or first
> > issue.
> > >
> > > I am not sure whether you noticed an argument list on Twitter,
> > > https://twitter.com/Manjusaka_Lee/status/1511267848735191042
> > > Twitter is nothing relative to ASF, but I want you to know the risk of
> > > other ppl's disagreements.
> > >
> > > Sheng Wu 吴晟
> > > Twitter, wusheng1108
> > >
> > >
> > > Zhiyuan Ju <ju...@apache.org> 于2022年4月8日周五 18:13写道：
> > >
> > > > Hi, folks,
> > > >
> > > > This question is benevolent and wise, and there is no uniform
> standard
> > to
> > > > measure. The reason for the question is that I found only a few good
> > > first
> > > > issues when I looked through all the subproject[1] issues of the
> Apache
> > > > APISIX community.
> > > >
> > > >
> > > > Last year, Ruofei Zhao helped to build the Good first issue page[2],
> > and
> > > > you will find that:
> > > >
> > > >
> > > > 1. There have 11 issues with the Good first issue label in the
> > > > apache/apisix repo,
> > > >
> > > > 2. There have four issues in the apache/apisix-dashboard repo
> > > >
> > > > 3. There have 0 or few good first issues in other repos.
> > > >
> > > >
> > > > Maybe we don't have many good first issues currently, but I'd like to
> > > know
> > > > if we should have a clear scope for the Good first issues in Apache
> > > APISIX
> > > > projects? What's the good first issue that our community needs?
> > > >
> > > >
> > > > Here's my proposal for different levels of contributors:
> > > >
> > > >
> > > > 1. Newbie
> > > >
> > > > 1.1 Description: People who have never been exposed to programming
> and
> > > have
> > > > no knowledge of the project but wish to be involved in an open source
> > > > project/community.
> > > >
> > > > 1.2 Cases: i18n, Documentation typo fix.
> > > >
> > > >
> > > > 2. Beginner
> > > >
> > > > 2.1 Description: Programming experience (at any level of depth), but
> no
> > > > background in the knowledge required for API gateways (technology:
> > Nginx,
> > > > OpenResty, etc.; knowledge: what is API gateway?)
> > > >
> > > > 2.2 Cases
> > > >
> > > > 2.2.1 Contribute independent features, i.e., issues that intersect
> less
> > > > with the core. e.g. apache/apisix plugins.
> > > >
> > > > 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress Controller
> > > > project test writing.
> > > >
> > > > 2.2.3 Optimization of documentation, such as higher quality
> > > > internationalized documentation.
> > > >
> > > >
> > > > 3. Familiar
> > > >
> > > > 3.1 Description: Experience with production use of API gateways
> > > (regardless
> > > > of usage) and unfamiliarity with Apache APISIX code/products, but can
> > get
> > > > up to speed quickly.
> > > >
> > > > 3.2 Cases: Contribute valuable features and try to fix non-urgent
> bugs
> > > > (giving each other some patience).
> > > >
> > > >
> > > > 4. Advanced
> > > >
> > > > 4.1 Description: Active participants in the project know what they
> are
> > > > doing and why.
> > > >
> > > > 5.2 Cases: No restrictions, but tends to lead to becoming a community
> > > KOL,
> > > > contributing more valuable features.
> > > >
> > > >
> > > > After discussing and confirming the proposal, I hope we can pick out
> > the
> > > > practical issues for contributors based on the recommendation.
> > > >
> > > >
> > > > Kindly share your opinion~
> > > >
> > > > [1] https://github.com/apache/?q=apisix-&type=all&language=&sort=
> > > > [2] https://apisix.apache.org/contribute/
> > > >
> > > > Best Regards!
> > > > @ Zhiyuan Ju <https://github.com/juzhiyuan>
> > > >
> > >
> >
>
--
来自 琚致远
Re: [DISCUSS] What is really a Good first issue?
Posted by Sheng Wu <wu...@gmail.com>.
Documentation polish is fine. The argument is about posting doc typo issue
by official
Sheng Wu 吴晟
Twitter, wusheng1108
Anita Ihuman <an...@api7.ai> 于2022年4月8日周五 20:16写道：
> Often times, contributors focus on improving documentation or project
> UI(minor fixes) before digging into the core parts of the project.
> Personally I consider those kind of issues as beginner friendly
>
> On Fri, Apr 8, 2022 at 1:06 PM Sheng Wu <wu...@gmail.com> wrote:
>
> > > Documentation typo fix.
> >
> > This is really not a good thing as an official quick start or first
> issue.
> >
> > I am not sure whether you noticed an argument list on Twitter,
> > https://twitter.com/Manjusaka_Lee/status/1511267848735191042
> > Twitter is nothing relative to ASF, but I want you to know the risk of
> > other ppl's disagreements.
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> >
> > Zhiyuan Ju <ju...@apache.org> 于2022年4月8日周五 18:13写道：
> >
> > > Hi, folks,
> > >
> > > This question is benevolent and wise, and there is no uniform standard
> to
> > > measure. The reason for the question is that I found only a few good
> > first
> > > issues when I looked through all the subproject[1] issues of the Apache
> > > APISIX community.
> > >
> > >
> > > Last year, Ruofei Zhao helped to build the Good first issue page[2],
> and
> > > you will find that:
> > >
> > >
> > > 1. There have 11 issues with the Good first issue label in the
> > > apache/apisix repo,
> > >
> > > 2. There have four issues in the apache/apisix-dashboard repo
> > >
> > > 3. There have 0 or few good first issues in other repos.
> > >
> > >
> > > Maybe we don't have many good first issues currently, but I'd like to
> > know
> > > if we should have a clear scope for the Good first issues in Apache
> > APISIX
> > > projects? What's the good first issue that our community needs?
> > >
> > >
> > > Here's my proposal for different levels of contributors:
> > >
> > >
> > > 1. Newbie
> > >
> > > 1.1 Description: People who have never been exposed to programming and
> > have
> > > no knowledge of the project but wish to be involved in an open source
> > > project/community.
> > >
> > > 1.2 Cases: i18n, Documentation typo fix.
> > >
> > >
> > > 2. Beginner
> > >
> > > 2.1 Description: Programming experience (at any level of depth), but no
> > > background in the knowledge required for API gateways (technology:
> Nginx,
> > > OpenResty, etc.; knowledge: what is API gateway?)
> > >
> > > 2.2 Cases
> > >
> > > 2.2.1 Contribute independent features, i.e., issues that intersect less
> > > with the core. e.g. apache/apisix plugins.
> > >
> > > 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress Controller
> > > project test writing.
> > >
> > > 2.2.3 Optimization of documentation, such as higher quality
> > > internationalized documentation.
> > >
> > >
> > > 3. Familiar
> > >
> > > 3.1 Description: Experience with production use of API gateways
> > (regardless
> > > of usage) and unfamiliarity with Apache APISIX code/products, but can
> get
> > > up to speed quickly.
> > >
> > > 3.2 Cases: Contribute valuable features and try to fix non-urgent bugs
> > > (giving each other some patience).
> > >
> > >
> > > 4. Advanced
> > >
> > > 4.1 Description: Active participants in the project know what they are
> > > doing and why.
> > >
> > > 5.2 Cases: No restrictions, but tends to lead to becoming a community
> > KOL,
> > > contributing more valuable features.
> > >
> > >
> > > After discussing and confirming the proposal, I hope we can pick out
> the
> > > practical issues for contributors based on the recommendation.
> > >
> > >
> > > Kindly share your opinion~
> > >
> > > [1] https://github.com/apache/?q=apisix-&type=all&language=&sort=
> > > [2] https://apisix.apache.org/contribute/
> > >
> > > Best Regards!
> > > @ Zhiyuan Ju <https://github.com/juzhiyuan>
> > >
> >
>
Re: [DISCUSS] What is really a Good first issue?
Posted by Anita Ihuman <an...@api7.ai>.
Often times, contributors focus on improving documentation or project
UI(minor fixes) before digging into the core parts of the project.
Personally I consider those kind of issues as beginner friendly
On Fri, Apr 8, 2022 at 1:06 PM Sheng Wu <wu...@gmail.com> wrote:
> > Documentation typo fix.
>
> This is really not a good thing as an official quick start or first issue.
>
> I am not sure whether you noticed an argument list on Twitter,
> https://twitter.com/Manjusaka_Lee/status/1511267848735191042
> Twitter is nothing relative to ASF, but I want you to know the risk of
> other ppl's disagreements.
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
> Zhiyuan Ju <ju...@apache.org> 于2022年4月8日周五 18:13写道：
>
> > Hi, folks,
> >
> > This question is benevolent and wise, and there is no uniform standard to
> > measure. The reason for the question is that I found only a few good
> first
> > issues when I looked through all the subproject[1] issues of the Apache
> > APISIX community.
> >
> >
> > Last year, Ruofei Zhao helped to build the Good first issue page[2], and
> > you will find that:
> >
> >
> > 1. There have 11 issues with the Good first issue label in the
> > apache/apisix repo,
> >
> > 2. There have four issues in the apache/apisix-dashboard repo
> >
> > 3. There have 0 or few good first issues in other repos.
> >
> >
> > Maybe we don't have many good first issues currently, but I'd like to
> know
> > if we should have a clear scope for the Good first issues in Apache
> APISIX
> > projects? What's the good first issue that our community needs?
> >
> >
> > Here's my proposal for different levels of contributors:
> >
> >
> > 1. Newbie
> >
> > 1.1 Description: People who have never been exposed to programming and
> have
> > no knowledge of the project but wish to be involved in an open source
> > project/community.
> >
> > 1.2 Cases: i18n, Documentation typo fix.
> >
> >
> > 2. Beginner
> >
> > 2.1 Description: Programming experience (at any level of depth), but no
> > background in the knowledge required for API gateways (technology: Nginx,
> > OpenResty, etc.; knowledge: what is API gateway?)
> >
> > 2.2 Cases
> >
> > 2.2.1 Contribute independent features, i.e., issues that intersect less
> > with the core. e.g. apache/apisix plugins.
> >
> > 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress Controller
> > project test writing.
> >
> > 2.2.3 Optimization of documentation, such as higher quality
> > internationalized documentation.
> >
> >
> > 3. Familiar
> >
> > 3.1 Description: Experience with production use of API gateways
> (regardless
> > of usage) and unfamiliarity with Apache APISIX code/products, but can get
> > up to speed quickly.
> >
> > 3.2 Cases: Contribute valuable features and try to fix non-urgent bugs
> > (giving each other some patience).
> >
> >
> > 4. Advanced
> >
> > 4.1 Description: Active participants in the project know what they are
> > doing and why.
> >
> > 5.2 Cases: No restrictions, but tends to lead to becoming a community
> KOL,
> > contributing more valuable features.
> >
> >
> > After discussing and confirming the proposal, I hope we can pick out the
> > practical issues for contributors based on the recommendation.
> >
> >
> > Kindly share your opinion~
> >
> > [1] https://github.com/apache/?q=apisix-&type=all&language=&sort=
> > [2] https://apisix.apache.org/contribute/
> >
> > Best Regards!
> > @ Zhiyuan Ju <https://github.com/juzhiyuan>
> >
>
Re: [DISCUSS] What is really a Good first issue?
Posted by Sheng Wu <wu...@gmail.com>.
> Documentation typo fix.
This is really not a good thing as an official quick start or first issue.
I am not sure whether you noticed an argument list on Twitter,
https://twitter.com/Manjusaka_Lee/status/1511267848735191042
Twitter is nothing relative to ASF, but I want you to know the risk of
other ppl's disagreements.
Sheng Wu 吴晟
Twitter, wusheng1108
Zhiyuan Ju <ju...@apache.org> 于2022年4月8日周五 18:13写道：
> Hi, folks,
>
> This question is benevolent and wise, and there is no uniform standard to
> measure. The reason for the question is that I found only a few good first
> issues when I looked through all the subproject[1] issues of the Apache
> APISIX community.
>
>
> Last year, Ruofei Zhao helped to build the Good first issue page[2], and
> you will find that:
>
>
> 1. There have 11 issues with the Good first issue label in the
> apache/apisix repo,
>
> 2. There have four issues in the apache/apisix-dashboard repo
>
> 3. There have 0 or few good first issues in other repos.
>
>
> Maybe we don't have many good first issues currently, but I'd like to know
> if we should have a clear scope for the Good first issues in Apache APISIX
> projects? What's the good first issue that our community needs?
>
>
> Here's my proposal for different levels of contributors:
>
>
> 1. Newbie
>
> 1.1 Description: People who have never been exposed to programming and have
> no knowledge of the project but wish to be involved in an open source
> project/community.
>
> 1.2 Cases: i18n, Documentation typo fix.
>
>
> 2. Beginner
>
> 2.1 Description: Programming experience (at any level of depth), but no
> background in the knowledge required for API gateways (technology: Nginx,
> OpenResty, etc.; knowledge: what is API gateway?)
>
> 2.2 Cases
>
> 2.2.1 Contribute independent features, i.e., issues that intersect less
> with the core. e.g. apache/apisix plugins.
>
> 2.2.2 Contributing test coverage, e.g., Dashboard, Ingress Controller
> project test writing.
>
> 2.2.3 Optimization of documentation, such as higher quality
> internationalized documentation.
>
>
> 3. Familiar
>
> 3.1 Description: Experience with production use of API gateways (regardless
> of usage) and unfamiliarity with Apache APISIX code/products, but can get
> up to speed quickly.
>
> 3.2 Cases: Contribute valuable features and try to fix non-urgent bugs
> (giving each other some patience).
>
>
> 4. Advanced
>
> 4.1 Description: Active participants in the project know what they are
> doing and why.
>
> 5.2 Cases: No restrictions, but tends to lead to becoming a community KOL,
> contributing more valuable features.
>
>
> After discussing and confirming the proposal, I hope we can pick out the
> practical issues for contributors based on the recommendation.
>
>
> Kindly share your opinion~
>
> [1] https://github.com/apache/?q=apisix-&type=all&language=&sort=
> [2] https://apisix.apache.org/contribute/
>
> Best Regards!
> @ Zhiyuan Ju <https://github.com/juzhiyuan>
>