Right, it contains ALv2 licensed code attributed to two authors - some is
from Guava, some is from Apache Spark contributors.
I thought this is how we should handle this. It's not feasible to go line
by line and say what came from where.
On Wed, Mar 1, 2023 at 1:33 AM Dongjoon Hyun
wrote:
> May
I was going to ask the same. I've seen ~5 proposals now, and was
surprised to see how they all copied and pasted the same boilerplate
to answer several points, including this stanza about risk of
excessive fascination with the brand.
I also suspect that there is excessive fascination, and that pay
I don't have enough knowledge of DeviceMap to have much opinion. Going
by the book
(http://incubator.apache.org/incubation/Incubation_Policy.html#Minimum+Graduation+Requirements)
at least 3 committers, presumably active, are as required as anything
can be said to be.
There were 12 committers prop
Belatedly, I also say +1 as the NOTICE and LICENSE look good (an
important issue of late), source compiles, tests pass, signature is
good, process is good, etc.
On Wed, Oct 22, 2014 at 8:29 AM, Robert Metzger wrote:
> Hi all,
>
> This is our second try to release Flink 0.7.0-incubating. The last
I'm reading http://incubator.apache.org/guides/graduation.html#community
"A major criterion for graduation is to have developed an open and
diverse meritocratic community ... The project is considered to have a
diverse community when it is not highly dependent on any single
contributor (there are
I have no strong opinion on the graduation, sounds fine, but can I ask
how much of the contribution is not from MapR? I got through the top
10 contributors, making up maybe 95+% of it, and didn't see any
non-employees, if my info is right:
https://github.com/apache/incubator-drill/graphs/contributo
Sounds OK to me too if that is the prevailing sentiment; I personally
do not operate (non-ASF) OSS projects that way. It seems just within
the letter of the law.
What about this little transitive dep of Netty I mentioned? This is
not a NOTICE issue, and I *think* this one is beyond interpreting
aw
On Sat, Oct 11, 2014 at 7:26 PM, Ted Dunning wrote:
> On Sat, Oct 11, 2014 at 11:08 AM, Sean Owen wrote:
>
>> On Sat, Oct 11, 2014 at 7:02 PM, Ted Dunning
>> wrote:
>> > Netty's artifacts ("its distribution") do not include a notice. Thus,
>>
On Sat, Oct 11, 2014 at 7:02 PM, Ted Dunning wrote:
> Netty's artifacts ("its distribution") do not include a notice. Thus,
They most certainly do. Please download the distribution of Netty 4.0.20:
https://github.com/netty/netty/releases/tag/netty-4.0.20.Final
and find the NOTICE.txt file.
I
On Sat, Oct 11, 2014 at 6:35 PM, Ted Dunning wrote:
> On Sat, Oct 11, 2014 at 8:13 AM, Sean Owen wrote:
>
>> Here's another example. Drill distributes Netty 4.0.20, which is AL2
>> licensed and contains a substantial NOTI
On Sat, Oct 11, 2014 at 3:43 PM, Ted Dunning wrote:
> It is a tortured and patently incorrect reading to assume that the license
> requires TWO copies of such notices.
Sure, but, nobody said that. The question is whether at least one copy
is present, and ideally in the right place.
Here's anothe
That may be so, and I find this issue irritating to deal with, but I
don't see that it has bearing on what is ultimately correct. I think
that the guidance you refer to was wrong, according to the text of the
licenses, and the link I pointed to.
But even those are a bit ambiguous, so I raise the q
On Sat, Oct 11, 2014 at 1:27 PM, Marvin Humphrey wrote:
> I admire the good-faith efforts that the Spark (and Solr) folks have put
> in attempting to comply with their interpretation of ASF requirements, but I
> don't think we should encourage podlings to emulate the current state of their
> licen
/.
>
> Under normal circumstances, there is no need to modify NOTICE.
>
> Over and over again, it is emphasized that NOTICE does not need to be
> modified and that the reference should be in the LICENSE file.
>
> This seems to contradict your assertion that these references need to b
No I just went straight for the binary distribution:
http://people.apache.org/~smp/apache-drill-0.6.0.rc0/apache-drill-0.6.0-incubating.tar.gz
This contains the third-party jar files in jars/.
I assume http://www.apache.org/dev/licensing-howto.html is still the
law of the land so to speak and in
I had a look, since I was just dealing with NOTICE for another
project. The key is whether copies of the third-party libraries are
distributed. In the case of Drill, yes there are loads of 3rd party
jars distributed in jars/; they are not just Maven deps referenced in
pom.xml.
I am sure this will
When I did this review for Spark, I used Maven's license plugin:
http://mojo.codehaus.org/license-maven-plugin/
mvn license:aggregate-add-third-party
It creates a report of all transitive deps and their license,
according to pom files.
I had to indeed review lots of the dependencies by hand to e
I think it would be useful to expand on how this is different from Sentry too:
"Argus is a framework to enable, monitor and manage comprehensive data
security across the Hadoop platform."
"The Apache Knox Gateway is a REST API Gateway for interacting with
Hadoop clusters. [for the purposes of...]
hair of the incubator (don't
>> know out of my head who that is at the moment).
>>
>> Best,
>> Sebastian
>>
>> On 04/10/2014 08:06 PM, Sean Owen wrote:
>>>
>>> Hello all, just pinging this request. I might be in the wrong place?
>>&g
Hello all, just pinging this request. I might be in the wrong place?
let me know what I can do to join the PMC for purposes of
Stratosphere's incubation.
Sean
On Sun, Mar 30, 2014 at 8:43 PM, Sean Owen wrote:
> Hello all, I've been invited to help mentor the Stratosphere project.
Hello all, I've been invited to help mentor the Stratosphere project.
Alan Gates reminds me that I will need to be a part of the Incubator
PMC I believe in order to do that? I am an ASF member already so I
believe it should be straightforward. How do we go about that?
Best regards,
Sean
-
21 matches
Mail list logo
