Hi!
> > I don't feel that is true at all, what we are doing here is providing a
> > well-documented way toward compliance and the reinstatement of our
> > license. That's a key issue with regards to the existing trolls we are
> > currently facing today, which we have to address in order to
Hi!
> > I don't feel that is true at all, what we are doing here is providing a
> > well-documented way toward compliance and the reinstatement of our
> > license. That's a key issue with regards to the existing trolls we are
> > currently facing today, which we have to address in order to
Hello all,
i'am new in the community. For me the intention of the document is clear but is
very spongy written.
It leaves a lot of interpretations and unclear to me.
Who is the community and who is we ? The names in the document ? In my opinion,
the list is incomplete or is that the community
Hello all,
i'am new in the community. For me the intention of the document is clear but is
very spongy written.
It leaves a lot of interpretations and unclear to me.
Who is the community and who is we ? The names in the document ? In my opinion,
the list is incomplete or is that the community
Hello all,
i'am new in the community. For me the intention of the document is clear but is
very spongy written.
It leaves a lot of interpretations and unclear to me.
Who is the community and who is we ? The names in the document ? In my opinion,
the list is incomplete or is that the community ?
Hello all,
i'am new in the community. For me the intention of the document is clear but is
very spongy written.
It leaves a lot of interpretations and unclear to me.
Who is the community and who is we ? The names in the document ? In my opinion,
the list is incomplete or is that the community ?
On Mon, Oct 23, 2017 at 04:11:14PM +0300, Pavel Nikulin wrote:
> The people signing there effectively say: "we, to big extend, limit
> our options to call for expedient permanent license revocation" - the
> only thing that will ever tickle a commercial entity.
This makes no sense. If a
On Mon, Oct 23, 2017 at 04:11:14PM +0300, Pavel Nikulin wrote:
> The people signing there effectively say: "we, to big extend, limit
> our options to call for expedient permanent license revocation" - the
> only thing that will ever tickle a commercial entity.
This makes no sense. If a
>If you don't agree with this, that's great, don't sign onto the
>agreement. But as you don't seem to be part of our community in the
>first place, I don't really understand your concern here at all.
My last patch submitted to kernel was over a decade ago, yes I have
not much say here. My worry
>If you don't agree with this, that's great, don't sign onto the
>agreement. But as you don't seem to be part of our community in the
>first place, I don't really understand your concern here at all.
My last patch submitted to kernel was over a decade ago, yes I have
not much say here. My worry
On Sat, Oct 21, 2017 at 10:16:12PM +0300, Pavel Nikulin wrote:
> If you say that your lawyers have comprehensively researched that,
> I can't say they did a good job.
Is there a open source knowledgable lawyer that you recommend we work
with in place of the ones that were consulted for this
On Sat, Oct 21, 2017 at 10:16:12PM +0300, Pavel Nikulin wrote:
> If you say that your lawyers have comprehensively researched that,
> I can't say they did a good job.
Is there a open source knowledgable lawyer that you recommend we work
with in place of the ones that were consulted for this
> On Thu, Oct 19, 2017 at 06:28:12PM +0300, Pavel Nikulin wrote:
> Modification of GPL V2 terms are explicitly disallowed.
Greg KH replied at 03:29 (US/Eastern) on Friday:
>> Again, we are not modifying the license, so all should be fine
I agree with Greg; the Linux Kernel Enforcement Statement
> On Thu, Oct 19, 2017 at 06:28:12PM +0300, Pavel Nikulin wrote:
> Modification of GPL V2 terms are explicitly disallowed.
Greg KH replied at 03:29 (US/Eastern) on Friday:
>> Again, we are not modifying the license, so all should be fine
I agree with Greg; the Linux Kernel Enforcement Statement
If you say that your lawyers have comprehensively researched that,
I can't say they did a good job. Almost every line sounds close to
being a contractual agreement. If you say that this is only a personal
promise, you have to state that. Like writing "this is not a an addendum
to license terms and
If you say that your lawyers have comprehensively researched that,
I can't say they did a good job. Almost every line sounds close to
being a contractual agreement. If you say that this is only a personal
promise, you have to state that. Like writing "this is not a an addendum
to license terms and
On Fri, Oct 20, 2017 at 07:25:37PM +0100, Alan Cox wrote:
> On Thu, 19 Oct 2017 18:28:12 +0300
> Pavel Nikulin wrote:
>
> > Hold!
> >
> > Greg, are you trying to put a new addendum to the terms of GPL v2?
>
> In many parts of the world if you make a promise about not
On Fri, Oct 20, 2017 at 07:25:37PM +0100, Alan Cox wrote:
> On Thu, 19 Oct 2017 18:28:12 +0300
> Pavel Nikulin wrote:
>
> > Hold!
> >
> > Greg, are you trying to put a new addendum to the terms of GPL v2?
>
> In many parts of the world if you make a promise about not enforcing a
> right to
On Thu, 19 Oct 2017 18:28:12 +0300
Pavel Nikulin wrote:
> Hold!
>
> Greg, are you trying to put a new addendum to the terms of GPL v2?
In many parts of the world if you make a promise about not enforcing a
right to take some action (sometimes even an implied one) you
On Thu, 19 Oct 2017 18:28:12 +0300
Pavel Nikulin wrote:
> Hold!
>
> Greg, are you trying to put a new addendum to the terms of GPL v2?
In many parts of the world if you make a promise about not enforcing a
right to take some action (sometimes even an implied one) you cannot then
take that
On Thu, Oct 19, 2017 at 06:28:12PM +0300, Pavel Nikulin wrote:
> Hold!
>
> Greg, are you trying to put a new addendum to the terms of GPL v2?
Nope, as I said many times, that's not what is happening here.
> I read the FAQ you posted, having you writing in that FAQ that this is
> not a change to
On Thu, Oct 19, 2017 at 06:28:12PM +0300, Pavel Nikulin wrote:
> Hold!
>
> Greg, are you trying to put a new addendum to the terms of GPL v2?
Nope, as I said many times, that's not what is happening here.
> I read the FAQ you posted, having you writing in that FAQ that this is
> not a change to
Hold!
Greg, are you trying to put a new addendum to the terms of GPL v2?
I read the FAQ you posted, having you writing in that FAQ that this is
not a change to license terms is not enough. Modification of GPL V2
terms are explicitly disallowed. IF you want to put such writing into
kernel, a very
Hold!
Greg, are you trying to put a new addendum to the terms of GPL v2?
I read the FAQ you posted, having you writing in that FAQ that this is
not a change to license terms is not enough. Modification of GPL V2
terms are explicitly disallowed. IF you want to put such writing into
kernel, a very
On Mon, Oct 16, 2017 at 03:50:19PM +0100, David Woodhouse wrote:
> On Mon, 2017-10-16 at 15:46 +0200, Greg KH wrote:
> > > conversations with the TAB on early drafts of this — but I'm a little
> > > concerned that what we've ended up with is a bit one-sided. We're
> > > giving something away, for
On Mon, Oct 16, 2017 at 03:50:19PM +0100, David Woodhouse wrote:
> On Mon, 2017-10-16 at 15:46 +0200, Greg KH wrote:
> > > conversations with the TAB on early drafts of this — but I'm a little
> > > concerned that what we've ended up with is a bit one-sided. We're
> > > giving something away, for
On Mon, Oct 16, 2017 at 03:46:32PM +0200, Greg KH wrote:
> On Mon, Oct 16, 2017 at 02:11:01PM +0100, David Woodhouse wrote:
> > On Mon, 2017-10-16 at 11:25 +0200, Greg KH wrote:
> > > Documentation: Add a file explaining the requested Linux kernel
> > > license enforcement policy
> > >
> > >
On Mon, Oct 16, 2017 at 03:46:32PM +0200, Greg KH wrote:
> On Mon, Oct 16, 2017 at 02:11:01PM +0100, David Woodhouse wrote:
> > On Mon, 2017-10-16 at 11:25 +0200, Greg KH wrote:
> > > Documentation: Add a file explaining the requested Linux kernel
> > > license enforcement policy
> > >
> > >
On Mon, 2017-10-16 at 15:46 +0200, Greg KH wrote:
> I'll go add it and push out the updated post in a bit.
Thanks. I think it's especially important to show how useful
Conservancy's work in this area is.
If there's anyone who's nodding in approval to this document but who
*hasn't* joined
On Mon, 2017-10-16 at 15:46 +0200, Greg KH wrote:
> I'll go add it and push out the updated post in a bit.
Thanks. I think it's especially important to show how useful
Conservancy's work in this area is.
If there's anyone who's nodding in approval to this document but who
*hasn't* joined
I want to thank everyone who has spent years putting together this Linux
Kernel Enforcement Statement. Conservancy issued a public thank-you today:
https://sfconservancy.org/news/2017/oct/16/linux-kernel-enforcement-statement/
Greg wrote:
> What? I thought I did in my blog post! Ugh, you are
I want to thank everyone who has spent years putting together this Linux
Kernel Enforcement Statement. Conservancy issued a public thank-you today:
https://sfconservancy.org/news/2017/oct/16/linux-kernel-enforcement-statement/
Greg wrote:
> What? I thought I did in my blog post! Ugh, you are
On Mon, Oct 16, 2017 at 02:11:01PM +0100, David Woodhouse wrote:
> On Mon, 2017-10-16 at 11:25 +0200, Greg KH wrote:
> > Documentation: Add a file explaining the requested Linux kernel
> > license enforcement policy
> >
> > Here's a pull request to add a new file to the kernel's Documentation
>
On Mon, Oct 16, 2017 at 02:11:01PM +0100, David Woodhouse wrote:
> On Mon, 2017-10-16 at 11:25 +0200, Greg KH wrote:
> > Documentation: Add a file explaining the requested Linux kernel
> > license enforcement policy
> >
> > Here's a pull request to add a new file to the kernel's Documentation
>
On Mon, 2017-10-16 at 11:25 +0200, Greg KH wrote:
> Documentation: Add a file explaining the requested Linux kernel
> license enforcement policy
>
> Here's a pull request to add a new file to the kernel's Documentation
> directory.
> It adds a short document describing the views of how the Linux
On Mon, 2017-10-16 at 11:25 +0200, Greg KH wrote:
> Documentation: Add a file explaining the requested Linux kernel
> license enforcement policy
>
> Here's a pull request to add a new file to the kernel's Documentation
> directory.
> It adds a short document describing the views of how the Linux
The following changes since commit 33d930e59a98fa10a0db9f56c7fa2f21a4aef9b9:
Linux 4.14-rc5 (2017-10-15 21:01:12 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/
tags/enforcement-4.14-rc6
for you to fetch changes up to
The following changes since commit 33d930e59a98fa10a0db9f56c7fa2f21a4aef9b9:
Linux 4.14-rc5 (2017-10-15 21:01:12 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/
tags/enforcement-4.14-rc6
for you to fetch changes up to
38 matches
Mail list logo