Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC2

2017-12-12 Thread Eric Friedrich (efriedri)
Hi Justin-
  I’m far from an expert on Creative Commons, so please bear with me.

 Reference 3 below is from the OWASP SecLists Project[1] which is under the 
Creative Commons Attribution ShareAlike (CC-BY-SA) 3.0 license.

The Apache “resolved” page places Creative Commons Attribution (CC-BY) 3.0 into 
category B, but the Creative Commons Attribution ShareAlike licenses are 
category A for “unmodified media” [2]

I would consider the passwords_list.txt file a form of unmodified media and 
think we should be able to include it in our release in source form. (This is 
actually the same reasoning we apply to the Maxmind .tgz, which is also 
Attribution-ShareAlike CC-BY-SA 4.0).

1. https://www.owasp.org/index.php/OWASP_SecLists_Project
2. https://www.apache.org/legal/resolved.html#cc-sa

— Eric

On Dec 11, 2017, at 1:03 AM, Justin Mclean 
mailto:jus...@classsoftware.com>> wrote:

Hi,

-1 (binding) until category B issue resolved [3], then I would be +1 on the 
release.

I checked:
- incubating in release name
- signatures and hashes good
- LICENSE and NOTICE files content good
- noticed one file possibly not having the correct header [1], but all other 
files look good
- no unexpected binary files in release
- can mostly compile from source (with some minor issues as I’m guessing OSX 
isn’t a supported platform?)

The inclusion Maxmind is CC by SA 4.0 [2] has been resolved from memory, 
however I'm not sure that this file [3] which is CC by SA 3 is allowed in the 
release and appears to be a "category B" file [4] (and not in binary form). I 
couldn’t find any discussion about on Apache lists, has this been discussed 
somewhere and I just missed it?

Thanks,
Justin

1. 
apache-trafficcontrol-2.1.0-incubating/traffic_router/core/src/main/java/com/comcast/cdn/traffic_control/traffic_router/core/config/ConfigHandler.java
2. apache-trafficcontrol-2.1.0-incubating/licenses/CC_A_SA_4-maxmind
3. 
apache-trafficcontrol-2.1.0-incubating/traffic_ops/app/conf/invalid_passwords.txt
4. https://www.apache.org/legal/resolved.html#category-b
-
To unsubscribe, e-mail: 
general-unsubscr...@incubator.apache.org
For additional commands, e-mail: 
general-h...@incubator.apache.org




Re: [VOTE] Accept ServiceComb into the Apache Incubator

2017-12-12 Thread Craig Russell
Ping. 

> On Dec 11, 2017, at 7:23 AM, Craig Russell  wrote:
> 
> Hi,
> 
> Can you please add this to https://wiki.apache.org/incubator/ProjectProposals 
> so it can be found easily.
> 
> Thanks,
> 
> Craig
> 
>> On Nov 13, 2017, at 10:15 PM, Willem Jiang  wrote:
>> 
>> Hi All,
>> 
>> I would like to start a VOTE to bring the ServiceComb project in as an
>> Apache incubator podling.
>> 
>> The ASF voting rules are described:
>> 
>> https://www.apache.org/foundation/voting.html
>> 
>> A vote for accepting a new Apache Incubator podling is a majority vote for
>> which only Incubator PMC member votes are binding.
>> 
>> This vote will run for at least 72 hours. Please VOTE as follows
>> [] +1 Accept ServiceComb into the Apache Incubator
>> [] +0 Abstain.
>> [] -1 Do not accept ServiceComb into the Apache Incubator because ...
>> 
>> The proposal is listed below, but you can also access it on the wiki:
>> 
>> https://wiki.apache.org/incubator/ServiceCombProposal
>> 
>> Best regards,
>> 
>> Willem Jiang
>> 
>> = ServiceComb Proposal =
>> 
>> == Abstract ==
>> 
>> ServiceComb is a microservice framework that provides a set of tools and
>> components to make development and deployment of cloud applications easier.
>> It provides functionalities such as service contract enforcement, service
>> registration, service discovery, load balance, service reliability (latency
>> and fault tolerance, flow control and graceful degradation, handler chain
>> tracing), eventual data consistency and so forth.
>> 
>> == Proposal ==
>> 
>> The goal of this proposal is to bring the existing ServiceComb codebase and
>> existing developers into the Apache Software Foundation (ASF) in order to
>> build a vibrant, diverse and self-governed open source community around the
>> technology.
>> So far the major contributors to the project have been affiliated with
>> Huawei and Huawei is planning to continue market and sell the Cloud Service
>> Engine leveraging the ServiceComb framework.
>> ServiceComb is currently a registered trademark owned by Huawei, and Huawei
>> is happy to donate this trademark to Apache.
>> 
>> Huawei is submitting this proposal to donate the Service source code and
>> associated artifacts (documentation, web site content, wiki, etc.) to the
>> Apache Software Foundation Incubator under the Apache License, Version 2.0
>> and is asking Incubator PMC to establish an open source community. These
>> artifacts are currently available on GitHub at
>> https://github.com/ServiceComb/ and include:
>> * Java Chassis: a multi-protocol (RPC & Restful) microservice framework
>> which adopts contract-first design
>> * Service Center: a service registry that enforces service contract upon
>> service registration and discovery
>> * Saga: a distributed coordinator to achieve eventual data consistency
>> based on the paper "Sagas" by Hector Garcia-Molina and Kenneth Salem
>> * ServiceComb.github.io:  the website repo of ServiceComb.
>> * The other projects will be moved to another place if ServiceComb is
>> accepted by Apache as an incubator project.
>> 
>> == Background ==
>> 
>> Microservices is a variant of the service-oriented architecture (SOA)
>> architectural style that structures an application as a collection of
>> loosely coupled services. ServiceComb is an open source microservice
>> framework initiated as part of Huawei CSE projects (Cloud Service Engine)
>> which was developed in 2015. It is a part of ServiceStage of Huawei Public
>> Cloud which is one-stop PaaS platform for enterprises and developers.
>> Besides ServiceStage, it’s  also used in the Huawei Core Network IOT
>> Platform and Huawei consumer cloud. The number of  companies using
>> ServiceComb to develop their enterprise applications, they are
>> chinasofti.com, isoftstone.com, pactera.com,zbj.com,movit-tech.com, and the
>> number is over 5 and counting.
>> 
>> == Rationale ==
>> 
>> ServiceComb has been developed as a total, open source solution for
>> developing cloud native applications. So far ServiceComb has existed as a
>> GitHub project with committers mostly working for Huawei. We feel that
>> moving it to a neutral organization like Apache, with its strong governance
>> model, is expected to help get more contributions from various
>> organizations and developers, who may be concerned by exclusive control of
>> ServiceComb by Huawei.
>> 
>> == Initial Goals ==
>> 
>> Our initial goals are to bring ServiceComb into the ASF, transition
>> internal engineering processes into the open, and foster a collaborative
>> development model according to the "Apache Way." Huawei and the current
>> contributors to ServiceComb plan to develop new functionality in an open,
>> community-driven way. To get there, the existing internal build, test and
>> release processes will be refactored to support open development.
>> 
>> 1. More specifically, our initial plan of moving ServiceComb to ASF is
>> focused on:
>> 2. open up the governance model in order to simplify 

Re: [VOTE] Accept ServiceComb into the Apache Incubator

2017-12-12 Thread Roman Shaposhnik
Done.

Thanks,
Roman.

On Tue, Dec 12, 2017 at 6:24 AM, Craig Russell  wrote:
> Ping.
>
>> On Dec 11, 2017, at 7:23 AM, Craig Russell  wrote:
>>
>> Hi,
>>
>> Can you please add this to 
>> https://wiki.apache.org/incubator/ProjectProposals so it can be found easily.
>>
>> Thanks,
>>
>> Craig
>>
>>> On Nov 13, 2017, at 10:15 PM, Willem Jiang  wrote:
>>>
>>> Hi All,
>>>
>>> I would like to start a VOTE to bring the ServiceComb project in as an
>>> Apache incubator podling.
>>>
>>> The ASF voting rules are described:
>>>
>>> https://www.apache.org/foundation/voting.html
>>>
>>> A vote for accepting a new Apache Incubator podling is a majority vote for
>>> which only Incubator PMC member votes are binding.
>>>
>>> This vote will run for at least 72 hours. Please VOTE as follows
>>> [] +1 Accept ServiceComb into the Apache Incubator
>>> [] +0 Abstain.
>>> [] -1 Do not accept ServiceComb into the Apache Incubator because ...
>>>
>>> The proposal is listed below, but you can also access it on the wiki:
>>>
>>> https://wiki.apache.org/incubator/ServiceCombProposal
>>>
>>> Best regards,
>>>
>>> Willem Jiang
>>>
>>> = ServiceComb Proposal =
>>>
>>> == Abstract ==
>>>
>>> ServiceComb is a microservice framework that provides a set of tools and
>>> components to make development and deployment of cloud applications easier.
>>> It provides functionalities such as service contract enforcement, service
>>> registration, service discovery, load balance, service reliability (latency
>>> and fault tolerance, flow control and graceful degradation, handler chain
>>> tracing), eventual data consistency and so forth.
>>>
>>> == Proposal ==
>>>
>>> The goal of this proposal is to bring the existing ServiceComb codebase and
>>> existing developers into the Apache Software Foundation (ASF) in order to
>>> build a vibrant, diverse and self-governed open source community around the
>>> technology.
>>> So far the major contributors to the project have been affiliated with
>>> Huawei and Huawei is planning to continue market and sell the Cloud Service
>>> Engine leveraging the ServiceComb framework.
>>> ServiceComb is currently a registered trademark owned by Huawei, and Huawei
>>> is happy to donate this trademark to Apache.
>>>
>>> Huawei is submitting this proposal to donate the Service source code and
>>> associated artifacts (documentation, web site content, wiki, etc.) to the
>>> Apache Software Foundation Incubator under the Apache License, Version 2.0
>>> and is asking Incubator PMC to establish an open source community. These
>>> artifacts are currently available on GitHub at
>>> https://github.com/ServiceComb/ and include:
>>> * Java Chassis: a multi-protocol (RPC & Restful) microservice framework
>>> which adopts contract-first design
>>> * Service Center: a service registry that enforces service contract upon
>>> service registration and discovery
>>> * Saga: a distributed coordinator to achieve eventual data consistency
>>> based on the paper "Sagas" by Hector Garcia-Molina and Kenneth Salem
>>> * ServiceComb.github.io:  the website repo of ServiceComb.
>>> * The other projects will be moved to another place if ServiceComb is
>>> accepted by Apache as an incubator project.
>>>
>>> == Background ==
>>>
>>> Microservices is a variant of the service-oriented architecture (SOA)
>>> architectural style that structures an application as a collection of
>>> loosely coupled services. ServiceComb is an open source microservice
>>> framework initiated as part of Huawei CSE projects (Cloud Service Engine)
>>> which was developed in 2015. It is a part of ServiceStage of Huawei Public
>>> Cloud which is one-stop PaaS platform for enterprises and developers.
>>> Besides ServiceStage, it’s  also used in the Huawei Core Network IOT
>>> Platform and Huawei consumer cloud. The number of  companies using
>>> ServiceComb to develop their enterprise applications, they are
>>> chinasofti.com, isoftstone.com, pactera.com,zbj.com,movit-tech.com, and the
>>> number is over 5 and counting.
>>>
>>> == Rationale ==
>>>
>>> ServiceComb has been developed as a total, open source solution for
>>> developing cloud native applications. So far ServiceComb has existed as a
>>> GitHub project with committers mostly working for Huawei. We feel that
>>> moving it to a neutral organization like Apache, with its strong governance
>>> model, is expected to help get more contributions from various
>>> organizations and developers, who may be concerned by exclusive control of
>>> ServiceComb by Huawei.
>>>
>>> == Initial Goals ==
>>>
>>> Our initial goals are to bring ServiceComb into the ASF, transition
>>> internal engineering processes into the open, and foster a collaborative
>>> development model according to the "Apache Way." Huawei and the current
>>> contributors to ServiceComb plan to develop new functionality in an open,
>>> community-driven way. To get there, the existing internal build, test and
>>> release processes will be refactored to support open 

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC2

2017-12-12 Thread Justin Mclean
Hi,

> The Apache “resolved” page places Creative Commons Attribution (CC-BY) 3.0 
> into category B, but the Creative Commons Attribution ShareAlike licenses are 
> category A for “unmodified media” [2]

Only if it is included in binary form [1] that file is plain text I suggest you 
ask on legal discuss if it’s OK to include or not.

Thanks,
Justin

1. https://www.apache.org/legal/resolved.html#category-b
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [PROPOSAL] PLC4X - proposal for Apache Incubation

2017-12-12 Thread Justin Mclean
Hi,

Anyone have feedback or see any issues with this proposal?

If there are none in the next couple of days I'll go ahead and call a vote.

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 Traffic Control (incubating) 2.1.0-RC2

2017-12-12 Thread Justin Mclean
Hi,

Or perhaps you can ask the author of the file to license under more ALv2 
compatible terms or is there a different list of password you can under under a 
more compatible license?

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



Re: [PROPOSAL] PLC4X - proposal for Apache Incubation

2017-12-12 Thread Mike Drob
> Can’t enter incubation without having code.

I think this has been done before, but it's not relevant now. I agree with
John that you should expect to need an SGA.

Good luck and good coding!

On Tue, Dec 12, 2017, 3:42 PM Justin Mclean 
wrote:

> Hi,
>
> Anyone have feedback or see any issues with this proposal?
>
> If there are none in the next couple of days I'll go ahead and call a vote.
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


RE: [VOTE] Pulsar 1.21.0-incubating Release Candidate 3

2017-12-12 Thread Nozomi Kurihara
Hi Henk,


Thanks for the comment.

I'll fix the extension.


Regards,

Nozomi


差出人: Henk P. Penning 
送信日時: 2017年12月12日 16:12:37
宛先: general@incubator.apache.org
件名: Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 3

On Tue, 12 Dec 2017, Nozomi Kurihara wrote:

> Date: Tue, 12 Dec 2017 03:52:27 +0100
> From: Nozomi Kurihara 
> To: "general@incubator.apache.org" 
> Subject: [VOTE] Pulsar 1.21.0-incubating Release Candidate 3

Hi Nozomi Kurihara,

   Please don't use the ".sha" extension ;
   use ".sha1", ".sha256", or ".sha512" instead.

   ref : http://www.apache.org/dev/release-distribution#sigs-and-sums

   Groeten,

   Henk Penning

   _
Henk P. Penning, ICT-beta R Uithof HFG-406   _/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Budapestlaan 6, 3584CD Utrecht, NLF +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/

> This is the fourth release candidate for Apache Pulsar, version 
> 1.21.0-incubating.
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub semantics over topics,
> guaranteed at-least-once delivery of messages, automatic cursor management
> for subscribers, and cross-datacenter replication.
>
> Note that we are voting upon the source (tag), binaries are provided for 
> convenience.
>
> Fixed issues:
> https://github.com/apache/incubator-pulsar/milestone/10?closed=1
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-1.21.0-incubating-candidate-3/
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1005/
>
> The tag to be voted upon:
> v1.21.0-incubating-candidate-3
> https://github.com/apache/incubator-pulsar/releases/tag/v1.21.0-incubating-candidate-3
>
> Pulsar's KEYS file containing PGP keys we use to sign the release:
> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
>
> Link to the voting thread from the dev@pulsar mailing list:
> https://lists.apache.org/thread.html/51c0737bcfee37073017291adb6453c27f9562dc9905f8eccdc78abe@%3Cdev.pulsar.apache.org%3E
>
> Please download the the source package, and follow the README to build and 
> run the Pulsar standalone service.
>
> This vote will stay open for at least 72 hours (around December 15th 2017, 
> 10:00 GMT).
>
> Regards,
> Nozomi
>

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



Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC2

2017-12-12 Thread Eric Friedrich (efriedri)
I’ll talk with the rest of the Traffic Control PPMC tomorrow about getting in 
touch with the author.

For now, I’ve also opened a legal discuss question for their opinion: 
https://issues.apache.org/jira/browse/LEGAL-356

—Eric

On Dec 12, 2017, at 7:28 PM, Justin Mclean 
mailto:jus...@classsoftware.com>> wrote:

Hi,

Or perhaps you can ask the author of the file to license under more ALv2 
compatible terms or is there a different list of password you can under under a 
more compatible license?

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




Re: [VOTE] Pulsar 1.21.0-incubating Release Candidate 3

2017-12-12 Thread Sergio Fernández
+1 (binding)

So far I've successfully checked:
* signatures and digests
* source releases file layouts
* matched git tags and commit ids
* incubator suffix and disclaimer
* NOTICE and LICENSE files
* license headers
* clean build (Java 1.8.0_151, Debian amd64)


On Mon, Dec 11, 2017 at 6:52 PM, Nozomi Kurihara 
wrote:

> This is the fourth release candidate for Apache Pulsar, version
> 1.21.0-incubating.
>
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub semantics over topics,
> guaranteed at-least-once delivery of messages, automatic cursor management
> for subscribers, and cross-datacenter replication.
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Fixed issues:
> https://github.com/apache/incubator-pulsar/milestone/10?closed=1
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/
> pulsar-1.21.0-incubating-candidate-3/
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1005/
>
> The tag to be voted upon:
> v1.21.0-incubating-candidate-3
> https://github.com/apache/incubator-pulsar/releases/tag/
> v1.21.0-incubating-candidate-3
>
> Pulsar's KEYS file containing PGP keys we use to sign the release:
> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
>
> Link to the voting thread from the dev@pulsar mailing list:
> https://lists.apache.org/thread.html/51c0737bcfee37073017291adb6453
> c27f9562dc9905f8eccdc78abe@%3Cdev.pulsar.apache.org%3E
>
> Please download the the source package, and follow the README to build and
> run the Pulsar standalone service.
>
> This vote will stay open for at least 72 hours (around December 15th 2017,
> 10:00 GMT).
>
> Regards,
> Nozomi
>


[IP CLEARANCE] Apache Felix Bundle Archive File Installer Extension

2017-12-12 Thread Karl Pauls
Hi,

the Apache Felix project has received the contribution of the Bundle
Archive File Installer Extension.

- The code is attached to FELIX-5732 [0].
- The IP Clearance form has been committed [1].
- The acceptance vote has passed on the dev@felix malining list [2].

The clearance passes by lazy consensus if no -1 votes are cast within
the next 72 hours.

regards,

Karl


[0] https://issues.apache.org/jira/browse/FELIX-5732
[1] 
https://incubator.apache.org/ip-clearance/felix-bar-file-install-extension.html
[2] https://www.mail-archive.com/dev@felix.apache.org/msg44409.html

-- 
Karl Pauls
karlpa...@gmail.com

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