[BCEL] Potential IP problem at GitHub

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[BCEL] Potential IP problem at GitHub

Benedikt Ritter-4
Hello,

I need some advice on how to handle this pull request at GitHub [1]. It
looks like it has been copied without notice from the ASM project. The
files added contain a license header mentioning INRIA, France Telecom. For
now I've just asked the contributor to sign an ICLA. But that is not enough
if the PR is violating IP of third parties.

Thank you,
Benedikt

[1] https://github.com/apache/commons-bcel/pull/7
Reply | Threaded
Open this post in threaded view
|

Re: [BCEL] Potential IP problem at GitHub

jochen-2
On Thu, Jul 28, 2016 at 9:14 AM, Benedikt Ritter <[hidden email]> wrote:

> I need some advice on how to handle this pull request at GitHub [1]. It
> looks like it has been copied without notice from the ASM project. The
> files added contain a license header mentioning INRIA, France Telecom. For
> now I've just asked the contributor to sign an ICLA. But that is not enough
> if the PR is violating IP of third parties.
>
> Thank you,
> Benedikt
>
> [1] https://github.com/apache/commons-bcel/pull/7

AFAICT, that PR adds two files with 1094 lines of code.That is, IMO no
trivial contribution. I'd therefore suggest to forward the matter to
[hidden email].

Jochen


--
The next time you hear: "Don't reinvent the wheel!"

http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [BCEL] Potential IP problem at GitHub

Benedikt Ritter-4
Jochen Wiedmann <[hidden email]> schrieb am Do., 28. Juli 2016
um 10:03 Uhr:

> On Thu, Jul 28, 2016 at 9:14 AM, Benedikt Ritter <[hidden email]>
> wrote:
>
> > I need some advice on how to handle this pull request at GitHub [1]. It
> > looks like it has been copied without notice from the ASM project. The
> > files added contain a license header mentioning INRIA, France Telecom.
> For
> > now I've just asked the contributor to sign an ICLA. But that is not
> enough
> > if the PR is violating IP of third parties.
> >
> > Thank you,
> > Benedikt
> >
> > [1] https://github.com/apache/commons-bcel/pull/7
>
> AFAICT, that PR adds two files with 1094 lines of code.That is, IMO no
> trivial contribution. I'd therefore suggest to forward the matter to
> [hidden email].
>

I have created https://issues.apache.org/jira/browse/LEGAL-267 for this.

Thank you!
Benedikt


>
> Jochen
>
>
> --
> The next time you hear: "Don't reinvent the wheel!"
>
>
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [BCEL] Potential IP problem at GitHub

jochen-2
On Fri, Jul 29, 2016 at 10:46 AM, Benedikt Ritter <[hidden email]> wrote:

> Jochen Wiedmann <[hidden email]> schrieb am Do., 28. Juli 2016
> um 10:03 Uhr:
>
>> On Thu, Jul 28, 2016 at 9:14 AM, Benedikt Ritter <[hidden email]>
>> wrote:
>>
>> > I need some advice on how to handle this pull request at GitHub [1]. It
>> > looks like it has been copied without notice from the ASM project. The
>> > files added contain a license header mentioning INRIA, France Telecom.
>> For
>> > now I've just asked the contributor to sign an ICLA. But that is not
>> enough
>> > if the PR is violating IP of third parties.
>> >
>> > Thank you,
>> > Benedikt
>> >
>> > [1] https://github.com/apache/commons-bcel/pull/7
>>
>> AFAICT, that PR adds two files with 1094 lines of code.That is, IMO no
>> trivial contribution. I'd therefore suggest to forward the matter to
>> [hidden email].
>>
>
> I have created https://issues.apache.org/jira/browse/LEGAL-267 for this.

Another good possibility.

Jochen


--
The next time you hear: "Don't reinvent the wheel!"

http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]