Re: [VOTE] Release Apache Liminal (incubating) 0.0.2rc1-INCUBATING

2021-04-21 Thread Lior Schachter
Hi Ash / Justin, This is indeed a very delicate issue. From my experience in several M/DD processes, LGPL license is very tricky and the approach suggested by Ash is the approach I'm familiar with. Both in Java & Python LGPL is very common and taking a stricter approach might result in a ripple

Re: [VOTE] Release Apache Liminal (incubating) 0.0.2rc1-INCUBATING

2021-04-21 Thread Ash Berlin-Taylor
Hi Aviem, Hi everyone, Airflow PMC here. First off, eek. Not sure how this happened, it's been like this for a while. I agree -- we could possibly fix the direct dependency on requests/chardet in Airflow, but as you have already discovered there are many more python libraries that depend upon

Re: [DISCUSS] Incubating Proposal of Shenyu

2021-04-21 Thread kezhenxu94@apache
In addition to Sheng’s list, I’ll also suggest the community to reconsider the project name “ShenYu”, because from a quick search, there are several potential branding / trademark conflicts, such as [1], [2], and [3]. Note that there is no official Chinese names for ASF Projects so you won’t have

Re: [VOTE] Release Apache Liminal (incubating) 0.0.2rc1-INCUBATING

2021-04-21 Thread Justin Mclean
Hi, > Meanwhile what do we do regarding releases of our artifacts? I would use a WIP DISCLAIMER and not it as an issue, that’s a short term solution, but it will enable you to get a release out. Kind Regards, Justin - To

Re: [VOTE] Release Apache Liminal (incubating) 0.0.2rc1-INCUBATING

2021-04-21 Thread Aviem Zur
We can try to reach out. It looks like `chardet` can't change their license and `requests` have a won't fix / no time to fix attitude towards it. Meanwhile what do we do regarding releases of our artifacts? I don't see how we can develop a python project without having an indirect dependency on

Re: [VOTE] Release Apache Liminal (incubating) 0.0.2rc1-INCUBATING

2021-04-21 Thread Justin Mclean
Hi, Sorry I’m not sure what to suggest. Normally I’d say contact the project and ask if they would be willing to distribute the library under another license e.g. dual license it under LGPL and ALv2 but this seem unlikely [1]. I guess it wouldn't hurt to ask again. Kind Regards, Justin 1.

Re: [VOTE] Release Apache Liminal (incubating) 0.0.2rc1-INCUBATING

2021-04-21 Thread Aviem Zur
We declare exactly 9 dependencies in our requirements.txt docker==4.2.0 apache-airflow==1.10.12 click==7.1.1 Flask==1.1.1 pyyaml==5.3.1 boto3==1.12.10 botocore==1.15.21 kubernetes==12.0.1 wheel==0.36.2

Re: [DISCUSS] YunionCloud Proposal

2021-04-21 Thread Juan Pan
Hi, This discussion is a nice start for the open-source community building. I left my preference in that issue, hope it goes well. :) --- Email:panj...@apache.org Juan Pan(Trista) Apache ShardingSphere On 04/19/2021 11:47,Jian Qiu wrote:

Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc05

2021-04-21 Thread Justin Mclean
Hi, > Thanks for voting. I will fix [4][5][6]. But I still don’t know how to > write a notice file Please follow [1]. Note that MIT and BSD software do not need to be listed in NOTICE and ALv2 software only need to be there if it has a NOTICE file and you need to take what is relevant from

Re: [VOTE] Release Apache Doris 0.14.0-incubating-rc05

2021-04-21 Thread 寒江雪
Hi Justin Thanks for voting. I will fix [4][5][6]. But I still don’t know how to write a notice file. I have referred to some graduated projects, such as impala, kudu, airflow, and the notice files in their projects are very similar to ours. Can you give an example of a notice file? Justin