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

[Liang Chen]

+1(binding), i checked : 
  - incubating in name 
  - Signatures and hashed good 
  - DISCLAIMER exists 
  - LICENSE is fine 
  - NOTICE is fine
  - source file have ASF headers 
  - No unexpected binary files 

Regards
Liang


Nirojan Selvanathan wrote
> Hello everyone,
> 
> This is a call for the vote to release Apache APISIX (Incubating) version
> 1.4-RC1.
> 
> The Apache APISIX community has voted on and approved a proposal to
> release Apache APISIX (Incubating) version 1.4-RC1.
> We now kindly request the Incubator IPMC members review and vote on
> this incubator release.
> 
> Apache APISIX is a cloud-native microservices API gateway, delivering the
> ultimate performance, security, open-source and scalable platform for all
> your APIs and microservices.
> Apache APISIX is based on Nginx and etcd, it has dynamic routing and
> plug-in hot loading, which is especially suitable for API management under
> the micro-service system.
> 
> Apache APISIX community vote and result threads:
> https://lists.apache.org/thread.html/r3304413b3d69f8d388c9f42714616776d6148f7eb674794861edc790%40%3Cdev.apisix.apache.org%3E
> 
> Release notes:
> https://github.com/apache/incubator-apisix/blob/v1.4/CHANGELOG.md#140
> 
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/
> 
> Git tag for the release:
> https://github.com/apache/incubator-apisix/tree/v1.4
> 
> Release Commit ID:
> https://github.com/apache/incubator-apisix/commit/f7584f680697179f5af44dbff5e26ad25cb860e8
> 
> Keys to verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS
> 
> Steps to validating the release:
> 
> 1. Download the release
> ```
> wget
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz
> ```
> 
> 
> 2. Checksums and signatures
> ```
> wget https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS
> wget
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz.asc
> wget
> https://dist.apache.org/repos/dist/dev/incubator/apisix/1.4-rc1/apache-apisix-1.4-rc1-incubating-src.tar.gz.sha512
> 
> shasum -c apache-apisix-1.4-rc1-incubating-src.tar.gz.sha512
> gpg --import KEYS
> 
> # input `trust`, `5`, then `save`
> 
> gpg --edit-key "Nirojan Selvanathan"
> gpg --verify apache-apisix-1.4-rc1-incubating-src.tar.gz.asc
> apache-apisix-1.4-rc1-incubating-src.tar.gz
> ```
> 
> 3. Unzip and Check files
> ```
> tar zxvf apache-apisix-1.4-rc1-incubating-src.tar.gz
> ```
> 
> 4. This release contains the dashboard code for APISIX
> https://github.com/apache/incubator-apisix-dashboard/tree/329b092dcaa7a505dcdec86c667b6803f5863d94
> 
> 
> 5. Build Apache APISIX:
> https://github.com/apache/incubator-apisix/blob/v1.4/doc/how-to-build.md
> 
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
> 
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> Checklist for reference:
> [ ] Download links are valid.
> [ ] Checksums and PGP signatures are valid.
> [ ] DISCLAIMER is included.
> [ ] LICENSE and NOTICE files are good.
> [ ] No binary file.
> [ ] All files have license headers if necessary.
> 
> And below is a more detailed checklist:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> 
> -- 
> Best Regards,
> S.Nirojan
> Linked-in https://www.linkedin.com/in/niroselva/;





--
Sent from: http://apache-incubator-general.996316.n3.nabble.com/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Sheng Wu]

+1 binding

Glad to see the potential dependency license issue fixed.
Good luck.

Sheng Wu 吴晟
Twitter, wusheng1108


Sheng Wu  于2020年6月28日周日 下午4:33写道：

> Hi Yuansheng
>
> Thanks for fixing this quickly.
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
> YuanSheng Wang  于2020年6月28日周日 下午4:22写道：
>
>> Many thx for you. I have updated the two repositories
>> `lua-resty-radixtree`
>> and `jsonschema`.
>>
>> radixtree v1.9: Apache 2.0 License
>> jsonschema 0.8: MIT license
>>
>> ^_^
>>
>>
>> On Sun, Jun 28, 2020 at 4:16 PM Justin Mclean 
>> wrote:
>>
>> > Hi,
>> >
>> > > I talked with the people of api7, they have updated the license, the
>> GPL
>> > > part has been removed. It should be better now.
>> >
>> > Thanks for doing that, much appreciated.
>> >
>> > Justin
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> >
>> >
>>
>> --
>>
>> *MembPhis*
>> My GitHub: https://github.com/membphis
>> Apache APISIX: https://github.com/apache/incubator-apisix
>>
>

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

[Sheng Wu]

Hi Yuansheng

Thanks for fixing this quickly.

Sheng Wu 吴晟
Twitter, wusheng1108


YuanSheng Wang  于2020年6月28日周日 下午4:22写道：

> Many thx for you. I have updated the two repositories `lua-resty-radixtree`
> and `jsonschema`.
>
> radixtree v1.9: Apache 2.0 License
> jsonschema 0.8: MIT license
>
> ^_^
>
>
> On Sun, Jun 28, 2020 at 4:16 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > I talked with the people of api7, they have updated the license, the
> GPL
> > > part has been removed. It should be better now.
> >
> > Thanks for doing that, much appreciated.
> >
> > Justin
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> --
>
> *MembPhis*
> My GitHub: https://github.com/membphis
> Apache APISIX: https://github.com/apache/incubator-apisix
>

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

[YuanSheng Wang]

Many thx for you. I have updated the two repositories `lua-resty-radixtree`
and `jsonschema`.

radixtree v1.9: Apache 2.0 License
jsonschema 0.8: MIT license

^_^


On Sun, Jun 28, 2020 at 4:16 PM Justin Mclean 
wrote:

> Hi,
>
> > I talked with the people of api7, they have updated the license, the GPL
> > part has been removed. It should be better now.
>
> Thanks for doing that, much appreciated.
>
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 

*MembPhis*
My GitHub: https://github.com/membphis
Apache APISIX: https://github.com/apache/incubator-apisix

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

[Justin Mclean]

Hi,

> I talked with the people of api7, they have updated the license, the GPL
> part has been removed. It should be better now.

Thanks for doing that, much appreciated.

Justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Sheng Wu]

Hi Justin

I talked with the people of api7, they have updated the license, the GPL
part has been removed.
It should be better now.

Sheng Wu 吴晟
Twitter, wusheng1108


Justin Mclean  于2020年6月28日周日 下午4:04写道：

> Hi,
>
> > These two dependencies are designed and implemented specifically for
> Apache
> > APISIX,
> > and will always keep the Apache 2.0 license for Apache APISIX.
> > At the same time, we don't want just use these two dependencies instead
> of
> > Apache APISIX as a whole,
> > so we've set up a dual licenses.
> > For Apache APISIX, I don't think there is a license issue because both
> are
> > the Apache 2.0 license.
> > If I'm wrong, please correct me and we can fix it.
>
> My concern is that with other Apache licensed projects anyone  can take
> that code and re-use it in their own project. Now these are dependancies
> but if someone took part of APISIX and reused in their own project (so it’s
> no longer APISIX) with these some dependancies does this license allow them
> to do that?
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

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

[Justin Mclean]

Hi,

> These two dependencies are designed and implemented specifically for Apache
> APISIX,
> and will always keep the Apache 2.0 license for Apache APISIX.
> At the same time, we don't want just use these two dependencies instead of
> Apache APISIX as a whole,
> so we've set up a dual licenses.
> For Apache APISIX, I don't think there is a license issue because both are
> the Apache 2.0 license.
> If I'm wrong, please correct me and we can fix it.

My concern is that with other Apache licensed projects anyone  can take that 
code and re-use it in their own project. Now these are dependancies but if 
someone took part of APISIX and reused in their own project (so it’s no longer 
APISIX) with these some dependancies does this license allow them to do that?

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Distribution guidelines for other platforms

[Justin Mclean]

Hi,

> The name on Pipy could be  https://pypi.org/project/apache- to
> keep consistent with other platforms.
> 
> The name on NPM has the same issue.

As long as it clear it’s an Apache project (for releases made by the PPMC) then 
any similar variations is fine.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Release Apache DolphinScheduler (Incubating) 1.3.0

[leon bao]

Hi all,

We are glad to announce the release of Apache DolphinScheduler(incubating)
1.3.0. Once again I would like to express my thanks to your help.

Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow
scheduling system,
dedicated to solving the complex dependencies in data processing, making
the scheduling system out of the box for data processing.

   Vote Thread Permalink:


https://lists.apache.org/thread.html/r857ec990603ec2a4487db5ce9de0614e757a51e6235fd584953bc8c6%40%3Cdev.dolphinscheduler.apache.org%3E


https://lists.apache.org/thread.html/r25253f39e2b2de1ea22cb445f940d1266c2c7f782a5fb1aa6f818e6d%40%3Cgeneral.incubator.apache.org%3E




Download Links:
https://dolphinscheduler.apache.org/en-us/docs/release/download.html

Release Notes:
https://github.com/apache/incubator-dolphinscheduler/releases/tag/1.3.0

Website: https://dolphinscheduler.apache.org/

DolphinScheduler Resources:
- Issue: https://github.com/apache/incubator-dolphinscheduler/issues/
- Mailing list: d...@dolphinscheduler.apache.org
- Documents:
https://github.com/apache/incubator-dolphinscheduler/blob/1.3.0/README.md

-- 
DolphinScheduler(Incubator)  PPMC
BaoLiang 鲍亮
leon...@apache.org

Re: [DISCUSS] Distribution guidelines for other platforms

[Xiangdong Huang]

Hi,

> The name on Pipy could be  https://pypi.org/project/apache- to
keep consistent with other platforms.

Sorry I mean, to keep consistent with current released projects [1].

[1] https://pypi.org/search/?q=apache

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Xiangdong Huang  于2020年6月28日周日 下午3:45写道：

> Hi Justin,
>
> The name on Pipy could be  https://pypi.org/project/apache- to
> keep consistent with other platforms.
>
> The name on NPM has the same issue.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Justin Mclean  于2020年6月28日周日 下午2:31写道：
>
>> Hi,
>>
>> > I have a question regarding the nature of the document and the vote. I
>> see
>> > that the title for this document is "Distribution Guidelines". Do you
>> > intend to have this document considered as a distribution policy?
>>
>> Yes it’s policy but podlings can ask for exceptions or come up with their
>> own ways of distributing releases that also follow ASF policy.
>>
>> > If so, why isn't the existing Apache policies regarding distribution
>> sufficient so
>> > that the incubator needs to impose additional distribution policy that
>> > top-level projects are not subject to?
>>
>> It doesn’t impose anything more than current ASF policy, it just
>> clarifies a few things and puts them in context. Currently distribution
>> policy is missing context of other platforms that software is now
>> distributed on. I have just asked for some clarification on that. All TLP
>> should be doing similar things to what is mentioned here, with the
>> exception of the incubator disclaimer. See may of come up with other ways
>> to comply with ASF policy.
>>
>> > If the document is not intended as a policy, but as a guide for podlings
>>
>> All ASF policies are guidelines. If you want to do something differently
>> than what is in a policy ask the incubator or board.
>>
>> > In addition, I was hoping to find past discussions on this draft
>> document.
>> > Unfortunately, I wasn't able to find any on this list with the document
>> > link.
>>
>> This has been discussed before and input from legal and others were taken
>> into consideration. I’ll see if I can find those conversations for you.
>>
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [DISCUSS] Distribution guidelines for other platforms

[Xiangdong Huang]

Hi Justin,

The name on Pipy could be  https://pypi.org/project/apache- to
keep consistent with other platforms.

The name on NPM has the same issue.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Justin Mclean  于2020年6月28日周日 下午2:31写道：

> Hi,
>
> > I have a question regarding the nature of the document and the vote. I
> see
> > that the title for this document is "Distribution Guidelines". Do you
> > intend to have this document considered as a distribution policy?
>
> Yes it’s policy but podlings can ask for exceptions or come up with their
> own ways of distributing releases that also follow ASF policy.
>
> > If so, why isn't the existing Apache policies regarding distribution
> sufficient so
> > that the incubator needs to impose additional distribution policy that
> > top-level projects are not subject to?
>
> It doesn’t impose anything more than current ASF policy, it just clarifies
> a few things and puts them in context. Currently distribution policy is
> missing context of other platforms that software is now distributed on. I
> have just asked for some clarification on that. All TLP should be doing
> similar things to what is mentioned here, with the exception of the
> incubator disclaimer. See may of come up with other ways to comply with ASF
> policy.
>
> > If the document is not intended as a policy, but as a guide for podlings
>
> All ASF policies are guidelines. If you want to do something differently
> than what is in a policy ask the incubator or board.
>
> > In addition, I was hoping to find past discussions on this draft
> document.
> > Unfortunately, I wasn't able to find any on this list with the document
> > link.
>
> This has been discussed before and input from legal and others were taken
> into consideration. I’ll see if I can find those conversations for you.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[RESULT][VOTE] Release Apache IoTDB 0.10.0

[Xiangdong Huang]

Hi,

The vote to release Apache IoTDB (incubating) 0.10.0 has passed with 4 +1
binding votes.

binding votes:

- Justin Mclean

- Julian Feinauer,

- Christofer Dutz,

- Willem Jiang,


Vote thread:


https://lists.apache.org/thread.html/ra47ec531af1422c8a5e3798dcc74d1c07a9b9793c86886aa4e494677%40%3Cgeneral.incubator.apache.org%3E


There are another 14 +1 non-binding votes on d...@iotdb.apache.org mailing
list before calling this vote.


Thank you to all IPMC members for taking the time to review and
provide guidance on our release!

We will proceed with publishing the approved artifacts and sending out the
appropriate announcements in the coming days.

On behalf of the Apache IoTDB Community,

Xiangdong Huang

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

[Sheng Wu]

Ming Wen  于2020年6月28日周日 下午2:36写道：

> > "This project is dual licensed under the Apache 2.0 and AGPL licenses：
> > 1. If used with Apache APISIX, the license is Apache License 2.0;
> > 2. otherwise the license is AGPL.”
> > How did this come about? I hav a possible concern about this but not sure
> if it’s an issue or not.
>

Ming

Based on your LICENSE,
https://github.com/api7/lua-resty-radixtree/blob/master/LICENSE#L1-L3
This is an unnormal dual-licensed, because from my understanding, Apache
2.0 doesn't set up the limitation of the usage, which is for public good.

But `otherwise the license is AGPL.` is another case, the key is, it is
hard to define what is `used in APISIX`, how about the re-distribution or
re-write or changed versions?


Sheng Wu 吴晟
Twitter, wusheng1108


>
> These two dependencies are designed and implemented specifically for Apache
> APISIX,
> and will always keep the Apache 2.0 license for Apache APISIX.
> At the same time, we don't want just use these two dependencies instead of
> Apache APISIX as a whole,
> so we've set up a dual licenses.
> For Apache APISIX, I don't think there is a license issue because both are
> the Apache 2.0 license.
> If I'm wrong, please correct me and we can fix it.
>
> Thanks,
> Ming Wen, Apache APISIX & Apache SkyWalking
> Twitter: _WenMing
>
>
> Justin Mclean  于2020年6月25日周四 下午2:51写道：
>
> > HI,
> >
> > +1 (binding)
> >
> > I checked:
> > - incubating in name
> > - signature and hash is fine
> > - DISCLAIMER exists
> > - NOTICE and LICENSE are all good
> > - No unextedtcd binary files
> > - All ASF file have correct headers
> > - Can compile
> >
> >
> > I did notice one odd thing I’ve not noticed before. In [1][2]
> >
> > "This project is dual licensed under the Apache 2.0 and AGPL licenses：
> > 1. If used with Apache APISIX, the license is Apache License 2.0;
> > 2. otherwise the license is AGPL.”
> >
> > How did this come about? I hav a possible concern about this but not sure
> > if it’s an issue or not.
> >
> > Thanks,
> > Justin
> >
> > 1. ./deps/lib/luarocks/rocks-5.1/jsonschema/0.8-0/doc/LICENSE
> > 2. ./deps/lib/luarocks/rocks-5.1/lua-resty-radixtree/1.9-0/doc/LICENSE
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Release Apache IoTDB 0.10.0

[Willem Jiang]

+1 （binding)

Here are my checks,
1. Signature and Hashed are good.
2. Release commit and Tag are good.
3. LICENSE and NOTICE files are good for me.
4. I can build the binary from the Source release kit.
5. DISCLAIMER is included.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Jun 24, 2020 at 9:39 AM Xiangdong Huang  wrote:
>
> Hello all,
>
> This is a call for vote to release Apache IoTDB (Incubating) version
> 0.10.0, which is the 3rd major version (and the  8th minor version) of
> Apache IoTDB Project.
>
> The Apache IoTDB community has voted on and approved a proposal to release
> Apache IoTDB (Incubating) version 0.10.0.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache IoTDB (incubating) (Database for the Internet of Things) is an
> integrated data management engine designed for timeseries data. It provides
> users with services for data collection, storage and analysis.
>
> IoTDB community vote and result thread:
>
>
> Result (17 +1 votes from mentors, IPMCs, PPMCs, committers and other
> contributors):
>
> -
> https://lists.apache.org/thread.html/rf40abefda97a0675cb44ae985e3a3b7741dcac90ac5b01408c6331f6%40%3Cdev.iotdb.apache.org%3E
>
>
> Vote:
>
> -
> https://lists.apache.org/thread.html/r67d045df992a3d5d400dbe396e926ed847e4e102559c9c6508544009%40%3Cdev.iotdb.apache.org%3E
>
> -
> https://lists.apache.org/thread.html/r89794d3741f9f63757b09ec440fcd5d557346540d40e74c0dd27%40%3Cdev.iotdb.apache.org%3E
>
> The release candidates (RC4):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.0/rc4
>
> Git tag for the release (RC4):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.10.0
>
> Hash for the release tag:
> f506d9c731231f97d8813528cbf062760d40
>
> Release Notes:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.10.0/rc4/RELEASE_NOTES.md
>
> The artifacts have been signed with Key : 2206EF8F64C35889, which can be
>
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
> Look at here for how to verify this release candidate:
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
> From the PPMC Vote we carry over 3 binding IPMC Votes:
>
> +1 from Justin Mclean,
> +1 from Julian Feinauer,
> +1 from Christofer Dutz
>
> The vote will be passed if there is no -1 vote ( as there are 3 IPMC +1
> votes already), but we still hope all other IPMCs vote for it.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Xiangdong Huang
> Apache IoTDB (incubating)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

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

[Ming Wen]

> "This project is dual licensed under the Apache 2.0 and AGPL licenses：
> 1. If used with Apache APISIX, the license is Apache License 2.0;
> 2. otherwise the license is AGPL.”
> How did this come about? I hav a possible concern about this but not sure
if it’s an issue or not.

These two dependencies are designed and implemented specifically for Apache
APISIX,
and will always keep the Apache 2.0 license for Apache APISIX.
At the same time, we don't want just use these two dependencies instead of
Apache APISIX as a whole,
so we've set up a dual licenses.
For Apache APISIX, I don't think there is a license issue because both are
the Apache 2.0 license.
If I'm wrong, please correct me and we can fix it.

Thanks,
Ming Wen, Apache APISIX & Apache SkyWalking
Twitter: _WenMing


Justin Mclean  于2020年6月25日周四 下午2:51写道：

> HI,
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - signature and hash is fine
> - DISCLAIMER exists
> - NOTICE and LICENSE are all good
> - No unextedtcd binary files
> - All ASF file have correct headers
> - Can compile
>
>
> I did notice one odd thing I’ve not noticed before. In [1][2]
>
> "This project is dual licensed under the Apache 2.0 and AGPL licenses：
> 1. If used with Apache APISIX, the license is Apache License 2.0;
> 2. otherwise the license is AGPL.”
>
> How did this come about? I hav a possible concern about this but not sure
> if it’s an issue or not.
>
> Thanks,
> Justin
>
> 1. ./deps/lib/luarocks/rocks-5.1/jsonschema/0.8-0/doc/LICENSE
> 2. ./deps/lib/luarocks/rocks-5.1/lua-resty-radixtree/1.9-0/doc/LICENSE
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Distribution guidelines for other platforms

[Justin Mclean]

Hi,

> I have a question regarding the nature of the document and the vote. I see
> that the title for this document is "Distribution Guidelines". Do you
> intend to have this document considered as a distribution policy?

Yes it’s policy but podlings can ask for exceptions or come up with their own 
ways of distributing releases that also follow ASF policy.

> If so, why isn't the existing Apache policies regarding distribution 
> sufficient so
> that the incubator needs to impose additional distribution policy that
> top-level projects are not subject to?

It doesn’t impose anything more than current ASF policy, it just clarifies a 
few things and puts them in context. Currently distribution policy is missing 
context of other platforms that software is now distributed on. I have just 
asked for some clarification on that. All TLP should be doing similar things to 
what is mentioned here, with the exception of the incubator disclaimer. See may 
of come up with other ways to comply with ASF policy.

> If the document is not intended as a policy, but as a guide for podlings

All ASF policies are guidelines. If you want to do something differently than 
what is in a policy ask the incubator or board.

> In addition, I was hoping to find past discussions on this draft document.
> Unfortunately, I wasn't able to find any on this list with the document
> link.

This has been discussed before and input from legal and others were taken into 
consideration. I’ll see if I can find those conversations for you.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org