Hi, Yes, please follow #6672 and #6651 and share your ideas :)
Best Regards! @ Zhiyuan Ju <https://github.com/juzhiyuan> Navendu Pottekkat <navendupottek...@gmail.com> 于2022年3月22日周二 15:35写道： > Hi, > > We had opened an issue to create a style guide for the docs. > > There will be style guides for English and Chinese languages and they > could overlap in some areas. These are tracked in issues #6672 > <https://github.com/apache/apisix/issues/6672> and #6651 > <https://github.com/apache/apisix/issues/6651>. > > It would be best if you could give your suggestions on these issue threads. > > Best, > > Navendu > > On 22/03/22 12:41 pm, Ayush Das wrote: > > Hi Zhiyuan, > > By any chance do you have any reference to share the style of > documentation > > we will be sticking with? Or should we give idea of documentation styling > > in this thread? > > > > Best Regards, > > Ayush Das<https://github.com/iamayushdas> > > > > On Tue, 22 Mar 2022 at 12:29 PM, Zhiyuan Ju<juzhiy...@apache.org> > wrote: > > > >> Hi, > >> > >>> 1. redesign documentation > >> Updates: I have split this into two projects: > >> > >> 1. Unify Apache APISIX Documentation Contents Style[1]. > >> 2. Restructure Apache APISIX Documentation[2]. > >> > >> We will have a more clear milestone for them. > >> > >> [1]https://github.com/orgs/apache/projects/35 > >> [2]https://github.com/orgs/apache/projects/34 > >> > >> > >> Best Regards! > >> @ Zhiyuan Ju<https://github.com/juzhiyuan> > >> > >> > >> Zexuan Luo<spacewan...@apache.org> 于2022年2月25日周五 09:11写道： > >> > >>> Yes, a better implementation of standalone mode or Admin API can sync > >>> configuration in file to etcd. > >>> > >>> Jintao Zhang<zhangjin...@apache.org> 于2022年2月24日周四 14:32写道： > >>>>> 8. declarative configuration like what we have done in apisix-ingress > >>>> A Kubernetes discovery module was recently added to APISIX[1]. > >>>> Is it possible that for some simple rules, it can be done directly > >> using > >>>> only APISIX without APISIX Ingress ? > >>>> > >>>> [1]:https://github.com/apache/apisix/pull/4880 > >>>> > >>>> Ming Wen<wenm...@apache.org> 于2022年2月24日周四 10:03写道： > >>>> > >>>>>> We are going to make APISIX proxy everything: > >>>>> I think you mean use Apache APISIX with Istio as Service Mesh, right? > >>>>> > >>>>> Thanks, > >>>>> Ming Wen, Apache APISIX PMC Chair > >>>>> Twitter: _WenMing > >>>>> > >>>>> > >>>>> Zexuan Luo<spacewan...@apache.org> 于2022年2月23日周三 22:43写道： > >>>>> > >>>>>> Hi Sheng > >>>>>> Thanks for your reminder. We will remove them from Apache APISIX's > >>>>> roadmap. > >>>>>> Sheng Wu<wu.sheng.841...@gmail.com> 于2022年2月23日周三 20:24写道： > >>>>>>> Hi Zexuan > >>>>>>> > >>>>>>> Please notice this is an ASF mail list, what `we` is the > >> community, > >>>>>>> API7's codes are owned by the company, which should not be a part > >>> of > >>>>>>> the community. > >>>>>>> ``` > >>>>>>> 4. support different backend as the source of configuration > >>> instead of > >>>>>>> etcd. We have already started to do it in > >>>>>>> https://github.com/api7/etcd-adapter > >>>>>>> 5. move some features to CP side. We will start to do CP side > >>> service > >>>>>>> discovery in > >>>>>>> https://github.com/api7/apisix-seed/ > >>>>>>> ``` > >>>>>>> If the codes are going to donate, it should be taken care of > >> first. > >>>>>>> > >>>>>>> Sheng Wu 吴晟 > >>>>>>> Twitter, wusheng1108 > >>>>>>> > >>>>>>> Zexuan Luo<spacewan...@apache.org> 于2022年2月23日周三 19:54写道： > >>>>>>>> We are going to release a new major version (V3) in 2022. > >>>>>>>> As a major version, we will remove deprecated fields, bring > >> break > >>>>>>>> changes, and most importantly, add great features. > >>>>>>>> > >>>>>>>> We are going to make APISIX easier to adopt: > >>>>>>>> 1. redesign documentation > >>>>>>>> 2. refactor the backend of Dashboard. Now, this backend will > >> talk > >>>>> with > >>>>>>>> Admin API instead of etcd. > >>>>>>>> 3. refactor the API definition in Admin API, so that it can > >>> match the > >>>>>>>> backend of Dashboard. > >>>>>>>> 4. support different backend as the source of configuration > >>> instead > >>>>> of > >>>>>>>> etcd. We have already started to do it in > >>>>>>>> https://github.com/api7/etcd-adapter > >>>>>>>> 5. move some features to CP side. We will start to do CP side > >>> service > >>>>>>>> discovery in > >>>>>>>> https://github.com/api7/apisix-seed/ > >>>>>>>> 6. smarter way to diagnose runtime issues. Probably a builtin > >>> plugin? > >>>>>>>> 7. Connect to etcd via gRPC and reduce the number of etcd > >>> connection > >>>>>>>> 8. declarative configuration like what we have done in > >>> apisix-ingress > >>>>>>>> We are going to make APISIX connect to more ecosystems: > >>>>>>>> 1. integrate with more Open Source projects > >>>>>>>> 2. integrate with cloud vendors > >>>>>>>> 3. integrate with OpenAPI spec and other API spec definitions > >>>>>>>> 4. write plugin without Lua, in the traditional way (Plugin > >>> Runner) > >>>>> or > >>>>>>>> the modern way (Wasm) > >>>>>>>> 5. native gRPC support as a client, so we can connect to > >> further > >>>>> places > >>>>>>>> We are going to make APISIX proxy everything: > >>>>>>>> 1. xRPC: an L4 proxy framework to provide wire-level > >>> observability of > >>>>>>>> databases & message queue & RPC. > >>>>>>>> And more L4 observability: Prometheus & logger in the L4 level. > >>>>>>>> 2. support XDS so APISIX can be used as the DP of istio
