-1 binding The whole topic is actually not a thing determined by the community or the PMC. This is wrong from an ownership perspective.
Sheng Wu 吴晟 Twitter, wusheng1108 shirui zhao <zhaoth...@gmail.com> 于2022年7月8日周五 14:34写道： > > +1, for sub project of Apache APISIX. It’s a very nice work! > > — > Thanks, > Shirui Zhao > > > 2022年7月8日 14:21，Zexuan Luo <spacewan...@apache.org> 写道： > > > > +1 for creating this project in the apache group as a > > sub-project of the Apache APISIX > > > > Ming Wen <wenm...@apache.org> 于2022年7月8日周五 14:05写道： > >> > >> +1 for sub project of Apache APISIX > >> > >> Thanks, > >> Ming Wen, Apache APISIX PMC Chair > >> Twitter: _WenMing > >> > >> > >> hui li <yo...@apache.org> 于2022年7月8日周五 11:04写道： > >> > >>> Hi, I currently have a new Profile Toolkit project dedicated to Apache > >>> APISIX in the Summer-OSPP. The project uses eBPF to capture and parse the > >>> lua call stack information in Apache APISIX, aggregate it and generate cpu > >>> flame maps. > >>> > >>> I would like to ask if this project is better created in the apache group > >>> ( > >>> https://github.com/apache) or in the api7 group (https://github.com/api7)? > >>> > >>> This tool is a profile tool specifically for Apache APISIX, so I > >>> personally > >>> think it is better to create this project in the apache group as a > >>> sub-project of the Apache APISIX > >>> > >>> Project Description. > >>> Use eBPF to capture and parse lua call stack information in Apache APISIX, > >>> summarize it and generate cpu flame graphs. > >>> Use eBPF to capture and parse both C and Lua mixed call stack information, > >>> summarize it and generate cpu flame graph. > >>> Support fetching Apache APISIX processes running in Docker > >>> Support to get Apache APISIX Openresty luajit 32/luajit 64 mode > >>> >
