Re: [VOTE] Accept DistributedLog into the Apache Incubator

+1 From: Sijie Guo > Date: Mon, Jun 20, 2016 at 10:11 PM > Subject: [VOTE] Accept DistributedLog into the Apache Incubator > To: general@incubator.apache.org > > > Hello All, > > Following the discussion thread, I would like to call a VOTE on accepting > DistributedLog into the

[VOTE] Accept DistributedLog into the Apache Incubator

Hello All, Following the discussion thread, I would like to call a VOTE on accepting DistributedLog into the Apache Incubator. [] +1 Accept DistributedLog into the Apache Incubator [] +0 Abstain. [] -1 Do not accept DistributedLog into the Apache Incubator because ... This vote will be open for

Re: Trafodion podling needs more mentors

Dave, Thanks for clarifying. I'm glad its these two items, as I would have been worried if there were others. 1. Ideally, the PPMC should be able to vet the release. You're pretty close, but you want to get to the day where you have 0 issues found during an incubating release. Realistically,

RE: Trafodion podling needs more mentors

At the moment, mainly two things: 1. Release validation 2. Occasional administrative items associated with adding new committers and/or podling PMC members -Original Message- From: John D. Ament [mailto:johndam...@apache.org] Sent: Monday, June 20, 2016 5:43 PM To:

Re: Trafodion podling needs more mentors

Also, could you please expound on what you are reliant on St.Ack on? On Mon, Jun 20, 2016 at 8:34 PM Roman Shaposhnik wrote: > Help me understand, why is this a mentor issue and not IPMC one? > > Thanks, > Roman. > > On Fri, Jun 17, 2016 at 6:38 PM, Atanu Mishra

Re: Trafodion podling needs more mentors

Help me understand, why is this a mentor issue and not IPMC one? Thanks, Roman. On Fri, Jun 17, 2016 at 6:38 PM, Atanu Mishra wrote: > Response below. > > On Fri, Jun 17, 2016 at 4:58 PM, Roman Shaposhnik > wrote: > >> On Wed, Jun 15, 2016 at 4:05

Re: Request to review updated License (Re: [VOTE] Release Apache Ranger 0.5.3 (incubating))

Hi, > LICENSE is missing reset.css. (7) Note this version bundled may not be public > domain unlike this one (8) so you may need to sort that out. This is still an issue as far as I can tell. The code in question doesn't have a license. I’d contact the author to conform or replace with a

Re: [DISCUSS] Juneau Incubation Proposal

On Thu, Jun 16, 2016 at 5:52 PM, James Bognar wrote: > Hi all, > > I'd like to propose Juneau to be an Apache Incubator project. > > Juneau is a toolkit for marshalling POJOs to a wide variety of content > types using a common framework, and for creating

Re: [DISCUSS] Juneau Incubation Proposal

I think we should plan to start a vote on this. Anyone see a reason not to? Thank you for those who have looked. i was able to replicate the issue Dennis mentioned with the download, will need to look though I suspect it may be an upstream issue. Also thank you kindly to Craig for stepping up

Re: Request to review updated License (Re: [VOTE] Release Apache Ranger 0.5.3 (incubating))

Hi, > Generally speaking, we only need to include the licenses for the > dependencies, not a notice that the dependency is contained. My understanding is that on things that are bundled need to be mentioned. [1] (and all the things mentioned in that license are bundled). There no need to

Re: Request to review updated License (Re: [VOTE] Release Apache Ranger 0.5.3 (incubating))

Velmurugan, I just want to make sure you understand... the comments are around compatible licenses, not specifically the jquery license. This was one that I grabbed as the first instance I saw. To point out, if for some reason these files were not in the source release (e.g. they're used on

Re: Request to review updated License (Re: [VOTE] Release Apache Ranger 0.5.3 (incubating))

Hi, > I would like to get your feedback on updated LICENSE.txt for Ranger. > https://github.com/apache/incubator-ranger/blob/master/LICENSE.txt Has the full text of each license been placed somewhere? Most permissive license (e.g. MIT, BSD) require you to do that, often the legal requirement

Re: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

Hi, > This is how it was suggested to us by our mentors; but we're open for > improvements Not it any way an issue, it’s just a bit more verbose that notice NOTICE files I’ve seen. > But is "Public Domain" valid outside US? Should we append ASF headers > on it? (That should be allowed if it's

Re: Request to review updated License (Re: [VOTE] Release Apache Ranger 0.5.3 (incubating))

Thank you. I will fix the line format (i.e. to include only jQuery license and link). Any other concerns? On Jun 20, 2016, at 4:01 PM, John D. Ament wrote: > On Mon, Jun 20, 2016 at 3:31 PM Alex Harui wrote: > >> IMO,

Re: Request to review updated License (Re: [VOTE] Release Apache Ranger 0.5.3 (incubating))

On Mon, Jun 20, 2016 at 3:31 PM Alex Harui wrote: > IMO, http://www.apache.org/dev/licensing-howto.html#permissive-deps > says the blurb about JQuery goes in LICENSE, not NOTICE. > Yes, sorry, I should have been clearer about that. I was referring to the line format, not the

Re: Request to review updated License (Re: [VOTE] Release Apache Ranger 0.5.3 (incubating))

IMO, http://www.apache.org/dev/licensing-howto.html#permissive-deps says the blurb about JQuery goes in LICENSE, not NOTICE. On 6/20/16, 12:14 PM, "John D. Ament" wrote: >Lines like this are contents for the notice file, not license file: > > >This product includes

Re: Request to review updated License (Re: [VOTE] Release Apache Ranger 0.5.3 (incubating))

Lines like this are contents for the notice file, not license file: This product includes jQuery (http://jquery.org - MIT license), Copyright © 2014, John Resig. license file should include the various licenses covering these works. On Mon, Jun 20, 2016 at 3:07 PM Velmurugan Periasamy

Request to review updated License (Re: [VOTE] Release Apache Ranger 0.5.3 (incubating))

Hi Justin: I would like to get your feedback on updated LICENSE.txt for Ranger. https://github.com/apache/incubator-ranger/blob/master/LICENSE.txt Please see below answers to your questions. Ranger dev community is getting prepared for the next major release, so getting your feedback and

[RESULT] [VOTE] Release Apache Myriad 0.2.0 (incubating)

The vote passed with 3 +1 binding votes from IPMC members and no -1s. +1 binding votes: Justin Mclean Drew Farris John Ament We will proceed with the post release activities: - Make the release artifacts available from [1] and [2] - github tag with "myriad-0.2.0-incubating" - Close the

Re: [DISCUSS] Juneau Incubation Proposal

On Mon, Jun 20, 2016 at 4:27 PM, James Bognar wrote: > @Stian, > > I've removed references to "Apache" from the temp site and removing all > links to the GitHub repo. The only thing I can't change is the google site > URL https://sites.google.com/site/apachejuneau/.

Re: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

On 20 June 2016 at 16:31, Donal Fellows wrote: >> But is "Public Domain" valid outside US? Should we append ASF headers > on it? (That should be allowed if it's PD.. at least if that is done > by an USAnian) > It certainly isn't on some jurisdictions (Germany is

Re: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

Stian Soiland-Reyes wrote: > But is "Public Domain" valid outside US? Should we append ASF headers on it? (That should be allowed if it's PD.. at least if that is done by an USAnian) It certainly isn't on some jurisdictions (Germany is the most notable one) but I would expect

Re: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

On 20 June 2016 at 12:24, Sergio Fernández wrote: > +1 (binding) Thanks! Much appreciated! > Non-blocking details I noticed (should be fixed in the next releases): > * The three artifacts are related with each other, so I'd include some > extra build information about the

Re: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

On 18 June 2016 at 01:50, Justin Mclean wrote: > Hi, > > +1 (binding). Can you fix the LICENSE and NOTICE issues in the next release > please. Thank you - already fixed in master. Getting smarter every day.. > I can help by reviewing the release but I’m at my limit

Re: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

HI, > I would think this means that the taverna-execution-hadoop.jar file > (which is distributed in Maven Central) must include the full notice > "somewhere”, Yes, it's normally it in a header of a file somewhere in a source release. That’s why it best to put it somewhere and add a pointer to

Re: [DISCUSS] Juneau Incubation Proposal

@Stian, I've removed references to "Apache" from the temp site and removing all links to the GitHub repo. The only thing I can't change is the google site URL https://sites.google.com/site/apachejuneau/. Hopefully this is okay until I can delete the site once Incubation is approved? On Sun,

Re: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

On 20 June 2016 at 12:49, Justin Mclean wrote: >> license text should go in the LICENSE files, while NOTICE should just >> contain a brief enumeration with some details (file/s, copyright holder, >> license name and original source) about the third-party source

Re: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

On Mon, Jun 20, 2016 at 1:49 PM, Justin Mclean wrote: > > > license text should go in the LICENSE files, while NOTICE should just > > contain a brief enumeration with some details (file/s, copyright holder, > > license name and original source) about the third-party

Re: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

Hi, > license text should go in the LICENSE files, while NOTICE should just > contain a brief enumeration with some details (file/s, copyright holder, > license name and original source) about the third-party source components > included. Agree but just to make clear NOTICE should usually not

Re: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

+1 (binding) So far I've checked: signatures and digests, source releases file layouts, matched git tags and commit ids, incubator suffix and disclaimer, NOTICE and LICENSE files, license headers, build sources in a clean environment (Maven 3.3.9, OpenJDK 1.8.0_91 64-Bit, Debian amd64).