Hi, Gosling, Thanks for your review. > We have known APISIX build around Nginx variant OpenRetry(iResty), so we'd better clarify why we put some links[1][2][3] in Apache APISIX README. These are the documentations about coding style of OpenResty, the role of the API gateway, and how to deploy Apache APISIX in ARM server. I agree that these external links and coding style documentation should be removed.
> And some links[4][5] seem not on Apache branding umbrella, Do we plan to move them to the apache repository? The first link is an online demo of the Apache APISIX dashboard, should we use the IP directly instead of the domain to avoid branding issues? The second link is the python sdk I wrote to use Apache APISIX. I'm not quite sure if donating is the only way to deal with this branding issue? > Anyway, we should have a reachable channel for that security report yes, we already have a public channel[1] for reporting security risks. [1] https://apisix.incubator.apache.org/contribute/security/ Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing Gosling Von <fengji...@gmail.com> 于2020年5月27日周三 下午2:29写道： > Hi, > > I reviewed the maturity assessment and project details on Github to > support the graduation discussion. Based on my previous experience, I also > found some problems with branding in the following, which I hope we can > solve it before calling for a vote formally. Meanwhile, I also hope to hear > more feedback from other mentors. > > We have known APISIX build around Nginx variant OpenRetry(iResty), so we'd > better clarify why we put some links[1][2][3] in Apache APISIX README. > > And some links[4][5] seem not on Apache branding umbrella, Do we plan to > move them to the apache repository? > > Last but not least, we don't seem to have dealt with reports of security > from the community. Anyway, we should have a reachable channel for that > security report :-) > > [1] https://github.com/apache/incubator-apisix/blob/master/CODE_STYLE.md > [2] > https://static.apiseven.com/2020/05/1589275276-Choosing-the-Right-Microservice-API-Gateway-for-the-Enterprise-User.pdf > [3] https://zhuanlan.zhihu.com/p/84467919 > [4] > https://apisix.iresty.com/apisix/dashboard/#/login?redirect=%2Fschema%2Froutes%2Flist > [5] https://github.com/api7/apache-apisix-python-sdk > [6] https://apisix.incubator.apache.org/security/ < > https://apisix.incubator.apache.org/security/> > > > Best Regards, > Von Gosling > > > On May 26, 2020, at 5:08 PM, Ming Wen <wenm...@apache.org> wrote: > > > > Hello community, > > > > I'd like to start a discussion about graduation as TLP for Apache > > APISIX(Incubating). > > > > The community grew quickly during Apache APISIX entry into the incubator. > > > > I've summarized some of the data below: > > - Released 6 Apache releases, through 6 different release managers > > - Invited 10 new committers (all accepted) > > - Invited 4 new PPMC members (all accepted) > > - Apache APISIX name search has been approved [1] > > - finished the Podling Maturity Assessment for APISIX, all items are > passed > > [2] > > - Our PPMC is diverse and consists of members from 10+ organizations > > - 1156 emails sent by 81 people in dev mailing-list excepted GitBox > > forwarded > > - There are 77 contributors for now > > - Resolved 360+ issues and 820+ pull requestsduring ASF incubating > > > > I think we are ready for graduation as Apache TLP. > > > > What do you think? > > > > [1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-180 > > [2] > > > https://cwiki.apache.org/confluence/display/APISIX/Podling+Maturity+Assessment+for+APISIX > > > > Thanks, > > Ming Wen, Apache APISIX & Apache SkyWalking > > Twitter: _WenMing > >
