Re: Help from Mentors

2016-04-08 Thread Gino Bustelo
We are correcting our LICENSE bundling to mirror what you've sent. Now, on NOTICE file, we are going by the statement at http://www.apache.org/dev/licensing-howto.html#mod-notice >However, elements such as the copyright notifications embedded within BSD and MIT licenses need not be duplicated in

Re: Help from Mentors

2016-04-08 Thread Hitesh Shah
Another useful doc which was being worked on as part of Kudu going through the same pains of its first release: https://docs.google.com/document/d/1eftfjrWpOG-dRkw9dZWRfcj3p_qCeE5xC-G0Y5j29Ck/edit — Hitesh On Apr 8, 2016, at 9:03 AM, Gino Bustelo wrote: > I'm reading https://github.com/zeromq/

Re: Help from Mentors

2016-04-08 Thread Hitesh Shah
Thats actually required for any bundled dependency that has a non ALv2 license even the permissible ones such as BSD, MIT, etc ( not only LGPL ones ). The top-level license file is meant to call out the licenses for all the things that are being bundled. To summarize for the license files - de

Re: Help from Mentors

2016-04-08 Thread Gino Bustelo
I'm reading https://github.com/zeromq/jeromq/blob/master/COPYING.LESSER#L91 and seems to me that we need to ship our bin distros with copies of the LGPL license. What is you all read? On Thu, Apr 7, 2016 at 6:00 PM, Gino Bustelo wrote: > @hitesh > > Awesome summary. This helps a ton. It confirms

Re: Help from Mentors

2016-04-07 Thread Gino Bustelo
@hitesh Awesome summary. This helps a ton. It confirms what we about to do with License/Notices files. Thanks Gino B. > On Apr 6, 2016, at 6:07 PM, Hitesh Shah wrote: > > Will take a look. > > Some general comments in the meantime: > - version should have incubating. tar balls should

Re: Help from Mentors

2016-04-06 Thread Hitesh Shah
Will take a look. Some general comments in the meantime: - version should have incubating. tar balls should be versioned and have incubating as part of their names ( this seems to be getting addressed in the pull request ) - the main LICENSE and NOTICE are for a source release. This mean

Re: Help from Mentors

2016-04-05 Thread Gino Bustelo
Thanks Hitesh... would you be available to take a look at all we are covering in the PR #13 . Would be great to get an idea if we are going in the right direction regarding LICENSE/NOTICE files and what is needed extra due to LGPL dependency. I t

Re: Help from Mentors

2016-04-05 Thread Hitesh Shah
For snapshot versions, I believe build tools are allowed to publish to the snapshot repo as needed. jenkins builds already support this and I am guessing travis should have similar provisions. For releases ( with a disclaimer as binary artifacts are not considered part of an official release),

Re: Help from Mentors

2016-04-05 Thread Gino Bustelo
Thanks Corey! On Tue, Apr 5, 2016 at 9:51 AM, Corey Stubbs wrote: > I found this article > > explaining podling releases. It appears we should our own directory, under > http://www.apache.org/dist/incubator/, to distribute

Re: Help from Mentors

2016-04-05 Thread Corey Stubbs
I found this article explaining podling releases. It appears we should our own directory, under http://www.apache.org/dist/incubator/, to distribute our releases. This seems

Help from Mentors

2016-04-05 Thread Gino Bustelo
We are getting close to completing work to our build scripts (PR #13 ) to make the project follow the Apache release criteria that we've been able to find through search. Mainly auditing license headers, POM content, jar generation with NOTICE/LICE