Re: [VOTE] Apache Gobblin 0.13.0 release RC2

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On 11/09/2018 06:51, Hung Tran wrote:
> The Apache Gobblin community has voted on and approved the release of Apache 
> Gobblin 0.13.0 (incubating):
> 
> https://www.mail-archive.com/dev@gobblin.incubator.apache.org/msg02175.html
> 
> Results:
> 3 binding +1 votes
> No 0 votes
> No -1 votes
> 
> The feedback from previous release candidates has been addressed:
> 
> RC1 thread:
> https://www.mail-archive.com/general@incubator.apache.org/msg64403.html
> Resolution:
> Removed the binary release tar from the source release tar.
> 
> I'd like to call a vote in general to approve the release.
> 
> The source release candidate RC2 with convenience binaries can be downloaded 
> here:
> https://dist.apache.org/repos/dist/dev/incubator/gobblin/apache-gobblin
> -incubating-0.13.0-rc2/
> 
> The artifacts (i.e. JARs) corresponding to this release candidate can be
> found here:
> https://repository.apache.org/content/repositories/orgapachegobblin-1007
> 
> This has been signed with PGP key 0x9BB772F1,corresponding to
> hut...@apache.org, which is included in the repository's KEYS file (
> https://dist.apache.org/repos/dist/release/incubator/gobblin/KEYS). This key 
> can be found on keyservers, such as:
> http://pgp.mit.edu/pks/lookup?op=get=0x9BB772F1
> 
> 
> The release candidate has been tagged with release-0.13.0-rc2.
> I've also created a branch 0.13.0.
> 
> 
> For reference, here is a list of all closed JIRAs tagged with 0.13.0:
> https://issues.apache.org/jira/issues/?filter=12343492
> 
> For a summary of the changes in this release, see:
> https://github.com/apache/incubator-gobblin/blob/0.13.0/CHANGELOG.md
> 
> Please review and vote. The vote will be open for at least 72 hours.
> 
>  [ ] +1 approve
>  [ ] +0 no opinion
>  [ ] -1 disapprove (and reason why)
> 
> Thanks,
> Hung, on behalf of the Apache Gobblin PPMC
> 
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help

[Jean-Baptiste Onofré]

Hi,

sure. I think we can update the wiki with the proposal.

Thoughts ?

Regards
JB

On 19/09/2018 04:34, Tan,Zhongyi wrote:
> Hi，JB，
> 
> can we invite you as the mentor of brpc？
> 
> thanks
> 
> 
> 在 2018/9/17 下午12:18， "Jean-Baptiste Onofré"  写入:
> 
>> Hi,
>>
>> With great pleasure. I'm not sure I will contribute so much on the code,
>> but I would be more than happy to help and guide the incubation.
>>
>> Regards
>> JB
>>
>> On 17/09/2018 05:21, Tan,Zhongyi wrote:
>>> Hi， JB
>>>
>>> Would you like to be champion for this project？
>>>
>>> Thanks
>>>
>>>
>>> 在 2018/9/14 下午5:20， "Jean-Baptiste Onofré"  写入:
>>>
 Thanks for the details. It helps.

 Let me do a new pass on the proposal.

 Regards
 JB

 On 14/09/2018 10:19, Tan,Zhongyi wrote:
> Hi， JB，
> Below are our answers to your questions，
> Please check，
> Thanks.
>
> 1. brpc doesn't depend on any other Apache projects. brpc currently
> depends on the following external project:
>- leveldb
>- openssl
>- protobuf
>- gperftools (optional)
>- glog (optional)
>- gtest
>
> 2. brpc is alternative for C++ rpc fcramework，implementations for
> other
> languages are not competitive enough (comparing to gRPC) to be
> opensourced.  Besides the basic RPC function, brpc(C++) provides
> additional features than gRPC:
>- Clients and servers can talk in multiple protocols: baidu
> internal
> protocol, http, thrift, http2(communicable with gRPC, the PR is under
> reviewing) and tens of other protocols.
>- Proved better performance in different scenarios, by eliminating
> locks on hotpaths and using goroutine-like concurrency(bthread) with
> cache
> friendly data structures
>- More useful debugging utilities to help C++ programers build
> solid
> online services.
>- Various access patterns such as one-to-one, one-to-many(fan out),
> streaming, which simplify implementation of complex distributed
> services.
>
>
>
> 在 2018/9/13 下午3:00， "Jean-Baptiste Onofré"  写入:
>
>> Hi,
>>
>> It's an interesting project. I have two questions:
>>
>> 1. do you have some interactions/dependencies with other Apache
>> projects, especially CXF for instance ?
>> 2. what's the comparison between brpc and gRPC ? An alternative ?
>> Different features ?
>>
>> I might be interested by mentoring the project, I would like to
>> understand exactly the target/purposes.
>>
>> Thanks !
>> Regards
>> JB
>>
>> On 13/09/2018 08:20, Tan,Zhongyi wrote:
>>> Hi, guys,
>>>
>>> brpc is one open source RPC framework that is very popular in baidu
>>> and
>>> china.
>>> We want to contribute it to ASF to make it more successful.
>>> And we are looking for champion and mentor for this project,
>>> if anyone would like to volunteer, we will be very appreciated.
>>>
>>> Thanks.
>>>
>>>
>>> Here is the draft for brpc proposal.
>>>
>>>
>>> # brpc Proposal
>>>
>>> ## Abstract
>>>
>>> brpc is an industrial-grade RPC framework for building reliable and
>>> high-performance services.
>>>
>>> ## Proposal
>>>
>>> We propose to contribute the brpc codebase and associated
>>> artifacts(e.g. documentation etc.) to the Apache Software
>>> Foundation,
>>> and aim to  build a wider open community around it in the 'Apache
>>> Way'.
>>>
>>>
>>> ## Background
>>>
>>> The RPC framework used in Baidu before 2014 was developed at 2008
>>> and
>>> limited in protocols and performance, and there were also serveral
>>> implementations focused on their own scenarios from Baidu's
>>> different
>>> BU. As an infrastructural team in Baidu, we tried to build a new
>>> framework to unify all RPC scenarios inside. The framework was named
>>> "baidu-rpc" internally the early versions were adopted and online at
>>> late 2014. The framework was rapidly iterated at 2015-2017, and
>>> thousands kinds of services and almost all core services adopted it.
>>> And
>>> in 2017, we opensourced it as "brpc" and hope to get more adoptions
>>> and
>>> contributions from outside. At the time of opensourcing, there're
>>> more
>>> than 1 million instances inside Baidu using baidu-rpc (not counting
>>> clients).
>>>
>>>
>>> ## Rationale
>>>
>>> brpc has been approved inside baidu, since many high performance
>>> core
>>> services are using it.
>>> And since its open source, it has been adopted by several other
>>> companies, including Iqiyi, Didi, Sougou, BiliBili etc.
>>>
>>> ## Current Status
>>>
>>> brpc has been an open source project on GitHub
>>> (https://github.com/brpc/brpc) since 2017.
>>>
>>> Currently it 

Re: Does Zipkin need to sign a SGA ?

[Adrian Cole]

OpenZipkin isn't a formal entity. The primary fork (master copy) was
moved from twitter to a github org named OpenZipkin. We aren't moving
any downstream forks to the exist they still exist for Lookout or any
other person.
On Wed, Sep 19, 2018 at 10:40 AM Dave Fisher  wrote:
>
> Hi,
>
> Is OpenZipkin a formal entity?
>
> What about Lookout who also had a fork (according to the references)?
>
> At Twitter you might try Remy DeCausemaker.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Sep 18, 2018, at 6:59 PM, Adrian Cole  wrote:
> >
> > Hi, John
> >
> > Thanks for the input. So, I would hazard a guess that Twitter folks
> > would like to help with this. I'm not sure who would want to hunt
> > through the management chain to find someone to reverse-own a decision
> > made 3 years ago, though! Regardless, on my part, I'll see if I can
> > find a champion inside Twitter to resurrect and SGA.
> >
> > Best,
> > -A
> >> On Wed, Sep 19, 2018 at 9:36 AM John D. Ament  
> >> wrote:
> >>
> >> Thanks Adrian.  Some comments/banter below.
> >>
> >> Migrating a repository from one org to another does not require an SGA.  If
> >> it did, we would not be able to have code living in our repos that had
> >> headers other than the ASF standard headers (e.g. BSD licenses, or Apache
> >> License w/ different copyright statements).  The SGA is used to replace the
> >> headers with the standard ASF headers.  We should not block migrating the
> >> repositories over while the SGA/ICLA is worked out.
> >>
> >> Resolving the SGA/ICLA situation would block graduation - we should ensure
> >> that the provenance is in place, which is part of the incubation process.
> >> This doesn't need to be solved on day 1, but by the time the podling is
> >> ready to graduate.
> >>
> >> With that said, from a pure foundation standpoint it would be ideal to
> >> receive a SGA from Twitter.  Even if the current code doesn't match the
> >> code at the time of Twitter's conversion, it gives us a better IP history
> >> for the codebase to answer questions and deal with any potential problems
> >> that may come up along the way.  However, to be realistic I believe if we
> >> receive an ICLA from the primary contributors based on [1], that should
> >> satisfy enough providence of the codebase, in addition to the contribution
> >> process that Adrian has pointed out below.
> >>
> >> Thoughts?
> >>
> >> John
> >>
> >> [1]: https://github.com/openzipkin/zipkin/graphs/contributors
> >>
> >>> On Tue, Sep 18, 2018 at 9:25 PM Adrian Cole  
> >>> wrote:
> >>>
> >>> There was a process involved at Twitter when we first moved it to the
> >>> openzipkin organization. It was 100% clear that this was an act for
> >>> the community to control the code.  Senior management were involved
> >>> https://groups.google.com/d/msg/zipkin-user/fbOgEZpuQx4/bWH1-__EmCoJ
> >>>
> >>> After that, all the repositories had contributing files like the below
> >>> indicating that all changes we to be redistributable under ASL
> >>>
> >>> https://github.com/openzipkine/zipkin/blob/master/.github/CONTRIBUTING.md#license
> >>> 
> >>>
> >>> There was no collection of contributor agreements beyond this. Most of
> >>> the code except save some UI assets have been completely rewritten
> >>> since the migration to OpenZipkin a few years back.
> >>>
> >>> Hope these details help,
> >>> -A
> >>> On Wed, Sep 19, 2018 at 9:09 AM Craig Russell 
> >>> wrote:
> 
>  Hi Mick,
> 
>  tldr; with my Incubator PMC hat on, "all that needs to be done" is to
> >>> establish that all of the copyright owners sign either a Software Grant or
> >>> an ICLA.
> 
>  In order to establish that Apache has the rights to the code base, every
> >>> line of code needs to have its provenance researched.
> 
>  Looking at the proposal https://wiki.apache.org/incubator/ZipkinProposal
> >>> it seems like most of the code is in the github repository
> >>> https://github.com/openzipkin/zipkin . Is there any code coming from
> >>> another source? Was the original code from Twitter granted to OpenZipkin?
> >>> Is there any documentation of that copyright transfer? Does Twitter retain
> >>> any rights?
> 
>  The capitalization of the "Initial Source" section is a bit strange. But
> >>> can we assume that the only committers to the project are listed at
> >>> https://github.com/openzipkin/zipkin/graphs/contributors ?
> 
>  The proposal also says that "All source code is copyrighted to 'The
> >>> OpenZipkin Authors', to which the existing core community(members list in
> >>> Initial Committers) has the rights to re-assign to the ASF. "
> 
>  It looks like there were many people who contributed a few lines of
> >>> code. Did they sign anything like a Contributor Agreement that grants 
> >>> their
> >>> copyright to The OpenZipkin Authors?
> 
>  Craig
> 
> > On Sep 18, 2018, at 4:58 

Re: Does Zipkin need to sign a SGA ?

[Dave Fisher]

Hi,

Is OpenZipkin a formal entity?

What about Lookout who also had a fork (according to the references)?

At Twitter you might try Remy DeCausemaker.

Regards,
Dave

Sent from my iPhone

> On Sep 18, 2018, at 6:59 PM, Adrian Cole  wrote:
> 
> Hi, John
> 
> Thanks for the input. So, I would hazard a guess that Twitter folks
> would like to help with this. I'm not sure who would want to hunt
> through the management chain to find someone to reverse-own a decision
> made 3 years ago, though! Regardless, on my part, I'll see if I can
> find a champion inside Twitter to resurrect and SGA.
> 
> Best,
> -A
>> On Wed, Sep 19, 2018 at 9:36 AM John D. Ament  wrote:
>> 
>> Thanks Adrian.  Some comments/banter below.
>> 
>> Migrating a repository from one org to another does not require an SGA.  If
>> it did, we would not be able to have code living in our repos that had
>> headers other than the ASF standard headers (e.g. BSD licenses, or Apache
>> License w/ different copyright statements).  The SGA is used to replace the
>> headers with the standard ASF headers.  We should not block migrating the
>> repositories over while the SGA/ICLA is worked out.
>> 
>> Resolving the SGA/ICLA situation would block graduation - we should ensure
>> that the provenance is in place, which is part of the incubation process.
>> This doesn't need to be solved on day 1, but by the time the podling is
>> ready to graduate.
>> 
>> With that said, from a pure foundation standpoint it would be ideal to
>> receive a SGA from Twitter.  Even if the current code doesn't match the
>> code at the time of Twitter's conversion, it gives us a better IP history
>> for the codebase to answer questions and deal with any potential problems
>> that may come up along the way.  However, to be realistic I believe if we
>> receive an ICLA from the primary contributors based on [1], that should
>> satisfy enough providence of the codebase, in addition to the contribution
>> process that Adrian has pointed out below.
>> 
>> Thoughts?
>> 
>> John
>> 
>> [1]: https://github.com/openzipkin/zipkin/graphs/contributors
>> 
>>> On Tue, Sep 18, 2018 at 9:25 PM Adrian Cole  wrote:
>>> 
>>> There was a process involved at Twitter when we first moved it to the
>>> openzipkin organization. It was 100% clear that this was an act for
>>> the community to control the code.  Senior management were involved
>>> https://groups.google.com/d/msg/zipkin-user/fbOgEZpuQx4/bWH1-__EmCoJ
>>> 
>>> After that, all the repositories had contributing files like the below
>>> indicating that all changes we to be redistributable under ASL
>>> 
>>> https://github.com/openzipkine/zipkin/blob/master/.github/CONTRIBUTING.md#license
>>> 
>>> 
>>> There was no collection of contributor agreements beyond this. Most of
>>> the code except save some UI assets have been completely rewritten
>>> since the migration to OpenZipkin a few years back.
>>> 
>>> Hope these details help,
>>> -A
>>> On Wed, Sep 19, 2018 at 9:09 AM Craig Russell 
>>> wrote:
 
 Hi Mick,
 
 tldr; with my Incubator PMC hat on, "all that needs to be done" is to
>>> establish that all of the copyright owners sign either a Software Grant or
>>> an ICLA.
 
 In order to establish that Apache has the rights to the code base, every
>>> line of code needs to have its provenance researched.
 
 Looking at the proposal https://wiki.apache.org/incubator/ZipkinProposal
>>> it seems like most of the code is in the github repository
>>> https://github.com/openzipkin/zipkin . Is there any code coming from
>>> another source? Was the original code from Twitter granted to OpenZipkin?
>>> Is there any documentation of that copyright transfer? Does Twitter retain
>>> any rights?
 
 The capitalization of the "Initial Source" section is a bit strange. But
>>> can we assume that the only committers to the project are listed at
>>> https://github.com/openzipkin/zipkin/graphs/contributors ?
 
 The proposal also says that "All source code is copyrighted to 'The
>>> OpenZipkin Authors', to which the existing core community(members list in
>>> Initial Committers) has the rights to re-assign to the ASF. "
 
 It looks like there were many people who contributed a few lines of
>>> code. Did they sign anything like a Contributor Agreement that grants their
>>> copyright to The OpenZipkin Authors?
 
 Craig
 
> On Sep 18, 2018, at 4:58 PM, Mick Semb Wever  wrote:
> 
> 
> It's come up that the migration of the github Zipkin repositories to
>>> ASF requires either a signed SGA or a sign-off from the Secretary. Chris
>>> raised this on `INFRA-16989 – Zipkin incubator project request for the
>>> GitHub repositories moving service`.
> 
> I was under the impression that if the Copyright was already held by
>>> the community, it is held by 'The OpenZipkin Authors', that the ICLA from
>>> all those 

Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help

[Tan,Zhongyi]

Hi，JB，

can we invite you as the mentor of brpc？

thanks


在 2018/9/17 下午12:18， "Jean-Baptiste Onofré"  写入:

>Hi,
>
>With great pleasure. I'm not sure I will contribute so much on the code,
>but I would be more than happy to help and guide the incubation.
>
>Regards
>JB
>
>On 17/09/2018 05:21, Tan,Zhongyi wrote:
>> Hi， JB
>> 
>> Would you like to be champion for this project？
>> 
>> Thanks
>> 
>> 
>> 在 2018/9/14 下午5:20， "Jean-Baptiste Onofré"  写入:
>> 
>>> Thanks for the details. It helps.
>>>
>>> Let me do a new pass on the proposal.
>>>
>>> Regards
>>> JB
>>>
>>> On 14/09/2018 10:19, Tan,Zhongyi wrote:
 Hi， JB，
 Below are our answers to your questions，
 Please check，
 Thanks.

 1. brpc doesn't depend on any other Apache projects. brpc currently
 depends on the following external project:
- leveldb
- openssl
- protobuf
- gperftools (optional)
- glog (optional)
- gtest

 2. brpc is alternative for C++ rpc fcramework，implementations for
other
 languages are not competitive enough (comparing to gRPC) to be
 opensourced.  Besides the basic RPC function, brpc(C++) provides
 additional features than gRPC:
- Clients and servers can talk in multiple protocols: baidu
internal
 protocol, http, thrift, http2(communicable with gRPC, the PR is under
 reviewing) and tens of other protocols.
- Proved better performance in different scenarios, by eliminating
 locks on hotpaths and using goroutine-like concurrency(bthread) with
 cache
 friendly data structures
- More useful debugging utilities to help C++ programers build
solid
 online services.
- Various access patterns such as one-to-one, one-to-many(fan out),
 streaming, which simplify implementation of complex distributed
 services.



 在 2018/9/13 下午3:00， "Jean-Baptiste Onofré"  写入:

> Hi,
>
> It's an interesting project. I have two questions:
>
> 1. do you have some interactions/dependencies with other Apache
> projects, especially CXF for instance ?
> 2. what's the comparison between brpc and gRPC ? An alternative ?
> Different features ?
>
> I might be interested by mentoring the project, I would like to
> understand exactly the target/purposes.
>
> Thanks !
> Regards
> JB
>
> On 13/09/2018 08:20, Tan,Zhongyi wrote:
>> Hi, guys,
>>
>> brpc is one open source RPC framework that is very popular in baidu
>> and
>> china.
>> We want to contribute it to ASF to make it more successful.
>> And we are looking for champion and mentor for this project,
>> if anyone would like to volunteer, we will be very appreciated.
>>
>> Thanks.
>>
>>
>> Here is the draft for brpc proposal.
>>
>>
>> # brpc Proposal
>>
>> ## Abstract
>>
>> brpc is an industrial-grade RPC framework for building reliable and
>> high-performance services.
>>
>> ## Proposal
>>
>> We propose to contribute the brpc codebase and associated
>> artifacts(e.g. documentation etc.) to the Apache Software
>>Foundation,
>> and aim to  build a wider open community around it in the 'Apache
>> Way'.
>>
>>
>> ## Background
>>
>> The RPC framework used in Baidu before 2014 was developed at 2008
>>and
>> limited in protocols and performance, and there were also serveral
>> implementations focused on their own scenarios from Baidu's
>>different
>> BU. As an infrastructural team in Baidu, we tried to build a new
>> framework to unify all RPC scenarios inside. The framework was named
>> "baidu-rpc" internally the early versions were adopted and online at
>> late 2014. The framework was rapidly iterated at 2015-2017, and
>> thousands kinds of services and almost all core services adopted it.
>> And
>> in 2017, we opensourced it as "brpc" and hope to get more adoptions
>> and
>> contributions from outside. At the time of opensourcing, there're
>>more
>> than 1 million instances inside Baidu using baidu-rpc (not counting
>> clients).
>>
>>
>> ## Rationale
>>
>> brpc has been approved inside baidu, since many high performance
>>core
>> services are using it.
>> And since its open source, it has been adopted by several other
>> companies, including Iqiyi, Didi, Sougou, BiliBili etc.
>>
>> ## Current Status
>>
>> brpc has been an open source project on GitHub
>> (https://github.com/brpc/brpc) since 2017.
>>
>> Currently it has more than 7.3k stars, 1.6k forks, and is one of the
>> most popular repositories in topic of rpc category in GitHub rpc
>> catelogy.
>> It has been widely used in Baidu, with 1,000,000+ instances and
>> thousands kinds of services.
>> Besides, many other companies have already 

Re: Does Zipkin need to sign a SGA ?

[Adrian Cole]

Hi, John

Thanks for the input. So, I would hazard a guess that Twitter folks
would like to help with this. I'm not sure who would want to hunt
through the management chain to find someone to reverse-own a decision
made 3 years ago, though! Regardless, on my part, I'll see if I can
find a champion inside Twitter to resurrect and SGA.

Best,
-A
On Wed, Sep 19, 2018 at 9:36 AM John D. Ament  wrote:
>
> Thanks Adrian.  Some comments/banter below.
>
> Migrating a repository from one org to another does not require an SGA.  If
> it did, we would not be able to have code living in our repos that had
> headers other than the ASF standard headers (e.g. BSD licenses, or Apache
> License w/ different copyright statements).  The SGA is used to replace the
> headers with the standard ASF headers.  We should not block migrating the
> repositories over while the SGA/ICLA is worked out.
>
> Resolving the SGA/ICLA situation would block graduation - we should ensure
> that the provenance is in place, which is part of the incubation process.
> This doesn't need to be solved on day 1, but by the time the podling is
> ready to graduate.
>
> With that said, from a pure foundation standpoint it would be ideal to
> receive a SGA from Twitter.  Even if the current code doesn't match the
> code at the time of Twitter's conversion, it gives us a better IP history
> for the codebase to answer questions and deal with any potential problems
> that may come up along the way.  However, to be realistic I believe if we
> receive an ICLA from the primary contributors based on [1], that should
> satisfy enough providence of the codebase, in addition to the contribution
> process that Adrian has pointed out below.
>
> Thoughts?
>
> John
>
> [1]: https://github.com/openzipkin/zipkin/graphs/contributors
>
> On Tue, Sep 18, 2018 at 9:25 PM Adrian Cole  wrote:
>
> > There was a process involved at Twitter when we first moved it to the
> > openzipkin organization. It was 100% clear that this was an act for
> > the community to control the code.  Senior management were involved
> > https://groups.google.com/d/msg/zipkin-user/fbOgEZpuQx4/bWH1-__EmCoJ
> >
> > After that, all the repositories had contributing files like the below
> > indicating that all changes we to be redistributable under ASL
> >
> > https://github.com/openzipkine/zipkin/blob/master/.github/CONTRIBUTING.md#license
> > 
> >
> > There was no collection of contributor agreements beyond this. Most of
> > the code except save some UI assets have been completely rewritten
> > since the migration to OpenZipkin a few years back.
> >
> > Hope these details help,
> > -A
> > On Wed, Sep 19, 2018 at 9:09 AM Craig Russell 
> > wrote:
> > >
> > > Hi Mick,
> > >
> > > tldr; with my Incubator PMC hat on, "all that needs to be done" is to
> > establish that all of the copyright owners sign either a Software Grant or
> > an ICLA.
> > >
> > > In order to establish that Apache has the rights to the code base, every
> > line of code needs to have its provenance researched.
> > >
> > > Looking at the proposal https://wiki.apache.org/incubator/ZipkinProposal
> > it seems like most of the code is in the github repository
> > https://github.com/openzipkin/zipkin . Is there any code coming from
> > another source? Was the original code from Twitter granted to OpenZipkin?
> > Is there any documentation of that copyright transfer? Does Twitter retain
> > any rights?
> > >
> > > The capitalization of the "Initial Source" section is a bit strange. But
> > can we assume that the only committers to the project are listed at
> > https://github.com/openzipkin/zipkin/graphs/contributors ?
> > >
> > > The proposal also says that "All source code is copyrighted to 'The
> > OpenZipkin Authors', to which the existing core community(members list in
> > Initial Committers) has the rights to re-assign to the ASF. "
> > >
> > > It looks like there were many people who contributed a few lines of
> > code. Did they sign anything like a Contributor Agreement that grants their
> > copyright to The OpenZipkin Authors?
> > >
> > > Craig
> > >
> > > > On Sep 18, 2018, at 4:58 PM, Mick Semb Wever  wrote:
> > > >
> > > >
> > > > It's come up that the migration of the github Zipkin repositories to
> > ASF requires either a signed SGA or a sign-off from the Secretary. Chris
> > raised this on `INFRA-16989 – Zipkin incubator project request for the
> > GitHub repositories moving service`.
> > > >
> > > > I was under the impression that if the Copyright was already held by
> > the community, it is held by 'The OpenZipkin Authors', that the ICLA from
> > all those authors would suffice and a SGA not be required. And it's news to
> > me that this would also require a sign-off from the ASF Secretary.
> > > >
> > > > What's the correct process here? who can help? should I forward the
> > question to the Secretary?
> > > >
> > > > regards,
> > > > Mick
> > > 

Re: [VOTE] Apache Gobblin 0.13.0 release RC2

[Olivier Lamy]

+1

On Tue, 18 Sep 2018 at 22:27, Jim Jagielski  wrote:

> Sorry for the delay...
>
> +1 for the source release (binding) but I agree w/ removing the binary
>
> > On Sep 17, 2018, at 6:27 PM, Abhishek Tiwari  wrote:
> >
> > Ping.
> >
> > Can someone help us review and vote :)
> >
> > Regards
> > Abhishek
> >
> > On Tue, Sep 11, 2018 at 2:59 PM Abhishek Tiwari  wrote:
> >
> >> +1
> >>
> >> Abhishek
> >>
> >> On Tue, Sep 11, 2018 at 2:51 PM Hung Tran  wrote:
> >>
> >>> Adding some CCs since the message was not received.
> >>>
> >>> Hung.
> >>> --
> >>> *From:* Hung Tran 
> >>> *Sent:* Monday, September 10, 2018 9:51:31 PM
> >>> *To:* general@incubator.apache.org
> >>> *Subject:* [VOTE] Apache Gobblin 0.13.0 release RC2
> >>>
> >>> The Apache Gobblin community has voted on and approved the release of
> >>> Apache Gobblin 0.13.0 (incubating):
> >>>
> >>>
> >>>
> https://www.mail-archive.com/dev@gobblin.incubator.apache.org/msg02175.html
> >>>
> >>> Results:
> >>> 3 binding +1 votes
> >>> No 0 votes
> >>> No -1 votes
> >>>
> >>> The feedback from previous release candidates has been addressed:
> >>>
> >>> RC1 thread:
> >>>
> https://www.mail-archive.com/general@incubator.apache.org/msg64403.html
> >>> Resolution:
> >>> Removed the binary release tar from the source release tar.
> >>>
> >>> I'd like to call a vote in general to approve the release.
> >>>
> >>> The source release candidate RC2 with convenience binaries can be
> >>> downloaded here:
> >>>
> https://dist.apache.org/repos/dist/dev/incubator/gobblin/apache-gobblin
> >>> -incubating-0.13.0-rc2/
> >>>
> >>> The artifacts (i.e. JARs) corresponding to this release candidate can
> be
> >>> found here:
> >>>
> https://repository.apache.org/content/repositories/orgapachegobblin-1007
> >>>
> >>> This has been signed with PGP key 0x9BB772F1,corresponding to
> >>> hut...@apache.org, which is included in the repository's KEYS file (
> >>> https://dist.apache.org/repos/dist/release/incubator/gobblin/KEYS).
> This
> >>> key can be found on keyservers, such as:
> >>> http://pgp.mit.edu/pks/lookup?op=get=0x9BB772F1
> >>>
> >>>
> >>> The release candidate has been tagged with release-0.13.0-rc2.
> >>> I've also created a branch 0.13.0.
> >>>
> >>>
> >>> For reference, here is a list of all closed JIRAs tagged with 0.13.0:
> >>> https://issues.apache.org/jira/issues/?filter=12343492
> >>>
> >>> For a summary of the changes in this release, see:
> >>> https://github.com/apache/incubator-gobblin/blob/0.13.0/CHANGELOG.md
> >>>
> >>> Please review and vote. The vote will be open for at least 72 hours.
> >>>
> >>> [ ] +1 approve
> >>> [ ] +0 no opinion
> >>> [ ] -1 disapprove (and reason why)
> >>>
> >>> Thanks,
> >>> Hung, on behalf of the Apache Gobblin PPMC
> >>>
> >>>
> >>>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Does Zipkin need to sign a SGA ?

[John D. Ament]

Thanks Adrian.  Some comments/banter below.

Migrating a repository from one org to another does not require an SGA.  If
it did, we would not be able to have code living in our repos that had
headers other than the ASF standard headers (e.g. BSD licenses, or Apache
License w/ different copyright statements).  The SGA is used to replace the
headers with the standard ASF headers.  We should not block migrating the
repositories over while the SGA/ICLA is worked out.

Resolving the SGA/ICLA situation would block graduation - we should ensure
that the provenance is in place, which is part of the incubation process.
This doesn't need to be solved on day 1, but by the time the podling is
ready to graduate.

With that said, from a pure foundation standpoint it would be ideal to
receive a SGA from Twitter.  Even if the current code doesn't match the
code at the time of Twitter's conversion, it gives us a better IP history
for the codebase to answer questions and deal with any potential problems
that may come up along the way.  However, to be realistic I believe if we
receive an ICLA from the primary contributors based on [1], that should
satisfy enough providence of the codebase, in addition to the contribution
process that Adrian has pointed out below.

Thoughts?

John

[1]: https://github.com/openzipkin/zipkin/graphs/contributors

On Tue, Sep 18, 2018 at 9:25 PM Adrian Cole  wrote:

> There was a process involved at Twitter when we first moved it to the
> openzipkin organization. It was 100% clear that this was an act for
> the community to control the code.  Senior management were involved
> https://groups.google.com/d/msg/zipkin-user/fbOgEZpuQx4/bWH1-__EmCoJ
>
> After that, all the repositories had contributing files like the below
> indicating that all changes we to be redistributable under ASL
>
> https://github.com/openzipkine/zipkin/blob/master/.github/CONTRIBUTING.md#license
> 
>
> There was no collection of contributor agreements beyond this. Most of
> the code except save some UI assets have been completely rewritten
> since the migration to OpenZipkin a few years back.
>
> Hope these details help,
> -A
> On Wed, Sep 19, 2018 at 9:09 AM Craig Russell 
> wrote:
> >
> > Hi Mick,
> >
> > tldr; with my Incubator PMC hat on, "all that needs to be done" is to
> establish that all of the copyright owners sign either a Software Grant or
> an ICLA.
> >
> > In order to establish that Apache has the rights to the code base, every
> line of code needs to have its provenance researched.
> >
> > Looking at the proposal https://wiki.apache.org/incubator/ZipkinProposal
> it seems like most of the code is in the github repository
> https://github.com/openzipkin/zipkin . Is there any code coming from
> another source? Was the original code from Twitter granted to OpenZipkin?
> Is there any documentation of that copyright transfer? Does Twitter retain
> any rights?
> >
> > The capitalization of the "Initial Source" section is a bit strange. But
> can we assume that the only committers to the project are listed at
> https://github.com/openzipkin/zipkin/graphs/contributors ?
> >
> > The proposal also says that "All source code is copyrighted to 'The
> OpenZipkin Authors', to which the existing core community(members list in
> Initial Committers) has the rights to re-assign to the ASF. "
> >
> > It looks like there were many people who contributed a few lines of
> code. Did they sign anything like a Contributor Agreement that grants their
> copyright to The OpenZipkin Authors?
> >
> > Craig
> >
> > > On Sep 18, 2018, at 4:58 PM, Mick Semb Wever  wrote:
> > >
> > >
> > > It's come up that the migration of the github Zipkin repositories to
> ASF requires either a signed SGA or a sign-off from the Secretary. Chris
> raised this on `INFRA-16989 – Zipkin incubator project request for the
> GitHub repositories moving service`.
> > >
> > > I was under the impression that if the Copyright was already held by
> the community, it is held by 'The OpenZipkin Authors', that the ICLA from
> all those authors would suffice and a SGA not be required. And it's news to
> me that this would also require a sign-off from the ASF Secretary.
> > >
> > > What's the correct process here? who can help? should I forward the
> question to the Secretary?
> > >
> > > regards,
> > > Mick
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > Craig L Russell
> > Secretary, Apache Software Foundation
> > c...@apache.org  http://db.apache.org/jdo <
> http://db.apache.org/jdo>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: 

Re: Does Zipkin need to sign a SGA ?

[Adrian Cole]

There was a process involved at Twitter when we first moved it to the
openzipkin organization. It was 100% clear that this was an act for
the community to control the code.  Senior management were involved
https://groups.google.com/d/msg/zipkin-user/fbOgEZpuQx4/bWH1-__EmCoJ

After that, all the repositories had contributing files like the below
indicating that all changes we to be redistributable under ASL
https://github.com/openzipkin/zipkin/blob/master/.github/CONTRIBUTING.md#license

There was no collection of contributor agreements beyond this. Most of
the code except save some UI assets have been completely rewritten
since the migration to OpenZipkin a few years back.

Hope these details help,
-A
On Wed, Sep 19, 2018 at 9:09 AM Craig Russell  wrote:
>
> Hi Mick,
>
> tldr; with my Incubator PMC hat on, "all that needs to be done" is to 
> establish that all of the copyright owners sign either a Software Grant or an 
> ICLA.
>
> In order to establish that Apache has the rights to the code base, every line 
> of code needs to have its provenance researched.
>
> Looking at the proposal https://wiki.apache.org/incubator/ZipkinProposal it 
> seems like most of the code is in the github repository 
> https://github.com/openzipkin/zipkin . Is there any code coming from another 
> source? Was the original code from Twitter granted to OpenZipkin? Is there 
> any documentation of that copyright transfer? Does Twitter retain any rights?
>
> The capitalization of the "Initial Source" section is a bit strange. But can 
> we assume that the only committers to the project are listed at 
> https://github.com/openzipkin/zipkin/graphs/contributors ?
>
> The proposal also says that "All source code is copyrighted to 'The 
> OpenZipkin Authors', to which the existing core community(members list in 
> Initial Committers) has the rights to re-assign to the ASF. "
>
> It looks like there were many people who contributed a few lines of code. Did 
> they sign anything like a Contributor Agreement that grants their copyright 
> to The OpenZipkin Authors?
>
> Craig
>
> > On Sep 18, 2018, at 4:58 PM, Mick Semb Wever  wrote:
> >
> >
> > It's come up that the migration of the github Zipkin repositories to ASF 
> > requires either a signed SGA or a sign-off from the Secretary. Chris raised 
> > this on `INFRA-16989 – Zipkin incubator project request for the GitHub 
> > repositories moving service`.
> >
> > I was under the impression that if the Copyright was already held by the 
> > community, it is held by 'The OpenZipkin Authors', that the ICLA from all 
> > those authors would suffice and a SGA not be required. And it's news to me 
> > that this would also require a sign-off from the ASF Secretary.
> >
> > What's the correct process here? who can help? should I forward the 
> > question to the Secretary?
> >
> > regards,
> > Mick
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org  http://db.apache.org/jdo 
> 

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

Re: Does Zipkin need to sign a SGA ?

[Craig Russell]

Hi Mick,

tldr; with my Incubator PMC hat on, "all that needs to be done" is to establish 
that all of the copyright owners sign either a Software Grant or an ICLA.

In order to establish that Apache has the rights to the code base, every line 
of code needs to have its provenance researched. 

Looking at the proposal https://wiki.apache.org/incubator/ZipkinProposal it 
seems like most of the code is in the github repository 
https://github.com/openzipkin/zipkin . Is there any code coming from another 
source? Was the original code from Twitter granted to OpenZipkin? Is there any 
documentation of that copyright transfer? Does Twitter retain any rights?

The capitalization of the "Initial Source" section is a bit strange. But can we 
assume that the only committers to the project are listed at 
https://github.com/openzipkin/zipkin/graphs/contributors ?

The proposal also says that "All source code is copyrighted to 'The OpenZipkin 
Authors', to which the existing core community(members list in Initial 
Committers) has the rights to re-assign to the ASF. " 

It looks like there were many people who contributed a few lines of code. Did 
they sign anything like a Contributor Agreement that grants their copyright to 
The OpenZipkin Authors?

Craig

> On Sep 18, 2018, at 4:58 PM, Mick Semb Wever  wrote:
> 
> 
> It's come up that the migration of the github Zipkin repositories to ASF 
> requires either a signed SGA or a sign-off from the Secretary. Chris raised 
> this on `INFRA-16989 – Zipkin incubator project request for the GitHub 
> repositories moving service`.
> 
> I was under the impression that if the Copyright was already held by the 
> community, it is held by 'The OpenZipkin Authors', that the ICLA from all 
> those authors would suffice and a SGA not be required. And it's news to me 
> that this would also require a sign-off from the ASF Secretary. 
> 
> What's the correct process here? who can help? should I forward the question 
> to the Secretary? 
> 
> regards,
> Mick
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org  http://db.apache.org/jdo 

Does Zipkin need to sign a SGA ?

[Mick Semb Wever]

It's come up that the migration of the github Zipkin repositories to ASF 
requires either a signed SGA or a sign-off from the Secretary. Chris raised 
this on `INFRA-16989 – Zipkin incubator project request for the GitHub 
repositories moving service`.

I was under the impression that if the Copyright was already held by the 
community, it is held by 'The OpenZipkin Authors', that the ICLA from all those 
authors would suffice and a SGA not be required. And it's news to me that this 
would also require a sign-off from the ASF Secretary. 

What's the correct process here? who can help? should I forward the question to 
the Secretary? 

regards,
Mick

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

Re: Email to be sent to inactive mentors

[Dave Fisher]

As requested - WHIMSY-207  
Show Github username on Roster Tables

Regards,
Dave

> On Sep 17, 2018, at 4:17 PM, sebb  wrote:
> 
> On 17 September 2018 at 23:02, Dave Fisher  wrote:
>> A mapping is made on id.apache.org and shown on whimsy. A patch to add a 
>> github username column to the roster page in whimsy would make life easier.
> 
> Please raise an enhancement JIRA .
> 
>> Regards,
>> Dave
>> 
>> Sent from my iPhone
>> 
>>> On Sep 17, 2018, at 2:24 PM, Ted Dunning  wrote:
>>> 
>>> Indeed.
>>> 
>>> And even if it seems obvious, that isn't always obviously correct.
>>> Establishing a mapping or using an Apache ID is important.
>>> 
 On Mon, Sep 17, 2018 at 4:45 PM Dave Fisher  wrote:
 
 Github id does not often equal Apache id. It is not always obvious.
 
 Regards,
 Dave
 
 Sent from my iPhone
 
> On Sep 17, 2018, at 12:35 PM, Ted Dunning  wrote:
> 
> Obviously, lots of informational activity occurs off the mailing list. A
> great example is answering questions on stack overflow. And ApacheCon
 talks
> which actually led to certain decisions being made should definitely be
> echoed back to the mailing list.
> 
> But apart from all of that GitHub issues should definitely be mirrored
 back
> to the mailing list.  There's no way to justify that an issue tracker is
> not echoed back.
> 
>> On Mon, Sep 17, 2018, 14:05 Julian Hyde  wrote:
>> 
>> By that argument there’s no point speaking at ApacheCon. Because it
>> doesn’t happen on a mailing list.
>> 
>> So let’s not be so strict.
>> 
>> Clearly there are many ways that a mentor can assist. Some of them are
 not
>> measurable (such as having a phone call). But I think any measurable
>> activity should count.
>> 
>> Julian
>> 
>> 
>>> On Sep 17, 2018, at 8:55 AM, sebb  wrote:
>>> 
>>> On 17 September 2018 at 12:10, Justin Mclean  
>> wrote:
 Hi,
 
> Maybe I am missing something here, but how would GitHub contributions
>> contribute to mentoring?
 
 Well I thought it wouldn't which is why I didn’t include it, but as
>> some projects use GitHub issues a lot, so some stuff tends to get
 discussed
>> there rather than on the dev list.
>>> 
>>> "If it did not happen on a mailing list then it did not happen"
>>> If the GitHub issues are not being copied to the mailing lists, then
>>> again I don't see how that contributes to the mentoring process.
>>> 
 There’s a few other factors in this case, but I think it’s on it way
 to
>> being sorted. I'll bring it to the mentors attention and see what they
>> think. (Sorry for being obtuse, but this is a public list.)
>>> 
 Thanks,
 Justin
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Re: [VOTE] Release Apache OpenWhisk (Incubating): python, php and swift runtimes 1.12.0 [RC1]

[Justin Mclean]

Hi,

+1 (binding)

I checked (for all 6 source releases):
- incubating in name
- hashes and signatures correct
- DISCLAIMER exits
- LICENSE and NOTICE good (boilerplate and no 3rd party code bundled)
- No binary files at all
- All source files have ASF headers
- Can compile from source

Just a question any reason you split this up into two votes given it’s the same 
RC?

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 OpenWhisk (Incubating): nodejs, java and docker runtimes 1.12.0 [RC1]

[Justin Mclean]

Hi,

+1 (binding)

I checked (for all 6 source releases):
- incubating in name
- hashes and signatures correct
- DISCLAIMER exits
- LICENSE and NOTICE good (boilerplate and no 3rd party code bundled)
- No binary files at all
- All source files have ASF headers
- Can compile from source

Thanks,
Justin

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

[ANNOUNCE] Apache OpenWhisk Catalog and Apigateway (incubating) 0.9.0 released

[Vincent S Hou]

Hi everyone,

We are pleased to announce that Apache OpenWhisk Catalog and Apigateway 
(incubating) 0.9.0 are released.

Apache OpenWhisk Catalog maintains package catalogs of OpenWhisk, which 
provides an easy way to enhance your application with useful capabilities, and 
to access external services in the ecosystem.
Apache OpenWhisk Apigateway is a performant API Gateway based on Openresty and 
NGINX.

The download links of the current release is available at:
https://openwhisk.apache.org/downloads.html

Vincent Hou
On behalf of the OpenWhisk team

=
*DISCLAIMER*
Apache OpenWhisk Catalog (incubating) is an effort undergoing incubation at The
Apache Software
Foundation (ASF), sponsored by Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

Apache OpenWhisk Apigateway (incubating) is an effort undergoing incubation at 
The
Apache Software
Foundation (ASF), sponsored by Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.


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

[VOTE] Release Apache OpenWhisk (Incubating): python, php and swift runtimes 1.12.0 [RC1]

[Vincent S Hou]

Dear IPMC members,

This is a call for vote to release Apache OpenWhisk (Incubating): OpenWhisk 
python, php and swift runtimes 1.12.0 [RC1].

The Apache OpenWhisk community has voted on and approved a proposal to release 
Apache OpenWhisk (Incubating): python, php and swift runtimes, Version 1.12.0.

We now kindly request the Incubator PMC members to review and vote on this 
incubator release.

OpenWhisk python, php and swift runtimes vote thread:
https://lists.apache.org/thread.html/d0cefe927585b38597805f5f42cae0f46308f8acf14bfd771295392a@%3Cdev.openwhisk.apache.org%3E

OpenWhisk python, php and swift runtimes vote result thread:
https://lists.apache.org/thread.html/498e0f18a3d399d6926bc3fd853af5c910d6c17a304c00c9d8f8ace5@%3Cdev.openwhisk.apache.org%3E

This release comprises of source code distribution only.


For OpenWhisk Runtime Python:
The source code artifact of OpenWhisk Runtime Python can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of OpenWhisk Runtime Python is:
openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz: 
CE78C962 05B22F78 0209C597 034684CE 48321E7D 39516DFC 3A93010C BF9CF4D0 CA2263F6
 287C9963 60A17082 398A1F61 32745543 0199DEEE 3BFABF6E 5C819230
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of OpenWhisk Runtime Python can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-python-1.12.0-incubating-sources.tar.gz.asc


For OpenWhisk Runtime PHP:
The source code artifact of OpenWhisk Runtime PHP can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of OpenWhisk Runtime PHP is:
openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz: 
417DF65E 881BEC2E 6F58F135 45E1C9EA 4C8CA88A 67A31B82 361D6818 796CC605 46484A35
 411E255C B29F1BAD 9298EB57 F89DD64E E340511C EF4ADBCE 948F87DB
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of OpenWhisk Runtime PHP can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-php-1.12.0-incubating-sources.tar.gz.asc


For OpenWhisk Runtime Docker:
The source code artifact of OpenWhisk Runtime Docker can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of OpenWhisk Runtime Docker is:
openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz: 
E16164FE 9AD218DF 5ACDA598 BC360A43 B52A9B3F F59B2BF4 429B177B F539804A 8166AFED
 FBA9E0F0 8918EDFC 7A485DA6 545DF3C8 C7924B68 D9DE9C22 99F783AC
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of OpenWhisk Runtime Docker can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-swift-1.12.0-incubating-sources.tar.gz.asc



KEYS file is available at:
https://www.apache.org/dist/incubator/openwhisk/KEYS
This key has been validated here: 
http://pgp.mit.edu/pks/lookup?search=houshengbo=index

This is the first time that Apache OpenWhisk: python, php and swift runtimes 
request for a release, so there is no file of CHANGELOG.

The documentation on how to verify the artifacts can be found at:
https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the+release+checklist+and+vote+on+OpenWhisk+modules+under+Apache

We are currently using the tool called 
openwhisk-release(https://github.com/apache/incubator-openwhisk-release) to 
release all the modules of OpenWhisk. The instruction for release managers can 
be found at: 
https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md.
 This tool
supports  both manual and automated modes to package the source code, sign the 
artifacts and upload the artifacts into Apache SVN repositories.

The vote will be open for at least 72 hours or until necessary number of votes 
are reached.

Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: 

[VOTE] Release Apache OpenWhisk (Incubating): nodejs, java and docker runtimes 1.12.0 [RC1]

[Vincent S Hou]

Dear IPMC members,

This is a call for vote to release Apache OpenWhisk (Incubating): OpenWhisk 
nodejs, java and docker runtimes 1.12.0 [RC1].

The  Apache OpenWhisk community has voted on and approved a proposal to release 
Apache OpenWhisk (Incubating): nodejs, java and docker runtimes, Version 1.12.0.

We now kindly request the Incubator PMC members to review and vote on this 
incubator release.

OpenWhisk nodejs, java and docker runtimes vote thread:
https://lists.apache.org/thread.html/443cbd5eb5f2b84c3b34b92bd8585a36cd8c1ce52ef5453a7ad33282@%3Cdev.openwhisk.apache.org%3E

OpenWhisk nodejs, java and docker runtimes vote result thread:
https://lists.apache.org/thread.html/257f62b54b1fd14e7b6e2347d0263169821f55ac4f57355e44c84194@%3Cdev.openwhisk.apache.org%3E

This release comprises of source code distribution only.


For OpenWhisk Runtime Nodejs:
The source code artifact of OpenWhisk Runtime Nodejs can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-nodejs-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of OpenWhisk Runtime Nodejs is:
openwhisk-runtime-nodejs-1.12.0-incubating-sources.tar.gz: 
D046ED19 A813D9A9 96986002 C7065C7A 41FDF48A B87440D9 CF86B227 B4E2D3BF A63DC4C0
 7BAC979F 998B9867 3492A8A5 07F739ED 822BFC14 2E44EFA9 7D29DF23
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-nodejs-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of OpenWhisk Runtime Nodejs can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-nodejs-1.12.0-incubating-sources.tar.gz.asc


For OpenWhisk Runtime Java:
The source code artifact of OpenWhisk Runtime Java can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of OpenWhisk Runtime Java is:
openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz: 
FADF0287 E4A65B8C F56F0CAD 128CB02E 89B701EA A621D394 6A8412FD 05522B44 1AD4EC05
 A52FF4CE 6B73FC6D 44B6730F E4023923 EE92C1C9 02DAC10F 1DB253C3
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of OpenWhisk Runtime Java can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-java-1.12.0-incubating-sources.tar.gz.asc


For OpenWhisk Runtime Docker:
The source code artifact of OpenWhisk Runtime Docker can be found at:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-docker-1.12.0-incubating-sources.tar.gz

The SHA-512 checksum for the artifact of OpenWhisk Runtime Docker is:
openwhisk-runtime-docker-1.12.0-incubating-sources.tar.gz: 
D668D079 CFBF8DBB 7356D50B 609F7A42 49C588BD 9BADC57B A06C025A CA5BFDFF BB3A3E72
 EF612A43 A4179A04 4EF12FD6 9BAA8047 46197280 6037C5EC BAA3F626
which can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-docker-1.12.0-incubating-sources.tar.gz.sha512

The signature of the artifact of OpenWhisk Runtime Docker can be found via:
https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-1.12.0-incubating-rc1/openwhisk-runtime-docker-1.12.0-incubating-sources.tar.gz.asc



KEYS file is available at:
https://www.apache.org/dist/incubator/openwhisk/KEYS
This key has been validated here: 
http://pgp.mit.edu/pks/lookup?search=houshengbo=index

This is the first time that Apache OpenWhisk: nodejs, java and docker runtimes 
request for a release, so there is no file of CHANGELOG.

The documentation on how to verify the artifacts can be found at:
https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the+release+checklist+and+vote+on+OpenWhisk+modules+under+Apache

We are currently using the tool called 
openwhisk-release(https://github.com/apache/incubator-openwhisk-release) to 
release all the modules of OpenWhisk. The instruction for release managers can 
be found at: 
https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md.
 This tool
supports  both manual and automated modes to package the source code, sign the 
artifacts and upload the artifacts into Apache SVN repositories.

The vote will be open for at least 72 hours or until necessary number of votes 
are reached.

Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason


Best wishes.
Vincent Hou (侯胜博)
On behalf of OpenWhisk team


-
To 

[RESULT][VOTE] Release Apache OpenWhisk (Incubating): OpenWhisk catalog and apigateway 0.9.0 [RC1]

[Vincent S Hou]

Hi all,

Thanks a lot for taking the time to vote the release 0.9.0 of OpenWhisk: 
catalog and apigateway modules

The vote is passed with 3 +1s (binding).

Binding +1:

Jim Jagielski
Justin Mclean
Sergio Fernández

There is no -1 vote or 0 vote.

I will proceed with the next steps for the release.
 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States


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

Re: [VOTE] Release Apache OpenWhisk (Incubating): OpenWhisk catalog and apigateway 0.9.0 [RC1]

[Vincent S Hou]

Hi everyone,

Thank you for your votes. This mail thread is closed now, since it has been 
open for over 72 hours.
I will consolidate the votes and send off the result.
Thanks.

 
Best wishes.
Vincent Hou (侯胜博)

Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud

Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
Phone: +1(919)254-7182
Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States

-Jim Jagielski  wrote: -
To: general 
From: Jim Jagielski 
Date: 09/18/2018 07:53AM
Subject: Re: [VOTE] Release Apache OpenWhisk (Incubating): OpenWhisk catalog 
and apigateway 0.9.0 [RC1]

+1 (binding)

> On Sep 10, 2018, at 11:14 AM, Vincent S Hou  wrote:
> 
> Dear IPMC members,
> 
> This is a call for vote to release Apache OpenWhisk (Incubating): OpenWhisk 
> catalog and apigateway 0.9.0 [RC1].
> 
> The  Apache OpenWhisk community has voted on and approved a proposal to 
> release Apache OpenWhisk (Incubating): catalog and apigateway, Version 0.9.0.
> 
> We now kindly request the Incubator PMC members to review and vote on this 
> incubator release.
> 
> Apache OpenWhisk Catalog maintains the package catalogs of openwhisk. In 
> OpenWhisk, the catalog of packages gives you an easy way to enhance your app 
> with useful capabilities, and to access external services in the ecosystem.
> Apache OpenWhisk Apigateway is a performant API Gateway based on Openresty 
> and NGINX.
> 
> OpenWhisk Catalog and apigateway vote thread:
> https://lists.apache.org/thread.html/87b2d4006c3502a6cc402ea54f940ddb5ae9dcae958779d60a75d875@%3Cdev.openwhisk.apache.org%3E
> 
> OpenWhisk Catalog and apigateway vote result thread:
> https://lists.apache.org/thread.html/8df308901539b825466505e7e51df32ba511fa2a39de8335a694bd05@%3Cdev.openwhisk.apache.org%3E
> 
> This release comprises of source code distribution only.
> 
> 
> For OpenWhisk Catalog:
> The source code artifact of OpenWhisk Catalog can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz
> 
> The SHA-512 checksum for the artifact of openwhisk catalog is:
> openwhisk-catalog-0.9.0-incubating-sources.tar.gz:
> 3BA28A6A 88B7700D 92929843 E742D6ED 65F3D48A DD537965 C0BA9822 E2414DCD 
> 010EFE8B
> 4774D652 1CA6E3F7 6DFF6BEE 76FA982D 5070290B 20CBA110 7750F7ED
> which can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.sha512
> 
> The signature of the artifact of openwhisk catalog can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.asc
> 
> 
> For OpenWhisk Apigateway:
> The source code artifact of OpenWhisk Apigateway can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz
> 
> The SHA-512 checksum for the artifact of openwhisk apigateway is:
> openwhisk-apigateway-0.9.0-incubating-sources.tar.gz:
> F62A50B7 970540B8 CA3C1796 13A75743 537B4374 3F0B9EA5 F4A35396 98A57D8E 
> EAA0EFA5
> AB8AF26D 46E2E6A4 7794AE50 03887F11 6D7D9825 2EA08733 77B369DA
> which can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.sha512
> 
> The signature of the artifact of openwhisk apigateway can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.asc
> 
> 
> KEYS file is available at:
> https://www.apache.org/dist/incubator/openwhisk/KEYS
> This key has been validated here: 
> http://pgp.mit.edu/pks/lookup?search=houshengbo=index
> 
> This is the first time that Apache OpenWhisk: Catalog and Apigateway request 
> for a release, so there is no file of CHANGELOG.
> 
> The documentation on how to verify the artifacts can be found at:
> https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the+release+checklist+and+vote+on+OpenWhisk+modules+under+Apache
> 
> We are currently using the tool called 
> openwhisk-release(https://github.com/apache/incubator-openwhisk-release) to 
> release all the modules of OpenWhisk. The instruction for release managers 
> can be found at: 
> https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md.
>  This tool
> supports  both manual and automated modes to package the source code, sign 
> the artifacts and upload the artifacts into Apache SVN repositories.
> 
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
> 
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> Best wishes.
> Vincent Hou 

Re: [VOTE]- Release Apache Weex (Incubating) 0.19.0 [RC4]

[Willem Jiang]

+1 (Binding)

1. Checked signed key and sha512 of source package
2. LICENSE and NOTICE are OK in source code
3. Apache RAT checked
4. DISCLAIMER existed

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Sep 17, 2018 at 2:22 PM Hanks Zhang  wrote:
>
> Here are the vote threads of RC4.
>
> Vote:
> https://lists.apache.org/thread.html/cdfd9cc5b9ade0bd86fc35a8e56fb76d45b1a785b1025de67f5b@%3Cdev.weex.apache.org%3E
>
> Vote Result:
> https://lists.apache.org/thread.html/935ccb2ee4ccfe7a9e775aabb155770dd1b7157fcc89ed0369b92998@%3Cdev.weex.apache.org%3E
>
> Best Regards,
> Hanks Zhang

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

Re: [VOTE] Apache Gobblin 0.13.0 release RC2

[Jim Jagielski]

Sorry for the delay...

+1 for the source release (binding) but I agree w/ removing the binary

> On Sep 17, 2018, at 6:27 PM, Abhishek Tiwari  wrote:
> 
> Ping.
> 
> Can someone help us review and vote :)
> 
> Regards
> Abhishek
> 
> On Tue, Sep 11, 2018 at 2:59 PM Abhishek Tiwari  wrote:
> 
>> +1
>> 
>> Abhishek
>> 
>> On Tue, Sep 11, 2018 at 2:51 PM Hung Tran  wrote:
>> 
>>> Adding some CCs since the message was not received.
>>> 
>>> Hung.
>>> --
>>> *From:* Hung Tran 
>>> *Sent:* Monday, September 10, 2018 9:51:31 PM
>>> *To:* general@incubator.apache.org
>>> *Subject:* [VOTE] Apache Gobblin 0.13.0 release RC2
>>> 
>>> The Apache Gobblin community has voted on and approved the release of
>>> Apache Gobblin 0.13.0 (incubating):
>>> 
>>> 
>>> https://www.mail-archive.com/dev@gobblin.incubator.apache.org/msg02175.html
>>> 
>>> Results:
>>> 3 binding +1 votes
>>> No 0 votes
>>> No -1 votes
>>> 
>>> The feedback from previous release candidates has been addressed:
>>> 
>>> RC1 thread:
>>> https://www.mail-archive.com/general@incubator.apache.org/msg64403.html
>>> Resolution:
>>> Removed the binary release tar from the source release tar.
>>> 
>>> I'd like to call a vote in general to approve the release.
>>> 
>>> The source release candidate RC2 with convenience binaries can be
>>> downloaded here:
>>> https://dist.apache.org/repos/dist/dev/incubator/gobblin/apache-gobblin
>>> -incubating-0.13.0-rc2/
>>> 
>>> The artifacts (i.e. JARs) corresponding to this release candidate can be
>>> found here:
>>> https://repository.apache.org/content/repositories/orgapachegobblin-1007
>>> 
>>> This has been signed with PGP key 0x9BB772F1,corresponding to
>>> hut...@apache.org, which is included in the repository's KEYS file (
>>> https://dist.apache.org/repos/dist/release/incubator/gobblin/KEYS). This
>>> key can be found on keyservers, such as:
>>> http://pgp.mit.edu/pks/lookup?op=get=0x9BB772F1
>>> 
>>> 
>>> The release candidate has been tagged with release-0.13.0-rc2.
>>> I've also created a branch 0.13.0.
>>> 
>>> 
>>> For reference, here is a list of all closed JIRAs tagged with 0.13.0:
>>> https://issues.apache.org/jira/issues/?filter=12343492
>>> 
>>> For a summary of the changes in this release, see:
>>> https://github.com/apache/incubator-gobblin/blob/0.13.0/CHANGELOG.md
>>> 
>>> Please review and vote. The vote will be open for at least 72 hours.
>>> 
>>> [ ] +1 approve
>>> [ ] +0 no opinion
>>> [ ] -1 disapprove (and reason why)
>>> 
>>> Thanks,
>>> Hung, on behalf of the Apache Gobblin PPMC
>>> 
>>> 
>>> 


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

Re: [VOTE] Release Apache OpenWhisk (Incubating): OpenWhisk catalog and apigateway 0.9.0 [RC1]

[Jim Jagielski]

+1 (binding)

> On Sep 10, 2018, at 11:14 AM, Vincent S Hou  wrote:
> 
> Dear IPMC members,
> 
> This is a call for vote to release Apache OpenWhisk (Incubating): OpenWhisk 
> catalog and apigateway 0.9.0 [RC1].
> 
> The  Apache OpenWhisk community has voted on and approved a proposal to 
> release Apache OpenWhisk (Incubating): catalog and apigateway, Version 0.9.0.
> 
> We now kindly request the Incubator PMC members to review and vote on this 
> incubator release.
> 
> Apache OpenWhisk Catalog maintains the package catalogs of openwhisk. In 
> OpenWhisk, the catalog of packages gives you an easy way to enhance your app 
> with useful capabilities, and to access external services in the ecosystem.
> Apache OpenWhisk Apigateway is a performant API Gateway based on Openresty 
> and NGINX.
> 
> OpenWhisk Catalog and apigateway vote thread:
> https://lists.apache.org/thread.html/87b2d4006c3502a6cc402ea54f940ddb5ae9dcae958779d60a75d875@%3Cdev.openwhisk.apache.org%3E
> 
> OpenWhisk Catalog and apigateway vote result thread:
> https://lists.apache.org/thread.html/8df308901539b825466505e7e51df32ba511fa2a39de8335a694bd05@%3Cdev.openwhisk.apache.org%3E
> 
> This release comprises of source code distribution only.
> 
> 
> For OpenWhisk Catalog:
> The source code artifact of OpenWhisk Catalog can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz
> 
> The SHA-512 checksum for the artifact of openwhisk catalog is:
> openwhisk-catalog-0.9.0-incubating-sources.tar.gz:
> 3BA28A6A 88B7700D 92929843 E742D6ED 65F3D48A DD537965 C0BA9822 E2414DCD 
> 010EFE8B
> 4774D652 1CA6E3F7 6DFF6BEE 76FA982D 5070290B 20CBA110 7750F7ED
> which can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.sha512
> 
> The signature of the artifact of openwhisk catalog can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.asc
> 
> 
> For OpenWhisk Apigateway:
> The source code artifact of OpenWhisk Apigateway can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz
> 
> The SHA-512 checksum for the artifact of openwhisk apigateway is:
> openwhisk-apigateway-0.9.0-incubating-sources.tar.gz:
> F62A50B7 970540B8 CA3C1796 13A75743 537B4374 3F0B9EA5 F4A35396 98A57D8E 
> EAA0EFA5
> AB8AF26D 46E2E6A4 7794AE50 03887F11 6D7D9825 2EA08733 77B369DA
> which can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.sha512
> 
> The signature of the artifact of openwhisk apigateway can be found via:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.asc
> 
> 
> KEYS file is available at:
> https://www.apache.org/dist/incubator/openwhisk/KEYS
> This key has been validated here: 
> http://pgp.mit.edu/pks/lookup?search=houshengbo=index
> 
> This is the first time that Apache OpenWhisk: Catalog and Apigateway request 
> for a release, so there is no file of CHANGELOG.
> 
> The documentation on how to verify the artifacts can be found at:
> https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the+release+checklist+and+vote+on+OpenWhisk+modules+under+Apache
> 
> We are currently using the tool called 
> openwhisk-release(https://github.com/apache/incubator-openwhisk-release) to 
> release all the modules of OpenWhisk. The instruction for release managers 
> can be found at: 
> https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md.
>  This tool
> supports  both manual and automated modes to package the source code, sign 
> the artifacts and upload the artifacts into Apache SVN repositories.
> 
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
> 
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> Best wishes.
> Vincent Hou (侯胜博)
> 
> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM Cloud
> 
> Notes ID: Vincent S Hou/Raleigh/IBM, E-mail: s...@us.ibm.com,
> Phone: +1(919)254-7182
> Address: 4205 S Miami Blvd (Cornwallis Drive), Durham, NC 27703, United States
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help

[Kevin A. McGrail]

On 9/18/2018 12:11 AM, Tan,Zhongyi wrote:
> Thanks，Kevin.
>
Thanks, Tan.

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

Re: [VOTE] Release Apache OpenWhisk (Incubating): OpenWhisk catalog and apigateway 0.9.0 [RC1]

[Sergio Fernández]

+1 (binding)

So far I've checked:

- incubating suffix and disclaimer
- signatures and checksums
- LICENSE files
- Apache License headers
- No binaries distributed
- No unexpected binary files

As well as Justin, I have one minor comment that doesn't block the release:
some JavaScript files do use an incorrect (shorter) version of the Apache
License header. I know the JS build stack may not support that. But if
there is no automatic add/check in the build, the project has to audit
those manually on regular basis.

I'm very happy to see this podling I used to mentor moving forward :-)

On Mon, Sep 10, 2018, 08:15 Vincent S Hou  wrote:

> Dear IPMC members,
>
> This is a call for vote to release Apache OpenWhisk (Incubating):
> OpenWhisk catalog and apigateway 0.9.0 [RC1].
>
> The  Apache OpenWhisk community has voted on and approved a proposal to
> release Apache OpenWhisk (Incubating): catalog and apigateway, Version
> 0.9.0.
>
> We now kindly request the Incubator PMC members to review and vote on this
> incubator release.
>
> Apache OpenWhisk Catalog maintains the package catalogs of openwhisk. In
> OpenWhisk, the catalog of packages gives you an easy way to enhance your
> app with useful capabilities, and to access external services in the
> ecosystem.
> Apache OpenWhisk Apigateway is a performant API Gateway based on Openresty
> and NGINX.
>
> OpenWhisk Catalog and apigateway vote thread:
>
> https://lists.apache.org/thread.html/87b2d4006c3502a6cc402ea54f940ddb5ae9dcae958779d60a75d875@%3Cdev.openwhisk.apache.org%3E
>
> OpenWhisk Catalog and apigateway vote result thread:
>
> https://lists.apache.org/thread.html/8df308901539b825466505e7e51df32ba511fa2a39de8335a694bd05@%3Cdev.openwhisk.apache.org%3E
>
> This release comprises of source code distribution only.
>
>
> For OpenWhisk Catalog:
> The source code artifact of OpenWhisk Catalog can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz
>
> The SHA-512 checksum for the artifact of openwhisk catalog is:
> openwhisk-catalog-0.9.0-incubating-sources.tar.gz:
> 3BA28A6A 88B7700D 92929843 E742D6ED 65F3D48A DD537965 C0BA9822 E2414DCD
> 010EFE8B
>  4774D652 1CA6E3F7 6DFF6BEE 76FA982D 5070290B 20CBA110 7750F7ED
> which can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.sha512
>
> The signature of the artifact of openwhisk catalog can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-catalog-0.9.0-incubating-sources.tar.gz.asc
>
>
> For OpenWhisk Apigateway:
> The source code artifact of OpenWhisk Apigateway can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz
>
> The SHA-512 checksum for the artifact of openwhisk apigateway is:
> openwhisk-apigateway-0.9.0-incubating-sources.tar.gz:
> F62A50B7 970540B8 CA3C1796 13A75743 537B4374 3F0B9EA5 F4A35396 98A57D8E
> EAA0EFA5
>  AB8AF26D 46E2E6A4 7794AE50 03887F11 6D7D9825 2EA08733 77B369DA
> which can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.sha512
>
> The signature of the artifact of openwhisk apigateway can be found via:
>
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-apigateway-0.9.0-incubating-sources.tar.gz.asc
>
>
> KEYS file is available at:
> https://www.apache.org/dist/incubator/openwhisk/KEYS
> This key has been validated here:
> http://pgp.mit.edu/pks/lookup?search=houshengbo=index
>
> This is the first time that Apache OpenWhisk: Catalog and Apigateway
> request for a release, so there is no file of CHANGELOG.
>
> The documentation on how to verify the artifacts can be found at:
>
> https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the+release+checklist+and+vote+on+OpenWhisk+modules+under+Apache
>
> We are currently using the tool called openwhisk-release(
> https://github.com/apache/incubator-openwhisk-release) to release all the
> modules of OpenWhisk. The instruction for release managers can be found at:
> https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md.
> This tool
> supports  both manual and automated modes to package the source code, sign
> the artifacts and upload the artifacts into Apache SVN repositories.
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Best wishes.
> Vincent Hou (侯胜博)
>
> Advisory Software Engineer, OpenWhisk Contributor, Open Technology, IBM
> Cloud
>
> Notes 

Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help

[Tan,Zhongyi]

Hi，Dave，
It is a pity that you have little time to be mentor of brpc.
Never mind, you have help us greatly.

Hi, guys, 
is there anyone who volunteer to be champion or mentor of brpc?

Thanks
 

在 2018/9/18 下午12:29， "Dave Fisher"  写入:

>Hi Zhongyi Tan,
>
>With Daffofil, Doris and eCharts I am mentoring three projects. I will
>watch this one as there are some similar challenges, but I don’t think I
>have time to Mentor this one. (I may pick up one other who have lost an
>inactive mentor.)
>
>All the best,
>Dave
>
>Sent from my iPhone
>
>> On Sep 17, 2018, at 9:11 PM, Tan,Zhongyi  wrote:
>> 
>> Thanks，Kevin.
>> 
>> Your help is very appreciated.
>> We will add you to mentor list.
>> 
>> 
>> 在 2018/9/17 下午6:52， "Kevin A. McGrail"  写入:
>> 
>>> Tan, I would be happy to help mentor this project as well.
>>> 
 On 9/17/2018 12:18 AM, Jean-Baptiste Onofré wrote:
 Hi,
 
 With great pleasure. I'm not sure I will contribute so much on the
code,
 but I would be more than happy to help and guide the incubation.
 
 Regards
 JB
 
> On 17/09/2018 05:21, Tan,Zhongyi wrote:
> Hi， JB
> 
> Would you like to be champion for this project？
> 
> Thanks
> 
> 
> 在 2018/9/14 下午5:20， "Jean-Baptiste Onofré"  写入:
> 
>> Thanks for the details. It helps.
>> 
>> Let me do a new pass on the proposal.
>> 
>> Regards
>> JB
>> 
>>> On 14/09/2018 10:19, Tan,Zhongyi wrote:
>>> Hi， JB，
>>> Below are our answers to your questions，
>>> Please check，
>>> Thanks.
>>> 
>>> 1. brpc doesn't depend on any other Apache projects. brpc currently
>>> depends on the following external project:
>>>   - leveldb
>>>   - openssl
>>>   - protobuf
>>>   - gperftools (optional)
>>>   - glog (optional)
>>>   - gtest
>>> 
>>> 2. brpc is alternative for C++ rpc fcramework，implementations for
>>> other
>>> languages are not competitive enough (comparing to gRPC) to be
>>> opensourced.  Besides the basic RPC function, brpc(C++) provides
>>> additional features than gRPC:
>>>   - Clients and servers can talk in multiple protocols: baidu
>>> internal
>>> protocol, http, thrift, http2(communicable with gRPC, the PR is
>>>under
>>> reviewing) and tens of other protocols.
>>>   - Proved better performance in different scenarios, by
>>>eliminating
>>> locks on hotpaths and using goroutine-like concurrency(bthread)
>>>with
>>> cache
>>> friendly data structures
>>>   - More useful debugging utilities to help C++ programers build
>>> solid
>>> online services.
>>>   - Various access patterns such as one-to-one, one-to-many(fan
>>> out),
>>> streaming, which simplify implementation of complex distributed
>>> services.
>>> 
>>> 
>>> 
>>> 在 2018/9/13 下午3:00， "Jean-Baptiste Onofré"  写入:
>>> 
 Hi,
 
 It's an interesting project. I have two questions:
 
 1. do you have some interactions/dependencies with other Apache
 projects, especially CXF for instance ?
 2. what's the comparison between brpc and gRPC ? An alternative ?
 Different features ?
 
 I might be interested by mentoring the project, I would like to
 understand exactly the target/purposes.
 
 Thanks !
 Regards
 JB
 
> On 13/09/2018 08:20, Tan,Zhongyi wrote:
> Hi, guys,
> 
> brpc is one open source RPC framework that is very popular in
>baidu
> and
> china.
> We want to contribute it to ASF to make it more successful.
> And we are looking for champion and mentor for this project,
> if anyone would like to volunteer, we will be very appreciated.
> 
> Thanks.
> 
> 
> Here is the draft for brpc proposal.
> 
> 
> # brpc Proposal
> 
> ## Abstract
> 
> brpc is an industrial-grade RPC framework for building reliable
>and
> high-performance services.
> 
> ## Proposal
> 
> We propose to contribute the brpc codebase and associated
> artifacts(e.g. documentation etc.) to the Apache Software
> Foundation,
> and aim to  build a wider open community around it in the 'Apache
> Way'.
> 
> 
> ## Background
> 
> The RPC framework used in Baidu before 2014 was developed at 2008
> and
> limited in protocols and performance, and there were also
>serveral
> implementations focused on their own scenarios from Baidu's
> different
> BU. As an infrastructural team in Baidu, we tried to build a new
> framework to unify all RPC scenarios inside. The framework was
> named
> "baidu-rpc"