Re: [VOTE] Apache Tuweni 0.9.0-incubating

2019-10-07 Thread Jim Jagielski
+1 (binding) - carried over from podling release vote

> On Oct 5, 2019, at 11:08 PM, Antoine Toulme  wrote:
> 
> Hi all,
> The Tuweni community voted on and has approved a proposal to release Apache 
> Tuweni 0.9.0-incubating.
> 
> Pursuant to the Releases section of the Incubation Policy and we would now 
> like to request the permission of the Incubator PMC to publish the tarball on 
> the Tuweni Download page.
> Note we have collected 3 +1 votes from IPMC members and have therefore the 
> necessary minimum votes.
> 
> The following changes were made since 0.8.2:
> * Scuttlebutt improvements: we now support calling the social graphs and 
> additional RPC methods.
> * Hobbits v3 support: we use binary messages.
> * SSZ improvements for homogeneous types
> 
> 
> Thanks
> Antoine
> 
> Vote thread:
> https://lists.apache.org/thread.html/95256d891a80a3bb9edabddebe8bddf6a3ad246b541a6b75665d10a2@%3Cdev.tuweni.apache.org%3E
> 
> Vote result:
> https://lists.apache.org/thread.html/caf4b015c6b0bdf94e44af2fc07e41f41dff9016e7e55ebd9811d215@%3Cdev.tuweni.apache.org%3E
> -
> 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: [MENTORS] Mentor guidance document

2019-09-24 Thread Jim Jagielski
First of all, thx for putting this together and thx for starting up a 
discussion/effort in the Incubator about how to improve the Incubator instead 
of just deciding that it is broken and needs to be replaced and/or alternatives 
found (although both of those PoVs have merit).

Let me spend some time digging in on this... It looks like it has usage and 
benefits not only w/i Incubator but elsewhere.

> On Aug 17, 2019, at 9:26 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> I've had hoped I'd get more of a response to the mentor guidance 
> documentation I suggested. Perhaps it got lost in the other noise?
> 
> https://cwiki.apache.org/confluence/display/INCUBATOR/Mentor+Guidance
> 
> Jim and Ross, you have recently stated that you are concerned about the 
> erosion of our values and principles. It would be great to see your input on 
> this. If you have other idea one how these values can be better passed to 
> incubating incubation it would be great to hear.
> 
> I also welcome other IPMC members who have experience and can offer some 
> advice to other mentors.
> 
> 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



Re: [IP CLEARANCE] Apache Pulsar - Pulsar Manager

2019-09-16 Thread Jim Jagielski
+1

> On Sep 11, 2019, at 3:47 AM, Sijie Guo  wrote:
> 
> Hi all,
> 
> Apache Pulsar received a donation which adds a new web UI - Pulsar Manager
> to Pulsar. Pulsar Manager is a web-based GUI management and monitoring tool
> that helps
> administrators and users manage and monitor tenants, namespaces, topics,
> subscriptions, brokers, clusters, and so on, and supports dynamic
> configuration of multiple environments.
> 
> The IP clearance form can be found at:
> http://incubator.apache.org/ip-clearance/pulsar-manager.html
> 
> The contribution can be found at:
> https://github.com/streamnative/pulsar-manager
> The git repo will be transferred to apache at the end of the process.
> 
> Please vote to approve this contribution. Lazy consensus applies: if no -1
> votes are being cast within the next 72 hours, the vote passes.
> 
> Thanks,
> Sijie


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



Re: [MENTORS] Mentor guidance document

2019-08-23 Thread Jim Jagielski
Ross said everything that I would have said... only better.

> On Aug 18, 2019, at 5:35 PM, Ross Gardler  wrote:
> 
> Only replying because I'm called out explicitly.
> 
> Documentation does not solve the problem. If someone doesn't already "get" 
> this stuff then they should not be mentoring. Having a document does not 
> replace for selecting good mentors who have the time to do the job right.
> 
> It's a good effort in the broader context, but doesn't solve the problem I 
> see in the IPMC (insufficient high quality mentoring coupled with too much 
> application of rules in the process). The proposed doc is interesting but 
> it's just more words, We need more action.
> 
> How would I solve the problem? If I were championing another project into the 
> ASF I would carefully select mentors, just as I have in the past. I'd select 
> those who don't need the above document and who I'm confident will pay 
> attention and be constructive. I'd then work with those mentors and the 
> community to ensure people coming through the process are equipped to help me 
> on the next project I champion.
> 
> This is not new. It's how we setup the Incubator in the first place. But over 
> the years it has become a machine rather than personal relationships. More 
> words about the design of the machine won't change this.
> 
> I don't mean to say the effort you are putting in is wasted effort. Clarity 
> in what is expected can help the podlings, but I don't see how this can 
> really help those people I would already trust to be good mentors i.e. People 
> who have a vested interest in the success of the project and already know how 
> to apply the Apache Way to new communities so that they might flourish in 
> their own way.
> 
> Ross
> 
> 
> ---
> 
> Sent from my phone, you know what that means - sorry
> 
> 
> From: Justin Mclean 
> Sent: Saturday, August 17, 2019 6:26:32 PM
> To: general@incubator.apache.org 
> Subject: Re: [MENTORS] Mentor guidance document
> 
> Hi,
> 
> I've had hoped I'd get more of a response to the mentor guidance 
> documentation I suggested. Perhaps it got lost in the other noise?
> 
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FINCUBATOR%2FMentor%2BGuidancedata=02%7C01%7C%7C0e716c1bb8a74438cd0108d7237b24aa%7C84df9e7fe9f640afb435%7C1%7C0%7C637016884106582384sdata=9v85p9zRNDFHPp3yJgpVp7GUz%2F0NDNvC8vQuZjT4X50%3Dreserved=0
> 
> Jim and Ross, you have recently stated that you are concerned about the 
> erosion of our values and principles. It would be great to see your input on 
> this. If you have other idea one how these values can be better passed to 
> incubating incubation it would be great to hear.
> 
> I also welcome other IPMC members who have experience and can offer some 
> advice to other mentors.
> 
> 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



Re: [MENTORS] Mentor guidance document

2019-08-19 Thread Jim Jagielski
I'll reply/respond asap.

> On Aug 17, 2019, at 9:26 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> I've had hoped I'd get more of a response to the mentor guidance 
> documentation I suggested. Perhaps it got lost in the other noise?
> 
> https://cwiki.apache.org/confluence/display/INCUBATOR/Mentor+Guidance
> 
> Jim and Ross, you have recently stated that you are concerned about the 
> erosion of our values and principles. It would be great to see your input on 
> this. If you have other idea one how these values can be better passed to 
> incubating incubation it would be great to hear.
> 
> I also welcome other IPMC members who have experience and can offer some 
> advice to other mentors.
> 
> 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



Re: [VOTE] Release Apache Superset (incubating) 0.34.0 [RC1]

2019-08-19 Thread Jim Jagielski
+1 (binding)

> On Aug 19, 2019, at 12:41 AM, Maxime Beauchemin  
> wrote:
> 
> Hi IPMC,
> 
> The Apache Superset community has voted on and approved a proposal to
> release
> Apache Superset (incubating) 0.34.0 (rc1). *This would be the first Apache
> release of Superset.*
> 
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
> 
> Apache Superset (incubating) is a business intelligence web application
> 
> The community voting thread can be found here:
> https://lists.apache.org/thread.html/c9ad3ce592a695ceeabfa92969c00c0d7be8e3420b6a221c7e806f40@%3Cdev.superset.apache.org%3E
> 
> The release candidate has been tagged in GitHub as tag 0.34.0rc1
> ,
> available here:
> https://github.com/apache/incubator-superset/releases/tag/0.34.0rc1
> 
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/superset/
> 
> Release artifacts are signed with the key located here:
> https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
> 
> This vote will be open for at least 72 hours. The vote will pass if a
> majority of at least three +1 IPMC votes are cast.
> 
> [ ] +1 Release this package as Apache Superset (incubating) 0.15.1
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
> 
> Thank you IPMC! We appreciate your efforts in helping the Apache Superset
> community to validate this release.
> 
> On behalf of the Apache Superset Community,
> 
> Max
> 
> 
> 
> Apache Superset (incubating) is an effort undergoing incubation at The
> Apache
> Software Foundation (ASF), sponsored by the Apache 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



Re: Business decisions and risk (was: [DISCUSS] IPMC votes on releases)

2019-08-15 Thread Jim Jagielski
FTR: I think the biggest risk to the foundation are not these procedural 
aspects, like releases, but the gradual but inexorable decline in our culture 
and our principles. That is, or at least should be, the bigger concern. And I 
think the Incubator should take that risk much more seriously and to heart.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Showcase your project at ApacheCON at a Podling's Shark Tank

2019-08-15 Thread Jim Jagielski
"but for now:

SIMPLY REPLY TO THIS EMAIL if you're interested.
"

:)

> On Aug 15, 2019, at 8:44 AM, Josh Fischer  wrote:
> 
> I tried to click on both links.  Both showed up as a Page Not Found
> 
> On Wed, Aug 14, 2019 at 3:45 PM Roman Shaposhnik  wrote:
> 
>> Hi Podlings!
>> 
>> in less than a month we're going to have our first
>> ApacheCON this year -- the one in Las Vegas. In
>> about two month there will be one more in Berlin.
>> 
>> These are not your regular ApacheCONs -- these are
>> 20th Anniversary of ASF ApacehCONs! In other words,
>> these are not to be missed!
>> 
>> And even if your talk didn't get accepted -- you still
>> get an opportunity to highlight your project to, what's
>> likely going to be the biggest audience attending.
>> 
>> Here's how: if you (or any community member who's
>> passionate about your project) are going to be at either
>> of those ApacheCONs consider signing up for
>>Podling's Shark Tank
>> events:
>>https://www.apachecon.com/acna19/s/#/scheduledEvent/1038
>>https://aceu19.apachecon.com/session/podlings-shark-tank
>> 
>> Each project presenting will get ~10 min for the pitch and ~5 min
>> of panel grilling them on all sorts of things. Kind of like this ;-)
>> https://www.youtube.com/watch?v=wmenN7NEdBc
>> 
>> You've got nothing to lose (in fact, the opposite: you're likely to get
>> a prize!) and you will get a chance to receive feedback that might
>> actually help you grow your community and ultimately graduate to the
>> TLP status. And! Given our awesome panel of judges:
>> * Myrle Krantz
>> * Justin Mclean
>> * Craig Russel
>> * Shane Curcuru
>> We guarantee this to be a fun and useful event for your community!
>> 
>> We will be tracking signups over here:
>> https://wiki.apache.org/apachecon/ACNA19PodlingSharkTank
>> https://wiki.apache.org/apachecon/ACEU19PodlingSharkTank
>> but for now:
>> 
>> SIMPLY REPLY TO THIS EMAIL if you're interested.
>> 
>> It is first come, first serve -- so don't delay -- sign up today!
>> 
>> Thanks,
>> Roman.
>> 
>> -
>> 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: Business decisions and risk (was: [DISCUSS] IPMC votes on releases)

2019-08-15 Thread Jim Jagielski



> On Aug 14, 2019, at 1:24 AM, Dave Fisher  wrote:
> 
>>> 
>>> Q: Does the IPMC want to produce non-ASF releases?
> 
> My answer is yes! I want podlings to be on a path towards graduation! I 
> recognize multiple requirements. The path may differ for each podling. I’m 
> the end there are two outcomes!
> 

What does it mean to be a "non-ASF release"?

To be clear: I want, when podlings do releases, that all podling members enjoy 
the legal protections inherent in doing a s/w release that all other people 
enjoy when *they* do a release. That is only possible if those releases are ASF 
releases. Heck, I would say that having protection at this stage is likely more 
important, and likely more needed, than when subversion, for example, does one.

HOWEVER, those releases are specifically noted as likely being of varying 
quality and compliance as typical ASF releases from TLP/PMCs.

So legally, they should be ASF releases. Culturally, and expectation-wise, they 
are non-typical releases.

Again, the Incubator is, or at least should be, a safe space where communities 
can learn about the Apache Way, and how to build communities and how to develop 
software and how to do releases... All of that stuff is inherently risky. 
That's what the Incubator is also there to do: assume that risk so that 
podlings can learn to the point where they can assume their own risk. This does 
not mean, however, that the Incubator should be constantly getting in the way 
of podlings, using risk-abatement as the reason for gatekeeping.


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



Re: Business decisions and risk (was: [DISCUSS] IPMC votes on releases)

2019-08-12 Thread Jim Jagielski
No, I don't mean to blame the mentors... It is a hard job, mostly uncelebrated 
and thankless and the 1st place people point to when problems arise.

Also, in general, most mentors are those who suffer from volunteeritis and tend 
to bite off more than they can chew. But the reality is that they have signed 
up and that the podling does need them and depend on them. There is no shame in 
saying "I need to resign as mentor... I just don't have the time anymore".

Agreed, BTW, that the Champion role needs to be really emphasized...

> On Aug 12, 2019, at 1:22 PM, Dave Fisher  wrote:
> 
> 
> 
>> On Aug 12, 2019, at 9:24 AM, Jim Jagielski  wrote:
>> 
>> 
>> 
>>> On Aug 12, 2019, at 10:44 AM, Ted Dunning  wrote:
>>> 
>>> On Mon, Aug 12, 2019 at 5:20 AM Jim Jagielski  wrote:
>>> 
>>>> ...
>>>> This does NOT mean that the IPMC should be gatekeepers though... Just as
>>>> PMC chairs are the "eyes and ears of the board", mentors are the "eyes and
>>>> ears of the IPMC". The IPMC "vote" should be little more than a formality.
>>>> IMO, if mentors are IPMC members, and there are at least 3 binding votes on
>>>> the podling list, and the mentors are acting as IPMC members when they
>>>> vote, then any other additional vote in the IPMC is not required... in
>>>> essence, consider it like extending the vote for a lazy consensus, so to
>>>> speak:
>>>> 
>>>> 
>>>> "The Apache Podling Foo has voted on releasing Foo 1.2.2 (url and
>>>> pointers here). We have 3 (or more) binding votes from mentors. We are
>>>> giving the IPMC and additional 72 hours to vote on said release."
>>>> 
>>> 
>>> 
>>> This is good in theory, but as Justin has pointed out, 90% of podling
>>> releases don't have enough mentor votes to follow this path.
>>> 
>>> The 10% that do have enough votes can easily follow this process.
>> 
>> Then the ones that don't have enough mentors still require the 3 +1 binding 
>> votes. The idea is that if the podling already has it, then the IPMC "vote" 
>> is more procedural than anything else. If they don't, then either the 
>> mentors need to step up or the IPMC fills in the gap.
>> 
>> The goal is to avoid having the Incubator be a gate-keeper.
> 
> You state here the paradox if the podling does not have enough engaged 
> mentors then the IPMC is the effective gateway.
> 
> FWIW - there are currently 47 Podlings[1] and 85 Mentors. [2] There are 
> several mentors who mentor 4-6 podlings. I’ve done the analysis before, but 
> it breaks down to about half the mentors having only a single Podling and a 
> quarter with only two.
> 
> Also, let’s not blame the mentors as a lot of times a podling has trouble 
> establishing themselves and the mentors move on for various reasons. 
> Typically mentors are all volunteers. (That some are paid by a third party is 
> perfectly fine.)
> 
> Do we need more mentors? Sure. We do have over 10% of the membership 
> mentoring and up to 30% on the IPMC. I sent a request to members@ some six 
> months ago and I think we got two or three.
> 
> Regards,
> Dave
> 
> [1] http://incubator.apache.org/clutch/#clutch 
> <http://incubator.apache.org/clutch/#clutch>
> [2] http://incubator.apache.org/clutch/#mentors 
> <http://incubator.apache.org/clutch/#mentors>
> 
> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
>> <mailto:general-unsubscr...@incubator.apache.org>
>> For additional commands, e-mail: general-h...@incubator.apache.org 
>> <mailto:general-h...@incubator.apache.org>
>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
> <mailto:general-unsubscr...@incubator.apache.org>
> For additional commands, e-mail: general-h...@incubator.apache.org 
> <mailto:general-h...@incubator.apache.org>


Re: Business decisions and risk (was: [DISCUSS] IPMC votes on releases)

2019-08-12 Thread Jim Jagielski



> On Aug 12, 2019, at 10:44 AM, Ted Dunning  wrote:
> 
> On Mon, Aug 12, 2019 at 5:20 AM Jim Jagielski  wrote:
> 
>> ...
>> This does NOT mean that the IPMC should be gatekeepers though... Just as
>> PMC chairs are the "eyes and ears of the board", mentors are the "eyes and
>> ears of the IPMC". The IPMC "vote" should be little more than a formality.
>> IMO, if mentors are IPMC members, and there are at least 3 binding votes on
>> the podling list, and the mentors are acting as IPMC members when they
>> vote, then any other additional vote in the IPMC is not required... in
>> essence, consider it like extending the vote for a lazy consensus, so to
>> speak:
>> 
>> 
>>   "The Apache Podling Foo has voted on releasing Foo 1.2.2 (url and
>> pointers here). We have 3 (or more) binding votes from mentors. We are
>> giving the IPMC and additional 72 hours to vote on said release."
>> 
> 
> 
> This is good in theory, but as Justin has pointed out, 90% of podling
> releases don't have enough mentor votes to follow this path.
> 
> The 10% that do have enough votes can easily follow this process.

Then the ones that don't have enough mentors still require the 3 +1 binding 
votes. The idea is that if the podling already has it, then the IPMC "vote" is 
more procedural than anything else. If they don't, then either the mentors need 
to step up or the IPMC fills in the gap.

The goal is to avoid having the Incubator be a gate-keeper.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Business decisions and risk (was: [DISCUSS] IPMC votes on releases)

2019-08-12 Thread Jim Jagielski
We have always had a mindset that we (the foundation) want to make it as "brain 
dead easy" for people to download, use, and consume ASF projects. This means 
that they don't need to worry about compliance, IP provenance, etc.

Incubator releases are a special case. The expectation is, and should be, that 
these releases may have issues. In fact, it is quite likely they will. Again, 
as long as those downloading these releases are aware of that, and we've done 
all we could to ensure that they are aware of it, then we have satisfied our 
requirements. IMO, with the naming and the DISCLAIMER and other such touches, 
we are achieving that.

And they are, in fact, *releases*. We need to recall that one function of the 
foundation, and PMCs, is to provide legal protection to those who are creating 
the software artifacts, and when a release is done, as a "formal" act of the 
foundation (via the PMC), it is when they legal coverage is at its most clear 
and explicit. So in order for those within the podling to enjoy the legal 
protection this foundation exists to provide, these do need to be releases. I 
would be opposed to not providing such coverage for those in our podlings, 
since they should be safe spaces to learn about the Apache Way and how to build 
communities and how to release software.

This does NOT mean that the IPMC should be gatekeepers though... Just as PMC 
chairs are the "eyes and ears of the board", mentors are the "eyes and ears of 
the IPMC". The IPMC "vote" should be little more than a formality. IMO, if 
mentors are IPMC members, and there are at least 3 binding votes on the podling 
list, and the mentors are acting as IPMC members when they vote, then any other 
additional vote in the IPMC is not required... in essence, consider it like 
extending the vote for a lazy consensus, so to speak:


   "The Apache Podling Foo has voted on releasing Foo 1.2.2 (url and pointers 
here). We have 3 (or more) binding votes from mentors. We are giving the IPMC 
and additional 72 hours to vote on said release."

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



Re: [VOTE] Apache Tuweni 0.8.1

2019-07-19 Thread Jim Jagielski
+1 (binding)

> On Jul 18, 2019, at 2:28 PM, Antoine Toulme  wrote:
> 
> Hi all,
> The Tuweni community voted on and has approved a proposal to release Tuweni 
> 0.8.1.
> 
> This release includes the following changes:
> * Exclude gradle wrapper jar from source distribution
> * Remove binary jar file from testing resources, recreating on the fly instead
> * Adding a stage task to automate staging releases
> 
> We are now bringing this proposal to the attention of the incubator PMC for a 
> vote.
> We have one +1 IPMC vote.
> 
> This vote will be open for no less than 72 hours.
> 
> Thanks
> Antoine
> 
> Proposal:
> https://lists.apache.org/thread.html/272c4a468f038af7b3f77b298d9f8de5e00a0f45b772c4897fbebc41@%3Cdev.tuweni.apache.org%3E
>  
> 
> 
> Vote result:
> https://lists.apache.org/thread.html/a3a475ce235ab14f53a00d0591b10424d6a96f34780914cfaba8f363@%3Cdev.tuweni.apache.org%3E
>  
> 
> 
> Releases section of the Incubation Policy:
> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases 
> 
> 


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



Re: [VOTE][LAZY] the Incubator as a service provider for podlings (was: overzealous bureaucracy...)

2019-07-18 Thread Jim Jagielski
Agreed. I think some of the conversation on that thread was likely polarizing 
and heated and my hope is that it isn't continued in this thread (whether it 
was self-justified as being "ham-handed" or not).

> On Jul 18, 2019, at 4:12 AM, Bertrand Delacretaz  
> wrote:
> 
> Hi,
> 
> As discussed in the "overzealous bureaucracy" thread, I suggest
> changing the text on the http://incubator.apache.org/ homepage to
> present the Incubator as a service provider for podlings.
> 
> I think the current description can be understood as the Incubator
> being a"stern gatekeeper to the ASF" and that's not good.
> 
> Defining the Incubator a service provider will give us a documented
> basis to adapt our tone and processes if we (or podlings) notice that
> we're being a stern gatekeeper again, as has happened in the past.
> 
> If people agree with the general idea we can discuss the details of
> the new text at https://github.com/apache/incubator/pull/12 if needed.
> 
> I suggest using this thread more to discuss (and hopefully approve ;-)
> the general idea of this change.
> 
> I'm planning to merge #12 in the next few days unless someone from the
> Incubator PMC objects.
> 
> -Bertrand
> 
> -
> 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: New disclaimer text

2019-07-15 Thread Jim Jagielski
Very good point... I'm personally fine w/ anything. Let's avoid bike shedding :)

> On Jul 15, 2019, at 11:07 AM, David Jencks  wrote:
> 
> To me, v2 implies an improvement over its predecessor and an expectation that 
> eventually it will universally replace said predecessor.
> 
> Perhaps 
> DISCLAIMER-b.txt
> DISCLAIMER-x.txt
> might avoid this implication?
> 
> David Jencks 
> 
> Sent from my iPhone
> 
>> On Jul 15, 2019, at 7:40 AM, Jim Jagielski  wrote:
>> 
>> 
>> 
>>> On Jul 13, 2019, at 9:49 PM, Craig Russell  wrote:
>>> 
>>> DISCLAIMER.txt for the current standard disclaimer and some other name for 
>>> the new disclaimer.
>>> 
>> 
>> This seems less confusing, I think. DISCLAIMERv2.txt for the other?
>> 
>> 
>> -
>> 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: New disclaimer text

2019-07-15 Thread Jim Jagielski



> On Jul 13, 2019, at 9:49 PM, Craig Russell  wrote:
> 
> DISCLAIMER.txt for the current standard disclaimer and some other name for 
> the new disclaimer.
> 

This seems less confusing, I think. DISCLAIMERv2.txt for the other?


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



Re: New disclaimer text

2019-07-12 Thread Jim Jagielski
This is a great idea... +1

> On Jul 12, 2019, at 6:31 PM, Craig Russell  wrote:
> 
> Hi,
> 
> I understand I'm a bit late to this particular discussion, but perhaps we can 
> consider two different disclaimers that podlings can choose:
> 
> The standard disclaimer that does not disclaim licensing issues; or,
> 
> The proposed new disclaimer to be used by podlings' first releases until they 
> sort their licensing issues
> 
> This "split roll" allows "mature" podlings the ability to assuage their 
> downstream that they have their licensing issues in hand. 
> 
> Use of the current disclaimer means that any licensing issues found during 
> release voting would cancel the release and require a respin.
> 
> Use of the proposed new disclaimer would allow new-ish podlings to get on 
> with releasing while they sort any licensing issues.
> 
> And we can add to the Maturity Model a section that discusses that the 
> podling has had at least one release with the standard disclaimer.
> 
> Regards,
> 
> Craig
> 
>> On Jul 10, 2019, at 2:44 PM, Justin Mclean  wrote:
>> 
>> Hi,
>> 
>>> Speaking as a member of a currently-incubating project (Apache Druid) where
>>> we have always strived to do releases with no known licensing issues, the
>>> text sounds needlessly scary to downstream consumers.
>> 
>> And that may be the problem with a one solution fits all process. It has 
>> been suggested before we let podlings choose which release process they 
>> want.  However that may get too complex and make voting on releases 
>> inconsistent.
>> 
>>> IMO this disclaims too much, and would chill adoption of incubating
>>> software by people that care about having clean licensing. PPMCs should be
>>> able to say "we believe this release is clean and have vetted it using a
>>> normal Apache vetting process" or maybe even "we have vetted this release
>>> and it is clean other than the following list of known issues". If they
>>> can't say one of those two statements, then maybe it's not time to do their
>>> first release yet.
>> 
>> The idea is to allow podlings to make releases that may not comply with 
>> policy. Have a hard switch from your releases doesn’t comply to everything 
>> must comply is too difficult for some podlings.
>> 
>>> And yeah, as a few others have mentioned, I believe that a more streamlined
>>> voting process
>> 
>> That I think is a different issue, ands may be best to start another thread 
>> on that. The main issue here is that IPMC members votes are binding, and not 
>> all mentors (who are IPMC members) vote on releases, so podlings need votes 
>> from the wider IPMC members to make releases (in about 90%+ of cases). There 
>> been a few ideas on how to improve this, including one approved method (but 
>> no podlings have take that up yet).
>> 
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> Craig L Russell
> c...@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: [ANNOUNCE] Apache Tuweni 0.8.0

2019-07-11 Thread Jim Jagielski
w00t!

> On Jul 9, 2019, at 11:59 PM, Antoine Toulme  wrote:
> 
> The Apache Tuweni team is proud to announce the release of Apache Tuweni
> (incubating) 0.8.0.
> 
> Apache Tuweni is a set of libraries and other tools to aid development of
> blockchain and other decentralized software in Java and other JVM 
> languages. It includes a low-level bytes library, serialization and 
> deserialization codecs (e.g. RLP), various cryptography functions 
> and primatives, and lots of other helpful utilities. Tuweni is 
> developed for JDK 1.8 or higher, and depends on various other FOSS libraries.
> 
> Apache Tuweni 0.8.0-incubating is our first release under the Apache 
> incubator.
> Source and binary distributions can be downloaded from:
> https://tuweni.apache.org/download
> 
> Release notes are at:
> https://github.com/apache/incubator-tuweni/releases/tag/v0.8.0
> 
> A big thank you to all the contributors in this milestone release!
> 
> 
> 
> Disclaimer: Apache Tuweni is an effort undergoing incubation at The Apache
> Software Foundation (ASF), sponsored by the Apache 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.
> 
> Please note the source distribution of Apache Tuweni contains a binary file, 
> the Gradle wrapper jar file. This file will be removed in the next release.
> -
> 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: Podlings, the Incubator, relationships and Apache

2019-07-03 Thread Jim Jagielski


> On Jul 3, 2019, at 5:06 PM, Roman Shaposhnik  wrote:
> 
>> 
>>  1.  Podlings, and PPMC members, to enjoy the legal protection of the 
>> foundation when they do a release
> 
> Let's be pedantic and define those in this particular case, shall we?
> What exactly are the expectations for PPMC members?

Do you mean what does the ASF expect from PPMC members (ie: "What will the PPMC 
members do for the ASF")? Or do you mean what do PPMC members expect by the ASF 
("What will the ASF do for PPMC members")?



Re: Podlings, the Incubator, relationships and Apache

2019-07-03 Thread Jim Jagielski


> On Jul 3, 2019, at 2:37 PM, Roman Shaposhnik  wrote:
> 
> 
> This is correct. Provided we *do* explicitly acknowledge that special
> status of the Incubator.
> 
> This acknowledgement will basically put podling source code releases
> at the same level we have convenience binary releases. Which is: they
> are NOT acts of the foundation.
> 

IMO, we want 2 things:

  1.  Podlings, and PPMC members, to enjoy the legal protection of the 
foundation when they do a release

  2. The outside world, and esp downstream end-users, to know that podling 
releases should be expected to not be fully compliant with the normal 
expectations associated w/ PMC releases.

#1 requires them to be acts of the foundation; #2 requires easily visible and 
discoverable disclaimers.

Anything else just seems excessive and somewhat unwarranted, I think. Let's 
make it as easy as possible, and as painless as possible, for podlings to 
learn; Heck, at the start of The Apache Group and the ASF, we didn't do 
everything right; we tried some things and some failed. It's in the nature of 
education and mentoring. Making mistakes is not a problem; not learning from 
them is.

After we resolve this, I *really* would like to switch the convo around to a 
discussion as deep, and as involved, but related to the other (IMO, more 
important) side of the Incubator coin: education in the Apache Way. So much 
derives from that... even the legal considerations of releases ultimately can 
be found there, IMO. And I still maintain that we do a Not-So-Good job here.

Re: Podlings, the Incubator, relationships and Apache

2019-07-03 Thread Jim Jagielski



> On Jul 3, 2019, at 1:01 AM, Justin Mclean  wrote:
> 
> Hi,
> 
>> Jim said "Let's also recall that the origin genesis of the Incubator was NOT 
>> to provide legal oversight, but rather education and guidance into The 
>> Apache Way”
> 
> If you look at the history threads I posted the other day one was about 
> “legal oversight” way back in 2004.
> 

There is history behind the Incubator from before 2004... Consider that the 
Incubator itself was created in late 2002 with:

"""
 charged with
 accepting new products into the Foundation, providing guidance
 and support to help each new product engender their own
 collaborative community, educating new developers in the
 philosophy and guidelines for collaborative development as
 defined by the members of the Foundation, and proposing to the
 board the promotion of such products to independent PMC
 status once their community has reached maturity.
"""

I am NOT discounting the importance of legal oversight. Far from it. Our legal 
protection is semi-worthless unless we take it seriously and ensure the correct 
checks. My position is rather that, IMO, most of the issues that podlings face, 
and even graduated TLPs, are not issues related to the legal matters but in 
understanding, groking and embracing The Apache Way, which was kind of the 
point at the very beginning.

If you consistently dilute a vaccine, after awhile, it will become useless.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Podlings, the Incubator, relationships and Apache

2019-07-02 Thread Jim Jagielski



> On Jul 1, 2019, at 1:45 AM, Alex Harui  wrote:
> 
> FWIW, I reconcile it as:
> 
> Incubator is a PMC and must record a business decision to call something an 
> ASF release in order to place that release under the legal protection of the 
> ASF.  ASF releases may have policy non-compliance issues.  No TLP can decide 
> on its own to never comply with policy.  But the business decision of the 
> costs of delaying a release to correct non-compliance vs risks of 
> distributing a release with any non-compliance is up to the TLP.  VP Legal 
> will assert a risk profile for any non-compliance and VP Legal or any ASF 
> Member or PMC Member should try to stop a release if a TLP decides to 
> distribute something highly risky.   But it is up to any TLP.  Including the 
> IPMC.  And so the Incubator can do whatever it wants within limits.  Any of 
> us should protest if the IPMC starts allowing releases with high risk.  But 
> with the disclaimer and -incubating suffixes, the risk of many non-compliance 
> issues are low, even CatX and binary inclusions.
> 
> Whether the incubator needs to have a secondary vote is not required by the 
> above.  IPMC members could drop in on the podling vote thread.  Podlings with 
> 3 active mentors that vote on the podling's vote thread could be deemed 
> sufficient.
> 

Although not a "real" PMC, we do need to provide legal protection for each PPMC 
and distributing releases is the time that most legal considerations "kick in" 
as it were. So we need a clear "paper trail" of approvals for that PPMC to 
enjoy the legal protection the foundation exists to provide. The IPMC vote, 
since the IPMC is, in fact, a true PMC, provides that legal provenance such 
that, should anything untoward happen, we can clearly show to outside legal 
entities corporate provenance without having to try to explain the intricacies 
of podlings, and PPMCs and PMC and et.al. :-)

Let's also recall that the origin genesis of the Incubator was NOT to provide 
legal oversight, but rather education and guidance into The Apache Way (TAW). 
Back then we had way too many projects that were TLP status that lacked even a 
basic awareness of TAW, and the board, rightfully, considered that a huge 
problem (this started with the mismanagement of the Jakarta project, which 
tried to create a sub-foundation within the ASF such that the Jakarta PMC was 
basically the "board" of that "foundation"... as these projects spun out, 
problems aplenty ensued). And so the Incubator was created to handle that 
problem.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: LGPL dependency

2019-07-01 Thread Jim Jagielski
Myrle, did you get all you needed? Enough votes and all to get the release 
unblocked?

> On Jun 28, 2019, at 11:24 AM, Myrle Krantz  wrote:
> 
> I've said it on dev@weex, and on private@incubator, but I wanted to make
> sure and say it here too.  Weex should cut the release.  We'll figure out
> the rest later.  The straw poll on private@incubator also confirms: you
> have my support and the support of many of the mentors in the incubator.  I
> apologize for us blocking you for so long.
> 
> Best Regards,
> Myrle Krantz
> PMC Member, Apache Incubator
> 
> On Thu, Jun 27, 2019 at 6:06 AM 申远  wrote:
> 
>> It looks like we have got result[1] from Legal VP, I will bring it here now
>> 
>>   1. It's fine if Weex only could include header files under 2-clause BSD
>>   license from Webkit at compiling time and has a dynamic link to
>> Webkit.so
>>   at runtime.
>>   2. It's recommended that excluding Webkit.so from Weex convenience
>>   library. Users would include the code snippet below to include both weex
>>   and webkit.
>> 
>> 
>> 
>>weex_sdk
>> 
>> 
>> 
>> 
>> 
>>webkit
>> 
>> 
>> 
>> 
>> The following is what I need to consult from Incubator:
>> 
>> Google will ban all apps without 64 bit published in Google Play from 1st,
>> August, 2019 [1]. Though it's a good idea of excluding Webkit.so from
>> convenience library of Weex, Weex community needs to publish next release
>> with 64-bit support ASAP to give users enough time to upgrade Weex. I'd
>> like to remain webkit.so in convenience library of Weex only for next
>> release.
>> 
>> [1] https://issues.apache.org/jira/browse/LEGAL-464
>> [2] https://developer.android.com/distribute/best-practices/develop/64-bit
>> 
>> Best Regards,
>> YorkShen
>> 
>> 申远
>> 
>> 
>> Roman Shaposhnik  于2019年6月24日周一 上午7:32写道:
>> 
>>> Lets continue this discussion on
>>> https://issues.apache.org/jira/browse/LEGAL-464 please
>>> 
>>> On Sat, Jun 22, 2019 at 2:18 PM Matt Sicker  wrote:
 
 WebKit dates back to KHTML, an LGPL web engine from KDE. It sounds like
 it’s some WebKit specific files that are BSD licensed. I haven’t
>>> inspected
 the individual files, but I suspect that the header files are BSD
>>> licensed
 to make linking less of a legal headache.
 
 On Sat, Jun 22, 2019 at 07:11, Craig Russell 
>>> wrote:
 
> The Webkit license page https://webkit.org/licensing-webkit/ says
> portions licensed under LGPL and BSD licenses.
> 
> Usually this means it's the user's choice which license to use.
> 
> We would choose the BSD License for the components that we use.
> 
> Can you find anywhere a statement that the Webkit.so is licensed only
> under LGPL?
> 
> Craig
> 
>> On Jun 14, 2019, at 1:40 AM, 申远  wrote:
>> 
>> As mentioned above, Webkit is under dual License(BSD and LPGL) and
>>> it's
>> almost impossible for us to figure out which function is a pure BSD
>> function. I don't know
>> Weex.apiA->Webkit.BSD.apiB->Webkit.BSD.apiC->Webkit.LGPL will
>> happen
>>> or
>> not. Perhaps pure BSD header file will lead to pure BSD
>>> implementation.
>> Perhaps?
>> 
>> As for alternative dependency, it's possible if we make some major
> changes
>> to Weex. But convenience binary of each Weex release includes
>>> Webkit.so,
>> how to solve that problem? Maybe publish two convenience binary,
>> one
> named
>> Weex_WebKit.aar and the other named Weex_BSDKit.aar ? Not sounds
>>> like a
>> good idea to me.
>> 
>> Best Regards,
>> YorkShen
>> 
>> 申远
>> 
>> 
>> Sheng Wu  于2019年6月14日周五 下午4:23写道:
>> 
>>> Hi York
>>> 
>>> I am not a C/C++ coder, so I could be wrong.
>>> 
>>> But from I saw, Catalog X dependency required is not right. Like
>> Hen
> said,
>>> alternative is an option.
>>> 
>>> Such as
>>> Today’s another incubating project, ShardingSphere.
>>> When user wants to MySQL sharing, then they needs to accept MySQL
>>> Driver
>>> license first(or already accepted).
>>> But user could use ShardingSphere with PostgreSQL JDBC Driver.
>>> 
>>> 
>>> Sheng Wu
>>> Apache Skywalking, ShardingSphere, Zipkin
>>> 
>>> 
>>> 
 在 2019年6月14日,下午4:15,Hen  写道:
 
 Assuming Weex requires Webkit and is unable to work with an
> alternative,
 the issue here is that users of Weex would seem to have to permit
> reverse
 engineering in their legal terms. Our position has been that that
>>> goes
 beyond the scope of the Apache 2.0 license and would be an
>>> unpleasant
 surprise for users.
 
 (seem to have to  =>  this is how we've discussed the license; an
> actual
 court may decide something completely different)
 
 Looking at Weex's website's description, it does not seem to be
>>> that a
>>> user
 of Weex will already have 

Re: Podlings, the Incubator, relationships and Apache

2019-06-28 Thread Jim Jagielski



> On Jun 27, 2019, at 7:57 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> The Incubator itself is a PMC.
> 
> OK that's sorted.
> 
>> Now let's talk about podling releases... When the IPMC votes on accepting a 
>> podling release, and it passes, my opinion is that the Incubator takes on 
>> the resultant legal obligations associated w/ any PMC doing a release. Now 
>> the podling releases themselves are noted and described as "not GA" and "not 
>> official", et.al. but this is, again IMO, simply to make it clear to anyone 
>> who is downloading and using the software that the expectations normally 
>> associated with "regular" Apache releases do not apply, such that there 
>> could be some licensing issues, etc, that would be verboten in "official" 
>> releases, but may exist here. In other words: this is a podling release; 
>> expect issues and mistakes and churn.
> 
> Except it's not, as it seems the IPMC doesn’t need to abide by what other 
> PMCs need to abide by when making releases :-) (Which is ironic given the 
> IPMC is tasked with teaching and passing that knowledge on.) And that policy 
> exception is not documented anywhere. :-) Nor has the board, to my knowledge, 
> approved such an exception. Yay! So how is a voted on PMC release, an act 
> which make it official, is not an official release? Do you see how this might 
> be confusing or open to a board range of interpretations?
> 

Yes, I see how it can be confusing and open to a range of opinions.

Recall that with other PMCs, the PMCs themselves are directly responsible for 
the development of the code. Not so with the IPMC. The expectation w/ other 
PMCs is that they know how to do releases, and that their releases will be 
correct and valid. With podlings, the expectation is the reverse. It is 
expected that podling releases will have issues... in fact, iirc, somewhere 
along the line *making* a podling do a release was added as a required step to 
graduation, to make sure that upon graduation, they knew how to do it.

Incubation should be a... wait for it... 'safe space' (/me ducks) for podlings 
to learn the ropes, to fail doing the "normal" things that a PMC must do 
(including releases), because that is how people learn best. As long as the 
outworld world is aware that podlings can not, and should not, be expected to 
be "the same" as other PMCs, we are OK.

Maybe we should think of the podlings more as "Apprenticeship PMCs" ;)


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



Re: [VOTE] Apache Tuweni 0.8.0

2019-06-28 Thread Jim Jagielski
+1

> On Jun 27, 2019, at 5:04 PM, Antoine Toulme  wrote:
> 
> I’m not quite sure what to do. If I don’t hear by tomorrow I’ll close this 
> vote as passing.
> 
>> On Jun 27, 2019, at 10:42 AM, Greg Stein  wrote:
>> 
>> On Thu, Jun 27, 2019 at 12:34 AM Justin Mclean 
>> wrote:
>> 
>>> Hi,
>>> 
 I see a lot of "oh no. a bad file". What is the takeaway from that? "The
 IPMC thinks we should not release.”
>>> 
>>> Has anyone voted -1? Nope. And even if they did a -1 vote is not a veto.
>>> 
>> 
>> Great. Semantics. "But I didn't really say veto."
>> 
>> Your "not allowed" is read as a veto by any reasonably-minded person. If
>> you think it should NOT be read as -1, then put a +1 into your message.
>> That did not happen. So it is NOT read as +1 for the podling. I added my +1
>> as the third. Mostly to get it over with, and (honestly:) for some spite
>> about the whole process.
>> 
>> Look. Clearly this discussion is about rulesmithing to keep the status quo.
>> Carry on.
>> 
>> Maybe I should say you're being an ass about the whole process. :-)
>> 
>> -g
>> 
>> ps. per your rules [1], I put a smiley on that sentence, so it doesn't mean
>> anything.
>> [1]
>> http://mail-archives.apache.org/mod_mbox/incubator-general/201906.mbox/%3CA2A7580A-20DA-4894-9590-14D563C3D0E0%40me.com%3E
> 
> 
> -
> 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] Apache Tuweni 0.8.0

2019-06-28 Thread Jim Jagielski


This speech policing is starting to get quite on my nerves. Especially when it 
ignores the intent behind such things... 99% of the time the smiley is there to 
say "Yeah, I know that sounds harsh, but it's a little joke". It is an attempt 
to replicate in text what is natural in "real life"... when someone says 
something and then, to defuse the situation a little, smiles.

This is how people talk. This is how people communicate.

Let's all recall that one of the big tenets in 1984 is that if you can control 
how people talk, you can control how they think. Can we PLEASE not go there.

> On Jun 27, 2019, at 6:15 PM, Greg Stein  wrote:
> 
> On Thu, Jun 27, 2019 at 4:29 PM Craig Russell  wrote:
>> ...
> 
>> No. Smiley face doesn't count.
>> 
> 
> Apparently you missed the point when Justin did that to me. Hmm?
> 
> Of course it doesn't count. Why don't you go police th VP Incubator, okay?
> 
> -g


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



Re: Podlings, the Incubator, relationships and Apache

2019-06-27 Thread Jim Jagielski



> On Jun 25, 2019, at 9:49 PM, Alex Harui  wrote:
> 
> 
> 
> On 6/24/19, 9:12 AM, "Roman Shaposhnik"  wrote:
> 
>> What kinds of policy violations truly affect the legal shield if the 
>> non-compliance:
> 
>You're asking the wrong question. You're still asking the TLP question.
> 
> I'm asking the TLP question to understand how big the difference is between 
> TLP and Podlings.

Please note that the only legal structure in this discussion is a PMC. The 
Bylaws have no concept of a podling nor a "top level project", although we tend 
to use the terms TLP and PMC interchangeably.

Now a podling is NOT a PMC because, again, the bylaws are clear on what 
constitutes a PMC and how one is created.

The Incubator itself is a PMC.

Now let's talk about podling releases... When the IPMC votes on accepting a 
podling release, and it passes, my opinion is that the Incubator takes on the 
resultant legal obligations associated w/ any PMC doing a release. Now the 
podling releases themselves are noted and described as "not GA" and "not 
official", et.al. but this is, again IMO, simply to make it clear to anyone who 
is downloading and using the software that the expectations normally associated 
with "regular" Apache releases do not apply, such that there could be some 
licensing issues, etc, that would be verboten in "official" releases, but may 
exist here. In other words: this is a podling release; expect issues and 
mistakes and churn.

The IPMC vote is not, and should not be, some sort of secondary QA test, some 
sort of verification of validity: it exists, IMO, simply so that the podling 
(and its contributors) can enjoy the legal protection under the Incubator 
"umbrella" when they do a release.

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



Re: [VOTE] Apache Tuweni 0.8.0

2019-06-24 Thread Jim Jagielski
+1 (binding) - carried over from PPMC vote

> On Jun 24, 2019, at 6:03 AM, Antoine Toulme  wrote:
> 
> Hi all,
> The Tuweni community voted on and has approved a proposal to release
> Tuweni 0.8.0. Pursuant to the Releases section of the Incubation
> Policy and we would now like to request the permission of the Incubator PMC 
> to publish the
> tarball on the Tuweni Download page.
> Note we have collected 4 +1 votes from IPMC members and have therefore the 
> necessary minimum votes.
> 
> Please vote by 12 PM Paris time Thursday, 6/27.
> 
> Thanks
> Antoine
> 
> Proposal:
> https://lists.apache.org/thread.html/7ad88c9725d954f0c58968b3ba53da007b8b48079fe24ee908e03a04@%3Cdev.tuweni.apache.org%3E
>  
> 
> 
> Vote result:
> https://lists.apache.org/thread.html/2d4ac9cc208218e87d916a9bfc01faec53b30a5e714fe1d632f5fe8c@%3Cdev.tuweni.apache.org%3E
>  
> 
> 
> Releases section of the Incubation Policy:
> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> 


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



Re: Podlings, the Incubator, relationships and Apache

2019-06-24 Thread Jim Jagielski
++1. I agree w/ Rich and Roman

> On Jun 23, 2019, at 11:25 PM, Roman Shaposhnik  wrote:
> 
> On Sat, Jun 22, 2019 at 3:31 PM Rich Bowen  > wrote:
>> 
>> A couple of thoughts:
> 
> And a couple of thoughts on top of that.
> 
>> Podlings are not permitted to call themselves "Apache Foo" because they are
>> not yet full Apache projects.
> 
> Correct. The I way I see this thread is this: *when it comes to
> releases*, there's
> always been two camps in Incubator. One thinks that Incubator is a TLP just
> like Apache Commons that happens to produce release artifacts that have
> nothing in common (just like Apache Commons'  JXPath has very little to do
> with Compress and). A second camp thinks that Incubator is actually a special
> construct within a foundation (after all, if it was just like Apache Commons 
> why
> would we make them put DISCLAIMER into release tarballs?).
> 
> It seems that David is closer to the 1st camp, and Rich and I are
> closer to the 2nd.
> 
> Looking at the community benefits, I really think we should acknowledge that
> Incubator is a special construct and optimize that special construct
> for a particular
> outcome: which is effectiveness of the graduation process.
> 
>> While in the incubator we should expect podlibgs to fail at the rules.
>> They're new to them and many of them feel arbitrary, even capricious, to
>> those coming in from outside. We should make it safe to fail until they are
>> ready to graduate. We should nurture them as long as they are moving
>> towards that goal.
> 
> Yup.
> 
>> I cannot disagree with your reading of our resolutions. But I wonder if
>> that reality is producing good citizen projects or a bunch of resentful
>> people following rules they don't understand or embrace because they know
>> they have to.
>> 
>> Zipkin is only the latest project which clearly didn't get it and has left
>> angry. I would rather a project realize that they don't fit and be able to
>> leave with their dignity without having also to leave hating what we stand
>> for.
>> 
>> I want our new graduates to love and understand the ASF not merely tolerate
>> it.
>> 
>> I want the incubator to respond to failure with gentle correction rather
>> than scoldings.
>> 
>> Specifically I think podlings should be able to produce releases that are
>> not asf complient and have them clearly labeled as such. Because they are
>> not TLPs yet and so cannot be held to the same standard. This must be
>> accompanied by a movement towards being a TLP, not some eternal incubation.
> 
> With my IPMC member hat on -- huge +1 to the above.
> 
> With my VP Legal hat on: I have no dog in this race. The IPMC needs to make
> a *business* (well, community in this case) decision and then we can work
> with a risk profile of that decision.
> 
> Like I said -- the decision to make is: 1st vs. 2nd camp.
> 
> Thanks,
> Roman.
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
> 
> For additional commands, e-mail: general-h...@incubator.apache.org 
> 


Re: [VOTE] Zipkin leave incubator, return back to OpenZipkin

2019-06-19 Thread Jim Jagielski
+1 (binding)

> On Jun 17, 2019, at 9:21 PM, Sheng Wu  wrote:
> 
> Hi
> 
> This is a call for official vote of Zipkin leave from incubator, and return 
> back to OpenZipkin.
> 
> PPMC have voted.[1], carried two IPMC +1 vote from Sheng Wu and Willem Jiang
> 
> There is no trademark, logo transfer, so, Zipkin community is OK to still use 
> the name(io.zipkin or zipkin + xxx) and logo. 
> `org.apache.zipkin` is not allowed or going to be used.
> All 9 repositories(GitHub repo) will be transferred back to OpenZipkin 
> org(GitHub).
> incubator-zipkin --> https://github.com/openzipkin/zipkin 
> ncubator-zipkin-dependencies --> 
> https://github.com/openzipkin/zipkin-dependencies 
> incubator-zipkin-api --> https://github.com/openzipkin/zipkin-api 
> incubator-zipkin-b3-propagation --> 
> https://github.com/openzipkin/b3-propagation 
> incubator-zipkin-reporter-java --> 
> https://github.com/openzipkin/zipkin-reporter-java 
> incubator-zipkin-brave --> https://github.com/openzipkin/brave 
> incubator-zipkin-brave-cassandra --> 
> https://github.com/openzipkin/brave-cassandra 
> incubator-zipkin-brave-karaf --> https://github.com/openzipkin/brave-karaf 
> incubator-zipkin-layout-factory --> 
> https://github.com/openzipkin/zipkin-layout-factory 
> 
> Voting will start now (2019-6-18 9:20 UTC+8) and will remain open 72 hours 
> only for consensus, Request all IPMC members to give their vote.
> [ ] +1 Agree
> [ ] +0 No opinion.
> [ ] -1 Do not agree because
> 
> [1] 
> https://lists.apache.org/thread.html/fbeb254f569d9852e9740d55532ee338580287ec384e26c7d9107964@%3Cdev.zipkin.apache.org%3E
>  
> 
> 
> 
> 
> Sheng Wu
> Apache Skywalking, ShardingSphere, Zipkin
> 
> 
> 


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



Re: overzealous bureaucracy (was: [VOTE] Zipkin leave incubator, return back to OpenZipkin)

2019-06-19 Thread Jim Jagielski
My only comment here is that the Incubator performed a legal action in 
accepting Zipkin; in doing so, Zipkin enjoyed some level of ASF services as 
well as legal protection.

To dissolve that 'relationship', there should be a clear trail of intent and 
action in doing so, not only by Zipkin but also by the Incubator itself.

What constitutes a "clear trail of intent and action" is another question. :)

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



Re: Incubation Pain Points

2019-06-18 Thread Jim Jagielski



> On Jun 18, 2019, at 7:42 AM, Bertrand Delacretaz  
> wrote:
> 
> On Tue, Jun 18, 2019 at 1:18 PM Jim Jagielski  wrote:
>> ...prepping the existing community regarding what "moving to the ASF means" 
>> is the job of the Champion, no?...
> 
> I agree but it has to be based on written docs, not oral tradition as
> that does not scale.
> 

Of course... but lack of it being on written docs does not make it invalid nor 
not policy.


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



Re: Incubation Pain Points

2019-06-18 Thread Jim Jagielski



> On Jun 17, 2019, at 1:25 PM, Dave Fisher  wrote:
> 
> Hi Roman,
> 
> All very true. What the Incubator could do better is to let people know the 
> key values of The Apache Way that will impact any existing community if they 
> come to the ASF through the Incubator. While it will be a community that 
> comes (or doesn’t), it will more likely be a vendor than a community that 
> decides to come to Apache. That will more likely be for the permissive 
> licensing than for community over code.

Certainly prepping the existing community regarding what "moving to the ASF 
means" is the job of the Champion, no?
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [IMPORTANT] Board proposal on podling releases

2019-06-10 Thread Jim Jagielski
Agreed... isn't the whole point of the Incubator is to provide not only 
training and guidance but also a "safe place" where these codlings can learn 
the ropes, including How To Do A Release? And don't we stress that such 
podlings are under incubation is to ensure (as much as we can) that those who 
download and/or use the project are aware that there might be 'issues' with 
that codebase and that they may not 100% comply with the standards associated 
w/ 'real' ASF projects?

Unless there is an actual *LEGAL* issue w/ assets within the released codebase, 
such that we do not have the rights to release said assets, I'm not sure what 
the hub-bub is. These are podling releases.

PS: and '*LEGAL*' is not GPL code or whatever

> On Jun 7, 2019, at 2:47 PM, Greg Stein  wrote:
> 
> blah blah "legal risk" blah blah.
> 
> Really. Let's step back and consider what we're talking about. A podling
> making a release as they learn the ropes of Apache-style governance. With a
> disclaimer.
> 
> "OMG! There is GPL code in there!" ... no legal risk. We only care about
> GPL from a policy standpoint. Let it through.
> 
> "OMG! No NOTICE file!" ... well, easy to fix, unlike a GPL dependency.
> Maybe stop the release, but there isn't any "legal risk" so maybe just
> write a Jira ticket and move on. Copyrights, IP, and licensing are not
> magically thrown out the window if a file is not present. All of that is
> inherent, and a NOTICE file merely helps to surface IP issues, rather than
> specify.
> 
> And just what is this "legal risk" term that people are throwing about?
> Please define, before use.
> 
> -g
> 
> 
> On Fri, Jun 7, 2019 at 1:00 PM Craig Russell  wrote:
> 
>> Hi Justin,
>> 
>> As a board member, I'm not comfortable with granting a blanket exception
>> to policy that might put us at legal risk.
>> 
>> As an IPMC member, I think that we do not want to allow podlings to
>> release material that might put us at legal risk. I do think that the IPMC
>> under today's policy has the ability to decide whether a podling release
>> puts us at risk and therefore should be blocked. So I am not convinced that
>> the IPMC needs to ask for this waiver from the board.
>> 
>> My understanding as an IPMC member is that there are some items in a
>> release that can be  allowed where they would not be in a TLP release.
>> These things have historically drawn -1 votes from IPMC members.
>> 
>> I think there is consensus that a podling release does not have to conform
>> in every respect to what we expect from a TLP release.
>> 
>> I think that the incubator IPMC should first flesh out (on the general@
>> list) which materials in a podling release are
>> a) fine;
>> b) minor issue (file a JIRA and fix before graduation); or
>> c) blocker (puts the foundation at risk).
>> 
>> The detail of what is minor versus what it a blocker is the most important
>> thing that needs clarity. As of now, I don't see consensus although I see
>> movement.
>> 
>> Craig
>> 
>> 
>>> On Jun 6, 2019, at 11:45 PM, Justin Mclean 
>> wrote:
>>> 
>>> Hi,
>>> 
>>> As suggested I’ve collated information from several threads and turned
>> it into a proposal for the board. Any edits, feedback, agreement,
>> disagreement etc etc is welcome. In particular it would be nice  to hear
>> some feedback from people who are in favour of this.
>>> 
>>> Note that this is important as it probably changes the advice mentors
>> will give their podlings on releases and change in a positive way how we
>> vote on releases with serious issues in them. If you are a mentor or vote
>> on releases please read it. Again feedback welcome.
>>> 
>>> If the board agrees with the proposal I think we'll need to update the
>> incubator DISCLAIMER. I’ve suggested what we might add in the proposal but
>> the exact changes can to be discussed here. If the board disagrees with the
>> proposal I suggest we discuss and come up with a list of serious issues
>> that the IPMC recommends voting -1 vote on a release. This is just
>> guidance, not rules, and there may of course be exceptions. (For instance
>> you could ask VP legal for an exception as has been done in the past.)
>> That way mentors and podlings have clear expectations on releases must
>> contain.
>>> 
>>> The proposal can be found in the draft board report. [1]
>>> 
>>> Thanks,
>>> Justin
>>> 
>>> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/June2019
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>> 
>> Craig L Russell
>> c...@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: 

Re: [Cava] Suitable name search - choosing a name

2019-03-21 Thread Jim Jagielski
How about Apache Bistro:

  o sounds like crypto
  o Blockchain dISTRO
  o distributed kinda means decentralized as well.



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



Re: [Cava] Suitable name search - choosing a name

2019-03-20 Thread Jim Jagielski
Personally, I'm fine w/ anything... 

> On Mar 19, 2019, at 6:53 PM, Antoine Toulme  wrote:
> 
> I think we will need a made up name, and we likely need a name that is rather 
> unambiguous across languages.
> 
> Based on our previous proposals, would you be ok with “RainBlock”?
> 
> 
>> On Mar 19, 2019, at 11:40 AM, Jim Jagielski  wrote:
>> 
>> Apache PawPaw
>> 
>>> On Mar 19, 2019, at 9:58 AM, Michael Wall  wrote:
>>> 
>>> Since Cava is the Guava for blockchains, what about sticking with the
>>> fruit/veggie theme?
>>> 
>>> Jackfruit
>>> Jambolan
>>> Jocote
>>> Kumquat
>>> KangKong
>>> Kabosu
>>> 
>>> I also saw the word postcava which is the "the inferior vena cava of
>>> vertebrates higher than fishes" according to
>>> https://www.merriam-webster.com/dictionary/postcava.  But is seemed like a
>>> name you could use after Cava.
>>> 
>>> Just brainstorming.
>>> 
>>> Mike
>>> 
>>> 
>>> 
>>> On Tue, Mar 19, 2019 at 8:19 AM Jim Jagielski  wrote:
>>> 
>>>> What is somewhat funny is that the "SkyWalking" podling is on the cusp of
>>>> graduation. :)
>>>> 
>>>>> On Mar 19, 2019, at 1:42 AM, Antoine Toulme  wrote:
>>>>> 
>>>>> All, the results are in, from VP Legal:
>>>>>> I am happy to approve the name in isolation. Specifically, the
>>>> community must refrain from linking the project to any Star Wars
>>>> references. The view of the community is that the community is likely to
>>>> find that difficult. It was therefore agreed to look for a different name.
>>>>> 
>>>>> We need to pick another name.
>>>>> 
>>>>>> On Mar 4, 2019, at 2:32 PM, Dave Fisher  wrote:
>>>>>> 
>>>>>> Hi -
>>>>>> 
>>>>>>> On Mar 4, 2019, at 2:10 PM, Antoine Toulme 
>>>> wrote:
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> On Mar 4, 2019, at 2:00 PM, Dave Fisher 
>>>> wrote:
>>>>>>>> 
>>>>>>>> Hi -
>>>>>>>> 
>>>>>>>> I went to look at the Trademark name search and something is either
>>>> messed up or autocorrected.
>>>>>>>> 
>>>>>>>> PODLINGNAMESEARCH-165 <
>>>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-165>Establish
>>>> whether "Apache Obiwarn" is a Suitable Name
>>>>>>>> 
>>>>>>>> Isn’t the name supposed to be Obiwan and not Obiwarn?
>>>>>>> No, the name is Obiwarn. With a r.
>>>>>> 
>>>>>> Well, my bad eye sight had my brain auto-correcting to what I expected
>>>> to see. Then Daniel wrote what he did.
>>>>>> 
>>>>>> OK. Let’s look into Obiwarn and deal with Apple autocorrecting it to
>>>> Obiwan … more Jedi mind tricks.
>>>>>> 
>>>>>> Regards,
>>>>>> Dave
>>>>>> 
>>>>>>>> 
>>>>>>>> Please look into it. Sorry, color me confused.
>>>>>>>> 
>>>>>>>> Regards,
>>>>>>>> Dave
>>>>>>>> 
>>>>>>>>> On Mar 4, 2019, at 12:20 PM, Jim Jagielski  wrote:
>>>>>>>>> 
>>>>>>>>> Thx. We'll wait for the decision.
>>>>>>>>> 
>>>>>>>>>> On Mar 4, 2019, at 2:05 AM, Antoine Toulme 
>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>> The ticket is now open:
>>>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-165
>>>>>>>>>> 
>>>>>>>>>> Cheers,
>>>>>>>>>> 
>>>>>>>>>> Antoine
>>>>>>>>>> 
>>>>>>>>>>> On Mar 1, 2019, at 3:24 PM, Antoine Toulme 
>>>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> Perfect, thank you.
>>>>>>>>>>> 
>>>>>>>>>>>> On Mar 1, 2019, at 3:17 PM, Daniel Shahaf 
>>>>

Re: [Cava] Suitable name search - choosing a name

2019-03-19 Thread Jim Jagielski
Apache PawPaw

> On Mar 19, 2019, at 9:58 AM, Michael Wall  wrote:
> 
> Since Cava is the Guava for blockchains, what about sticking with the
> fruit/veggie theme?
> 
> Jackfruit
> Jambolan
> Jocote
> Kumquat
> KangKong
> Kabosu
> 
> I also saw the word postcava which is the "the inferior vena cava of
> vertebrates higher than fishes" according to
> https://www.merriam-webster.com/dictionary/postcava.  But is seemed like a
> name you could use after Cava.
> 
> Just brainstorming.
> 
> Mike
> 
> 
> 
> On Tue, Mar 19, 2019 at 8:19 AM Jim Jagielski  wrote:
> 
>> What is somewhat funny is that the "SkyWalking" podling is on the cusp of
>> graduation. :)
>> 
>>> On Mar 19, 2019, at 1:42 AM, Antoine Toulme  wrote:
>>> 
>>> All, the results are in, from VP Legal:
>>>> I am happy to approve the name in isolation. Specifically, the
>> community must refrain from linking the project to any Star Wars
>> references. The view of the community is that the community is likely to
>> find that difficult. It was therefore agreed to look for a different name.
>>> 
>>> We need to pick another name.
>>> 
>>>> On Mar 4, 2019, at 2:32 PM, Dave Fisher  wrote:
>>>> 
>>>> Hi -
>>>> 
>>>>> On Mar 4, 2019, at 2:10 PM, Antoine Toulme 
>> wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Mar 4, 2019, at 2:00 PM, Dave Fisher 
>> wrote:
>>>>>> 
>>>>>> Hi -
>>>>>> 
>>>>>> I went to look at the Trademark name search and something is either
>> messed up or autocorrected.
>>>>>> 
>>>>>> PODLINGNAMESEARCH-165 <
>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-165>Establish
>> whether "Apache Obiwarn" is a Suitable Name
>>>>>> 
>>>>>> Isn’t the name supposed to be Obiwan and not Obiwarn?
>>>>> No, the name is Obiwarn. With a r.
>>>> 
>>>> Well, my bad eye sight had my brain auto-correcting to what I expected
>> to see. Then Daniel wrote what he did.
>>>> 
>>>> OK. Let’s look into Obiwarn and deal with Apple autocorrecting it to
>> Obiwan … more Jedi mind tricks.
>>>> 
>>>> Regards,
>>>> Dave
>>>> 
>>>>>> 
>>>>>> Please look into it. Sorry, color me confused.
>>>>>> 
>>>>>> Regards,
>>>>>> Dave
>>>>>> 
>>>>>>> On Mar 4, 2019, at 12:20 PM, Jim Jagielski  wrote:
>>>>>>> 
>>>>>>> Thx. We'll wait for the decision.
>>>>>>> 
>>>>>>>> On Mar 4, 2019, at 2:05 AM, Antoine Toulme 
>> wrote:
>>>>>>>> 
>>>>>>>> The ticket is now open:
>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-165
>>>>>>>> 
>>>>>>>> Cheers,
>>>>>>>> 
>>>>>>>> Antoine
>>>>>>>> 
>>>>>>>>> On Mar 1, 2019, at 3:24 PM, Antoine Toulme 
>> wrote:
>>>>>>>>> 
>>>>>>>>> Perfect, thank you.
>>>>>>>>> 
>>>>>>>>>> On Mar 1, 2019, at 3:17 PM, Daniel Shahaf 
>> wrote:
>>>>>>>>>> 
>>>>>>>>>> Antoine Toulme wrote on Fri, Mar 01, 2019 at 15:09:39 -0800:
>>>>>>>>>>> I am happy to mention that you mentioned this term on list.
>>>>>>>>>> 
>>>>>>>>>> Thanks.
>>>>>>>>>> 
>>>>>>>>>>> What language should I use?
>>>>>>>>>> 
>>>>>>>>>> The public part of PNS tickets should be factual, so I'd say:
>>>>>>>>>> .
>>>>>>>>>> "In the _Star Wars_ universe there exists a character named
>> Obi-Wan Kenobi"
>>>>>>>>>> .
>>>>>>>>>> with a link to Wikipedia for good measure.
>>>>>>>>>> 
>>>>>>>>>> Cheers,
>>>>>>>>>> 
>>>>>>>>>> Daniel
>>>>>>>

Re: [Cava] Suitable name search - choosing a name

2019-03-19 Thread Jim Jagielski



> On Mar 19, 2019, at 11:36 AM, Kevin A. McGrail  wrote:
> 
> On 3/19/2019 8:19 AM, Jim Jagielski wrote:
>> What is somewhat funny is that the "SkyWalking" podling is on the cusp of 
>> graduation. :)
> 
> I would say that's irrelevant.

Yeah, I simply said it was funny :)
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [Cava] Suitable name search - choosing a name

2019-03-19 Thread Jim Jagielski
What is somewhat funny is that the "SkyWalking" podling is on the cusp of 
graduation. :)

> On Mar 19, 2019, at 1:42 AM, Antoine Toulme  wrote:
> 
> All, the results are in, from VP Legal:
>> I am happy to approve the name in isolation. Specifically, the community 
>> must refrain from linking the project to any Star Wars references. The view 
>> of the community is that the community is likely to find that difficult. It 
>> was therefore agreed to look for a different name.
> 
> We need to pick another name.
> 
>> On Mar 4, 2019, at 2:32 PM, Dave Fisher  wrote:
>> 
>> Hi -
>> 
>>> On Mar 4, 2019, at 2:10 PM, Antoine Toulme  wrote:
>>> 
>>> 
>>> 
>>>> On Mar 4, 2019, at 2:00 PM, Dave Fisher  wrote:
>>>> 
>>>> Hi -
>>>> 
>>>> I went to look at the Trademark name search and something is either messed 
>>>> up or autocorrected.
>>>> 
>>>> PODLINGNAMESEARCH-165 
>>>> <https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-165>Establish 
>>>> whether "Apache Obiwarn" is a Suitable Name
>>>> 
>>>> Isn’t the name supposed to be Obiwan and not Obiwarn?
>>> No, the name is Obiwarn. With a r.
>> 
>> Well, my bad eye sight had my brain auto-correcting to what I expected to 
>> see. Then Daniel wrote what he did.
>> 
>> OK. Let’s look into Obiwarn and deal with Apple autocorrecting it to Obiwan 
>> … more Jedi mind tricks.
>> 
>> Regards,
>> Dave
>> 
>>>> 
>>>> Please look into it. Sorry, color me confused.
>>>> 
>>>> Regards,
>>>> Dave
>>>> 
>>>>> On Mar 4, 2019, at 12:20 PM, Jim Jagielski  wrote:
>>>>> 
>>>>> Thx. We'll wait for the decision.
>>>>> 
>>>>>> On Mar 4, 2019, at 2:05 AM, Antoine Toulme  wrote:
>>>>>> 
>>>>>> The ticket is now open: 
>>>>>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-165
>>>>>> 
>>>>>> Cheers,
>>>>>> 
>>>>>> Antoine
>>>>>> 
>>>>>>> On Mar 1, 2019, at 3:24 PM, Antoine Toulme  wrote:
>>>>>>> 
>>>>>>> Perfect, thank you.
>>>>>>> 
>>>>>>>> On Mar 1, 2019, at 3:17 PM, Daniel Shahaf  
>>>>>>>> wrote:
>>>>>>>> 
>>>>>>>> Antoine Toulme wrote on Fri, Mar 01, 2019 at 15:09:39 -0800:
>>>>>>>>> I am happy to mention that you mentioned this term on list.
>>>>>>>> 
>>>>>>>> Thanks.
>>>>>>>> 
>>>>>>>>> What language should I use?
>>>>>>>> 
>>>>>>>> The public part of PNS tickets should be factual, so I'd say:
>>>>>>>> .
>>>>>>>> "In the _Star Wars_ universe there exists a character named Obi-Wan 
>>>>>>>> Kenobi"
>>>>>>>> .
>>>>>>>> with a link to Wikipedia for good measure.
>>>>>>>> 
>>>>>>>> Cheers,
>>>>>>>> 
>>>>>>>> Daniel
>>>>>>>> 
>>>>>>>>>> On Mar 1, 2019, at 3:06 PM, Daniel Shahaf  
>>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>> Antoine Toulme wrote on Fri, Mar 01, 2019 at 09:10:08 -0800:
>>>>>>>>>>> I’ll open a pooling name search ticket for Obiwarn and will test 
>>>>>>>>>>> the waters over there.
>>>>>>>>>> 
>>>>>>>>>> When you create a PNS ticket, please note on it the existence of
>>>>>>>>>> <https://en.wikipedia.org/wiki/Obi-Wan_Kenobi>.
>>>>>>>> 
>>>>>>>> -
>>>>>>>> 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
>> 
> 
> 
> -
> 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: [Cava] Suitable name search - choosing a name

2019-03-04 Thread Jim Jagielski
Thx. We'll wait for the decision.

> On Mar 4, 2019, at 2:05 AM, Antoine Toulme  wrote:
> 
> The ticket is now open: 
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-165
> 
> Cheers,
> 
> Antoine
> 
>> On Mar 1, 2019, at 3:24 PM, Antoine Toulme  wrote:
>> 
>> Perfect, thank you.
>> 
>>> On Mar 1, 2019, at 3:17 PM, Daniel Shahaf  wrote:
>>> 
>>> Antoine Toulme wrote on Fri, Mar 01, 2019 at 15:09:39 -0800:
 I am happy to mention that you mentioned this term on list.
>>> 
>>> Thanks.
>>> 
 What language should I use?
>>> 
>>> The public part of PNS tickets should be factual, so I'd say:
>>> .
>>>  "In the _Star Wars_ universe there exists a character named Obi-Wan Kenobi"
>>> .
>>> with a link to Wikipedia for good measure.
>>> 
>>> Cheers,
>>> 
>>> Daniel
>>> 
> On Mar 1, 2019, at 3:06 PM, Daniel Shahaf  wrote:
> 
> Antoine Toulme wrote on Fri, Mar 01, 2019 at 09:10:08 -0800:
>> I’ll open a pooling name search ticket for Obiwarn and will test the 
>> waters over there.
> 
> When you create a PNS ticket, please note on it the existence of
> .
>>> 
>>> -
>>> 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: [Cava] Suitable name search - choosing a name

2019-03-01 Thread Jim Jagielski
either works for me.

> On Feb 28, 2019, at 6:07 PM, Antoine Toulme  wrote:
> 
> I’ll change my vote.
> 
> +1 to Obiwarn.
> 
>> On Feb 28, 2019, at 3:04 PM, jonathan.r...@gmail.com wrote:
>> 
>> -1 to Bava
>> How about Obiwarn. it is an anagram for rainbow and it sounds cool. 
>> 
>> On 2019/02/28 22:20:00, Kenneth Knowles  wrote: 
>>> +1 to Bava
>>> 
>>> On Thu, Feb 28, 2019 at 2:11 PM Antoine Toulme  wrote:
>>> 
>>>> +1 for Bava. Checking usage now.
>>>> 
>>>> https://github.com/search?o=desc=bava
>>>> No repo using the name or active. Most repos hobbyists.
>>>> 
>>>> Google code:
>>>> https://opensource.google.com/projects/search?q=bava
>>>> No hits
>>>> 
>>>> Sourceforge:
>>>> https://sourceforge.net/directory/os:mac/?q=bava
>>>> No hits
>>>> 
>>>> Openhub:
>>>> https://www.openhub.net/p?ref=homepage=bava
>>>> 2 hits. But https://www.openhub.net/p/bava is empty with no code.
>>>> 
>>>> Trademarks:
>>>> https://www.trademarkia.com/trademarks-search.aspx?tn=bava
>>>> No hits in computer science domain
>>>> 
>>>> https://trademarks.justia.com/search?q=bava
>>>> No hits in computer science. Mostly sparkling wine.
>>>> 
>>>> USPTO:
>>>> 
>>>> http://tmsearch.uspto.gov/bin/showfield?f=toc=4805%3Avniyw0.1.1_search=searchss_L=50=_plural=yes_s_PARA1=_tagrepl~%3A=PARA1%24LD=PARA1+AND+PARA2_s_PARA2=bava_tagrepl~%3A=PARA2%24COMB_op_ALL=AND_default=search_search=Submit+Query_search=Submit+Query
>>>> 9 records found, 5 live. None about computer science.
>>>> 
>>>> Web presence:
>>>> 
>>>> https://www.google.com/search?q=bava=bava
>>>> 12,100,000 results
>>>> 
>>>> Mostly about Mario Bava. https://en.wikipedia.org/wiki/Mario_Bava Created
>>>> the horror “slasher” film.
>>>> 
>>>> Bava also means god in Sri Lanka: https://en.wikipedia.org/wiki/Bava
>>>> 
>>>> Finally, Bava is a conjugation of the verb to drool in French.
>>>> https://en.wiktionary.org/wiki/bava
>>>> 
>>>> StackOverflow:
>>>> https://stackoverflow.com/search?q=bava
>>>> 14 results because a user’s last name is Bava.
>>>> 
>>>> LinkedIn: I found one company named Bava International Ltd. They
>>>> specialize in apparel and fashion.
>>>> https://www.linkedin.com/company/bava-international-ltd/about/
>>>> 
>>>> No matches in Oxford dictionary:
>>>> https://en.oxforddictionaries.com/search?filter=dictionary=bava
>>>> 
>>>> No matches on Spotify.
>>>> 
>>>> Cheers,
>>>> 
>>>> Antoine
>>>> 
>>>> 
>>>>> On Feb 28, 2019, at 1:37 PM, Jim Jagielski  wrote:
>>>>> 
>>>>> What about Bava? Blockchain Java and no offensive meanings that I can
>>>> find.
>>>> 
>>>> 
>>> 
>> 
>> -
>> 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: [Cava] Suitable name search - choosing a name

2019-02-28 Thread Jim Jagielski



> On Feb 28, 2019, at 3:26 PM, Kevin A. McGrail  wrote:
> 
> On 2/28/2019 3:24 PM, Daniel Gruno wrote:
>>> 
>>> It also seems to imply that usage of the name rainbow would somehow
>>> be offensive or insensitive. Again, I'm not sure how. Nor am I aware
>>> of situations where the LGBT+ community "has expressed concerns"
>>> about usage *of the name* Rainbow.
>> 
>> +1
>> 
>> Anyone could hypothetically be offended by anything, I could list a
>> large number of theoretical offenses in project names. Let's please
>> stick to *actual* feedback and not preemptively censor ourselves. If
>> such feedback exists, fair enough, but I am also not aware of any such. 
> 
> I have asked off-list for someone I trust in the LGBTQ community who is
> also an ASF member to weigh in on this but I am aware that this is a
> concern.  I just can't articulate how much of a concern it is.  I will
> work to get that better clarified for the podling.

I am aware of various members of the LGBT+ community being offended by companies
trying to *co-opt* the rainbow *symbol* specifically and explicitly in relation 
to a cheap
and easy way to show "support" or a way to be "hip" or "cool"... heck, I'm 
offended by it as well.

But that's not what we're talking about.

And yeah, "just figure out a new name if there is any possible doubt" is
a safe strategy, but it does edge us closer to a slippery slope.

--
Signed Jim (who recalls the debate long ago about the Apache "Jakarta" name)
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [Cava] Suitable name search - choosing a name

2019-02-28 Thread Jim Jagielski
What about Bava? Blockchain Java and no offensive meanings that I can find.

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



Re: [Cava] Suitable name search - choosing a name

2019-02-28 Thread Jim Jagielski
Hmm... in less than 20mins the request for Rainbow was shut down...

I'm not sure how I feel about this... The justification seems a real stretch to 
me:


https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-164?filter=allissues

It also seems to imply that usage of the name rainbow would somehow be 
offensive or insensitive. Again, I'm not sure how. Nor am I aware of situations 
where the LGBT+ community "has expressed concerns" about usage *of the name* 
Rainbow.

But, I guess another name needs to be found...
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [Cava] Suitable name search - choosing a name

2019-02-28 Thread Jim Jagielski
Well, I have no doubt that the proposal is going to pass, so we might as well 
progress on w/ that assumption. ;)

> On Feb 28, 2019, at 10:09 AM, Kevin A. McGrail  wrote:
> 
> Jim, I don't read https://incubator.apache.org/guides/names.html to lead
> me to believe we are at that stage yet.  I think we want to have
> discussions about a provisional name first.  Specifically, "A podling
> needs to discover whether a name is suitable."
> 
> Regards,
> KAM
> 
> On 2/28/2019 9:42 AM, Jim Jagielski wrote:
>> We should simply file a standard Jira request for a podling namecheck.
>> 
>>> On Feb 28, 2019, at 9:36 AM, Kevin A. McGrail  wrote:
>>> 
>>> Not an objection per se but two comments:
>>> 
>>> 1 - Rainbow is associated with LGBTQ communities and there have been
>>> concerns about it being co-opted for other uses.  For example,
>>> https://www.theguardian.com/commentisfree/2017/jul/02/brands-rainbow-queasy-but-bring-lgbt-lives-into-mainstream-skittles-gay
>>> 
>>> 2 - I cannot speak for the LGBTQ community and I support them so I would
>>> say rainbow would be something I would avoid.
>>> 
>>> In the business world I often recommend people consider made up words. 
>>> Less chance of conflictions.
>>> 
>>> Regards,
>>> KAM
>>> 
>>> On 2/28/2019 3:28 AM, Antoine Toulme wrote:
>>>> Hey folks, just checking in.
>>>> 
>>>> I would like to establish rough consensus. If you’re still following, we 
>>>> have narrowed down the list to rainbow, sprocket and winch.
>>>> 
>>>> We have one vote for rainbow, and one for winch.
>>>> 
>>>> When establishing rough consensus, it’s a good idea to push proposals to 
>>>> hear objections.
>>>> 
>>>> At this time, I’d like to push for the name rainbow. Any objections?
>>>> 
>>>>> On Feb 26, 2019, at 10:10 PM, Antoine Toulme  wrote:
>>>>> 
>>>>> I ran searches for rainbow, sprocket and winch and didn’t find OSS 
>>>>> projects with those names.
>>>>> 
>>>>> I personally would like to vouch for Rainbow. It does fit the whimsical 
>>>>> requirement of Apache project names.
>>>>> 
>>>>>> On Feb 26, 2019, at 3:57 PM, Kevin A. McGrail  
>>>>>> wrote:
>>>>>> 
>>>>>> On 2/26/2019 6:24 PM, Kenneth Knowles wrote:
>>>>>>> I searched for "Jal" and came up with Japan Air Lines, which is clearly 
>>>>>>> a
>>>>>>> really different field of use.
>>>>>>> 
>>>>>>> I also found the Wikipedia article on JAL but was hasty in presuming it
>>>>>>> described a historical language. If it is an active open source project,
>>>>>>> let's not collide.
>>>>>>> 
>>>>>>> So I'll change my vote to "Winch". I again did a quick search, but 
>>>>>>> sounds
>>>>>>> like someone should check my work...
>>>>>> Re: JAL, the airline is just not an issue.  The programming language I
>>>>>> think is as there are books on Amazon less than 6 years old on PAL
>>>>>> (https://www.amazon.com/PIC-Microcontroller-Programming-captivating-lessons/dp/190792017X)
>>>>>>  
>>>>>> I don't think it's legacy just perhaps mature and things like Raspberry
>>>>>> Pi's overtaking the field.
>>>>>> 
>>>>>> Re: Winch, might be a common name and undefendable as a trademark, etc. 
>>>>>> Otherwise, though, I couldn't find much relevant in OSS spaces except a
>>>>>> company called winch gate. 
>>>>>> 
>>>>>> http://tmsearch.uspto.gov/ might help
>>>>>> 
>>>>>> Regards,
>>>>>> 
>>>>>> KAM
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> -- 
>>>>>> Kevin A. McGrail
>>>>>> Member, Apache Software Foundation
>>>>>> Chair Emeritus Apache SpamAssassin Project
>>>>>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>>>>> 
>>>>>> 
>>>>>> -
>>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.ap

Re: [Cava] Suitable name search - choosing a name

2019-02-28 Thread Jim Jagielski
We should simply file a standard Jira request for a podling namecheck.

> On Feb 28, 2019, at 9:36 AM, Kevin A. McGrail  wrote:
> 
> Not an objection per se but two comments:
> 
> 1 - Rainbow is associated with LGBTQ communities and there have been
> concerns about it being co-opted for other uses.  For example,
> https://www.theguardian.com/commentisfree/2017/jul/02/brands-rainbow-queasy-but-bring-lgbt-lives-into-mainstream-skittles-gay
> 
> 2 - I cannot speak for the LGBTQ community and I support them so I would
> say rainbow would be something I would avoid.
> 
> In the business world I often recommend people consider made up words. 
> Less chance of conflictions.
> 
> Regards,
> KAM
> 
> On 2/28/2019 3:28 AM, Antoine Toulme wrote:
>> Hey folks, just checking in.
>> 
>> I would like to establish rough consensus. If you’re still following, we 
>> have narrowed down the list to rainbow, sprocket and winch.
>> 
>> We have one vote for rainbow, and one for winch.
>> 
>> When establishing rough consensus, it’s a good idea to push proposals to 
>> hear objections.
>> 
>> At this time, I’d like to push for the name rainbow. Any objections?
>> 
>>> On Feb 26, 2019, at 10:10 PM, Antoine Toulme  wrote:
>>> 
>>> I ran searches for rainbow, sprocket and winch and didn’t find OSS projects 
>>> with those names.
>>> 
>>> I personally would like to vouch for Rainbow. It does fit the whimsical 
>>> requirement of Apache project names.
>>> 
 On Feb 26, 2019, at 3:57 PM, Kevin A. McGrail  wrote:
 
 On 2/26/2019 6:24 PM, Kenneth Knowles wrote:
> I searched for "Jal" and came up with Japan Air Lines, which is clearly a
> really different field of use.
> 
> I also found the Wikipedia article on JAL but was hasty in presuming it
> described a historical language. If it is an active open source project,
> let's not collide.
> 
> So I'll change my vote to "Winch". I again did a quick search, but sounds
> like someone should check my work...
 Re: JAL, the airline is just not an issue.  The programming language I
 think is as there are books on Amazon less than 6 years old on PAL
 (https://www.amazon.com/PIC-Microcontroller-Programming-captivating-lessons/dp/190792017X)
  
 I don't think it's legacy just perhaps mature and things like Raspberry
 Pi's overtaking the field.
 
 Re: Winch, might be a common name and undefendable as a trademark, etc. 
 Otherwise, though, I couldn't find much relevant in OSS spaces except a
 company called winch gate. 
 
 http://tmsearch.uspto.gov/ might help
 
 Regards,
 
 KAM
 
 
 
 -- 
 Kevin A. McGrail
 Member, Apache Software Foundation
 Chair Emeritus Apache SpamAssassin Project
 https://www.linkedin.com/in/kmcgrail - 703.798.0171
 
 
 -
 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
>> 
> 
> -- 
> Kevin A. McGrail
> Member, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
> 
> 
> -
> 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] Accept Cava into the Apache Incubator

2019-02-21 Thread Jim Jagielski
+1 (binding)

> On Feb 20, 2019, at 2:50 PM, Antoine Toulme  wrote:
> 
> Hi everyone,
> 
> we've discussed the proposal for the Cava project in [1] and [2]. The
> proposal itself can be found on the wiki[3].
> 
> We discussed how to go about finding a suitable name for the project in [2].
> I will kick off a vote to pick a name based on the proposals made there.
> 
> According to the Incubator rules[4] I'd like to call a vote to accept the
> new "Cava" project as a podling in the Apache Incubator.
> 
> A vote for accepting a new Apache Incubator podling is a majority vote.
> Everyone is welcome to vote, only Incubator PMC member votes are binding.
> It would be helpful (but not required) if you could add a comment stating
> whether your vote is binding or non-binding.
> 
> This vote will run for at least 72 hours (but I expect to keep it open for
> longer). Please VOTE as follows:
> 
> [ ] +1 Accept Cava into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept Cava into the Apache Incubator because ...
> 
> Thank you for everyone who decided to join in in the past discussions!
> Antoine
> 
> [1]: 
> https://lists.apache.org/thread.html/5a7f6a218b11a1cac61fbd53f4c995fd7716f8ad3751cf9f171ebd57@%3Cgeneral.incubator.apache.org%3E
> [2]: 
> https://lists.apache.org/thread.html/8d8014f53f140a3ccdd517c3c303de1d45cc04afdaee5961ac43e7fc@%3Cgeneral.incubator.apache.org%3E
> [3]: https://wiki.apache.org/incubator/CavaProposal?action=recall=14
> [4]: https://incubator.apache.org/guides/proposal.html#the_vote
> -
> 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: [Cava] Suitable name search

2019-02-20 Thread Jim Jagielski
Ah yes... agreed.

> On Feb 19, 2019, at 5:33 PM, Dave Fisher  wrote:
> 
> Jim,
> 
> The potential conflict is a small San Francisco blockchain software comp[any 
> called kava.io <http://kava.io/>.
> 
> Regards,
> Dave
> 
>> On Feb 19, 2019, at 5:50 AM, Jim Jagielski  wrote:
>> 
>> +1 keeping as-is.
>> 
>>> On Feb 18, 2019, at 1:28 PM, Antoine Toulme  wrote:
>>> 
>>> First, a heartfelt thank you to all for participating in this discussion.
>>> 
>>> I am tempted to keep Cava _for now_ given this late feedback, and proceed 
>>> to proposing the project.
>>> To be more precise, I recommend we get the project into the incubator with 
>>> this name. We can change the name of the project 3 to 6 months in.
>>> 
>>> We have so far received significant interest from the Apache community and 
>>> others, and it looks like we can go from there.
>>> 
>>> John, good point on this website, kava.io. I note the company is named Kava 
>>> Labs Inc. and their GitHub is Kava-Labs.
>>> https://github.com/Kava-Labs
>>> It also looks like their code is in the crypto domain, but more on the 
>>> interchange/wallet side and written in Go and TypeScript.
>>> I’ll add them to the list when performing the suitable name search item on 
>>> Jira.
>>> 
>>> I am going to give everyone 48 hours to voice strong opinions against this 
>>> approach.
>>> 
>>> Cheers,
>>> 
>>> Antoine
>>> 
>>>> On Feb 18, 2019, at 9:04 AM, John D. Ament  wrote:
>>>> 
>>>> If the project is already known as Cava and is looking to move to Apache, I
>>>> would recommend starting off as Cava.  I can see that there's already a
>>>> presence for it - https://github.com/ConsenSys/cava
>>>> 
>>>> However, I can see there's a pretty strong conflict on the name -
>>>> https://kava.io/
>>>> 
>>>> John
>>>> 
>>>> On Mon, Feb 18, 2019 at 11:43 AM Serge Huber  wrote:
>>>> 
>>>>> I agree that it doesn't matter if it "meant" something, you can simply
>>>>> forget the original meaning.
>>>>> 
>>>>> So it could mean "Cryptographic Java"
>>>>> 
>>>>> Here are other suggestions, because I like have the block and/or in the
>>>>> name :)
>>>>> 
>>>>> - Blockava
>>>>> - Blockva
>>>>> - Chainava
>>>>> 
>>>>> Please note I didn't do any proper name search for the above :)
>>>>> 
>>>>> Regards,
>>>>> Serge...
>>>>> 
>>>>> On Mon, Feb 18, 2019 at 5:32 PM Jim Jagielski  wrote:
>>>>>> 
>>>>>> Consensus Java :)
>>>>>> 
>>>>>>> On Feb 16, 2019, at 1:59 PM, Antoine Toulme 
>>>>> wrote:
>>>>>>> 
>>>>>>> I explained it in the proposal and the original thread, Cava stands
>>>>> for “ConsenSys Java”, after Guava.
>>>>>>> 
>>>>>>> It’s not a bad name per se, so let’s add it to the proposals.
>>>>>>> 
>>>>>>>> On Feb 16, 2019, at 9:58 AM, Henry Saputra 
>>>>> wrote:
>>>>>>>> 
>>>>>>>> From last thread, I was not sure why Cava was not a suitable name?
>>>>>>>> 
>>>>>>>> If there is a concern about trademarked name, the community can
>>>>> always go
>>>>>>>> with Apache Cava name.
>>>>>>>> 
>>>>>>>> - Henry
>>>>>>>> 
>>>>>>>> On Fri, Feb 15, 2019, 5:21 PM Antoine Toulme >>>> wrote:
>>>>>>>> 
>>>>>>>>> Thank you Anu.
>>>>>>>>> 
>>>>>>>>> I’ll add your proposal to mine and start a vote Monday if that’s
>>>>> agreeable.
>>>>>>>>> 
>>>>>>>>> Cheers,
>>>>>>>>> 
>>>>>>>>> Antoine
>>>>>>>>> 
>>>>>>>>>> On Feb 13, 2019, at 12:03 PM, Anu Engineer <
>>>>> aengin...@hortonworks.com>
>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>

Re: [VOTE] Accept Training into the Apache Incubator

2019-02-19 Thread Jim Jagielski
PS: I'd also like to be added to the initial Contributor's list, if possible.

> On Feb 19, 2019, at 8:51 AM, Jim Jagielski  wrote:
> 
> +1 (binding)
> 
>> On Feb 13, 2019, at 2:57 AM, Lars Francke  wrote:
>> 
>> Hi everyone,
>> 
>> we've discussed the proposal for the Training project in [1] and [2]. The
>> proposal itself can be found on the wiki[3].
>> 
>> According to the Incubator rules[4] I'd like to call a vote to accept the
>> new "Training" project as a podling in the Apache Incubator.
>> 
>> A vote for accepting a new Apache Incubator podling is a majority vote.
>> Everyone is welcome to vote, only Incubator PMC member votes are binding.
>> It would be helpful (but not required) if you could add a comment stating
>> whether your vote is binding or non-binding.
>> 
>> This vote will run for at least 72 hours (but I expect to keep it open for
>> longer). Please VOTE as follows:
>> 
>> [ ] +1 Accept Training into the Apache Incubator
>> [ ] +0 Abstain
>> [ ] -1 Do not accept Training into the Apache Incubator because ...
>> 
>> Thank you for everyone who decided to join in in the past discussions!
>> Lars
>> 
>> [1] <
>> https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E
>>> 
>> 
>> [2] <
>> https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E
>>> 
>> 
>> [3] <https://wiki.apache.org/incubator/TrainingProposal#preview>
>> 
>> [4] <
>> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
>>> 
> 


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



Re: [VOTE] Accept Training into the Apache Incubator

2019-02-19 Thread Jim Jagielski
+1 (binding)

> On Feb 13, 2019, at 2:57 AM, Lars Francke  wrote:
> 
> Hi everyone,
> 
> we've discussed the proposal for the Training project in [1] and [2]. The
> proposal itself can be found on the wiki[3].
> 
> According to the Incubator rules[4] I'd like to call a vote to accept the
> new "Training" project as a podling in the Apache Incubator.
> 
> A vote for accepting a new Apache Incubator podling is a majority vote.
> Everyone is welcome to vote, only Incubator PMC member votes are binding.
> It would be helpful (but not required) if you could add a comment stating
> whether your vote is binding or non-binding.
> 
> This vote will run for at least 72 hours (but I expect to keep it open for
> longer). Please VOTE as follows:
> 
> [ ] +1 Accept Training into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept Training into the Apache Incubator because ...
> 
> Thank you for everyone who decided to join in in the past discussions!
> Lars
> 
> [1] <
> https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E
>> 
> 
> [2] <
> https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E
>> 
> 
> [3] 
> 
> [4] <
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
>> 


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



Re: [Cava] Suitable name search

2019-02-19 Thread Jim Jagielski
+1 keeping as-is.

> On Feb 18, 2019, at 1:28 PM, Antoine Toulme  wrote:
> 
> First, a heartfelt thank you to all for participating in this discussion.
> 
> I am tempted to keep Cava _for now_ given this late feedback, and proceed to 
> proposing the project.
> To be more precise, I recommend we get the project into the incubator with 
> this name. We can change the name of the project 3 to 6 months in.
> 
> We have so far received significant interest from the Apache community and 
> others, and it looks like we can go from there.
> 
> John, good point on this website, kava.io. I note the company is named Kava 
> Labs Inc. and their GitHub is Kava-Labs.
> https://github.com/Kava-Labs
> It also looks like their code is in the crypto domain, but more on the 
> interchange/wallet side and written in Go and TypeScript.
> I’ll add them to the list when performing the suitable name search item on 
> Jira.
> 
> I am going to give everyone 48 hours to voice strong opinions against this 
> approach.
> 
> Cheers,
> 
> Antoine
> 
>> On Feb 18, 2019, at 9:04 AM, John D. Ament  wrote:
>> 
>> If the project is already known as Cava and is looking to move to Apache, I
>> would recommend starting off as Cava.  I can see that there's already a
>> presence for it - https://github.com/ConsenSys/cava
>> 
>> However, I can see there's a pretty strong conflict on the name -
>> https://kava.io/
>> 
>> John
>> 
>> On Mon, Feb 18, 2019 at 11:43 AM Serge Huber  wrote:
>> 
>>> I agree that it doesn't matter if it "meant" something, you can simply
>>> forget the original meaning.
>>> 
>>> So it could mean "Cryptographic Java"
>>> 
>>> Here are other suggestions, because I like have the block and/or in the
>>> name :)
>>> 
>>> - Blockava
>>> - Blockva
>>> - Chainava
>>> 
>>> Please note I didn't do any proper name search for the above :)
>>> 
>>> Regards,
>>> Serge...
>>> 
>>> On Mon, Feb 18, 2019 at 5:32 PM Jim Jagielski  wrote:
>>>> 
>>>> Consensus Java :)
>>>> 
>>>>> On Feb 16, 2019, at 1:59 PM, Antoine Toulme 
>>> wrote:
>>>>> 
>>>>> I explained it in the proposal and the original thread, Cava stands
>>> for “ConsenSys Java”, after Guava.
>>>>> 
>>>>> It’s not a bad name per se, so let’s add it to the proposals.
>>>>> 
>>>>>> On Feb 16, 2019, at 9:58 AM, Henry Saputra 
>>> wrote:
>>>>>> 
>>>>>> From last thread, I was not sure why Cava was not a suitable name?
>>>>>> 
>>>>>> If there is a concern about trademarked name, the community can
>>> always go
>>>>>> with Apache Cava name.
>>>>>> 
>>>>>> - Henry
>>>>>> 
>>>>>> On Fri, Feb 15, 2019, 5:21 PM Antoine Toulme >> wrote:
>>>>>> 
>>>>>>> Thank you Anu.
>>>>>>> 
>>>>>>> I’ll add your proposal to mine and start a vote Monday if that’s
>>> agreeable.
>>>>>>> 
>>>>>>> Cheers,
>>>>>>> 
>>>>>>> Antoine
>>>>>>> 
>>>>>>>> On Feb 13, 2019, at 12:03 PM, Anu Engineer <
>>> aengin...@hortonworks.com>
>>>>>>> wrote:
>>>>>>>> 
>>>>>>>> I would like to suggest “Jal”, in reference to Indra’s net (or Indra
>>>>>>> jal) https://en.wikipedia.org/wiki/Indra%27s_net
>>>>>>>> 
>>>>>>>> From the link:
>>>>>>>> "Imagine a multidimensional spider's web in the early morning
>>> covered
>>>>>>> with dew drops. And every dew drop contains the reflection of all
>>> the other
>>>>>>> dew drops.
>>>>>>>> And, in each reflected dew drop, the reflections of all the other
>>> dew
>>>>>>> drops in that reflection. And so ad infinitum. That is the Buddhist
>>>>>>> conception of the universe in an image." –Alan Watts[1]
>>>>>>>> 
>>>>>>>> And for what it is worth, it is the ultimate connected chain or
>>> graph (
>>>>>>>> 
>>>>>>>> --Anu
>>>>>>>> 
>>>>>>>>

Re: [PROPOSAL] New blockchain project: Cava

2019-02-19 Thread Jim Jagielski
I see nothing wrong w/ Cava and see no need to change it, esp before incubation.

> On Feb 18, 2019, at 11:40 AM, John D. Ament  wrote:
> 
> On Tue, Feb 5, 2019 at 6:52 PM Michael Wall  wrote:
> 
>> Interesting proposal.  I would be interested in helping.  Seems like you
>> don't need anymore mentors so I can volunteer in any capacity you need.
>> 
>> I think you are going to have trouble with the name though as
>> https://cava.com/ is a great restaurant.
>> 
>> 
> Sorry for the late reply - but that's not how naming works.  I would
> suggest that the proposed podling works with their champion to figure out
> if the name needs to be changed before incubation.  This isn't typically
> how we do it.
> 
> Typically, a name needs to be in a related field.  If there was something
> called "Cava" that also dealt with Blockchain or databases or similar, then
> the name "Cava" would be an issue.  Just because a restaurant chain is
> named Cava doesn't mean it's not a suitable name.
> 
> John
> 
> 
>> Mike
>> 
>> On Tue, Feb 5, 2019 at 6:36 PM Dave Fisher  wrote:
>> 
>>> Hi -
>>> 
>>> I would also be happy to volunteer as a Mentor to this podling.
>>> 
>>> Regards,
>>> Dave
>>> 
 On Feb 5, 2019, at 3:28 PM, Kenneth Knowles  wrote:
 
 +1
 
 I would like to volunteer as an additional mentor.
 
 Kenn
 
 On Tue, Feb 5, 2019 at 2:57 PM Justin Mclean >> 
 wrote:
 
> Hi,
> 
> Nice proposal. Just a couple of  comments.
> 
>> The project is well established and counts 2 active committers. Some
> contributions were made from the community.
> 
> Being that small may be a concern, the ASF prefers project with a
> community around them, but it’s not always a barrier to entry see for
> example Apache PLC4X.
> 
>> Blockchain protocol developers organize well in communities, and some
> lively discussions take place over Twitter, Gitter, Telegram.
> 
> At the ASF all decisions need to be made on the mailing list not on
>> any
> external platform mentioned above. Would the project be OK with moving
> discussions to a mailing list and having them in an asynchronous
>> manner?
> 
>> We will remain in incubation for a period of no less than a year so
>> we
> can properly invest and build a community of users, contributors and
> committers around our goals.
> 
> Most projects take more than a year to graduate, two years is usual
>> but
> some projects do take longer. Is the project OK with that and will
>> your
> mentors stay around for that long?
> 
>> '''Initial Committers'''
>> 
>> Antoine Toulme (toulmean at apache dot org) *
> 
> Seem odd to only list one initial committer, all initial committer s
>> are
> on the PPMC and you would need a minimum of 3 active people. The IPMC
> generally likes to see 5.
> 
> 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



Re: [Cava] Suitable name search

2019-02-18 Thread Jim Jagielski
Consensus Java :)

> On Feb 16, 2019, at 1:59 PM, Antoine Toulme  wrote:
> 
> I explained it in the proposal and the original thread, Cava stands for 
> “ConsenSys Java”, after Guava.
> 
> It’s not a bad name per se, so let’s add it to the proposals.
> 
>> On Feb 16, 2019, at 9:58 AM, Henry Saputra  wrote:
>> 
>> From last thread, I was not sure why Cava was not a suitable name?
>> 
>> If there is a concern about trademarked name, the community can always go
>> with Apache Cava name.
>> 
>> - Henry
>> 
>> On Fri, Feb 15, 2019, 5:21 PM Antoine Toulme > 
>>> Thank you Anu.
>>> 
>>> I’ll add your proposal to mine and start a vote Monday if that’s agreeable.
>>> 
>>> Cheers,
>>> 
>>> Antoine
>>> 
 On Feb 13, 2019, at 12:03 PM, Anu Engineer 
>>> wrote:
 
 I would like to suggest “Jal”, in reference to Indra’s net (or Indra
>>> jal) https://en.wikipedia.org/wiki/Indra%27s_net
 
 From the link:
 "Imagine a multidimensional spider's web in the early morning covered
>>> with dew drops. And every dew drop contains the reflection of all the other
>>> dew drops.
 And, in each reflected dew drop, the reflections of all the other dew
>>> drops in that reflection. And so ad infinitum. That is the Buddhist
>>> conception of the universe in an image." –Alan Watts[1]
 
 And for what it is worth, it is the ultimate connected chain or graph (
 
 --Anu
 
 
 
 
 
 On 2/13/19, 10:58 AM, "Antoine Toulme"  wrote:
 
  Hello all,
 
  As discussed previously, Cava is not a proper name for the proposal
>>> discussed last week on this list and published to the wiki [0].
 
  I humbly would like to ask the community for feedback and proposals
>>> on a suitable name for this proposal, in line with the guidelines [1].
 
  In preparation for this search, I have put together a list of names:
 
  - Rainbow (after the name of my kid’s favorite toy, and in line with
>>> the crypto community unicorn punk theme [2].
  - Winch (a mechanical device used to wind up or wind out wires
>>> (Wikipedia) , in the chain theme)
  - Sprocket (a profiled wheel with teeth, or cogs, that mesh with a
>>> chain, track or other perforated or indented material. (Wikipedia), in the
>>> chain theme as well)
 
  I have researched those names lightly and I have not seen them used
>>> heavily by an open source project in crypto. I followed the guidelines to
>>> search across different open source communities.
 
  Please provide your own proposal and let’s work together towards a
>>> rough consensus. If one of the proposals above registers, please let us
>>> know as well.
 
  Cheers,
 
  Antoine
 
  [0]: https://wiki.apache.org/incubator/CavaProposal
  [1]: https://incubator.apache.org/guides/names.html <
>>> https://incubator.apache.org/guides/names.html>
  [2]: https://www.urbandictionary.com/define.php?term=unicorn%20punk
 
 
 -
 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: Incubator exit interview

2019-01-14 Thread Jim Jagielski
Isn't that starting off on the wrong foot? off list communication, 
non-transparancy,
treating the VP of the PMC as "more" than an administrative position, etc...

> On Dec 22, 2018, at 6:27 PM, Julian Hyde  wrote:
> 
> Another idea is for Justin (or someone else active in the IPMC) to
> have a phone call with the incoming chair of the newly-graduated
> project. People are more likely to open up in an "off the record" and
> interactive setting.
> 
> This would be in addition to the written questions.
> On Sat, Dec 22, 2018 at 1:38 PM Justin Mclean  wrote:
>> 
>> Hi,
>> 
>> Thanks for putting this together. I took a quick look and have some
>>> suggestions (so perhaps getting the edit access would be good, if you are
>>> happy for me to change things).
>>> 
>> 
>> I'm happy for you to change things I'll give you access once in the front
>> of a real computer.
>> 
>> The question about the Apache Way is a simple yes / no. I suppose no one is
>>> going to respond no when they have graduated or just about to graduate.
>> 
>> 
>> I'm willing to be surprised and I think we will get some nos If people
>> answer honestly.
>> 
>> What does the Apache way mean to you?
>>> What do you think are the most important aspects of Apache culture?
>>> How would you describe the Apache Way?
>>> What you you understand about the Apache Way?
>>> 
>> 
>> All good questions, feel free to add them.
>> 
>> The responses will be more text based and I hope will capture a bit more
>>> than a yes/no type question would.
>> 
>> 
>> I was trying to keep it short, the longer it is the less likely people will
>> fill it in.
>> 
>> 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



Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc0

2019-01-02 Thread Jim Jagielski
+1 (binding)

> On Dec 28, 2018, at 2:07 PM, Steffen Rochel  wrote:
> 
> Dear community,
> 
> This is a call for releasing Apache MXNet (incubating) 1.4.0, release
> candidate 0
> 
> Apache MXNet (incubating) community has voted and approved the release.
> 
> Vote thread:
> https://lists.apache.org/thread.html/28f4d4bb62ce10d85b1ef856602b27cb6d8971e4ece6f212411b8ca6@%3Cdev.mxnet.apache.org%3E
> 
> Result thread:
> https://lists.apache.org/thread.html/236554041a412415df783d652830272beb21d36660e8e0d5e0237f58@%3Cdev.mxnet.apache.org%3E
> 
> 
> 
> The source tarball, including signatures, digests, etc. can be found at:
> 
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.4.0.rc0/
> 
> The tag to be voted upon:
> https://github.com/apache/incubator-mxnet/releases/tag/1.4.0.rc0
> 
> The release hash is c84bb78
> 
> :
> https://github.com/apache/incubator-mxnet/commit/c84bb7880a51d22ee1e2bfc688d0a2099c0b977b
> 
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
> 
> For information about the contents of this release, see:
> https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubating%29+1.4.0+Release+Notes
> 
> The vote will be open until January 3rd noon PST.
> 
> [ ] +1 release this package as 1.4.0
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
> 
> Best regards,
> Steffen


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



Re: Incubator exit interview

2018-12-11 Thread Jim Jagielski
Yeah... I remember chatting w/ you about this idea at ApacheCon... +1

> On Dec 7, 2018, at 10:15 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> I was just wondering if it would be a good idea to ask projects a few 
> questions of committers/PPMC members once they leave the incubator to gauge 
> how we are doing and find out where there is room for improvement? It would 
> be simple to try as a proof of concept on a couple of graduating projects to 
> see to we get any valuable feedback that we don’t normally get on this list 
> or in the podling reports.
> 
> Some suggested questions off the top of my head:
> 
> Thinking about the project that you have just graduated as part of:
> - I am a X committer X PMC member X mentor X none of those X rather not say
> - How many times have you gone through the incubation process: X one X two X 
> three X more than three
> - Have you felt supported by the incubator? If not what could be improved?
> - Have you felt supported by the your mentors? If not what could be improved?
> - Did you run into any issues with any part of the incubating process? If so 
> what?
> - Was is clear what you needed to do to graduate?
> - What, if anything, could be done to make the graduation process smoother?
> - Is the time taken to graduate X too short? X just right? X too long?
> - Do you have a good understanding of the Apache Way? If not what areas are 
> you unclear on?
> - Anything else you want to add or comment on?
> 
> Probably best if answers were anonymous. Anyone have any ideas for other 
> questions or improvement to the above? I’d like to keep it under a dozen 
> questions.
> 
> 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



Re: [VOTE] - Release Apache OpenWhisk (Incubating) Composer module 0.9.0 (rc1)

2018-12-04 Thread Jim Jagielski
+1 (binding) :)

> On Dec 3, 2018, at 9:59 AM, Dave Grove  wrote:
> 
> After 7 days, this vote still needs two additional +1 binding votes to pass.  
> (Bertrand Delacretaz's binding +1 from the Podling PPMC vote [1] carries to 
> this VOTE).
> 
> The OpenWhisk podling only has two mentors (Bertrand Delacretaz and Jim 
> Jagielski), so we need at least one vote beyond our mentors to be able to 
> close this voting thread.
> 
> thank you,
> 
> --dave
> 
> [1] 
> https://lists.apache.org/thread.html/8b182e4b0ad7e402f4be61500285abedf44067215a5d351bdaeb005b@%3Cdev.openwhisk.apache.org%3E
> 
> On 2018/11/26 18:59:23, "David P Grove"  wrote: 
>> 
>> 
>> Dear IPMC members,
>> 
>> This is a call for the vote to release Apache OpenWhisk (Incubating):
>> Composer module, 0.9.0.
>> 
>> The Apache OpenWhisk community has voted on and approved a proposal to
>> release Apache OpenWhisk (Incubating): Composer module 0.9.0.
>> 
>> We now request the Incubator PMC members to review and vote on this
>> incubator release.
>> 
>> Apache OpenWhisk Composer is a programming model for composing cloud
>> functions built on Apache OpenWhisk.
>> 
>> OpenWhisk Composer vote thread:
>> https://lists.apache.org/thread.html/5bc79c5f16661d46cd77557b2b1a4ec7d41d184c7dc44026fd92a3de@%3Cdev.openwhisk.apache.org%3E
>> 
>> OpenWhisk Composer vote result email:
>> https://lists.apache.org/thread.html/0962026eef420586a482b7fbe29c0db1fb28bad38a7ad5cbe943aba1@%3Cdev.openwhisk.apache.org%3E
>> 
>> This release comprises of source code distribution only. There is only one
>> module within this release number 0.9.0. The artifact were built from the
>> following Git commit IDs:
>> * openwhisk-composer: 7ae7f08,
>> 
>> The source code artifact of openwhisk composer can be found at:
>> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-composer-0.9.0-incubating-sources.tar.gz
>> 
>> The SHA-512 checksum for the artifact of openwhisk composer is
>> openwhisk-composer-0.9.0-incubating-sources.tar.gz:
>> 7D5ECB65 DF653840 C8A33C7B DDF346AD 2AA36507 DD1D6DE6 8CB99238 BDC93EF6
>> 425B5BAF
>> 1371C4BE 6F1E0DEF 01D60D18 03AADC33 B0B7BD95 40724450 5FF6D131
>> which can can be found via:
>> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-composer-0.9.0-incubating-sources.tar.gz.sha512
>> 
>> The signature of the artifact of openwhisk composer can be found via:
>> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-composer-0.9.0-incubating-sources.tar.gz.asc
>> 
>> This release was signed with key 147F886E.
>> KEYS file is available here:
>> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
>> 
>> This is the first release of Apache OpenWhisk, Composer module. so there is
>> no CHANGELOG file.
>> 
>> 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
>> 
>> Regards,
>> 
>> --dave
>> 
>> 
> 
> -
> 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 MXNet (incubating) version 1.3.1.rc0

2018-11-26 Thread Jim Jagielski
+1 (binding)

> On Nov 21, 2018, at 9:30 AM, Anton Chernov  wrote:
> 
> Dear community,
> 
> This is a call for a releasing Apache MXNet (incubating) 1.3.1, release
> candidate 0.
> 
> Apache MXNet (incubating) community has voted and approved the release.
> 
> Vote thread:
> https://lists.apache.org/thread.html/32ab13b6d2d80fd75dbc2ec62151d12d09f6e0ca89799ae0aa26894b@%3Cdev.mxnet.apache.org%3E
> 
> Result thread:
> https://lists.apache.org/thread.html/4b6559e75a1027a99fada99faa3161eac6604af9e786da457e051bc7@%3Cdev.mxnet.apache.org%3E
> 
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.3.1.rc0/
> 
> The tag to be voted upon is 1.3.1.rc0:
> https://github.com/apache/incubator-mxnet/releases/tag/1.3.1.rc0
> 
> The release hash is c1327f3:
> https://github.com/apache/incubator-mxnet/commit/c1327f317a7f371a9803a3f27be6ff90dc6af707
> 
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
> 
> For information about the contents of this release, see:
> https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubating%29+1.3.1+Release+Notes
> 
> The vote will be open for 72 hours.
> 
> [ ] +1 release this package as 1.3.1
> [ ] +0 no opinion
> [ ] -1 do not release this package because...
> 
> Best regards,
> Anton Chernov


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



Re: [VOTE][LAZY][IP CLEARANCE] OpenWhisk Composer

2018-11-19 Thread Jim Jagielski
+1

> On Nov 17, 2018, at 10:38 AM, Bertrand Delacretaz  
> wrote:
> 
> Hi Incubator PMC members,
> 
> The OpenwWhisk podling would like to accept a donation of the Composer
> module, as per https://issues.apache.org/jira/browse/INCUBATOR-222
> 
> See http://incubator.apache.org/ip-clearance/openwhisk-composer.html
> 
> Please vote to approve this contribution.
> 
> This majority vote is open for at least 72 hours and as usual lazy
> consensus applies.
> 
> -Bertrand
> 
> -
> 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: How to review so-called "binary releases"?

2018-11-16 Thread Jim Jagielski



> On Nov 15, 2018, at 2:41 AM, Bertrand Delacretaz  
> wrote:
> 
> 
> I see this as a two-level thing:
> 
> a) The source release is an Act of the Foundation, it is what the
> foundation produces
> 
> b) For the binaries, the PMC states that it thinks they are good and
> declares that the published digests and signatures are the correct
> ones. The Foundation does not state anything about them - use at your
> own risk but in practice that risk is very low if the PMC members
> collectively recommend using them.
> 
> That's not very different from what other open source projects do - we
> need a) for our legal shield but b) is exactly like random open source
> projects operate.
> 
> You have to trust an open source project when you use their binaries,
> and you can use digests and signatures to verify that those binaries
> are the same that everyone else uses - I don't think anyone provides
> more guarantees than that, except when you pay for someone to state
> that those binaries are good.
> 
> If people agree with this view we might need to explain this better,
> "unofficial" does not mean much, this two-level view might be more
> useful.

Agree 100%. Thx for very clearly and accurately describing all this.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: How to review so-called "binary releases"?

2018-11-14 Thread Jim Jagielski
The reason we "only officially" support source code releases is because that is 
what we produce.

> On Nov 14, 2018, at 6:24 AM, Myrle Krantz  wrote:
> 
> I had understood the reason that the foundation only officially supports
> source releases to be the fear of undetected malware in the release (like
> in the Ken Thompson hack).
> 
> Is that correct?  Are we all are in agreement that the probability of that
> kind of hack is very low?
> 
> I'd extend that by one step: Isn't the probably of that kind of hack
> *lower* if we compile our code ourselves, than if we ask our users to do it?
> 
> Best Regards,
> Myrle
> 
> On Wed, Nov 14, 2018 at 12:08 PM Mark Thomas  wrote:
> 
>> 1. Dependencies with inappropriate licenses. Perhaps more likely with
>> binary releases because they tend to ship with more dependencies but I
>> don't recall this ever being more than "Whoops. Tell the users. Do a new
>> release to fix it. Be more careful in future. Carry on." for either
>> binary or source releases.
>> 
>> 2. Copyright infringement. The only instance I can recall of this was a)
>> related to a source release and b) invalid because the accusing party
>> had actually originally copied "their" source from us and removed our
>> license headers. If anything, I think issue is less likely with a binary
>> release.
>> 
>> 3. Download traffic. Some binaries are large and much more likely to
>> cause infrastructure issues if the mirror network is not used correctly.
>> Infra has monitoring in place to a) identify issues and b) stop them
>> causing outages.
>> 
>> So overall, the liability looks to be well within what we are already
>> managing. I don't see anything that concerns me. Unless I have missed
>> something.
>> 
>> Mark
>> 
>> -
>> 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: How to review so-called "binary releases"?

2018-11-07 Thread Jim Jagielski
IMO, that was (and in many cases) still IS a Good Thing... the issue is that it 
must be made clear that what the ASF releases are source code artifacts. Any 
binary releases that are done are not official releases of the foundation nor 
the PMC, but are community provided conveniences.

> On Nov 7, 2018, at 8:14 AM, Carlos Santana  wrote:
> 
> Jim
> 
> What do you think now?
> Was that a good or bad thing?
> 
> TLDR; I’m in favor of convenient binaries is just the how they are handled. 
> 
> Sorry for my brevity, what I meant is that binaries should not be beside next 
> to the source release seating on the same server and giving the same 
> guarantees for both type of artifacts (source vs binary).  
> 
> Now in terms of convenience :-)
> ASF should not block a project of making binaries available to their 
> community for what ever purpose they think appropriate (ie nightly, binary of 
> a RC, binary of final RC)
> 
> ASF should provide guidance to the projects to make sure they make their 
> communities aware that a source artifact is different from a binary artifact. 
> A project for example can put warnings and bold text on the location (ie 
> directory, readme, inside the binary, download webpage, wiki etc) where the 
> community downloads a copy of the binary. 
> The warning can say this is not a release of the ASF, is just a convenient 
> binary “download on your own risk”, we provide sha256 sum and maybe the 
> binary is even signed, but best practice is for you to download the source 
> and be in control of building the binary. 
> 
> 
> 
> - Carlos Santana
> @csantanapr
> 
>> On Nov 7, 2018, at 7:04 AM, Jim Jagielski  wrote:
>> 
>> Just a FYI that in the early days of the ASF (and the httpd project), 
>> community binaries were a common offering...
>> -
>> 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: How to review so-called "binary releases"?

2018-11-07 Thread Jim Jagielski
Just a FYI that in the early days of the ASF (and the httpd project), community 
binaries were a common offering...
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: UNICEF Open Source project- Apache Foundation

2018-10-29 Thread Jim Jagielski
Hello there! I would be quite willing to chat. My personal cell is +1 (443) 
324-8390.

> On Oct 26, 2018, at 1:59 PM, Ariam Mogos  wrote:
> 
> Hi there,
> 
> I work in UNICEF’s Office of Innovation and was hoping to speak to someone 
> about a fantastic open source project in which we’re interested in working 
> with the Apache Foundation.
> 
> Look forward to hearing from you.
> 
> Best,
> Ariam
> 
> -
> Ariam Mogos
> Learning Lead
> UNICEF Ventures
> Office of Innovation
> skype: ariammogos
> mobile: +1 917-974-5997
> 
> www.unicefstories.org
> www.unicefinnovationfund.org
> 


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



Re: How to review so-called "binary releases"?

2018-10-25 Thread Jim Jagielski
+1. That distinction is important. The ASF, and our projects, release source 
code.

> On Oct 25, 2018, at 6:39 AM, Greg Stein  wrote:
> 
> Those are "convenience binaries" ... not "binary releases".
> 
> On Thu, Oct 25, 2018 at 2:25 AM Luciano Resende 
> wrote:
> 
>> While I agree that binary artifacts are for convenience purposes, if one
>> searches  our dist folder they will find lots of projects with binary
>> releases.
>> 
>> When reviewing binary archives we need to make sure that the license file
>> is updated with the shiped dependencies licenses appropriately and that
>> they are all compatible with the Apache License (notice file might also
>> need to be updated).
>> 
>> 
>> On Thu, Oct 25, 2018 at 05:38 Greg Stein  wrote:
>> 
>>> On Wed, Oct 24, 2018 at 10:25 PM Julian Hyde  wrote:
 ...
>>> 
 As a reviewer, how am I to vote on this release candidate?
>>> 
>>> 
>>> You do NOT vote on binary artifacts. Since you cannot release binaries,
>> you
>>> should not put the Foundation's imprimatur on those artifacts (and as PMC
>>> Member, that is what your vote represents).
>>> 
>>> 
 Should I vote -1 because the RC contains binaries?
>>> 
>>> 
>>> Vote on the source artifacts only. Clarify that your vote does not apply
>> to
>>> the binaries.
>>> 
>>> Cheers,
>>> -g
>>> 
>> --
>> Sent from my Mobile device
>> 


-
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]

2018-09-25 Thread Jim Jagielski
+1 (binding)

> On Sep 18, 2018, at 12:28 PM, Vincent S Hou  wrote:
> 
> 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.
> 
> 

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

2018-09-19 Thread Jim Jagielski
+1 (binding)

> On Sep 18, 2018, at 12:28 PM, Vincent S Hou  wrote:
> 
> 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.
> 
> 

Re: [VOTE] Apache Gobblin 0.13.0 release RC2

2018-09-18 Thread 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]

2018-09-18 Thread 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: [VOTE] Pulsar Release 2.1.1-incubating Candidate 1

2018-09-13 Thread Jim Jagielski
+1 on release... and +1 on removing the SHA-1s

> On Sep 11, 2018, at 7:34 PM, Henk P. Penning  wrote:
> 
> On Wed, 12 Sep 2018, Jerry Peng wrote:
> 
>> Date: Wed, 12 Sep 2018 00:31:35 +0200
>> From: Jerry Peng 
>> To: general@incubator.apache.org
>> Cc: d...@pulsar.incubator.apache.org
>> Subject: [VOTE] Pulsar Release 2.1.1-incubating Candidate 1
>> This is the first release candidate for Apache Pulsar, version
>> 2.1.1-incubating.
> 
>> Source and binary files:
>> https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-2.1.1-incubating-candidate-1/
> 
>> SHA-1 checksums:
> 
> Hi,
> 
>  SHA-1 checksum files shouldn't be publish checksums anymore.
> 
>  https://www.apache.org/dev/release-distribution#sigs-and-sums
> 
>  Please remove ; the vote may continue.
> 
>  Thanks ; regards,
> 
>  Henk Penning
> 
>    _
> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
> 
>> 506c172b13c1581f9b52769a4c6594541628b928
>> apache-pulsar-2.1.1-incubating-bin.tar.gz
>> de3a74449a78d0713998544237dde59765ee121f
>> apache-pulsar-2.1.1-incubating-src.tar.gz
>> 1d38554e58cfd733fc2d54ec1442747daeb8fc1b
>> apache-pulsar-io-connectors-2.1.1-incubating-bin.tar.gz
>> 
>> Maven staging repo:
>> https://repository.apache.org/content/repositories/orgapachepulsar-1026
>> 
>> The tag to be voted upon:
>> v2.1.1-incubating-candidate-1 68faf85083025b29bb6ab39028a1d467bd3d5217
>> https://github.com/apache/incubator-pulsar/releases/tag/v2.1.1-incubating-candidate-1
>> 
>> Pulsar's KEYS file containing PGP keys we use to sign the release:
>> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
>> 
>> Please download the the source package, and follow the README to build and
>> run the Pulsar standalone service.
>> 
>> Here is a guide for validating a release candidate:
>> https://github.com/apache/incubator-pulsar/wiki/Release-Candidate-Validation
>> 


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



Re: [VOTE] Graduate Apache Pulsar (incubating) as a TLP

2018-09-13 Thread Jim Jagielski
+1 (binding)

> On Sep 12, 2018, at 11:40 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> The Apache Pulsar project is ready to graduate as a TLP. They entered 
> Incubation on June 1, 2017, have had many releases and have grown the 
> community.
> 
> Vote:
> [ ] +1 - Recommend Graduation of Apache Pulsar as a TLP
> [ ] -1 - Do not recommend graduation of Apache Pulsar because ….
> 
> At the mentors request they did a maturity model analysis [1] and wrote 
> contribution guidelines. [2]
> 
> The Graduation Proposal was written and discussed on the dev list. [3] At the 
> mentor's recommendation the By-Laws Clause was removed. 
> 
> The new prospective PMC is set and the VOTE thread in the podling is here [4] 
> with these results. [5]
> 
> Regards,
> Dave
> 
> [1] 
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
>  
> <https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar>
> [2] http://pulsar.incubator.apache.org/en/contributing/ 
> <http://pulsar.incubator.apache.org/en/contributing/>
> [3] 
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
>  
> <https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E>
> [4] 
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
>  
> <https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E>
> [5] 
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
>  
> <https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E>
> 
> 
>  
> 
> Establish the Apache Pulsar Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of 
> the Foundation and consistent with the Foundation's purpose to establish 
> a Project Management Committee charged with the creation and maintenance 
> of open-source software, for distribution at no charge to the public, 
> related to a highly scalable, low latency messaging platform running on 
> commodity hardware. It provides simple pub-sub and queue semantics over 
> topics, lightweight compute framework, automatic cursor management for 
> subscribers, and cross-datacenter replication.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee 
> (PMC), to be known as the "Apache Pulsar Project", be and hereby is 
> established pursuant to Bylaws of the Foundation; and be it further  
> 
> RESOLVED, that the Apache Pulsar Project be and hereby is responsible 
> for the creation and maintenance of software related to a highly 
> scalable, low latency messaging platform running on commodity hardware. 
> It provides simple pub-sub and queue semantics over topics, lightweight 
> compute framework, automatic cursor management for subscribers, and 
> cross-datacenter replication; and be it further  
> 
> RESOLVED, that the office of "Vice President, Apache Pulsar" be and 
> hereby is created, the person holding such office to serve at the 
> direction of the Board of Directors as the chair of the Apache Pulsar 
> Project, and to have primary responsibility for management of the 
> projects within the scope of responsibility of the Apache Pulsar 
> Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are 
> appointed to serve as the initial members of the Apache Pulsar Project:
>   
> * Boyang Jerry Peng mailto:jerryp...@apache.org>> 
> * Brad McMillen mailto:bra...@apache.org>> 
> * David Fisher mailto:w...@apache.org>> 
> * Francis Christopher Liu mailto:tof...@apache.org>> 
> * Hiroyuki Sakai mailto:hrsa...@apache.org>> 
> * Ivan Brendan Kelly mailto:iv...@apache.org>> 
> * Jai Asher mailto:j...@apache.org>> 
> * Jia Zhai mailto:zhai...@apache.org>> 
> * Jim Jagielski mailto:j...@apache.org>> 
> * Joe Francis mailto:j...@apache.org>> 
> * Ludwig Pummer mailto:ludw...@apache.org>> 
> * Masahiro Sakamoto mailto:massa...@apache.org>> 
> * Masakazu Kitajo mailto:mas...@apache.org>> 
> * Matteo Merli mailto:mme...@apache.org>> 
> * Nozomi Kurihara mailto:nkuri...@apache.org>> 
> * P. Taylor Goetz mailto:ptgo...@apache.org>> 
> * Rajan Dhabalia mailto:rdhaba...@apache.org>> 
> * Sahaya Andrews mailto:andr...@apache.org>&

Re: [DISCUSS] Graduate Apache Pulsar (incubating) as a TLP

2018-09-11 Thread Jim Jagielski
+1 (binding)!

> On Sep 10, 2018, at 11:48 PM, Dave Fisher  wrote:
> 
> Hi -
> 
> The Apache Pulsar project is ready to graduate as a TLP. They entered 
> Incubation on June 1, 2017, have had many releases and have grown the 
> community.
> 
> At the mentors request they did a maturity model analysis [1] and wrote 
> contribution guidelines. [2]
> 
> The Graduation Proposal was written and discussed on the dev list. [3] At the 
> mentor's recommendation the By-Laws Clause was removed. 
> 
> The new prospective PMC is set and the VOTE thread in the podling is here [4] 
> with these results. [5]
> 
> Let’s see if there is any discussion here on general@incubator before moving 
> onto a VOTE.
> 
> Regards,
> Dave
> 
> [1] 
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
>  
> <https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar>
> [2] http://pulsar.incubator.apache.org/en/contributing/ 
> <http://pulsar.incubator.apache.org/en/contributing/>
> [3] 
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
>  
> <https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E>
> [4] 
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
>  
> <https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E>
> [5] 
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
>  
> <https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E>
> 
> 
>  
> 
> Establish the Apache Pulsar Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of 
> the Foundation and consistent with the Foundation's purpose to establish 
> a Project Management Committee charged with the creation and maintenance 
> of open-source software, for distribution at no charge to the public, 
> related to a highly scalable, low latency messaging platform running on 
> commodity hardware. It provides simple pub-sub and queue semantics over 
> topics, lightweight compute framework, automatic cursor management for 
> subscribers, and cross-datacenter replication.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee 
> (PMC), to be known as the "Apache Pulsar Project", be and hereby is 
> established pursuant to Bylaws of the Foundation; and be it further  
> 
> RESOLVED, that the Apache Pulsar Project be and hereby is responsible 
> for the creation and maintenance of software related to a highly 
> scalable, low latency messaging platform running on commodity hardware. 
> It provides simple pub-sub and queue semantics over topics, lightweight 
> compute framework, automatic cursor management for subscribers, and 
> cross-datacenter replication; and be it further  
> 
> RESOLVED, that the office of "Vice President, Apache Pulsar" be and 
> hereby is created, the person holding such office to serve at the 
> direction of the Board of Directors as the chair of the Apache Pulsar 
> Project, and to have primary responsibility for management of the 
> projects within the scope of responsibility of the Apache Pulsar 
> Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are 
> appointed to serve as the initial members of the Apache Pulsar Project:
>   
> * Boyang Jerry Peng mailto:jerryp...@apache.org>> 
> * Brad McMillen mailto:bra...@apache.org>> 
> * David Fisher mailto:w...@apache.org>> 
> * Francis Christopher Liu mailto:tof...@apache.org>> 
> * Hiroyuki Sakai mailto:hrsa...@apache.org>> 
> * Ivan Brendan Kelly mailto:iv...@apache.org>> 
> * Jai Asher mailto:j...@apache.org>> 
> * Jia Zhai mailto:zhai...@apache.org>> 
> * Jim Jagielski mailto:j...@apache.org>> 
> * Joe Francis mailto:j...@apache.org>> 
> * Ludwig Pummer mailto:ludw...@apache.org>> 
> * Masahiro Sakamoto mailto:massa...@apache.org>> 
> * Masakazu Kitajo mailto:mas...@apache.org>> 
> * Matteo Merli mailto:mme...@apache.org>> 
> * Nozomi Kurihara mailto:nkuri...@apache.org>> 
> * P. Taylor Goetz mailto:ptgo...@apache.org>> 
> * Rajan Dhabalia mailto:rdhaba...@apache.org>> 
> * Sahaya Andrews mailto:andr...@apache.org>> 
> * Sanjeev Kulkarni mailt

Re: [DISCUSS] Graduate Apache Pulsar (incubating) as a TLP

2018-09-11 Thread Jim Jagielski
Even Events is there under the Community tab.

> On Sep 11, 2018, at 12:33 AM, Justin Mclean  wrote:
> 
> Hi,
> 
> Just a couple of minor things I noticed on the website which checking it. 
> While this is mostly red [1] all seems all links are there other than Events? 
>  I'm curious to why organisations are mention on the team page [2] and why 
> Matteo is listed as the co-creator here [3]. Nothing that would stop 
> graduation of course.
> 
> Thanks,
> Justin
> 
> 1. https://whimsy.apache.org/pods/project/pulsar
> 2. http://pulsar.apache.org/en/team/
> 3. http://pulsar.apache.org/en/resources/
> -
> 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] Apache MXNet (incubating) 1.3.0 release RC0

2018-09-11 Thread Jim Jagielski
+1 (binding)

> On Sep 10, 2018, at 8:21 PM, Roshani Nagmote  
> wrote:
> 
> Thanks for testing the release and voting. I will remove md5 hashes as
> instructed.
> 
> Just a reminder: voting will end tomorrow, (Tuesday, September 11th,
> 11:30am PDT).
> It will be great if more members can test the release and vote by tomorrow.
> 
> - Roshani
> 
> On Sun, Sep 9, 2018 at 10:42 PM Sergio Fernández  wrote:
> 
>> +1 (binding)
>> 
>> So far I've checked:
>> * signatures and digests (md5 checksums can be removed)
>> * source releases file layouts
>> * matched git tags and commit ids
>> * incubator suffix and disclaimer
>> * LICENSE & NOTICE files look good
>> * no binary files in the source release
>> * clean build (osx 10.12.6)
>> 
>> I'd like to state this is a just a legal binding vote, which is what we
>> check at this stage. Functionally speaking the podling is responsible of
>> the good state of every release. I remark that because from the dev@ vote
>> I
>> can't see that feeling represented unanimously by the community.
>> 
>> 
>> On Fri, Sep 7, 2018, 11:36 Roshani Nagmote 
>> wrote:
>> 
>>> Hi all,
>>> 
>>> This is a call for releasing Apache MXNet (incubating) 1.3.0, release
>>> candidate RC0.
>>> 
>>> Apache MXNet (incubating) community has voted and approved the release.
>>> 
>>> Vote thread:
>>> 
>>> *
>>> 
>> https://lists.apache.org/thread.html/8ad6f14811be465cdf663d6962980fd95e12193626292631a21ec6f1@%3Cdev.mxnet.apache.org%3E
>>> <
>>> 
>> https://lists.apache.org/thread.html/8ad6f14811be465cdf663d6962980fd95e12193626292631a21ec6f1@%3Cdev.mxnet.apache.org%3E
 *
>>> 
>>> Results thread:
>>> 
>>> *
>>> 
>> https://lists.apache.org/thread.html/8dad26e9a485180a3dd36f2b54de24395b626a57b5e847bc99dda0e9@%3Cdev.mxnet.apache.org%3E
>>> <
>>> 
>> https://lists.apache.org/thread.html/8dad26e9a485180a3dd36f2b54de24395b626a57b5e847bc99dda0e9@%3Cdev.mxnet.apache.org%3E
 *
>>> 
>>> The source tarball, including signatures, digests etc. can be found at:
>>> 
>>> *https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.3.0.rc0/
>>> *
>>> 
>>> The release tag can be found here:
>>> 
>>> *https://github.com/apache/incubator-mxnet/releases/tag/1.3.0.rc0
>>> *
>>> 
>>> The release hash is b3be92f4a48bce62a5a8424271871c2f81c8f7f1 and can be
>>> found here:
>>> 
>>> *
>>> 
>> https://github.com/apache/incubator-mxnet/commit/b3be92f4a48bce62a5a8424271871c2f81c8f7f1
>>> <
>>> 
>> https://github.com/apache/incubator-mxnet/commit/b3be92f4a48bce62a5a8424271871c2f81c8f7f1
 *
>>> 
>>> Release artifacts are signed with the following key:
>>> 
>>> CB91 64C7 6A80 3D86 1DE1  6E5B 9105 2D92 2E28 A38F
>>> 
>>> 
>>> KEYS file available:
>>> 
>>> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
>>> 
>>> The vote will end on Tuesday, September 11th, 11:30am PDT or until the
>>> necessary number of votes is reached.
>>> 
>>> [ ] +1 Release this package as 1.3.0
>>> [ ] +0 no opinion
>>> [ ] -1 Do not release this package because ...
>>> 
>>> Thanks,
>>> Roshani
>>> 
>> 


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



Re: Missing mentor sign off on podling reports

2018-09-07 Thread Jim Jagielski
It would be helpful if the URL for the report was included.

> On Sep 7, 2018, at 4:59 AM, Justin Mclean  wrote:
> 
> Hi,
> 
> While we have a couple of day to go, we still have serval projects who don’t 
> have any sign offs by their mentors.
> 
> Congratulations to Nemo where 5 of the 6 mentors have already signed off the 
> report.
> 
> The podlings currently missing sign off are:
> Myriad
> PageSpeed
> S2Graph
> Spot
> Tamaya
> Warble
> 
> Warble seems to have only one mentor so may need some help there.
> 
> There’s also a number of other podlings that I’d like to see more mentors 
> sign off on:
> Airflow
> Annotator
> Daffodil
> Druid
> Griffin
> Omid
> Ponytail
> Samoa
> SensSoft
> Singa
> Superset
> Taverna
> Tephra
> 
> 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



Re: Superset releases [was Re: ASF release process]

2018-09-02 Thread Jim Jagielski
I have responded on the dev@superset list on what I think the PPMC's
next step should be.

> On Sep 1, 2018, at 11:11 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> I’m considering asking the podling to report monthly until this issue is 
> sorted. What do others think?
> 
> 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



Re: [RESULT][VOTE] Accept Marvin-AI into Apache Incubator

2018-08-28 Thread Jim Jagielski
uses
>>> VirtualBox and vagrant to non mac and Linux users;
>>> * marvin-ai/marvin-paper - Source code (latex format) of the first
>> Marvin
>>> paper published in PAPIS.io conference in Boston.
>>> * marvin-ai/marvin-cluster-admin - Admin module responsible to manage
>>> Marvin cluster;
>>> * marvin-ai/marvin-automl - AutoML module responsible to help data
>>> scientist to build machine learning models with a very simple visual
>>> interface;
>>> 
>>> 
>>> == External Dependencies ==
>>> 
>>> It is very likely that all our dependencies are using either the Apache
>> or
>>> MIT license. Upon acceptance to the incubator, we would begin a thorough
>>> analysis of all transitive dependencies to verify this fact and introduce
>>> license checking into the build and release process.
>>> 
>>> == Required Resources ==
>>> 
>>> === Mailing lists ===
>>> 
>>>  * priv...@marvin.incubator.apache.org (with moderated subscriptions)
>>>  * d...@marvin.incubator.apache.org
>>>  * comm...@marvin.incubator.apache.org
>>> 
>>> 
>>> === Git Repositories ===
>>> 
>>>  * https://git-wip-us.apache.org/repos/asf/incubator-marvin.git
>>> 
>>> === Issue Tracking ===
>>> 
>>>  * JIRA (MARVIN)
>>> 
>>> == Initial Committers ==
>>> 
>>> * Lucas Bonatto Miguel  - Qume Labs (California
>>> - USA)
>>> * Daniel Takabayashi  - B2W Digital (São
>>> Paulo - BR) / Laguro.com (California - USA)
>>> * Bruno Piraja  - B2W Digital (São Paulo -
>>> BR)
>>> * Zhang Yifei  - B2W Digital (São Paulo -
>> BR)
>>> * Harrison Wang  - MIT (USA)
>>> * Brody West  - MIT (USA)
>>> * Rafael Novello  - B2W Digital (São
>>> Paulo - BR)
>>> * Willian Leite  - CBYK (São Paulo - BR)
>>> * Danilo Nunes  - Qume Labs (California - USA)
>>> * Alan Silva  Cloudera (USA)
>>> * Jeremy Elster  - B2W Digital (São Paulo
>>> - BR)
>>> 
>>> 
>>> == Sponsors ==
>>> 
>>> === Champion ===
>>> 
>>> * Luciano Resende - (lresende)
>>> 
>>> === Nominated Mentors ===
>>> 
>>> * Luciano Resende - (lresende)
>>> * Jim Jagielski - (jim)
>>> * William Colen - (colen)
>>> 
>>> === Sponsoring Entity ===
>>> We would like to propose the Apache Incubator to sponsor this project.
>>> 
>>> 
>>> 
>> Vote has passed with 6 +1 binding votes
>> Dave Fisher
>> Jim Jagielski
>> William Colen
>> Luciano Resende
>> Matt Sicker
>> Willem Jiang
>> 
>> And 2 +1 non binding non binding votes from:
>> Tan Zhongyi
>> Vasas Szabolcs
>> 
>> 
>> Thanks for the time reviewing and voting on this proposal. I will start the
>> infra work slowly as I am on the road for the rest of the week.
>> 
>> 
>> --
>> Luciano Resende
>> http://twitter.com/lresende1975
>> http://lresende.blogspot.com/
>> 


-
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): wskdeploy module 0.9.8

2018-08-28 Thread Jim Jagielski
+1 (binding)

> On Aug 27, 2018, at 11:04 AM, Vincent S Hou  wrote:
> 
> Dear IPMC members,
> 
> This is a call for vote to release Apache OpenWhisk (Incubating): wskdeploy 
> module, Version 0.9.8.
> 
> The Apache OpenWhisk community has voted on and approved a proposal to 
> release Apache OpenWhisk (Incubating): wskdeploy, Version 0.9.8.
> 
> We now kindly request the Incubator PMC members to review and vote on this 
> incubator release.
> 
> Apache OpenWhisk Wskdeploy is a utility to help you describe and deploy any 
> part of the OpenWhisk programming model using a Manifest file written in YAML.
> 
> OpenWhisk Wskdeploy vote thread:
> https://lists.apache.org/thread.html/b2beb87458fca80d326725b8fb0e92d533f90b784f7c2cc5bbd84c31@%3Cdev.openwhisk.apache.org%3E
> 
> OpenWhisk Wskdeploy vote result thread:
> https://lists.apache.org/thread.html/caea29e3b3c8ea56f5bb3e40ee4b57153787ef193dc64ff63024230b@%3Cdev.openwhisk.apache.org%3E
> 
> This release comprises of source code distribution only.
> 
> The source code artifact of OpenWhisk Wskdeploy can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz
> 
> The SHA-512 checksum for OpenWhisk Wskdeploy is
> openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz: 
> B1979B93 573BB04B B495FA1A 8D0C1D93 ACD6371D 96BED392 A47D972C 6232AE41 
> 0E1FA1DF
> DB79D4AA B2D10F87 1942ED94 BF83A200 6D82EABB 2BCE951C 31B5A8D3
> 
> which can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-incubating-sources.tar.gz.sha512
> 
> The signature for OpenWhisk Wskdeploy can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.8-incubating-rc1/openwhisk-wskdeploy-0.9.8-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: wskdeploy request for a 
> release, so there is no file of CHANGELOG.
> 
> 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: general-h...@incubator.apache.org



Re: [VOTE] Accept Marvin-AI into Apache Incubator

2018-08-21 Thread Jim Jagielski
t; additional collaboration between these projects furthering the already
> existing integration points and expanding the community of contributors.
> 
> 
> == Known Risks ==
> 
> === Orphaned products ===
> 
> Given the current maturity of Marvin and how well it has been received at
> technical conferences, the risk of the project being abandoned is minimal.
> AI is not academia-exclusive anymore, and as enterprises start to add
> data-science pipelines to their applications, demand for Marvin will only
> increase.
> 
> === Inexperience with Open Source ===
> 
> Marvin AI has been an open-source project since October 2017. The project
> was started in a company where open-source culture is foundational. B2W
> Digital runs the largest e-commerce in Latin America on top of open-source
> projects.
> 
> === Reliance on Salaried Developers ===
> 
> Marvin AI receives substantial efforts from salaried developers -- a few of
> which were hired by companies to work exclusively for the project -- but
> the majority devote "after-hours" or spare time to this project. Some
> developers are graduate students that contribute in their free time at
> school.
> 
> === Relationships with Other Apache Products ===
> 
> Marvin integrates with several Apache products, such as Hadoop (HDFS) and
> Spark. Marvin shares some similar features with PredictionIO, specifically
> the model application server and a design pattern that was inspired by the
> DASE. Despite these similarities, Marvin is catered towards a different
> clientele (data scientists), and for that reason, it includes many critical
> features that are not provided by PredictionIO.
> 
> === An Excessive Fascination with the Apache Brand ===
> 
> While the ASF brand will undoubtedly help Marvin become a successful
> project, Marvin is already gaining traction at companies around the globe.
> 
> == Documentation ==
> 
> http://www.marvin-ai.org
> 
> 
> == Initial Source ==
> 
> The current codebase is available at http://github.com/marvin-ai. This is
> practically the same code that will be migrating to the Apache Foundation,
> the notable difference being that the multiple repositories will be merged
> into a single repository (if necessary).
> 
> These are the main repositories and a very simplified explanation about
> each one:
> 
> '''Main repositories'''
> 
> * marvin-ai/marvin-python-toolbox - Data Science toolbox that helps in the
> creation of new ML engines
> * marvin-ai/marvin-engine-executor - Component responsible for
> interpreting, serving and managing Marvin engines
> * marvin-ai/marvin-public-engines - Marvin engine examples to help new
> Marvin users to build engines
> * marvin-ai/marvin-platform-book - Documentation in GitHub book site format
> 
> '''Secondary repositories (Experimental and Initial)'''
> * marvin-ai/marvin-vagrant-dev - Development environment that uses
> VirtualBox and vagrant to non mac and Linux users;
> * marvin-ai/marvin-paper - Source code (latex format) of the first Marvin
> paper published in PAPIS.io conference in Boston.
> * marvin-ai/marvin-cluster-admin - Admin module responsible to manage
> Marvin cluster;
> * marvin-ai/marvin-automl - AutoML module responsible to help data
> scientist to build machine learning models with a very simple visual
> interface;
> 
> 
> == External Dependencies ==
> 
> It is very likely that all our dependencies are using either the Apache or
> MIT license. Upon acceptance to the incubator, we would begin a thorough
> analysis of all transitive dependencies to verify this fact and introduce
> license checking into the build and release process.
> 
> == Required Resources ==
> 
> === Mailing lists ===
> 
>  * priv...@marvin.incubator.apache.org (with moderated subscriptions)
>  * d...@marvin.incubator.apache.org
>  * comm...@marvin.incubator.apache.org
> 
> 
> === Git Repositories ===
> 
>  * https://git-wip-us.apache.org/repos/asf/incubator-marvin.git
> 
> === Issue Tracking ===
> 
>  * JIRA (MARVIN)
> 
> == Initial Committers ==
> 
> * Lucas Bonatto Miguel  - Qume Labs (California -
> USA)
> * Daniel Takabayashi  - B2W Digital (São
> Paulo - BR) / Laguro.com (California - USA)
> * Bruno Piraja  - B2W Digital (São Paulo - BR)
> * Zhang Yifei  - B2W Digital (São Paulo - BR)
> * Harrison Wang  - MIT (USA)
> * Brody West  - MIT (USA)
> * Rafael Novello  - B2W Digital (São Paulo
> - BR)
> * Willian Leite  - CBYK (São Paulo - BR)
> * Danilo Nunes  - Qume Labs (California - USA)
> * Alan Silva  Cloudera (USA)
> * Jeremy Elster  - B2W Digital (São Paulo -
> BR)
> 
> 
> == Sponsors ==
> 
> === Champion ===
> 
> * Luciano Resende - (lresende)
> 
> === Nominated Mentors ===
> 
> * Luciano Resende - (lresende)
> * Jim Jagielski - (jim)
> * William Colen - (colen)
> 
> === Sponsoring Entity ===
> We would like to propose the Apache Incubator to sponsor this project.
> 
> 
> -- 
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/


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



Re: [PROPOSAL] Zipkin for Apache Incubator

2018-08-20 Thread Jim Jagielski
That's boilerplate:

   https://incubator.apache.org/guides/proposal.html
   https://wiki.apache.org/incubator/ProjectProposals

> On Aug 17, 2018, at 9:58 AM, Kevin A. McGrail  wrote:
> 
> Have to say this made me chuckle:
> 
> 
>  A Excessive Fascination with the Apache Brand
> 
> I'm +1 on this proposal.


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



Re: [DISCUSS] Marvin-AI Incubator Proposal

2018-08-16 Thread Jim Jagielski
+1... please let me know if you want another mentor

> On Aug 15, 2018, at 3:13 PM, Luciano Resende  wrote:
> 
> We would like to start a discussion on accepting Marvin-AI as an Apache
> Incubator project.
> 
> The proposal is available at the incubator wiki, and also copied below:
> https://wiki.apache.org/incubator/Marvin-AI
> 
> As part of the initial due diligence, we have done a preliminary name
> search and the results are available on the JIRA below:
> 
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-144
> 
> We are also looking for two additional mentors.
> 
> 
> Thanks in advance for your time reviewing and providing feedback.
> 
> ===
> 
> = Marvin-AI =
> 
> == Abstract ==
> 
> Marvin-AI is an open-source artificial intelligence (AI) platform that
> helps data scientists, prototype and productionalize complex solutions with
> a scalable, low-latency, language-agnostic, and standardized architecture
> while simplifies the process of exploration and modeling.
> 
> == Proposal ==
> 
> Marvin helps non-experienced developers create industry-grade AI
> applications. It has three core components:  a development environment to
> be used during data exploration and hypothesis validation (Toolbox), a
> library which should be extended to create Marvin engines, and a Scala
> application server which interprets engines (Engine Executor).
> A basic premise of Marvin is that it should be language-agnostic, able to
> interpret engines implemented in different programming languages.
> 
> == Background ==
> 
> The Marvin AI project was initiated as an internal project at B2W Digital
> (Brazil), the largest e-commerce company in Latin America. Nowadays, it is
> used by all data scientists within the B2W team. Oftentimes, data
> scientists don't have an extensive background in software engineering, yet
> are in charge of creating AI applications that need to scale to high
> throughput and provide millisecond-level response times. At B2W, Marvin AI
> plays an important role in this process, abstracting advanced software
> engineering procedures, allowing data scientists to focus on their
> knowledge domain.
> 
> == Rationale ==
> 
> With recent advances in computer architecture and a corresponding increase
> in the amount of data generated by always-connected devices, AI algorithms
> offer a solution to problems that have long troubled modern corporations.
> Since AI developers come from various fields, such as statistics, physics,
> and math, there exists a strong need for platforms which enable them to
> move from prototypes to enterprise applications. Although some tools claim
> to offer this service, in reality, there is no reliable open-source
> solution.
> 
> == Initial Goals ==
> 
> The initial goals will most likely be to merge the existing codebase into a
> single repository, migrate it to Apache, and then integrate with the Apache
> development process. Furthermore, we plan for incremental development and
> releases, as per Apache guidelines.
> 
> == Current Status ==
> 
> === Meritocracy ===
> 
> Marvin already works under principles of meritocracy. Today, Marvin already
> has some contributors that are part of other institutions. Although there
> is no formal process defined to become a committer, contributors that make
> major changes/improvements to the platform are naturally granted write
> access to the repository.
> 
> 
> === Community ===
> 
> Acceptance into the Apache foundation would substantially boost both
> Marvin's user and developer communities. The current community includes a
> few experienced developers that have either academic or professional
> experience with AI. The community is largely comprised of data scientists
> working at B2W and other companies such as Cloudera, MIT, Qume Labs,
> Laguro.com, and CBYK. Also, there is a  meetup group of hundreds of users
> who meet regularly to exchange ideas about Marvin and, more generally, AI.
> 
> Reference to the group: https://www.meetup.com/marvin-ai/members/
> 
> === Core Developers ===
> 
> The core developers for Marvin are listed in the contributor's list and
> initial PPMC below. These lists include B2W employees, MIT students, UFSCAR
> researchers, independent contributors, and some employees of other
> companies like Cloudera, Qume Labs, Laguro.com, and CBYK.
> 
> === Alignment ===
> 
> The initial committers strongly believe that by being part of the Apache
> Software Foundation, Marvin AI will be part of a comprehensive suite for AI
> applications that can process big data and enable enterprises to extract
> value from their data lakes. Also, we hope that by integrating with other
> Apache projects such as Apache Spark, Apache Hadoop; that this will foster
> additional collaboration between these projects furthering the already
> existing integration points and expanding the community of contributors.
> 
> 
> == Known Risks ==
> 
> === Orphaned products ===
> 
> Given the current maturity of Marvin and how well it has 

Re: [VOTE] Release Apache OpenWhisk (Incubating): Client Go and CLI 0.9.0 [RC1]

2018-08-16 Thread Jim Jagielski
I've finally gotten a chance to review...

+1 (binding)!

> On Aug 13, 2018, at 11:22 AM, Vincent S Hou  wrote:
> 
> Dear IPMC members,
> 
> This is a call for vote to release Apache OpenWhisk (Incubating): Client Go 
> and CLI, Version 0.9.0.
> 
> The  Apache OpenWhisk community has voted on and approved a proposal to  
> release Apache OpenWhisk (Incubating): Client Go and CLI, Version 0.9.0.
> 
> We now kindly request the Incubator PMC members to review and vote on this 
> incubator release.
> 
> Apache OpenWhisk Client Go is a Go client library to access Openwhisk API.
> Apache OpenWhisk CLI is a command-line interface, based on Go client library, 
> to access Openwhisk API.
> 
> OpenWhisk Client Go and CLI vote thread:
> https://lists.apache.org/thread.html/da01355c62ec6aedf8cd049ad7449ebdc796528e9015fdb1220a19ad@%3Cdev.openwhisk.apache.org%3E
> 
> OpenWhisk Client Go and CLI vote result thread:
> https://lists.apache.org/thread.html/55f6a6e9218a21ad02c6a13624c368d78d40b68d22e1095543ffdd3c@%3Cdev.openwhisk.apache.org%3E
> 
> This release comprises of source code distribution only.
> 
> 
> For Client Go:
> The source code artifact of OpenWhisk Client Go can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz
> 
> The SHA-512 checksum for OpenWhisk Client Go is
> openwhisk-client-go-0.9.0-incubating-sources.tar.gz: 
> D5A69445 EF0082D7 B57FBDA4 13DCB591 0E06372F 0F308D2C 8FA49A80 F99FBF13 
> 6E299EBC
> CCF3722C 832492C4 215FB107 657EB521 0B72A364 9366F7CF 682DCA87
> 
> which can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.sha512
> 
> The signature for OpenWhisk Client Go can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-client-go-0.9.0-incubating-sources.tar.gz.asc
> 
> 
> For CLI:
> The source code artifact of OpenWhisk CLI can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz
> 
> The SHA-512 checksum for OpenWhisk CLI is:
> openwhisk-cli-0.9.0-incubating-sources.tar.gz: 
> F033568C 40286D74 CF6B6C5C 26470988 AD560DFA 39C1E521 34F96FF9 9FB86022 
> 5CB6700B
> 2862D2C8 35D5C407 F18F3AD0 5B0E26B8 F5178A0E 734C5EAE 763AEB18
> 
> which can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-0.9.0-incubating-sources.tar.gz.sha512
> 
> The signature for OpenWhisk CLI can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-cli-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: Client Go and CLI request for a 
> release, so there is no file of CHANGELOG.
> 
> The documentation can be found at:
> https://github.com/apache/incubator-openwhisk-release/blob/master/releases/0.9.0-incubating/INSTALL.md
>  or
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/doc/INSTALL.md
> 
> 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: general-h...@incubator.apache.org



Re: [VOTE] Pulsar Release 2.1.0-incubating Candidate 5

2018-07-31 Thread Jim Jagielski
+1 (binding) from me

> On Jul 30, 2018, at 11:24 AM, Sijie Guo  wrote:
> 
> Thank you Willem!
> 
> On Sun, Jul 29, 2018 at 5:45 PM Willem Jiang  wrote:
> 
>> Hi Sijie
>> 
>> I just have a quick question for the apache-pulsar-io-connectors-
>> 2.1.0-incubating-bin.tar.gz.
>> I guess the source is from apache-pulsar-2.1.0-incubating-src.tar.gz, but I
>> need to know how to build this artifact.
>> 
> 
> Ah, when you run "mvn clean install -Dmaven.gitcommitid.skip=true
> -DskipTests", the apache-pulsar-io-connectors-2.1.0-incubating-bin.tar.gz
> will be produced under `distribution/io/target` directory. This is the io
> binary bundle contains all the built-in connectors.
> 
>> 
>> BTW, it looks like the License of
>> apache-pulsar-io-connectors-2.1.0-incubating-bin.tar.gz
>> doesn't reflect the bundled third party dependencies.
>> 
> 
> We are using NIFI NAR plugin for packing io connector. for each connector,
> a META-INF/DEPENDENCIES file with licensing  information for all its
> transitive dependencies is bundled with each NAR package.
> 
> 
>> 
>> 
>> 
>> Willem Jiang
>> 
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>> On Thu, Jul 26, 2018 at 2:17 AM, Sijie Guo  wrote:
>> 
>>> This is the 5th release candidate for Apache Pulsar, version
>>> 2.1.0-incubating.
>>> 
>>> Link to the vote on dev@pulsar list:
>>> https://lists.apache.org/thread.html/9f1ec1266c02dde859d19e11a61416
>>> b3747eb4920d8bd8868dbb2988@%3Cdev.pulsar.apache.org%3E
>>> 
>>> 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
>>> and effective-once delivery of messages, automatic cursor management for
>>> subscribers, and geo-replication.
>>> 
>>> This is a feature release, introducing following new features:
>>> 
>>> - Pulsar I/O: a serverless connector framework built on top of Pulsar
>>> Functions.
>>> - TieredStorage: offloads bookkeeper ledgers to a cold storage (like S3).
>>> - Stateful Function: Pulsar Functions supports storing state back to
>>> bookkeeper.
>>> - Go Client: a Go client wrapping over existing cpp client.
>>> - Avro and Protobuf schema are supported.
>>> 
>>> Full list of changes and fixes are available:
>>> 
>>> https://github.com/apache/incubator-pulsar/milestone/13?closed=1
>>> 
>>> *** Please download, test and vote on this release. This vote will stay
>>> open
>>> for at least 72 hours ***
>>> 
>>> Note that we are voting upon the source (tag), binaries are provided for
>>> convenience.
>>> 
>>> Source and binary files:
>>> https://dist.apache.org/repos/dist/dev/incubator/pulsar/
>>> pulsar-2.1.0-incubating-candidate-5/
>>> 
>>> SHA-1 checksums:
>>> 
>>> f0f6b6d7c48d119da36fc4fa1f934fd1f9ba8498
>>> ./apache-pulsar-2.1.0-incubating-bin.tar.gz
>>> 
>>> b6a968249a7c5d21be89ece27895b862efda9a92
>>> ./apache-pulsar-2.1.0-incubating-src.tar.gz
>>> 
>>> ddcf929eb18082ff2b9979507054453e8e803ed3
>>> ./apache-pulsar-io-connectors-2.1.0-incubating-bin.tar.gz
>>> 
>>> 
>>> Maven staging repo:
>>> https://repository.apache.org/content/repositories/orgapachepulsar-1025/
>>> 
>>> The tag to be voted upon:
>>> v2.1.0-incubating-candidate-5 (75f79b77f55fbad351cb517e7f3b8ba4ab2dc177)
>>> https://github.com/apache/incubator-pulsar/releases/tag/
>>> v2.1.0-incubating-candidate-5
>>> 
>>> Pulsar's KEYS file containing PGP keys we use to sign the release:
>>> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
>>> 
>>> Please download the the source package, and follow the README to build
>>> and run the Pulsar standalone service.
>>> 
>>> A few notes for voting 2.1.0 release:
>>> 
>>> - For compiling source distribution, use "mvn clean install
>>> -Dmaven.gitcommitid.skip=true
>>> [-DskipTests]".
>>> - Starting from this release, Pulsar is shipping RPM & DEB packages for
>>> pulsar non-java clients.
>>> - Starting from this release, Pulsar is shipping a binary distribution
>>> called `apache-pulsar-io-connectors`
>>>  including all built-in connectors. Each connector is packaged with all
>>> their dependencies and
>>>  a META-INF/DEPEDENCIES file with licensing information for
>>> all dependencies.
>>> - Since there are a lot of features introduced in 2.1, You can use the
>>> instructions documented in the link for
>>>  validating the binary release candidate:
>>> https://github.com/apache/incubator-pulsar/wiki/Release-
>>> Candidate-Validation
>>> 
>>> - Sijie
>>> 
>> 


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



Re: [VOTE] Apache MXNet (incubating) 1.2.1 release RC1

2018-07-16 Thread Jim Jagielski
+1 (binding)

> On Jul 12, 2018, at 11:17 PM, Anirudh Subramanian  
> wrote:
> 
> Hi all,
> 
> This is a call for releasing Apache MXNet (incubating) 1.2.1, release
> candidate RC1.
> 
> Apache MXNet (incubating) community has voted and approved the release.
> 
> Vote thread:
> 
> https://lists.apache.org/thread.html/6a0459a54dd0b13fc89f653af91306810aa83d5d1a578a2abbac89fe@%3Cdev.mxnet.apache.org%3E
> 
> Results thread:
> 
> https://lists.apache.org/thread.html/94dfdc2cee82664a63a47d7ce0a011629903c5fca8ae96057974526f@%3Cdev.mxnet.apache.org%3E
> 
> Explanation for RC1:
> 
> https://lists.apache.org/thread.html/891c902c28251b0dbb90a64de086c8c5f02c22e070e58d55c923285d@%3Cdev.mxnet.apache.org%3E
> 
> The source tarball, including signatures, digests etc. can be found at:
> 
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.2.1.rc1/
> 
> The release tag can be found here:
> 
> https://github.com/apache/incubator-mxnet/releases/tag/1.2.1.rc1
> 
> The release hash is 106391a1f0ee012b1ea38764d711e76774ce77e1 and can be
> found here:
> 
> https://github.com/apache/incubator-mxnet/commit/106391a1f0ee012b1ea38764d711e76774ce77e1
> 
> Release artifacts are signed with the following key:
> 
> 0D04 3D0F 92CA 7333 22A8  D131 9067 CC8E AF55 CD6D
> 
> KEYS file available:
> 
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS
> 
> The vote will end at Monday July 16th, 8:10 PDT.
> 
> [ ] +1 Release this package as 1.2.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
> 
> Thanks,
> 
> Anirudh


-
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): main module 0.9.0 [RC2]

2018-07-16 Thread Jim Jagielski
+1 (binding) (if not too late :) )

> On Jul 11, 2018, at 10:38 AM, Vincent S Hou  wrote:
> 
> Dear IPMC members,
> 
> This is a call for vote to release Apache OpenWhisk (Incubating): main module 
> version 0.9.0.
> 
> The Apache OpenWhisk community has voted on and approved a proposal to 
> release Apache OpenWhisk (Incubating): main module version 0.9.0.
> 
> We now kindly request the Incubator PMC members to review and vote on this 
> incubator release.
> 
> Apache OpenWhisk (incubating) is a serverless, open source cloud platform 
> that executes functions in response to events at any scale.
> 
> OpenWhisk main module vote thread:
> https://lists.apache.org/thread.html/3d4952420a38936cbc6caeddf1979270f77469928e6092df84299ca1@%3Cdev.openwhisk.apache.org%3E
> 
> OpenWhisk main module vote result thread:
> https://lists.apache.org/thread.html/a825791284657c9860e0f63ec68f08d085da818e93cc14a6756273dc@%3Cdev.openwhisk.apache.org%3E
> 
> This release comprises of source code distribution only. There is one module 
> within this release. The artifact was built from the following Git commit ID:
> * openwhisk: b1476b9, add until for all ansible retries (#3806), 
> https://github.com/apache/incubator-openwhisk/commit/b1476b9992bab90c077ac2f1fbdc67d10d9d2c39
> It will be tagged with the version.
> 
> The source code artifacts can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz
> 
> The SHA-512 checksum for each artifact can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.sha512
> 
> The signature of this artifact can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/openwhisk-0.9.0-incubating-sources.tar.gz.asc
> 
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/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: main module requests for a 
> release, so there is no file of CHANGELOG.
> 
> The documentation can be found at:
> https://github.com/apache/incubator-openwhisk-release/blob/master/releases/0.9.0-incubating/INSTALL.md
>  or
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc2/doc/INSTALL.md
> 
> 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
> 
> Apache OpenWhisk team
> 
> 
> -
> 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] Apache Gobblin 0.12.0 release RC3

2018-07-02 Thread Jim Jagielski
Just got back from a week+ in Scotland... sorry for the delay.

+1 (binding) from me.

> On Jul 1, 2018, at 1:18 PM, Abhishek Tiwari  wrote:
> 
> We are still looking for 1 more +1, will really appreciate it if anyone can
> spare sometime to review and vote :)
> 
> Abhishek
> 
> On Sun, Jul 1, 2018 at 6:41 AM Abhishek Tiwari  wrote:
> 
>> Thanks Justin. I will remove the md5.
>> 
>> Abhishek
>> 
>> On Sun, Jul 1, 2018 at 3:02 AM Justin Mclean 
>> wrote:
>> 
>>> Hi,
>>> 
>>> +1 (binding)
>>> 
>>> Please remove the md5 hash from the release area before releasing as
>>> these should not longer be used.
>>> 
>>> I checked:
>>> - incubating in artefacts name
>>> - signatures ands hashes correct
>>> - DISCLAIMER exists
>>> - LICENSE is missing a license
>>> - NOTICE is correct
>>> - Source file have headers, but there a few shell scripts missing them
>>> [1][2][3][4][5]
>>> - can compile from source
>>> 
>>> LICENSE is missing license for the glyphicons-halflings font. [6]
>>> 
>>> Thanks,
>>> Justin
>>> 
>>> 1. apache-gobblin-incubating-sources-0.12.0/bin/gobblin-cluster-worker.sh
>>> 2. apache-gobblin-incubating-sources-0.12.0/bin/gobblin-service.sh
>>> 3. apache-gobblin-incubating-sources-0.12.0/bin/gobblin-cluster-master.sh
>>> 4.
>>> apache-gobblin-incubating-sources-0.12.0/gobblin-aws/src/test/resources/workerCloudInit.sh
>>> 5.
>>> apache-gobblin-incubating-sources-0.12.0/gobblin-aws/src/test/resources/masterCloudInit.sh
>>> 6.
>>> apache-gobblin-incubating-sources-0.12.0/gobblin-admin/src/main/resources/static/fonts/glyphicons-halflings-regular.*
>>> -
>>> 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: Welcome to Apache MXNet

2018-06-17 Thread Jim Jagielski
It is my pleasure to (re)join the PPMC!!

Thanks! I whole-heartedly accept.

> On Jun 16, 2018, at 7:35 PM, Naveen Swamy  wrote:
> 
> Hello Jim,
> 
> It was great meeting you in FOSS backstage and thank for your offer to mentor 
> the project.  We discussed within the MXNet ppmc and would love to accept 
> your offer to mentor our project. 
> 
> Your vast experience in building open source projects and communities around 
> it will be very helpful to grow our project and work towards graduation, we 
> look forward to learning from you.
> 
> To give you a brief background of MXNet:
> MXNet was a research project driven by PhD students from CMU, UW, NYU and 
> professionals working in many other organizations under the DMLC umbrella. In 
> mid 2016 some of the contributors joined Amazon and continued to contribute 
> to MXNet. In Jan-2017 a proposal was made to Incubate at Apache, Amazon was 
> supportive of this initiative and has been contributing in terms of code and 
> documentation and also partnering with other organizations such as Nvidia and 
> Intel to further advance MXNet.
> (request ppmc members to fix/fill in any details that I might have missed.)
> 
> Welcome to MXNet!.
> 
> Thanks, Naveen
> 
> 
>  
> 
> 
> 



Re: [VOTE] Pulsar Release 2.0.1-incubating Candidate 2

2018-06-17 Thread Jim Jagielski
Sorry for the delay... been traveling.

+1 (binding)

> On Jun 11, 2018, at 6:00 PM, Matteo Merli  wrote:
> 
> This is the second release candidate for Apache Pulsar, version
> 2.0.1-incubating.
> 
> Link to the vote on dev@pulsar list
> https://lists.apache.org/thread.html/620813d66d43a43680d3afd587e72f0d6f9607f1566aa88ef73d359c@%3Cdev.pulsar.apache.org%3E
> 
> 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 geo-replication.
> 
> This is a patch release that fixes few issues identified in previous
> release 2.0.0-rc1-incubating.
> 
> It fixes the following issues:
> https://github.com/apache/incubator-pulsar/milestone/14?closed=1
> 
> *** Please download, test and vote on this release. This vote will stay
> open
> for at least 72 hours ***
> 
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
> 
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-2.0.1-incubating-candidate-2/
> 
> SHA-1 checksums:
> 
> 5acd63f8aa1fa75f386df7b9fd803a943978e609
> apache-pulsar-2.0.1-incubating-bin.tar.gz
> 312bc0f1ae170c1d2dc38b1e362fb50f82c00525
> apache-pulsar-2.0.1-incubating-src.tar.gz
> 
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1020
> 
> 
> The tag to be voted upon:
> v2.0.1-incubating-candidate-2 (fd47532380d770e4fd78cabe71dea293fc2f0e06)
> https://github.com/apache/incubator-pulsar/releases/tag/v2.0.1-incubating-candidate-2
> 
> 
> Pulsar's KEYS file containing PGP keys we use to sign the release:
> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> 
> Please download the the source package, and follow the README to build
> and run the Pulsar standalone service.
> -- 
> Matteo Merli
> 


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



Re: [VOTE] Pulsar Release 1.22.1-incubating Candidate 2

2018-06-11 Thread Jim Jagielski
+1 (if not too late) - binding

> On Jun 7, 2018, at 2:29 PM, Jai Asher  wrote:
> 
> This is the second release candidate for Apache Pulsar, patch release
> version 1.22.1-incubating.
> 
> It fixes the following issues:
> https://github.com/apache/incubator-pulsar/milestone/15?closed=1
> 
> *** Please download, test and vote on this release. This vote will stay
> open for at least 72 hours ***
> 
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
> 
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-1.22.1-incubating-candidate-2/
> 
> SHA-1 checksums:
> 
> f2d29aa5e046c5bdefd8f466bce8e9ead80a2e09
> apache-pulsar-1.22.1-incubating-src.tar.gz
> f2704cae22b7fb3c1b72daab6ebe7d484fdfec6b
> apache-pulsar-1.22.1-incubating-bin.tar.gz
> 
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1018/
> 
> The tag to be voted upon:
> v1.22.1-incubating-candidate-2 (c9a369936af3b3ecc663b86ae959a3fbfa627aca)
> https://github.com/apache/incubator-pulsar/releases/tag/v1.22.1-incubating-candidate-2
> 
> Pulsar's KEYS file containing PGP keys we use to sign the release:
> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
> 
> Please download the source package, and follow the README to build and run
> the Pulsar standalone service.


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



Re: [DISCUSS] IP Clearance

2018-06-05 Thread Jim Jagielski



> On Jun 5, 2018, at 4:53 AM, Bertrand Delacretaz  
> wrote:
> 
> On Mon, Jun 4, 2018 at 9:30 PM, Jim Jagielski  wrote:
>> ...In other words, unless the code is for a podling, the IPMC shouldn't be 
>> involved, IMHO
> 
> But it's good to have a central place to record those IP clearances, IMO.
> 

Since it's a foundation record, that should be the secretary's job, I think. 
That is, the responsible PMC does the IP clearance and then submits that 
info/record to the ASF secretary for filing.


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



Re: [DISCUSS] IP Clearance

2018-06-04 Thread Jim Jagielski
I can see the IPMC being responsible for IP clearance for new incoming podlings 
and current podlings.

For code being donated directly to a current TLP, they should be able to do all 
that is required to ensure correct clearance and provenance.

In other words, unless the code is for a podling, the IPMC shouldn't be 
involved, IMHO.

> On Jun 4, 2018, at 1:46 PM, Dave Fisher  wrote:
> 
> Hi -
> 
> I think that the IP Clearance process has become very much a bureaucratic 
> process where the IPMC is contributing little of value. Very seldom is there 
> any feedback provided.
> 
> (1) It is separate from the SGA process for new podlings, but it is similar 
> in that the Secretary will record the SGA and/or CCLA.
> (2) The documentation is confusing about whether or not podlings need to 
> follow it or not.
> (3) Top Level Projects are supposed to understand how to clear IP as that is 
> a major part of the incubation process. If there are any questions the 
> legal-discuss mailing list and JIRA are available.
> (4) The Incubator is already stretched to provide Mentoring to all of our 
> Podlings and IP Clearance seems to be off topic and not really scalable.
> (5) Once a TLP graduates from the Incubator it seems regressive to have to go 
> back unless there is a Community around the grant to be Incubated. That would 
> lead to a Podling Proposal and not IP Clearance.
> 
> I think that the IPMC should recommend to the Board that this recording 
> process be fully moved to the Secretary.
> 
> Regards,
> Dave


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



Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

2018-05-14 Thread Jim Jagielski
If it is part of a releasable artifact, then source needs to be provided.

> On May 14, 2018, at 2:16 PM, Sijie Guo  wrote:
> 
> On Mon, May 14, 2018 at 10:53 AM, Matt Sicker  wrote:
> 
>> I'm not sure about a specific policy, but sources by definition aren't the
>> binaries. Sources combine with a tool or tools to create binaries.
>> 
> 
> Okay. But this is a test "resource" used by other sources on testing.
> 
> Image you are writing an image processing library, you include some
> "images" for testing the library. Is it allowed to include those "images"
> in the source release?
> 
> If you change "image" to "functions", pulsar-functions provides a
> framework/library for processing functions, we include some user-defined
> "functions" (aka jars) as test resources for testing the library. Is it
> allowed or not?
> 
> From what I can see here, the jars included in source binary are test
> resources for testing. What is the ASF policy for handling test resources?
> 
> 
> - Sijie
> 
> 
> 
> 
>> 
>> On 14 May 2018 at 12:41, Sijie Guo  wrote:
>> 
>>> On Sat, May 12, 2018 at 3:52 PM, Justin Mclean >> 
>>> wrote:
>>> 
 Hi,
 
 Sorry but it’s -1 binding due to compiled code in source release.
 
>>> 
>>> 
>>> Can anyone point me the ASF policy page about this - "compiled code in
>>> source release"?
>>> 
>>> 
 
 Frankly I’m surprised to see so many +1s with this obvious issue.
 
 I checked:
 - incubating in name
 - signatures and hashes correct
 - DISCLAIMER exists
 - LICENSE and NOTICE good
 - Unexpected jar in source release [1]
 - All source files have headers
 
 Thanks,
 Justin
 
 
 1.  pulsar-functions/utils/src/test/resources/multifunction.jar
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
>>> 
>> 
>> 
>> 
>> --
>> Matt Sicker 
>> 


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



Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

2018-05-12 Thread Jim Jagielski
+1 (binding)

> On May 11, 2018, at 7:09 PM, Matteo Merli  wrote:
> 
> This is the third release candidate for Apache Pulsar, version
> 2.0.0-rc1-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 geo-replication.
> 
> Link to the voting thread on pulsar dev list:
> https://lists.apache.org/thread.html/79e78ddc1e1348b8a625e6dcc485cdbb145030fa6546546149d6b1a4@%3Cdev.pulsar.apache.org%3E
> 
> It fixes the following issues:
> https://github.com/apache/incubator-pulsar/milestone/12?closed=1
> 
> *** Please download, test and vote on this release. This vote will stay open
> for at least 72 hours ***
> 
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
> 
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-2.0.0-rc1-incubating-candidate-3/
> 
> SHA-1 checksums:
> b1a392c5935448da195eb927520fe6deb20182fc
> apache-pulsar-2.0.0-rc1-incubating-bin.tar.gz
> 8c547a3e0afaee3446c770c076d5803e7e7da1c2
> apache-pulsar-2.0.0-rc1-incubating-src.tar.gz
> 
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1013/
> 
> The tag to be voted upon:
> v2.0.0-rc1-incubating-candidate-3 (9b33a8788f171f98528aeaa9040d16fc702404ef)
> https://github.com/apache/incubator-pulsar/releases/tag/v2.0.0-rc1-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
> 
> Please download the the source package, and follow the README to build
> and run the Pulsar standalone service.
> 
> -- 
> Matteo Merli
> 
> -- 
> Matteo Merli
> 


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



Re: [VOTE] Graduate Traffic Control to a top level project

2018-04-23 Thread Jim Jagielski
+1 (binding)

> On Apr 20, 2018, at 2:02 PM, Dave Neuman  wrote:
> 
> Hello IPMC,
> The Traffic Control PMC would like to call a vote to graduate from the
> incubator to a top level Apache project!  The traffic control community has
> voted to graduate [1], voted on our resolution [2], and opened a thread to
> discuss our resolution on this list [3].
> 
> Traffic Control entered the incubator on July 12, 2016.  Since then we have
> announced 4 releases, nominated 4 new committers, organized 4 summits, had
> more than 8,000 commits from 63 different contributors, and -- most
> importantly -- we have grown and diversified our community.  Apache Traffic
> Control is a healthy project that is already acting like an Apache top
> level project, and we are ready to take the next step.
> 
> I would like to ask that you please take a moment to vote on our
> resolution.  Please respond with one of the following:
> 
> [ ] +1 Graduate Traffic Control from the incubator
> [ ] +0 No Opinion
> [ ] -1 Do not graduate Traffic Control from the incubator (please provide a
> reason)
> 


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



Re: The role of a mentor

2018-04-10 Thread Jim Jagielski
+1

> On Apr 9, 2018, at 12:45 PM, Julian Hyde  wrote:
> 
> Has anyone here taught someone how to fish? (Or how to make cookies, or ski?)
> 
> Mostly you just stand off, watching what they do. If you see them about to 
> screw up in a big way, step in. Occasionally, offer them hints for how they 
> might do what they’re doing a little bit better. (Not too often, because 
> they’ll start to resent the advice.)
> 
> It’s a time-intensive process, and most of the time the person being taught 
> thinks you’re doing nothing.
> 
> Sometimes they ask for help, and very occasionally they ask for guidance (but 
> only if you have not given them more unsolicited advice than they think they 
> need, see above).
> 
> Julian
> 
> 
>> On Apr 9, 2018, at 5:52 AM, Liang Chen > > wrote:
>> 
>> Hi
>> 
>> +1, agree with JB points.
>> Mentor mostly just focus on ASF policy and rules, then is ok. 
>> "Teach him how to fish", it is more important, so it would be better if
>> mentors could provide some good example cases(role model) for them to learn,
>> tell them how to find the solution from ASF website.
>> 
>> Regards
>> Liang
>> 
>> Jean-Baptiste Onofré wrote
>>> Hi John,
>>> 
>>> IMHO, a mentor is not necessary involved in the project technics/codebase
>>> (it's
>>> actually a bonus).
>>> 
>>> As a mentor, I'm focusing:
>>> 1. Insure of the legal aspect of the project (ICLA/CCLA, SGA, ...)
>>> 2. Help around infra and release preparation according to Apache rules
>>> 3. Help to promote the project and build communities around
>>> 4. See if there's potential interaction with other podlings and existing
>>> TLPs
>>> 5. Help to go to graduation (following the graduation checklist)
>>> 6. (optional) Help on the contribution (codebase, website, ...)
>>> 
>>> My $0.01
>>> 
>>> Regards
>>> JB
>>> 
>>> On 04/03/2018 12:54 AM, John D. Ament wrote:
 I've been following along the absent mentors discussion.  But I'm
 curious,
 from both an IPMC member's perspective as well as a member of a podling,
 what roles do you see for a mentor?  What are their responsibilities to
 the
 podling?
 
 We have a few things written down, and I'm not too interested in
 rehashing
 the written version.  But what do podlings need from their mentors? 
 Point
 you in a direction to run with?  Do the apache work for the podling?  Do
 we
 (the ASF) need mentors to ensure that podlings are operating within
 certain
 bounds?  Do we rely on mentors to be a read of the pulse of a podling?
 
 John
 
>>> 
>>> -- 
>>> Jean-Baptiste Onofré
>> 
>>> jbonofre@
>> 
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>> 
>>> -
>>> To unsubscribe, e-mail: 
>> 
>>> general-unsubscribe@.apache
>> 
>>> For additional commands, e-mail: 
>> 
>>> general-help@.apache
>> 
>> 
>> 
>> 
>> 
>> --
>> Sent from: http://apache-incubator-general.996316.n3.nabble.com/ 
>>  
>> > >
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org 
>>  
>> > >
>> For additional commands, e-mail: general-h...@incubator.apache.org 
>>  
>> > >



Re: [VOTE] Apache Gobblin 0.12.0 release RC2

2018-04-02 Thread Jim Jagielski
First of all, one cannot "veto" a release, so a -1 vote on a release
is not, really, a blocker. One can still do the release; but it does
indicate a lack of consensus within the (P)PMC that the release
is in a "releasable" state.

> On Apr 1, 2018, at 7:19 PM, Abhishek Tiwari  wrote:
> 
> Although the vote is over and successful, at this point I think I will just
> update the NOTICE file and bring in another RC for vote.
> 
> However, I am puzzled that this improvement (not blocker) is attracting -1
> votes. I would have expected +1 or 0 with improvement suggestion,
> specifically because I see that this is a very common pattern in many if
> not most of the major Apache TLP projects.
> The two entries in our NOTICE file is for: bootstrap and Glyphicon icons.
> And, for exactly the same included bits, here are the NOTICE files for a
> few other major TLPs:
> Apache Hadoop: https://github.com/apache/hadoop/blob/trunk/NOTICE.txt
> 
> 
> Apache HBase: https://github.com/apache/hbase/blob/master/NOTICE.txt
> 
> 
> Apache Ambari: https://github.com/apache/ambari/blob/trunk/
> ambari-web/app/assets/licenses/NOTICE.txt
> 
> 
> Apache Spark: https://github.com/apache/spark/blob/master/NOTICE
> 
> 
> .. there are many more, but I stopped at these.
> 
> So, isn't enforcing improvements on podling not harsh when it does not
> attracts -1 or blocks releases for other Apache TLP releases?
> 
> Abhishek
> 
> On Sun, Apr 1, 2018 at 3:12 PM, Justin Mclean 
> wrote:
> 
>> Hi,
>> 
>> It's hard to come up with a single simple sentence that applies in all
>> cases. So when I said "if something is bundled then it's license and
>> copyright needs to be in LICENSE not NOTICE.” I’m wrong as it's not going
>> to all cover all cases.
>> 
>> For bundling Apache licensed (v2) bits of software the copyright isn’t in
>> the license. If the software has a NOTICE file then that is very likely
>> going to effect your NOTICE file - which I think what Sebb was getting at
>> and this is certainly the most common situation.
>> 
>> In general other permissive licenses (like MIT and BSD) include a
>> copyright line in the license text and theres’s no need to include anything
>> in NOTICE.
>> 
>> Then we come to required notices which are going to be uncommon. The
>> licenses with required notices (ignoring ALv2) that I know of are the BSD
>> with advertising clause (Category X), CDDL (list of modifications and how
>> to get source) and MPL (info how to get source code) which are both
>> Category B. None of these would be bundled in a source release (but may
>> affect a binary one). I can’t think of any category A license which has a
>> required notices. Does anyone know of one?
>> 
>> 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



Re: [VOTE] Apache Gobblin 0.12.0 release RC2

2018-04-01 Thread Jim Jagielski


> On Apr 1, 2018, at 10:48 AM, sebb  wrote:
> 
> 
> I don't think that is true; I think bundled bits can affect the NOTICE
> file (albeit perhaps rarely).

That is my position as well, fwiw.

Re: [VOTE] Apache Gobblin 0.12.0 release RC2

2018-04-01 Thread Jim Jagielski


> On Apr 1, 2018, at 9:35 AM, sebb  wrote:
> 
> 
> If bundled bits never affect the NOTICE file, why is there a concern
> about minimising the NOTICE contents?
> 

Let's consider the "touch points" between what we release and
the downstream user and consumer eco-system. For these
entities, the 3 "main" files that affect what they can do, as well
as information that is of primary importance that determines
their responsibilities are the README, LICENSE and NOTICE
files:

  o README: because it is the main communication channel between
the project and downstream
  o LICENSE: because it provides the distribution requirements
and conditions
  o NOTICE: because it provides the addition information that
is required to be maintained and "transparent" for the
downstream

In many ways, NOTICE is extra data that must be included
for all subsequent downstream and distros and, therefore,
should include only what MUST be folded into the file. That's
why it is defined as such ("... and nothing more"). We want
to minimize extraneous work and efforts required for downstreams
in order to make the use and consumption of Apache code and
projects as easy as possible. A bloated NOTICE with lots
of duplicate information unnecessarily adds addition workload
and, esp, oversight.


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



Re: [DISCUSS] Absent mentors

2018-04-01 Thread Jim Jagielski
Would it be possible to generate a short list of all current
mentors for all current podlings to see how many podlings
each mentor is signed up for? That would be a good metric
to know.

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



Re: [VOTE] Apache Gobblin 0.12.0 release RC2

2018-04-01 Thread Jim Jagielski
I am also going to vote -1 for the same reason. It seems to me that
simply fixing this issue is all that's required for a successful RC3 and GA.

> On Mar 31, 2018, at 7:08 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> -1 binding as NOTICE should not contain copyrights of bundled 3rd party 
> software. The NOTICE file needs to only contain what is required  (and not 
> already in LICENSE) and needs to be as small as possible as it affects 
> downstream projects. [2]
> 
> I checked:
> - incubating in name
> - signatures and hashes good
> - DISCLAIMER exists
> - LICENSE is missing info for fonts [1]
> - NOTICE is incorrect
> - Some .sh files are missing ASF headers
> - Can compile from source
> 
> Thanks,
> Justin
> 
> 1. 
> apache-gobblin-incubating-sources-0.12.0/gobblin-admin/src/main/resources/static/fonts/*
> 2. http://www.apache.org/dev/licensing-howto.html#mod-notice
> 
> 
> 
> -
> 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



  1   2   3   4   5   6   7   8   >