Incorrect claim by API7

Hi, At [1], it states, "Built by the creators of Apache APISIX". 3rd parties cannot claim this as the ASF community created the project. They could say "the original creators of". Could someone on the PMC please reach out to them and have them correct this. Kind Regards, Justin 1. https://ap

Re: [VOTE] Release Apache APISIX Dashboard 2.7.1

Hi, I also think LICENSE is missing the license for this file: ./web/scripts/verifyCommit.js Thanks, Justin

Re: [VOTE] Release Apache APISIX Dashboard 2.7.1

HI, What is the issue? It looks fine to me. kind Regards, Justin

Re: [VOTE] Relase Apache APISIX Java Plugin Runner 0.1

Hi, From a quick look I think you still have far too much in the binary NOTICE file. Please see [1] in general there should be minimal licensing information in the NOTICE file and no need to mention MIT or BSD licenses. [2] Kind Regards, Justin 1. https://infra.apache.org/licensing-howto.html

Re: [VOTE] Relase Apache APISIX Java Plugin Runner 0.1

Hi, I am -1 ( binding) as the LICENSE and NOTICE is not correct and it may contain software that is not compatible with the Apache license. However the LICENSE and NOTICE file are not correct and contain way too much information and doesn’t mention what is contained in the release. e.g. [1] The

Re: [VOTE] Relase Apache APISIX Java Plugin Runner 0.1

Hi, > I want to ask from a Java developer perspective, why there is no binary in > the vote? The ASF release source code not binaries, it is totally fine for a release to not have a convenience binary. Kind Regards, Justin

Re: [VOTE][New Subproject] Establish APISIX java plugin runner

Hi, This seems a little unusual, usually a new code base would come in via a software grant and the committers voted on, initial committers are for incubating projects not TLPs. Thanks, Justin On Thu, 6 May 2021, 2:06 pm ZhengSong Tu, wrote: > Hi Dev Team: > > We would like to start a new prop

Re: [Discuss] Add GitHub bot to improve community experience

Hi, > Thanks for your recommendation, then I think we may add the "stale" > label for issues lacking interactions for more than a long while. I would suggest you don’t do this, but I’ll leave it up to the PMC. Justin

Re: [Discuss] Add GitHub bot to improve community experience

Hi, > What about adding the automatic closing stale issue? I would recommend against doing this. If you have stale issues it is most likely because you haven’t interacted with the contributor or a committer has not addressed it. And even if that’s no the case, auto closing an issue that someon

Re: [DISCUSS] Create a DockerHub repo for APISIX Dashboard

Hi, Don't forget to: a) Make clear this is an Apache project. b) Don’t publish unreleased code to the general public via DockerHub. While this deals with Incubating projects, this may help. [1] Thanks, Justin 1. https://incubator.apache.org/guides/distribution.html#docker

Re: [VOTE] ingress-controller donation

Hi, > Yes, we will sign SGA after the vote is over. > Is CCLA or ICLA also need? It’s best to get ICLA’s from all significant committers. A CCLA may be required by the committers employers but that will depend on them. Thanks, Justin

Re: [VOTE] ingress-controller donation

HI, Is there going to be a software grant to impart this after the vote is over? Thanks, Justin

Re: Podling Apisix Report Reminder - October 2020

Hi, > Apache APISIX has graduated as a top-level project. > Should we remove it from the incubator report? thanks Yes I can fix that for you, but you do need to report to the ASF board rather than the Incubator. Thanks, Justin

Re: [DISCUSS]Modify the manager-api DB from mysql to sqllite

HI, Last I looked mysql was also GPL which is not compatible with the Apache License. I assume this is an optional dependancy? Thanks, Justin

Re: [HELP]Questions about new project naming

Hi, > I want to create a new project under APISIX, I have a few questions: > > 1. Are there any restrictions on project naming? Does the name have to > contain the keyword `apisix`? While the project is called APISIX, the products don’t have to be, but it’s useful in terms of branding. When co

Re: [VOTE] Release Apache APISIX (Incubating) 1.4.1-RC1

HI, +1 (binding) I checked: - incubating in name - signatures and hashes are fine - disclaimer exists - LICENSE and NOTICE are correct - No unexpected binary files - All source files have ASF headers - Can compel from source Thanks, Justin

ApacheCon @Home 2020 call for papers closes in 2 days!

Hi, Only a couple of days to go before to call for papers closes for ApacheCon @Home 2020 on Monday. The Incubator will be running a track at this online conference, so if you're thinking of submitting something, please don't delay. We'll accept talks on the Apache incubator itself, and talks

Re: [discuss] APISIX report (June)

Hi,m > Now I am ready to apply report to Apache confluence, but I have no > permission to update report document. > Here any mentor can helps? Anyone in the APISIX PPMC can edit that area, it look like you are a committer and don’t have permission? Thanks, Justin

Re: [VOTE] Graduate Apache APISIX (incubating) as a top level project

HI, +1 and congratulations. Good luck with the incubator vote. Thanks, Justin

Re: PMC and committer list after graduation

HI, > Anything we missed? I think we should plan to call for dev ml vote. If there is I don’t think it would halt a vote. I’ve been very impressed by the way the project has handled the graduation process (without a lot of direction from it mentors) and proactively fixed any minor issues it fou

Re: [MENTORS] Invite to join the PMC team after graduation of Apache APISIX

HI, If you want me to tay on I will and help answer any question and check releases. Thanks, Justin

Re: [DISCUSS] Write an Open Source eBook:

Hi, > +1 for writing a book about the Apache APISIX. > For the License about the Open Source eBook, you may consider to use > the CC License[1] beside the code part. > There are lot of options which you can choose according to the writer needs. Just be aware that most CC licenses, while a good ch

Re: [DISCUSS] Write an Open Source eBook:

Hi, See [1] it doesn’t have to be at Apache but it might be good if it was. Perhaps consider donating it to the Apache Training project [2]? Thanks, Justin 1. https://www.apache.org/foundation/marks/#books 2. https://training.apache.org

Re: [VOTE] Release Apache APISIX (Incubating) 1.3-RC1

Hi, The issue is as Sheng pointed out. > The key issue is, as a release tar, the LICENSE file in the root folder is > the `primary` license. I know you have put the MIT license in the dashboard > folder, but you missed the pointer in the primary license. Yep this is the issue. All that needs to

Re: [VOTE] Release Apache APISIX (Incubating) 1.3-RC1

Hi, Sorry but its -1 (binding) from me I checked: - incubating in name - DISCLAIMER is OK - LICENSE is missing licensing information - NOTICE is fine - No unexpected binary files - ASF file have ASF headers There is a 40 odd files with "Copyright (c) 2018 Chong Guo” in the dashboard which seems

Re: [DISCUSS] bi-weekly online video meeting

Hi, > `bi-weekly` means having one every 2 weeks. It can also confusingly mean twice a week. Here in Australia it usually means twice a week and fortnightly once every two weeks,. Justin

Re: [DISCUSS] bi-weekly online video meeting

Hi, It a good idea in these times. Just take care that it doesn’t replace communication on this list and anything discussed is brought back to this list so that those who are unable to attend (due to for example their time zone) can participate as well. Thanks, Justin

Re: [VOTE] Release Apache APISIX (Incubating) 1.2-RC1

Hi, +1 (binding) I checked: - incubating in name - signatures and hash fine - DISCLAIMER exists - LICENSE and NOTICE all good - All source files have ASF headers - No unexpected binary files - I didn’t;t compile form source (environment not set up) Thanks, Justin

Re: [DISCUSS] Draft of Podling Maturity Assessment for APISIX

HI, > both of them[3]. I've added instructions for the apache release, as well as > a developer-only tip for master. > please take a look. thanks. What version is latest pointing to there? it a little unclear to me. By default a user should get the last released version not what is in master. T

Re: [DISCUSS] Draft of Podling Maturity Assessment for APISIX

Hi, > we use `luarocks` to manage dependencies and compile C libraries, and use > travis as the continuous integration tool. Which is fine but what about your users? > releases are cut from github repository. All releases are tagged and > archived: https://github.com/apache/incubator-apisix/rele

Re: [DISCUSS] Draft of Podling Maturity Assessment for APISIX

Hi, Some feedback: CD30 - You may of misunderstood this question, while having CI is a good think , not all users would want to use Jenkins to compile the software. CD40 - Releases should also be archived. Are they currently and if so where? RE40 - I think there may be an issue here, it not clear

Re: [Sign Off the Report] [Mentors] Podling Apisix Report - April 2020

Hi, You can just use one of these links and it should take you to the latest report: https://s.apache.org/incubator-report https://cwiki.apache.org/confluence/display/INCUBATOR/Report Thanks,

Re: Podling Apisix Report - April 2020 [ 3rd draft ]

Hi, > "elected a new PPMC @Sheng Wu member who helped us a lot on the mail list” Opps, even I got that one wrong try this instead: "elected a new PPMC member @Sheng Wu who helped us a lot on the mail list” Thanks, Justin

Re: Podling Apisix Report - April 2020 [ 3rd draft ]

Hi, You should say “PPMC member” when referring to an individual, and say PPMC when referring to the whole committee. For example: "we also elected first non-initial PPMC member @lilien1010.” "we also elected @Sheng Wu ( from the PMC of Apache Skywalking ) as a member of our PPMC” "elected a ne

Re: APISIX Incubator page has broken links and some status are missing

Hi, You may also want to check: https://incubator.apache.org/clutch/ https://whimsy.apache.org/pods/ Thanks, Justin

Re: Podling Apisix Report - April 2020

Hi, Good to see the report being worked on early. > ### How has the community developed since the last report? > > - We have some talks about how to build a good dashboard for impoving > easiness of using Apache APISXI APISIX I think you mean :-) > , Mar 14th. Then it can make more users quick

Fwd: New JIRA project created: APISIX

Created as requested. > Hi there, > As requested by jmcl...@apache.org, a new JIRA project has been set up at: > https://issues.apache.org/jira/browse/APISIX > > URL: http://apisix.apache.org > Name/Description: Cloud-native microservices API gateway. > Lead: jmclean > > > > > With regards, >

Re: [ANNOUNCE] SkyWalking Nginx LUA 0.1.0 test build available

Hi, > BTW, this is not APISIX thing, I just forward a mail to this channel, as > there is an integration work here. I realise that, I just want to make sure that APISIX knows the right process. Thanks, Justin

Re: [ANNOUNCE] SkyWalking Nginx LUA 0.1.0 test build available

Hi, > If the test fails, there will be no vote for this. We are making sure the > release feature quality. Announcements should only be made for released software, otherwise users could be confused and download it. It probably would be better to make a release candidate. Some projects make a R

Re: [ANNOUNCE] SkyWalking Nginx LUA 0.1.0 test build available

Hi, I don’t see a vote for this release, the ANNOUNCE come after the VOTE has passed. Thanks, Justin

Re: Some minor issues with the download page

Hi, Thanks for that. Justin

Some minor issues with the download page

Hi, I noticed a couple of minor issue with the download page [1], links to ,asc or .sha512 need to go via https://www.apache.org/dist/ or https://archive.apache.org/dist. [2] Links that need to change: http://www.apache.org/dist/incubator/apisix/0.9/apache-apisix-0.9-incubating-src.tar.gz.asc

Re: [help] need help from mentor to add me to Apache APISIX podling.

HI, > I asked help from Secretsry, He said that mentor from APISIX PPMC > should be able to get me added to the correct podling. I’ve added you to the roster. Thanks, Justin

Re: [VOTE] Release Apache APISIX (Incubating) 1.1-RC1

Hi, +1 (binding) I checked: - incubating in name - signatures and hashes are fine - disclaimer exits - license and notice are fine - no unexpected binary files - all files have ASF headers - didn’t try to compile from source Git tags are changeable, btw some releases, for variously reasons e.g.

Re: [VOTE] Release Apache APISIX Dashboard (Incubating) 1.0-RC2

Hi, +1 (binding) I checked: - incubating in name - signatures and hashes are fine - disclaimer exits - no unexpected binary files - all ASF files have ASF headers - can compile from source Thanks, Justin

Re: [VOTE] Release Apache APISIX Dashboard (Incubating) 1.0-RC1

Hi, The KEYS file is now fine. However i’m still -1 due to Category X dependancies, can you explain the below? While this is being sorted out you could make a release with the work in progress disclaimer noting this issue. However I installed this [1] and running this: license-checker --produc

Re: [VOTE] Release Apache APISIX Dashboard (Incubating) 1.0-RC1

Hi, -1 (binding) no public key and key not in [1] (Note this is easily fixed and there’s no need to cancel the vote) I checked: - incubating in name - signature not able to be verified, hash fine - DISCLAIMER exists - LICENSE is fine - NOTICE has wrong year - All source files have ASF headers -

Re: [RESULT] [VOTE] Release Apache APISIX (Incubating) 1.0-RC2

Hi, > yuu can not announce the vote result before vote in the > gene...@incubator.apache.org. You can on the project list that fine, and in fact having a summary for tweet IPMC to look at is a good idea. You just need to make it clear that it passed the PPMC vote and not the IPMC one. This vot

Re: [DISCUSS] My way to enable tls 1.3 cipher suites with apisix

Hi, Please read [1] as heir may be implications here. Thanks, Justin 1. https://www.apache.org/dev/crypto.html

Re: [VOTE] Release Apache APISIX (Incubating) 1.0-RC2

Hi, +1 (binding) I checked: - incubating in name - DISCLAIMER exists - LICENSE and NOTICE are good - No unexpected binary files - All source files have ASF headers - had an issue compile but probably my setup / I don’t know what I’m doing / don’t have all dependancies Thanks, Justin

Re: add a free and available IP library to APISIX, what do you think about GeoIP2?

Hi, > Back to Justin's question, GeoIP2 also provides the geolite2 version[2], > which is under the Creative Commons Attribution-Share Alike 4.0 license. > So if Apache APISIX wants to support GeoIP2, We need to clearly indicate > its geoip2 and geolite2 version in the document. Right, there are

Re: add a free and available IP library to APISIX, what do you think about GeoIP2?

Hi, > We only provide GeoIP2 driver code, APISIX users should fetch the IP > database by himself if they want to enable the IP location feature. > > So I think that is fine for the license. Perhaps / perhaps not - it will depend on how this is done and how the user is informed. [1] Thanks, Jus

Re: [VOTE] Release Apache APISIX (Incubating) 1.0-RC1

Hi, > Because of this bug, we have to cancel this vote and release 1.0-rc2 later. > Sorry for this mistake. It's fine to release stuff with minor issues, bugs like this can be fixed in the next release. Thanks, Justin

Re: [VOTE] Release Apache APISIX (Incubating) 1.0-RC1

Hi, +1 (binding) Please fix the NOTICE year for the next release. I checked: - incubating in name - signatures and hashes are fine - Disclaimer exists - LICENSE is good - NOTICE has wrong year please fix - no unexpected binary files - all source file have ASF headers - can compile from source Th

Re: add a free and available IP library to APISIX, what do you think about GeoIP2?

Hi, > Add a free and available IP library to APISIX, what do you think about > GeoIP2? My reading of that page is that you would need a commercial license and that would mean it's not compatible with the Apache License. Thanks, Justin

Re: [VOTE] Release Apache APISIX (Incubating) 1.0-RC1

Hi, Just a note only IPMC members are actually binding on incubator releases, but it’s expected that you get 3 +1 PPMC votes on the dev list vote. Thanks, Justin

[MENTORS] Report formatting issues

Hi, We had a large number of reports that needed manual editing to fix formatting issues this month. Podlings that required to most changes have been BCCed. Please try and follow teh instructions at the top of the page and and keep the formatting consistent. II’s best to follow what is below:

Re: [DISCUSS] The quarterly report of December

> > > Hi, > > - We have solved the APISIX brand issues in the documentation, code, > website, etc. > I think it is too early to say this. Again a quick Google search shows some minor issues. This needs to be ongoing work by the PPMC. Thanks, Justin >

Re: [LICENSE] question about apisix-dashboard

. > > > > [1] vue-typescript-admin-template > > <https://github.com/Armour/vue-typescript-admin-template> > > [2] https://github.com/apache/incubator-apisix-dashboard > > > > Best Regards! > > @ Zhiyuan Ju <https://www.shaoyaoju.org/> > > > >

Re: [LICENSE] question about apisix-dashboard

Hi, A couple of questions: - where did this this code [1] come from? - A large number of files (40 odd) are Copyright 2018 Chong Guo is this correct? That more files than have ASF licenses. Thanks, Justin 1. ./src/styles/*.scss

Re: [LICENSE] question about apisix-dashboard

Hi, > Could you help to give some advice about the incoming release of this > dashboard? I’ll take a look, but can you point me a release candidate or similar that I can check? It not really possible to check a report as what goes into a release may be different. Thanks, Justin

Re: about Apache APISIX brand management

Hi, > Currently this package manager uses my personal account. If Apache APISIX > graduates, is there a problem here? Any specific comments? Yes all of the PMC should have access OR is clear that this is not related to the project. > > Here is the home page of APISIX in Luarocks: > https://lu

Re: [DISCUSS] First draft version of Apache APISIX of PMC report for December 2019

Hi, > thanks for your detailed search. It only took a few minutes, which is why I raised the concern. > To sum up, these issues can be handled quickly and properly without > external dependencies. Which is great, but the issue is this wasn’t reflected in the report which said there were no iss

Re: [DISCUSS] First draft version of Apache APISIX of PMC report for December 2019

HI, > I've post the Apache APISIX PMC report for December 2019 at the ASAP wiki > page: > https://cwiki.apache.org/confluence/display/INCUBATOR/December2019#apisix > . You need to list 3 most important things that you n

Re: [DISCUSS] First draft version of Apache APISIX of PMC report for December 2019

Hi, Thanks for the detailed report, some comments have already been posted so I’ll just mention one other thing. > - Supported to run apisix based on alibaba [Tengine][1]. Why is this important for this Apache project? I see no mention of the Apache project at that repo. Thanks, Justin

Re: Podling Apisix Report Reminder - December 2019

Hi, Is this report being worked on? It ben to wrk on it in the open and get input from everyone well before the due date. Thanks, Justin

Re: [VOTE] Release Apache APISIX (Incubating) 0.9-RC1 ROUND 2

Hi, +1 (binding) This should probably be called RC2 (RC stands for release candidate). Putting it in the same spot as the previous one can be confusing. I checked: - incubating in name - signatures and hashes fine - DISCLAIMER exists - LICENSE and NOTICE good - no unexpected binary files in rel

Re: [apache/incubator-apisix] bug: APISIX v0.8 doesn't support the Stand-alone mode, need fix the doc. (#838)

Hi, > Anyway, I always advise you to use the latest version of APISIX. > The latest version of APISIX is 0.8, please do not point users to unreleased code. Thanks, Justin

Re: [VOTE] Release Apache APISIX (Incubating) 0.9-RC1

Hi, > These files are from the compiled dashboard code. > I think that APISIX can no longer contain compiled dashboard code, but > instead guides the user to compile the dashboard from source, > and it will solve the license problem. That's a solution, but then you would need to release it as wel

Re: [incubator-apisix] branch master updated: change: update v0.9.0-rc1 changelog. (#832)

Hi, > +## 0.9.0-RC1 > +> Released on 2019/11/11 A minor thing but RCs are not released, it's a release candidate and only voted on release candidates are released, when that is done the RCX part is dropped. The heading here should probably be 0.9.0 dropping the RC1. Thanks, Justin

Re: [VOTE] Release Apache APISIX (Incubating) 0.9-RC1

HI, -1 (binding) due to missing license information and unable to compile the source release. This -1 vote may have been avoided if you had used the work in progress DISCLAIMER. [1] When maligning a release anything minded in the release needs to listed in LICENSE, this is ofter referred to as

Re: [DISCUSS] Building a plugin ecosystem for Apache APISXI

Hi, > If these features are merge into APISIX, they > may cause problems for other users and increase the work of maintainers. How is this the case? Doing the development in the open at the ASF generally mean the quality is higher and their as less issues, it also means you have a large pool o

Re: [LICENSE] question about apisix-dashboard

Hi, The LICENSE and NOTICE need to reflect what is in the release, if the code is not bundled then there no need to add it to LICENSE (or NOTICE). If the dashboard is not included then there no need to add it’s license (which with be ALv2 anyway). Thanks, Justin

Re: [DISCUSS] Building a plugin ecosystem for Apache APISXI

Hi, > I do agree with the idea to make the non-core plugins out of APISIX repo, > since users requirements are always different , if the plugin numbers keep > growth, the APISIX become heavy ,which is not what we wanted. You do realise you don’t have to put everything in one repo or release

Re: [DISCUSS] Building a plugin ecosystem for Apache APISXI

Hi, This approach can b tricky for a project to manage and several projects who have done so have run into branding and trademark issues and issues with community growth.In a few cases this has stopped a project from graduating and has been a lot of work to correct. I can go into a little more

Re: [LICENSE] question about apisix-dashboard

Hi, > Then should we use the original repo MIT License[1]? I would suggest so yes. > Also, if we could change the package.json file's contents such as author, > name, repository [2]? Well is not long that package I assume so that will have to change, the other it depends if it referring to the

Re: [Sign Off the Monthly Report] [Mentors] Apache APISIX of PMC report for November 2019

Hi, I notice this question and it's answer is missing: Are there any issues that the IPMC or ASF Board need to be aware of? Can you please add it. Thanks, Justin

Re: [LICENSE] question about apisix-dashboard

Hi, > 3. start developing: create our needed files or modify existing files; You'll need to distinguish between the files you have created and their files. I would suggest adding a MIT header to their files to make it clear where they are from and that they are not ALv2. If you have headily mo

Re: [LICENSE] question about apisix-dashboard

HI, > This repository[1] is a kind of Vue.js scaffolds, under MIT License, and we > can use this repository's rich components to build Dashboard :) I’m still a little confused if file from this repo have been copied to one of our repos or it is just been used as a dependancy. Thanks, Just8in

Re: [LICENSE] question about apisix-dashboard

Hi, > The incubator-apisix-dashboard repo is using one template which is under > MIT License, so we'd like to know which license is suitable for the > incubator-apisix-dashboard-built repo? If the release contains something under the MIT license, then you leave the header as MIT, and you add the

Re: [LICENSE] question about apisix-dashboard

Sorry for bad autocorrect in my last message. It depends on who owns the IP of the file. You should never remove or replace a 3rd party header from a file without their permission even if you have made changes. On Tue, 5 Nov 2019, 11:33 Justin Mclean, wrote: > Hi, > It celebs who the

Re: [LICENSE] question about apisix-dashboard

hanged > files should remove our ALv2 header and all significant > changes files will be added the ALv2 header, and the repo will keep the > MIT License? > > Justin Mclean 于 2019年11月4日周一 22:25写道： > > > Hi, > > > > > I have two issues about the dash

Re: [LICENSE] question about apisix-dashboard

Hi, > I have two issues about the dashboard license so far I replied to this before. > 1. The first one is the question mentioned in the email above： >how to deal with the license for frontend production build files in > incubator-apisix-dashboard-built [1]? It ALv2 in an apache repo so wha

Re: [DISCUSS] dockerhub image not updated,should we keep it updated with master branch?

Hi, >As we can see from dockerhub, when I search apis,it still the old version. >Is there any way to automatically push image to dockerhub use master > branch? This would not be possible as only releases approved by the (P)PMC are allowed to be distributed to the general public. It wou

Re: [LICENSE] question about apisix-dashboard

Hi, > I think we need to spend more time to fix dashboard license issues, What issue exists here? Thanks, Justin

Re: Review of PRs

Hi, > This is because he reviewed the PR and requested a change. > > After resolving these issues, we need him to confirm that the changes are > correct. Is this workflow documented anywhere on the website? How would someone new to teh project find this out? Thanks, Justin

Review of PRs

HI, I’m notice a lot of PRs with "@moonming please take a look” or words rot that effect, why is this? Thanks, Justin

Re: [incubator-apisix] branch master updated: Bugfix: change dir apisix into incubator-apisix (#762)

Hi, > Apache APISIX can be installed via Luarocks automatically, but the Luarocsk > cannot fetch the folder dashboard, because of it is a git submodule. > > That is why we have to call "git clone" again. This is not allowed as you are directing users to unreleased source code, they can only be

Re: [GitHub] [incubator-apisix-docker] moonming commented on a change in pull request #30: Simplify the docker run documentation and run quickly with docker-com…

Hi, > +$ docker pull iresty/apisix:latest > > Review comment: > we will upload the image to Apache later. Take case that you don’t pull the latest from master, but only the last released version. Thanks, Justin

Re: [DISCUSS] Some questions about quarterly reports

Hi, > 2.How has the community developed since the last report? > > - Github stars grew from 800+ to 1201 in October. Why would the IPMC or board care about this? Being popular is not the same as community growth. > - Over 13 company users have announced that he is using APISIX: > https://githu

Re: [incubator-apisix] branch master updated: Bugfix: change dir apisix into incubator-apisix (#762)

Hi, I sort of curious what this makefile is being used for. I can see it’s checking out the master branch from GitHub, is there a reason why you would do this when you already have the code? Thanks, Justin

Re: [Task] deploy Apache APISIX's website

Hi, > We have set disclaimer at the bottom-left on our site :) Oh yes hidden right at the very bottom :-) > Also, the link of the GitHub button at the home center has been updated to > https://github.com/apache/incubator-apisix. Which I think misses the point I was trying to make. The first thi

Re: [Task] deploy Apache APISIX's website

Hi, Don’t forget to add the incubating disclaimer to your website. Thanks, Justin

Re: [DISCUSS] Some questions about quarterly reports

Hi, > But I don't know how to answer question 1. I hope everyone can put forward > their own opinions. You just need to list the three most important thing that are currently stopping you from graduating. For a project starting out they are typically: - Make a release - Create an Apache website

Re: [Task] deploy Apache APISIX's website

Hi, Thanks for that, I see what is being done and where it come from. What does the PPMC plan to do about the Github button? Thanks, Justin

Re: [Task] deploy Apache APISIX's website

Hi, I can see that the website prominatly links to GitHub. You really only want to direct developers to GitHub, users should not be directed to unreleased code. I can see that the Apache Github states "Cloud-Native Microservices API Gateway https://www.iresty.com”. Can someone explain the relat

Re: [DISCUSS] I want to be the release manager for Apache APISIX 0.9 RC-1

Hi, The incubator also has a check list.[1] If you have any 3rd party code in your source release you need to follow this. [2] If you need any help just ask. Thanks, Justin 1. https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist 2. http://www.apache.org/dev/licen

Re: [DISCUSS] container first

Hi, We’re still waiting on “official” guidelines on how to use docker at the ASF, but many project so use it and comply with ASF release and distribution policies. The incubator has these draft guidelines that might help [1], but if you want to do it differently to that just discussion it on

Re: [DISCUSS] container first

Hi, > Very clear explain, Justin, thanks. If you wonder why this is this way it is so that: 1) The ASF legal shield covers the people involved in making a releases. 2) Users who use an ASF product have confidence that they can use it and not run into any legal issues. See [1] for more explanati

Re: [DISCUSS] Share a site about commit specification

Hi, > Happy to be that we use a squash based workflow as this link says[3], and > only collaborators have access to Squash & Merge PR into the master branch. Who do you mean by collaborators? Only project committers will have access to the master branch. Thanks, Justin

  1   2   >