Re: [VOTE] Graduate to a top-level project

2020-05-21 Thread Ryan Blue
> I would assume because it's a dependancy and not bundled in the source release. I searched for "copied from" to test that assumption and found code from Apache Commons:

Re: [VOTE] Graduate to a top-level project

2020-05-20 Thread Justin Mclean
Hi, > Mark is talking about what they did for the Tomcat NOTICE, with no mention > of Commons: https://github.com/apache/tomcat/blob/master/NOTICE I would assume because it's a dependancy and not bundled in the source release. Even if that is the case older projects may not be in line with ASF

Re: [VOTE] Graduate to a top-level project

2020-05-20 Thread Ryan Blue
> You see in that Mark recommends including the project name/copyright line in the NOTICE file as I’ve suggested to you. Are you sure about that? Mark is talking about what they did for the Tomcat NOTICE, with no mention of Commons: https://github.com/apache/tomcat/blob/master/NOTICE And the

Re: [VOTE] Graduate to a top-level project

2020-05-20 Thread Justin Mclean
Hi, > 1. Should the entire file header be moved into NOTICE when a third-party > file is contributed, or should we edit it When a 3rd party file is contributed, it’s header stays were it is on the file, it’s not moved to NOTICE. It the file was part of a software grant then the copyright

Re: [VOTE] Graduate to a top-level project

2020-05-20 Thread Ryan Blue
To summarize, it looks like there are two issues: 1. Should the entire file header be moved into NOTICE when a third-party file is contributed, or should we edit it 2. When including all or part of another ASF project is the standard NOTICE sufficient? I went back through

Re: [VOTE] Graduate to a top-level project

2020-05-18 Thread Justin Mclean
Hi, > At the time, we considered the whole header to be the relevant "Copyright > notification". Do you think this practice is incorrect? I’ve not seem other projects do it this way, it's generally: "Portions of this software were developed at Acme Inc, copyright 20XX.” > Which ones are you

Re: [VOTE] Graduate to a top-level project

2020-05-18 Thread Ryan Blue
On Mon, May 18, 2020 at 4:40 PM Justin Mclean wrote: > > Per NOTICE policy > > : "Copyright > > notifications which have been relocated, rather than removed, from source > > files must be preserved in NOTICE” > > Yes the copyright line

Re: [VOTE] Graduate to a top-level project

2020-05-18 Thread Justin Mclean
Hi, > Per NOTICE policy > : "Copyright > notifications which have been relocated, rather than removed, from source > files must be preserved in NOTICE” Yes the copyright line needs to be mentioned not the licenser header. > My

Re: [VOTE] Graduate to a top-level project

2020-05-18 Thread Ryan Blue
On Mon, May 18, 2020 at 3:35 PM Justin Mclean wrote: > Hi, > > > What license information are you referring to? > > " Licensed under the Apache License” by Cloudera > This is not a license, it is the original copyright header for files that were contributed by Cloudera. Here's the commit

Re: [VOTE] Graduate to a top-level project

2020-05-18 Thread Justin Mclean
Hi, > What license information are you referring to? " Licensed under the Apache License” by Cloudera > Which entries in the LICENSE file? Many Apache-licensed projects don't have > NOTICE files. Yes but all ASF projects do, your license mentions Apache Avro, Apache Parquet, Apache iBATIS,

Re: [VOTE] Graduate to a top-level project

2020-05-18 Thread Ryan Blue
Hi Justin, I have more questions for you inline: On Sat, May 16, 2020 at 6:29 PM Justin Mclean wrote: > Hi, > 1. You have included some license information this should be in LICENSE > not NOTICE > What license information are you referring to? > 2. Going on what is listed in the LICENSE

Re: [VOTE] Graduate to a top-level project

2020-05-16 Thread Justin Mclean
Hi, Looking at your notice file in the last release it still needs some work: 1. You have included some license information this should be in LICENSE not NOTICE 2. Going on what is listed in the LICENSE file you are missing content from bundled code NOTICE files [1] (see bundling an apache 2.0

Re: [VOTE] Graduate to a top-level project

2020-05-13 Thread Justin Mclean
Hi Owen and Ryan, Thanks for the detailed responses, I don’t think anything more is needed. I personally think it would be best if you did another release before exiting the incubator, but if you mentors are good with only making two than that should be OK. I’ll follow up on the NOTICE issue

Re: [VOTE] Graduate to a top-level project

2020-05-13 Thread Owen O'Malley
On Tue, May 12, 2020 at 10:44 PM Justin Mclean wrote: > I notice a few minor things that may need to be sorted out/dicussed: - You have only made two releases and the last one had some issue around > licensing and NOTICE files > Obviously the first release at Apache takes the longest as the

Re: [VOTE] Graduate to a top-level project

2020-05-13 Thread Ryan Blue
Thanks for taking a look, Justin. I appreciate playing devil's advocate here to ensure this is well thought through. I'll add replies inline. On Tue, May 12, 2020 at 10:44 PM Justin Mclean wrote: > Has the project filled in a maturity model? This is optional but give the > project and the IPMC

Re: [VOTE] Graduate to a top-level project

2020-05-12 Thread Justin Mclean
HI, I think the incubator will need more information before voting on this. Has the project filled in a maturity model? This is optional but give the project and the IPMC more information about the project. I notice a few minor things that may need to be sorted out/dicussed: - The incubator

Fwd: [VOTE] Graduate to a top-level project

2020-05-12 Thread Ryan Blue
] Graduate to a top-level project To: Iceberg Dev List Hi everyone, I propose that the Iceberg community should petition to graduate from the Apache Incubator to a top-level project. Here is the draft board resolution: Establish the Apache Iceberg Project WHEREAS, the Board of Directors deems