Hi, community members,

Yesterday, one of Apache APISIX's community users asked me how to involve
in our community, so I hold a webinar and share the information in the
WeChat Group (something like WhatsApp), 20 developers joined in and the
webinar lasts 90min :)

Here is the summary of this event:
1. Developer Experience is not good and smooth for newcomers.
1.1 Some communities will reject PRs that developers submit;
1.2 Users don't know what or how they can contribute;
1.3 There has a high bar to develop Apache APISIX and its products:
1.3.1 There have a lot of Documentations that lack tech details, and
developers need to read and debug from source codes;
1.3.2 There have a lot of environments and dependencies that need to take
care of or install;
1.3.3 Developers need to use Test Nginx to program test cases, but Test
Nginx lacks docs either. Also, when developers run test cases locally, it's
hard to pass all test cases because of environmental issues.
1.4 Chinese attendees often ask the workflow about how to corporate with
others in the community, they need more courage and mentors.

2. Documentation
2.1 We have repos like `apache/apisix`, `apache/apisix-dashboard`,
`apache/apisix-ingress-controller` and others, and only `apache/apisix`
repo's docs are maintained regularly and frequently, attendees complained
about the Docs Quality.
2.2 Attendees hope our projects could include Production Best Practice
sections, when users use Apache APISIX, they could easily find the
appropriate scenarios instead of just seeing a demo.

2.3 Products
2.3.1 Most attendees complain about Apache APISIX Dashboard is just a demo,
and it lacks many scenario-based functions. We hope it's not only
out-of-box but also reducing the difficulty to use it in production. The
same as Ingress Controller.

Yes, there have a lot of issues that our developers are facing, but it's
also a great feeling to hold events like this! For the issues above, kindly
share your ideas and thoughts :)

Best Regards!
@ Zhiyuan Ju <https://github.com/juzhiyuan>

Reply via email to