All posts by Bradley M. Kuhn

Conservancy’s Coordinated Compliance Efforts

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/05/29/compliance.html

As most readers might have guessed, my work
at Software Freedom Conservancy
has been so demanding in the last few months that I’ve been unable to
blog, although I have kept up (along with my
co-host Karen Sandler) releasing new
episodes of the Free as in
Freedom
oggcast
.

Today, Karen and I released
a special episode of
FaiF
(which is merely special because it was released during a
week that we don’t normally release a show). In it, Karen and I
discuss in
detail Conservancy’s
announcement today of its new coordinated compliance program
that
includes many copyright holders and projects.

This new program is an outgrowth of the debate that happened over the
last few months regarding
Conservancy’s GPL
compliance efforts. Specifically, I noticed that, buried in the
FUD over the last four
months regarding GPL compliance, there was one key criticism that was
valid and couldn’t be ignored: Linux copyright holders should be
involved in compliance actions on embedded systems. Linux is a central
component of such work, and the BusyBox developers agreed wholeheartedly
that having some Linux developers involved with compliance would be very
helpful. Conservancy has addressed this issue by building a broad
coalition of copyright holders in many different projects who seek to
work on compliance with Conservancy, including not just Linux and
BusyBox, but other projects as well.

I’m looking forward in my day job to working collaboratively with
copyright holders of many different projects to uphold the rights
guaranteed by GPL. I’m also elated at the broad showing of support by
other Conservancy projects. In addition to the primary group in the
announcement (i.e., copyright holders in BusyBox, Samba and Linux), a
total of seven other GPL’d
and/or LGPL‘d
projects have chosen Conservancy to handle compliance efforts. It’s
clear that Conservancy’s compliance efforts are widely supported by many
projects.

The funniest part about all this, though, is that while there has been
no end of discussion of Conservancy’s and other’s compliance efforts
this year, most Free Software users never actually have to deal with
the details of compliance. Requirements of most copyleft licenses like
GPL generally trigger on distribution of the software —
particularly distribution of binaries. Since most users simply receive
distribution of binaries, and run them locally on their own computer,
rarely do they face complex issues of compliance. As the GPLv2
says
, The act of running the Program is not restricted.

Conservancy’s Coordinated Compliance Efforts

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/05/29/compliance.html

As most readers might have guessed, my work
at Software Freedom Conservancy
has been so demanding in the last few months that I’ve been unable to
blog, although I have kept up (along with my
co-host Karen Sandler) releasing new
episodes of the Free as in
Freedom
oggcast
.

Today, Karen and I released
a special episode of
FaiF
(which is merely special because it was released during a
week that we don’t normally release a show). In it, Karen and I
discuss in
detail Conservancy’s
announcement today of its new coordinated compliance program
that
includes many copyright holders and projects.

This new program is an outgrowth of the debate that happened over the
last few months regarding
Conservancy’s GPL
compliance efforts. Specifically, I noticed that, buried in the
FUD over the last four
months regarding GPL compliance, there was one key criticism that was
valid and couldn’t be ignored: Linux copyright holders should be
involved in compliance actions on embedded systems. Linux is a central
component of such work, and the BusyBox developers agreed wholeheartedly
that having some Linux developers involved with compliance would be very
helpful. Conservancy has addressed this issue by building a broad
coalition of copyright holders in many different projects who seek to
work on compliance with Conservancy, including not just Linux and
BusyBox, but other projects as well.

I’m looking forward in my day job to working collaboratively with
copyright holders of many different projects to uphold the rights
guaranteed by GPL. I’m also elated at the broad showing of support by
other Conservancy projects. In addition to the primary group in the
announcement (i.e., copyright holders in BusyBox, Samba and Linux), a
total of seven other GPL’d
and/or LGPL‘d
projects have chosen Conservancy to handle compliance efforts. It’s
clear that Conservancy’s compliance efforts are widely supported by many
projects.

The funniest part about all this, though, is that while there has been
no end of discussion of Conservancy’s and other’s compliance efforts
this year, most Free Software users never actually have to deal with
the details of compliance. Requirements of most copyleft licenses like
GPL generally trigger on distribution of the software —
particularly distribution of binaries. Since most users simply receive
distribution of binaries, and run them locally on their own computer,
rarely do they face complex issues of compliance. As the GPLv2
says
, The act of running the Program is not restricted.

Conservancy’s Coordinated Compliance Efforts

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/05/29/compliance.html

As most readers might have guessed, my work
at Software Freedom Conservancy
has been so demanding in the last few months that I’ve been unable to
blog, although I have kept up (along with my
co-host Karen Sandler) releasing new
episodes of the Free as in
Freedom
oggcast
.

Today, Karen and I released
a special episode of
FaiF
(which is merely special because it was released during a
week that we don’t normally release a show). In it, Karen and I
discuss in
detail Conservancy’s
announcement today of its new coordinated compliance program
that
includes many copyright holders and projects.

This new program is an outgrowth of the debate that happened over the
last few months regarding
Conservancy’s GPL
compliance efforts. Specifically, I noticed that, buried in the
FUD over the last four
months regarding GPL compliance, there was one key criticism that was
valid and couldn’t be ignored: Linux copyright holders should be
involved in compliance actions on embedded systems. Linux is a central
component of such work, and the BusyBox developers agreed wholeheartedly
that having some Linux developers involved with compliance would be very
helpful. Conservancy has addressed this issue by building a broad
coalition of copyright holders in many different projects who seek to
work on compliance with Conservancy, including not just Linux and
BusyBox, but other projects as well.

I’m looking forward in my day job to working collaboratively with
copyright holders of many different projects to uphold the rights
guaranteed by GPL. I’m also elated at the broad showing of support by
other Conservancy projects. In addition to the primary group in the
announcement (i.e., copyright holders in BusyBox, Samba and Linux), a
total of seven other GPL’d
and/or LGPL‘d
projects have chosen Conservancy to handle compliance efforts. It’s
clear that Conservancy’s compliance efforts are widely supported by many
projects.

The funniest part about all this, though, is that while there has been
no end of discussion of Conservancy’s and other’s compliance efforts
this year, most Free Software users never actually have to deal with
the details of compliance. Requirements of most copyleft licenses like
GPL generally trigger on distribution of the software —
particularly distribution of binaries. Since most users simply receive
distribution of binaries, and run them locally on their own computer,
rarely do they face complex issues of compliance. As the GPLv2
says
, The act of running the Program is not restricted.

Conservancy’s Coordinated Compliance Efforts

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/05/29/compliance.html

As most readers might have guessed, my work
at Software Freedom Conservancy
has been so demanding in the last few months that I’ve been unable to
blog, although I have kept up (along with my
co-host Karen Sandler) releasing new
episodes of the Free as in
Freedom
oggcast
.

Today, Karen and I released
a special episode of
FaiF
(which is merely special because it was released during a
week that we don’t normally release a show). In it, Karen and I
discuss in
detail Conservancy’s
announcement today of its new coordinated compliance program
that
includes many copyright holders and projects.

This new program is an outgrowth of the debate that happened over the
last few months regarding
Conservancy’s GPL
compliance efforts. Specifically, I noticed that, buried in the
FUD over the last four
months regarding GPL compliance, there was one key criticism that was
valid and couldn’t be ignored: Linux copyright holders should be
involved in compliance actions on embedded systems. Linux is a central
component of such work, and the BusyBox developers agreed wholeheartedly
that having some Linux developers involved with compliance would be very
helpful. Conservancy has addressed this issue by building a broad
coalition of copyright holders in many different projects who seek to
work on compliance with Conservancy, including not just Linux and
BusyBox, but other projects as well.

I’m looking forward in my day job to working collaboratively with
copyright holders of many different projects to uphold the rights
guaranteed by GPL. I’m also elated at the broad showing of support by
other Conservancy projects. In addition to the primary group in the
announcement (i.e., copyright holders in BusyBox, Samba and Linux), a
total of seven other GPL’d
and/or LGPL‘d
projects have chosen Conservancy to handle compliance efforts. It’s
clear that Conservancy’s compliance efforts are widely supported by many
projects.

The funniest part about all this, though, is that while there has been
no end of discussion of Conservancy’s and other’s compliance efforts
this year, most Free Software users never actually have to deal with
the details of compliance. Requirements of most copyleft licenses like
GPL generally trigger on distribution of the software —
particularly distribution of binaries. Since most users simply receive
distribution of binaries, and run them locally on their own computer,
rarely do they face complex issues of compliance. As the GPLv2
says
, The act of running the Program is not restricted.

Conservancy’s Coordinated Compliance Efforts

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/05/29/compliance.html

As most readers might have guessed, my work
at Software Freedom Conservancy
has been so demanding in the last few months that I’ve been unable to
blog, although I have kept up (along with my
co-host Karen Sandler) releasing new
episodes of the Free as in
Freedom
oggcast
.

Today, Karen and I released
a special episode of
FaiF
(which is merely special because it was released during a
week that we don’t normally release a show). In it, Karen and I
discuss in
detail Conservancy’s
announcement today of its new coordinated compliance program
that
includes many copyright holders and projects.

This new program is an outgrowth of the debate that happened over the
last few months regarding
Conservancy’s GPL
compliance efforts. Specifically, I noticed that, buried in the
FUD over the last four
months regarding GPL compliance, there was one key criticism that was
valid and couldn’t be ignored: Linux copyright holders should be
involved in compliance actions on embedded systems. Linux is a central
component of such work, and the BusyBox developers agreed wholeheartedly
that having some Linux developers involved with compliance would be very
helpful. Conservancy has addressed this issue by building a broad
coalition of copyright holders in many different projects who seek to
work on compliance with Conservancy, including not just Linux and
BusyBox, but other projects as well.

I’m looking forward in my day job to working collaboratively with
copyright holders of many different projects to uphold the rights
guaranteed by GPL. I’m also elated at the broad showing of support by
other Conservancy projects. In addition to the primary group in the
announcement (i.e., copyright holders in BusyBox, Samba and Linux), a
total of seven other GPL’d
and/or LGPL‘d
projects have chosen Conservancy to handle compliance efforts. It’s
clear that Conservancy’s compliance efforts are widely supported by many
projects.

The funniest part about all this, though, is that while there has been
no end of discussion of Conservancy’s and other’s compliance efforts
this year, most Free Software users never actually have to deal with
the details of compliance. Requirements of most copyleft licenses like
GPL generally trigger on distribution of the software —
particularly distribution of binaries. Since most users simply receive
distribution of binaries, and run them locally on their own computer,
rarely do they face complex issues of compliance. As the GPLv2
says
, The act of running the Program is not restricted.

Conservancy’s Coordinated Compliance Efforts

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/05/29/compliance.html

As most readers might have guessed, my work
at Software Freedom Conservancy
has been so demanding in the last few months that I’ve been unable to
blog, although I have kept up (along with my
co-host Karen Sandler) releasing new
episodes of the Free as in
Freedom
oggcast
.

Today, Karen and I released
a special episode of
FaiF
(which is merely special because it was released during a
week that we don’t normally release a show). In it, Karen and I
discuss in
detail Conservancy’s
announcement today of its new coordinated compliance program
that
includes many copyright holders and projects.

This new program is an outgrowth of the debate that happened over the
last few months regarding
Conservancy’s GPL
compliance efforts. Specifically, I noticed that, buried in the
FUD over the last four
months regarding GPL compliance, there was one key criticism that was
valid and couldn’t be ignored: Linux copyright holders should be
involved in compliance actions on embedded systems. Linux is a central
component of such work, and the BusyBox developers agreed wholeheartedly
that having some Linux developers involved with compliance would be very
helpful. Conservancy has addressed this issue by building a broad
coalition of copyright holders in many different projects who seek to
work on compliance with Conservancy, including not just Linux and
BusyBox, but other projects as well.

I’m looking forward in my day job to working collaboratively with
copyright holders of many different projects to uphold the rights
guaranteed by GPL. I’m also elated at the broad showing of support by
other Conservancy projects. In addition to the primary group in the
announcement (i.e., copyright holders in BusyBox, Samba and Linux), a
total of seven other GPL’d
and/or LGPL‘d
projects have chosen Conservancy to handle compliance efforts. It’s
clear that Conservancy’s compliance efforts are widely supported by many
projects.

The funniest part about all this, though, is that while there has been
no end of discussion of Conservancy’s and other’s compliance efforts
this year, most Free Software users never actually have to deal with
the details of compliance. Requirements of most copyleft licenses like
GPL generally trigger on distribution of the software —
particularly distribution of binaries. Since most users simply receive
distribution of binaries, and run them locally on their own computer,
rarely do they face complex issues of compliance. As the GPLv2
says
, The act of running the Program is not restricted.

Conservancy’s Coordinated Compliance Efforts

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/05/29/compliance.html

As most readers might have guessed, my work
at Software Freedom Conservancy
has been so demanding in the last few months that I’ve been unable to
blog, although I have kept up (along with my
co-host Karen Sandler) releasing new
episodes of the Free as in
Freedom
oggcast
.

Today, Karen and I released
a special episode of
FaiF
(which is merely special because it was released during a
week that we don’t normally release a show). In it, Karen and I
discuss in
detail Conservancy’s
announcement today of its new coordinated compliance program
that
includes many copyright holders and projects.

This new program is an outgrowth of the debate that happened over the
last few months regarding
Conservancy’s GPL
compliance efforts. Specifically, I noticed that, buried in the
FUD over the last four
months regarding GPL compliance, there was one key criticism that was
valid and couldn’t be ignored: Linux copyright holders should be
involved in compliance actions on embedded systems. Linux is a central
component of such work, and the BusyBox developers agreed wholeheartedly
that having some Linux developers involved with compliance would be very
helpful. Conservancy has addressed this issue by building a broad
coalition of copyright holders in many different projects who seek to
work on compliance with Conservancy, including not just Linux and
BusyBox, but other projects as well.

I’m looking forward in my day job to working collaboratively with
copyright holders of many different projects to uphold the rights
guaranteed by GPL. I’m also elated at the broad showing of support by
other Conservancy projects. In addition to the primary group in the
announcement (i.e., copyright holders in BusyBox, Samba and Linux), a
total of seven other GPL’d
and/or LGPL‘d
projects have chosen Conservancy to handle compliance efforts. It’s
clear that Conservancy’s compliance efforts are widely supported by many
projects.

The funniest part about all this, though, is that while there has been
no end of discussion of Conservancy’s and other’s compliance efforts
this year, most Free Software users never actually have to deal with
the details of compliance. Requirements of most copyleft licenses like
GPL generally trigger on distribution of the software —
particularly distribution of binaries. Since most users simply receive
distribution of binaries, and run them locally on their own computer,
rarely do they face complex issues of compliance. As the GPLv2
says
, The act of running the Program is not restricted.

Conservancy’s Coordinated Compliance Efforts

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/05/29/compliance.html

As most readers might have guessed, my work
at Software Freedom Conservancy
has been so demanding in the last few months that I’ve been unable to
blog, although I have kept up (along with my
co-host Karen Sandler) releasing new
episodes of the Free as in
Freedom
oggcast
.

Today, Karen and I released
a special episode of
FaiF
(which is merely special because it was released during a
week that we don’t normally release a show). In it, Karen and I
discuss in
detail Conservancy’s
announcement today of its new coordinated compliance program
that
includes many copyright holders and projects.

This new program is an outgrowth of the debate that happened over the
last few months regarding
Conservancy’s GPL
compliance efforts. Specifically, I noticed that, buried in the
FUD over the last four
months regarding GPL compliance, there was one key criticism that was
valid and couldn’t be ignored: Linux copyright holders should be
involved in compliance actions on embedded systems. Linux is a central
component of such work, and the BusyBox developers agreed wholeheartedly
that having some Linux developers involved with compliance would be very
helpful. Conservancy has addressed this issue by building a broad
coalition of copyright holders in many different projects who seek to
work on compliance with Conservancy, including not just Linux and
BusyBox, but other projects as well.

I’m looking forward in my day job to working collaboratively with
copyright holders of many different projects to uphold the rights
guaranteed by GPL. I’m also elated at the broad showing of support by
other Conservancy projects. In addition to the primary group in the
announcement (i.e., copyright holders in BusyBox, Samba and Linux), a
total of seven other GPL’d
and/or LGPL‘d
projects have chosen Conservancy to handle compliance efforts. It’s
clear that Conservancy’s compliance efforts are widely supported by many
projects.

The funniest part about all this, though, is that while there has been
no end of discussion of Conservancy’s and other’s compliance efforts
this year, most Free Software users never actually have to deal with
the details of compliance. Requirements of most copyleft licenses like
GPL generally trigger on distribution of the software —
particularly distribution of binaries. Since most users simply receive
distribution of binaries, and run them locally on their own computer,
rarely do they face complex issues of compliance. As the GPLv2
says
, The act of running the Program is not restricted.

Conservancy’s Coordinated Compliance Efforts

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/05/29/compliance.html

As most readers might have guessed, my work
at Software Freedom Conservancy
has been so demanding in the last few months that I’ve been unable to
blog, although I have kept up (along with my
co-host Karen Sandler) releasing new
episodes of the Free as in
Freedom
oggcast
.

Today, Karen and I released
a special episode of
FaiF
(which is merely special because it was released during a
week that we don’t normally release a show). In it, Karen and I
discuss in
detail Conservancy’s
announcement today of its new coordinated compliance program
that
includes many copyright holders and projects.

This new program is an outgrowth of the debate that happened over the
last few months regarding
Conservancy’s GPL
compliance efforts. Specifically, I noticed that, buried in the
FUD over the last four
months regarding GPL compliance, there was one key criticism that was
valid and couldn’t be ignored: Linux copyright holders should be
involved in compliance actions on embedded systems. Linux is a central
component of such work, and the BusyBox developers agreed wholeheartedly
that having some Linux developers involved with compliance would be very
helpful. Conservancy has addressed this issue by building a broad
coalition of copyright holders in many different projects who seek to
work on compliance with Conservancy, including not just Linux and
BusyBox, but other projects as well.

I’m looking forward in my day job to working collaboratively with
copyright holders of many different projects to uphold the rights
guaranteed by GPL. I’m also elated at the broad showing of support by
other Conservancy projects. In addition to the primary group in the
announcement (i.e., copyright holders in BusyBox, Samba and Linux), a
total of seven other GPL’d
and/or LGPL‘d
projects have chosen Conservancy to handle compliance efforts. It’s
clear that Conservancy’s compliance efforts are widely supported by many
projects.

The funniest part about all this, though, is that while there has been
no end of discussion of Conservancy’s and other’s compliance efforts
this year, most Free Software users never actually have to deal with
the details of compliance. Requirements of most copyleft licenses like
GPL generally trigger on distribution of the software —
particularly distribution of binaries. Since most users simply receive
distribution of binaries, and run them locally on their own computer,
rarely do they face complex issues of compliance. As the GPLv2
says
, The act of running the Program is not restricted.

Cutting Through The Anti-Copyleft Political Ruse

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/02/11/harald-on-enforcement.html

I’d like to thank Harald Welte for
his reasoned
and clear blog post about GPL enforcement
which I hope helps to
clear up some of the confusions
that I
also wrote about recently
.

Harald and I appear to agree that all enforcement actions should
request, encourage, and pressure companies toward full FLOSS
compliance. Our only disagreement, therefore, is on a minor strategy
point. Specifically, Harald believes that the “reinstatement of
rights lever” shouldn’t be used to require compliance on all FLOSS
licenses when resolving a violation matter, and I believe such use of
that lever is acceptable in some cases. In other words, Harald and I
have only a minor disagreement on how aggressively a specific legal
tools should be utilized. (I’d also note that given Harald’s
interpretation of German law, he never had the opportunity to even
consider using that tool, whereas it’s always been a default tool in the
USA.) Anyway, other than this minor side point, Harald and I appear to
otherwise be in full in agreement on everything else regarding GPL
enforcement.

Specifically, one key place where Harald and I are in total agreement
is: copyright holders who enforce should approve all enforcement
strategies. In every GPL enforcement action that I’ve done in my life,
I’ve always made sure of that. Indeed, even while I’m a very minor
copyright holder in BusyBox
(just a
few patches
), I still nevertheless defer to
Erik Andersen
(who holds a plurality of the BusyBox copyrights)
and Denys
Vlasenko
(who is the current BusyBox maintainer) about enforcement
strategy for BusyBox.

I hope that Harald’s post helps to end this silly recent debate about
GPL enforcement. I think the overflowing comment pages can be
summarized quite succinctly: some people don’t like copyleft and don’t
want it enforced. Others disagree, and want to enforce. I’ve
written before that
if
you support copyleft, the only logically consistent position is to also
support enforcement
. The real disagreement here, thus, is one about
whether or not people like copyleft: that’s an age-old debate that we
just had again.

However, the anti-copyleft side used a more sophisticated political
strategy this time. Specifically, copyleft opponents are attempting to
scapegoat minor strategy disagreements among those who do GPL
enforcement. I’m grateful to Harald for cutting through that ruse.
Those of us that support copyleft may have minor disagreements about
enforcement strategy, but we all support GPL enforcement and want to see
it continue. Copyleft opponents will of course use political
maneuvering to portray such minor disagreements as serious policy
questions. Copyleft opponents just want to distract the debate away
from the only policy question that matters: Is copyleft a good force
in the world for software freedom?
I say yes, and thus I’m going to
keep enforcing it, until there are no developers left who want to
enforce it.

Cutting Through The Anti-Copyleft Political Ruse

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/02/11/harald-on-enforcement.html

I’d like to thank Harald Welte for
his reasoned
and clear blog post about GPL enforcement
which I hope helps to
clear up some of the confusions
that I
also wrote about recently
.

Harald and I appear to agree that all enforcement actions should
request, encourage, and pressure companies toward full FLOSS
compliance. Our only disagreement, therefore, is on a minor strategy
point. Specifically, Harald believes that the “reinstatement of
rights lever” shouldn’t be used to require compliance on all FLOSS
licenses when resolving a violation matter, and I believe such use of
that lever is acceptable in some cases. In other words, Harald and I
have only a minor disagreement on how aggressively a specific legal
tools should be utilized. (I’d also note that given Harald’s
interpretation of German law, he never had the opportunity to even
consider using that tool, whereas it’s always been a default tool in the
USA.) Anyway, other than this minor side point, Harald and I appear to
otherwise be in full in agreement on everything else regarding GPL
enforcement.

Specifically, one key place where Harald and I are in total agreement
is: copyright holders who enforce should approve all enforcement
strategies. In every GPL enforcement action that I’ve done in my life,
I’ve always made sure of that. Indeed, even while I’m a very minor
copyright holder in BusyBox
(just a
few patches
), I still nevertheless defer to
Erik Andersen
(who holds a plurality of the BusyBox copyrights)
and Denys
Vlasenko
(who is the current BusyBox maintainer) about enforcement
strategy for BusyBox.

I hope that Harald’s post helps to end this silly recent debate about
GPL enforcement. I think the overflowing comment pages can be
summarized quite succinctly: some people don’t like copyleft and don’t
want it enforced. Others disagree, and want to enforce. I’ve
written before that
if
you support copyleft, the only logically consistent position is to also
support enforcement
. The real disagreement here, thus, is one about
whether or not people like copyleft: that’s an age-old debate that we
just had again.

However, the anti-copyleft side used a more sophisticated political
strategy this time. Specifically, copyleft opponents are attempting to
scapegoat minor strategy disagreements among those who do GPL
enforcement. I’m grateful to Harald for cutting through that ruse.
Those of us that support copyleft may have minor disagreements about
enforcement strategy, but we all support GPL enforcement and want to see
it continue. Copyleft opponents will of course use political
maneuvering to portray such minor disagreements as serious policy
questions. Copyleft opponents just want to distract the debate away
from the only policy question that matters: Is copyleft a good force
in the world for software freedom?
I say yes, and thus I’m going to
keep enforcing it, until there are no developers left who want to
enforce it.

Cutting Through The Anti-Copyleft Political Ruse

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/02/11/harald-on-enforcement.html

I’d like to thank Harald Welte for
his reasoned
and clear blog post about GPL enforcement
which I hope helps to
clear up some of the confusions
that I
also wrote about recently
.

Harald and I appear to agree that all enforcement actions should
request, encourage, and pressure companies toward full FLOSS
compliance. Our only disagreement, therefore, is on a minor strategy
point. Specifically, Harald believes that the “reinstatement of
rights lever” shouldn’t be used to require compliance on all FLOSS
licenses when resolving a violation matter, and I believe such use of
that lever is acceptable in some cases. In other words, Harald and I
have only a minor disagreement on how aggressively a specific legal
tools should be utilized. (I’d also note that given Harald’s
interpretation of German law, he never had the opportunity to even
consider using that tool, whereas it’s always been a default tool in the
USA.) Anyway, other than this minor side point, Harald and I appear to
otherwise be in full in agreement on everything else regarding GPL
enforcement.

Specifically, one key place where Harald and I are in total agreement
is: copyright holders who enforce should approve all enforcement
strategies. In every GPL enforcement action that I’ve done in my life,
I’ve always made sure of that. Indeed, even while I’m a very minor
copyright holder in BusyBox
(just a
few patches
), I still nevertheless defer to
Erik Andersen
(who holds a plurality of the BusyBox copyrights)
and Denys
Vlasenko
(who is the current BusyBox maintainer) about enforcement
strategy for BusyBox.

I hope that Harald’s post helps to end this silly recent debate about
GPL enforcement. I think the overflowing comment pages can be
summarized quite succinctly: some people don’t like copyleft and don’t
want it enforced. Others disagree, and want to enforce. I’ve
written before that
if
you support copyleft, the only logically consistent position is to also
support enforcement
. The real disagreement here, thus, is one about
whether or not people like copyleft: that’s an age-old debate that we
just had again.

However, the anti-copyleft side used a more sophisticated political
strategy this time. Specifically, copyleft opponents are attempting to
scapegoat minor strategy disagreements among those who do GPL
enforcement. I’m grateful to Harald for cutting through that ruse.
Those of us that support copyleft may have minor disagreements about
enforcement strategy, but we all support GPL enforcement and want to see
it continue. Copyleft opponents will of course use political
maneuvering to portray such minor disagreements as serious policy
questions. Copyleft opponents just want to distract the debate away
from the only policy question that matters: Is copyleft a good force
in the world for software freedom?
I say yes, and thus I’m going to
keep enforcing it, until there are no developers left who want to
enforce it.

Cutting Through The Anti-Copyleft Political Ruse

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/02/11/harald-on-enforcement.html

I’d like to thank Harald Welte for
his reasoned
and clear blog post about GPL enforcement
which I hope helps to
clear up some of the confusions
that I
also wrote about recently
.

Harald and I appear to agree that all enforcement actions should
request, encourage, and pressure companies toward full FLOSS
compliance. Our only disagreement, therefore, is on a minor strategy
point. Specifically, Harald believes that the “reinstatement of
rights lever” shouldn’t be used to require compliance on all FLOSS
licenses when resolving a violation matter, and I believe such use of
that lever is acceptable in some cases. In other words, Harald and I
have only a minor disagreement on how aggressively a specific legal
tools should be utilized. (I’d also note that given Harald’s
interpretation of German law, he never had the opportunity to even
consider using that tool, whereas it’s always been a default tool in the
USA.) Anyway, other than this minor side point, Harald and I appear to
otherwise be in full in agreement on everything else regarding GPL
enforcement.

Specifically, one key place where Harald and I are in total agreement
is: copyright holders who enforce should approve all enforcement
strategies. In every GPL enforcement action that I’ve done in my life,
I’ve always made sure of that. Indeed, even while I’m a very minor
copyright holder in BusyBox
(just a
few patches
), I still nevertheless defer to
Erik Andersen
(who holds a plurality of the BusyBox copyrights)
and Denys
Vlasenko
(who is the current BusyBox maintainer) about enforcement
strategy for BusyBox.

I hope that Harald’s post helps to end this silly recent debate about
GPL enforcement. I think the overflowing comment pages can be
summarized quite succinctly: some people don’t like copyleft and don’t
want it enforced. Others disagree, and want to enforce. I’ve
written before that
if
you support copyleft, the only logically consistent position is to also
support enforcement
. The real disagreement here, thus, is one about
whether or not people like copyleft: that’s an age-old debate that we
just had again.

However, the anti-copyleft side used a more sophisticated political
strategy this time. Specifically, copyleft opponents are attempting to
scapegoat minor strategy disagreements among those who do GPL
enforcement. I’m grateful to Harald for cutting through that ruse.
Those of us that support copyleft may have minor disagreements about
enforcement strategy, but we all support GPL enforcement and want to see
it continue. Copyleft opponents will of course use political
maneuvering to portray such minor disagreements as serious policy
questions. Copyleft opponents just want to distract the debate away
from the only policy question that matters: Is copyleft a good force
in the world for software freedom?
I say yes, and thus I’m going to
keep enforcing it, until there are no developers left who want to
enforce it.

Cutting Through The Anti-Copyleft Political Ruse

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/02/11/harald-on-enforcement.html

I’d like to thank Harald Welte for
his reasoned
and clear blog post about GPL enforcement
which I hope helps to
clear up some of the confusions
that I
also wrote about recently
.

Harald and I appear to agree that all enforcement actions should
request, encourage, and pressure companies toward full FLOSS
compliance. Our only disagreement, therefore, is on a minor strategy
point. Specifically, Harald believes that the “reinstatement of
rights lever” shouldn’t be used to require compliance on all FLOSS
licenses when resolving a violation matter, and I believe such use of
that lever is acceptable in some cases. In other words, Harald and I
have only a minor disagreement on how aggressively a specific legal
tools should be utilized. (I’d also note that given Harald’s
interpretation of German law, he never had the opportunity to even
consider using that tool, whereas it’s always been a default tool in the
USA.) Anyway, other than this minor side point, Harald and I appear to
otherwise be in full in agreement on everything else regarding GPL
enforcement.

Specifically, one key place where Harald and I are in total agreement
is: copyright holders who enforce should approve all enforcement
strategies. In every GPL enforcement action that I’ve done in my life,
I’ve always made sure of that. Indeed, even while I’m a very minor
copyright holder in BusyBox
(just a
few patches
), I still nevertheless defer to
Erik Andersen
(who holds a plurality of the BusyBox copyrights)
and Denys
Vlasenko
(who is the current BusyBox maintainer) about enforcement
strategy for BusyBox.

I hope that Harald’s post helps to end this silly recent debate about
GPL enforcement. I think the overflowing comment pages can be
summarized quite succinctly: some people don’t like copyleft and don’t
want it enforced. Others disagree, and want to enforce. I’ve
written before that
if
you support copyleft, the only logically consistent position is to also
support enforcement
. The real disagreement here, thus, is one about
whether or not people like copyleft: that’s an age-old debate that we
just had again.

However, the anti-copyleft side used a more sophisticated political
strategy this time. Specifically, copyleft opponents are attempting to
scapegoat minor strategy disagreements among those who do GPL
enforcement. I’m grateful to Harald for cutting through that ruse.
Those of us that support copyleft may have minor disagreements about
enforcement strategy, but we all support GPL enforcement and want to see
it continue. Copyleft opponents will of course use political
maneuvering to portray such minor disagreements as serious policy
questions. Copyleft opponents just want to distract the debate away
from the only policy question that matters: Is copyleft a good force
in the world for software freedom?
I say yes, and thus I’m going to
keep enforcing it, until there are no developers left who want to
enforce it.

Cutting Through The Anti-Copyleft Political Ruse

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/02/11/harald-on-enforcement.html

I’d like to thank Harald Welte for
his reasoned
and clear blog post about GPL enforcement
which I hope helps to
clear up some of the confusions
that I
also wrote about recently
.

Harald and I appear to agree that all enforcement actions should
request, encourage, and pressure companies toward full FLOSS
compliance. Our only disagreement, therefore, is on a minor strategy
point. Specifically, Harald believes that the “reinstatement of
rights lever” shouldn’t be used to require compliance on all FLOSS
licenses when resolving a violation matter, and I believe such use of
that lever is acceptable in some cases. In other words, Harald and I
have only a minor disagreement on how aggressively a specific legal
tools should be utilized. (I’d also note that given Harald’s
interpretation of German law, he never had the opportunity to even
consider using that tool, whereas it’s always been a default tool in the
USA.) Anyway, other than this minor side point, Harald and I appear to
otherwise be in full in agreement on everything else regarding GPL
enforcement.

Specifically, one key place where Harald and I are in total agreement
is: copyright holders who enforce should approve all enforcement
strategies. In every GPL enforcement action that I’ve done in my life,
I’ve always made sure of that. Indeed, even while I’m a very minor
copyright holder in BusyBox
(just a
few patches
), I still nevertheless defer to
Erik Andersen
(who holds a plurality of the BusyBox copyrights)
and Denys
Vlasenko
(who is the current BusyBox maintainer) about enforcement
strategy for BusyBox.

I hope that Harald’s post helps to end this silly recent debate about
GPL enforcement. I think the overflowing comment pages can be
summarized quite succinctly: some people don’t like copyleft and don’t
want it enforced. Others disagree, and want to enforce. I’ve
written before that
if
you support copyleft, the only logically consistent position is to also
support enforcement
. The real disagreement here, thus, is one about
whether or not people like copyleft: that’s an age-old debate that we
just had again.

However, the anti-copyleft side used a more sophisticated political
strategy this time. Specifically, copyleft opponents are attempting to
scapegoat minor strategy disagreements among those who do GPL
enforcement. I’m grateful to Harald for cutting through that ruse.
Those of us that support copyleft may have minor disagreements about
enforcement strategy, but we all support GPL enforcement and want to see
it continue. Copyleft opponents will of course use political
maneuvering to portray such minor disagreements as serious policy
questions. Copyleft opponents just want to distract the debate away
from the only policy question that matters: Is copyleft a good force
in the world for software freedom?
I say yes, and thus I’m going to
keep enforcing it, until there are no developers left who want to
enforce it.

Cutting Through The Anti-Copyleft Political Ruse

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/02/11/harald-on-enforcement.html

I’d like to thank Harald Welte for
his reasoned
and clear blog post about GPL enforcement
which I hope helps to
clear up some of the confusions
that I
also wrote about recently
.

Harald and I appear to agree that all enforcement actions should
request, encourage, and pressure companies toward full FLOSS
compliance. Our only disagreement, therefore, is on a minor strategy
point. Specifically, Harald believes that the “reinstatement of
rights lever” shouldn’t be used to require compliance on all FLOSS
licenses when resolving a violation matter, and I believe such use of
that lever is acceptable in some cases. In other words, Harald and I
have only a minor disagreement on how aggressively a specific legal
tools should be utilized. (I’d also note that given Harald’s
interpretation of German law, he never had the opportunity to even
consider using that tool, whereas it’s always been a default tool in the
USA.) Anyway, other than this minor side point, Harald and I appear to
otherwise be in full in agreement on everything else regarding GPL
enforcement.

Specifically, one key place where Harald and I are in total agreement
is: copyright holders who enforce should approve all enforcement
strategies. In every GPL enforcement action that I’ve done in my life,
I’ve always made sure of that. Indeed, even while I’m a very minor
copyright holder in BusyBox
(just a
few patches
), I still nevertheless defer to
Erik Andersen
(who holds a plurality of the BusyBox copyrights)
and Denys
Vlasenko
(who is the current BusyBox maintainer) about enforcement
strategy for BusyBox.

I hope that Harald’s post helps to end this silly recent debate about
GPL enforcement. I think the overflowing comment pages can be
summarized quite succinctly: some people don’t like copyleft and don’t
want it enforced. Others disagree, and want to enforce. I’ve
written before that
if
you support copyleft, the only logically consistent position is to also
support enforcement
. The real disagreement here, thus, is one about
whether or not people like copyleft: that’s an age-old debate that we
just had again.

However, the anti-copyleft side used a more sophisticated political
strategy this time. Specifically, copyleft opponents are attempting to
scapegoat minor strategy disagreements among those who do GPL
enforcement. I’m grateful to Harald for cutting through that ruse.
Those of us that support copyleft may have minor disagreements about
enforcement strategy, but we all support GPL enforcement and want to see
it continue. Copyleft opponents will of course use political
maneuvering to portray such minor disagreements as serious policy
questions. Copyleft opponents just want to distract the debate away
from the only policy question that matters: Is copyleft a good force
in the world for software freedom?
I say yes, and thus I’m going to
keep enforcing it, until there are no developers left who want to
enforce it.

Cutting Through The Anti-Copyleft Political Ruse

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/02/11/harald-on-enforcement.html

I’d like to thank Harald Welte for
his reasoned
and clear blog post about GPL enforcement
which I hope helps to
clear up some of the confusions
that I
also wrote about recently
.

Harald and I appear to agree that all enforcement actions should
request, encourage, and pressure companies toward full FLOSS
compliance. Our only disagreement, therefore, is on a minor strategy
point. Specifically, Harald believes that the “reinstatement of
rights lever” shouldn’t be used to require compliance on all FLOSS
licenses when resolving a violation matter, and I believe such use of
that lever is acceptable in some cases. In other words, Harald and I
have only a minor disagreement on how aggressively a specific legal
tools should be utilized. (I’d also note that given Harald’s
interpretation of German law, he never had the opportunity to even
consider using that tool, whereas it’s always been a default tool in the
USA.) Anyway, other than this minor side point, Harald and I appear to
otherwise be in full in agreement on everything else regarding GPL
enforcement.

Specifically, one key place where Harald and I are in total agreement
is: copyright holders who enforce should approve all enforcement
strategies. In every GPL enforcement action that I’ve done in my life,
I’ve always made sure of that. Indeed, even while I’m a very minor
copyright holder in BusyBox
(just a
few patches
), I still nevertheless defer to
Erik Andersen
(who holds a plurality of the BusyBox copyrights)
and Denys
Vlasenko
(who is the current BusyBox maintainer) about enforcement
strategy for BusyBox.

I hope that Harald’s post helps to end this silly recent debate about
GPL enforcement. I think the overflowing comment pages can be
summarized quite succinctly: some people don’t like copyleft and don’t
want it enforced. Others disagree, and want to enforce. I’ve
written before that
if
you support copyleft, the only logically consistent position is to also
support enforcement
. The real disagreement here, thus, is one about
whether or not people like copyleft: that’s an age-old debate that we
just had again.

However, the anti-copyleft side used a more sophisticated political
strategy this time. Specifically, copyleft opponents are attempting to
scapegoat minor strategy disagreements among those who do GPL
enforcement. I’m grateful to Harald for cutting through that ruse.
Those of us that support copyleft may have minor disagreements about
enforcement strategy, but we all support GPL enforcement and want to see
it continue. Copyleft opponents will of course use political
maneuvering to portray such minor disagreements as serious policy
questions. Copyleft opponents just want to distract the debate away
from the only policy question that matters: Is copyleft a good force
in the world for software freedom?
I say yes, and thus I’m going to
keep enforcing it, until there are no developers left who want to
enforce it.

Cutting Through The Anti-Copyleft Political Ruse

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/02/11/harald-on-enforcement.html

I’d like to thank Harald Welte for
his reasoned
and clear blog post about GPL enforcement
which I hope helps to
clear up some of the confusions
that I
also wrote about recently
.

Harald and I appear to agree that all enforcement actions should
request, encourage, and pressure companies toward full FLOSS
compliance. Our only disagreement, therefore, is on a minor strategy
point. Specifically, Harald believes that the “reinstatement of
rights lever” shouldn’t be used to require compliance on all FLOSS
licenses when resolving a violation matter, and I believe such use of
that lever is acceptable in some cases. In other words, Harald and I
have only a minor disagreement on how aggressively a specific legal
tools should be utilized. (I’d also note that given Harald’s
interpretation of German law, he never had the opportunity to even
consider using that tool, whereas it’s always been a default tool in the
USA.) Anyway, other than this minor side point, Harald and I appear to
otherwise be in full in agreement on everything else regarding GPL
enforcement.

Specifically, one key place where Harald and I are in total agreement
is: copyright holders who enforce should approve all enforcement
strategies. In every GPL enforcement action that I’ve done in my life,
I’ve always made sure of that. Indeed, even while I’m a very minor
copyright holder in BusyBox
(just a
few patches
), I still nevertheless defer to
Erik Andersen
(who holds a plurality of the BusyBox copyrights)
and Denys
Vlasenko
(who is the current BusyBox maintainer) about enforcement
strategy for BusyBox.

I hope that Harald’s post helps to end this silly recent debate about
GPL enforcement. I think the overflowing comment pages can be
summarized quite succinctly: some people don’t like copyleft and don’t
want it enforced. Others disagree, and want to enforce. I’ve
written before that
if
you support copyleft, the only logically consistent position is to also
support enforcement
. The real disagreement here, thus, is one about
whether or not people like copyleft: that’s an age-old debate that we
just had again.

However, the anti-copyleft side used a more sophisticated political
strategy this time. Specifically, copyleft opponents are attempting to
scapegoat minor strategy disagreements among those who do GPL
enforcement. I’m grateful to Harald for cutting through that ruse.
Those of us that support copyleft may have minor disagreements about
enforcement strategy, but we all support GPL enforcement and want to see
it continue. Copyleft opponents will of course use political
maneuvering to portray such minor disagreements as serious policy
questions. Copyleft opponents just want to distract the debate away
from the only policy question that matters: Is copyleft a good force
in the world for software freedom?
I say yes, and thus I’m going to
keep enforcing it, until there are no developers left who want to
enforce it.

Cutting Through The Anti-Copyleft Political Ruse

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/02/11/harald-on-enforcement.html

I’d like to thank Harald Welte for
his reasoned
and clear blog post about GPL enforcement
which I hope helps to
clear up some of the confusions
that I
also wrote about recently
.

Harald and I appear to agree that all enforcement actions should
request, encourage, and pressure companies toward full FLOSS
compliance. Our only disagreement, therefore, is on a minor strategy
point. Specifically, Harald believes that the “reinstatement of
rights lever” shouldn’t be used to require compliance on all FLOSS
licenses when resolving a violation matter, and I believe such use of
that lever is acceptable in some cases. In other words, Harald and I
have only a minor disagreement on how aggressively a specific legal
tools should be utilized. (I’d also note that given Harald’s
interpretation of German law, he never had the opportunity to even
consider using that tool, whereas it’s always been a default tool in the
USA.) Anyway, other than this minor side point, Harald and I appear to
otherwise be in full in agreement on everything else regarding GPL
enforcement.

Specifically, one key place where Harald and I are in total agreement
is: copyright holders who enforce should approve all enforcement
strategies. In every GPL enforcement action that I’ve done in my life,
I’ve always made sure of that. Indeed, even while I’m a very minor
copyright holder in BusyBox
(just a
few patches
), I still nevertheless defer to
Erik Andersen
(who holds a plurality of the BusyBox copyrights)
and Denys
Vlasenko
(who is the current BusyBox maintainer) about enforcement
strategy for BusyBox.

I hope that Harald’s post helps to end this silly recent debate about
GPL enforcement. I think the overflowing comment pages can be
summarized quite succinctly: some people don’t like copyleft and don’t
want it enforced. Others disagree, and want to enforce. I’ve
written before that
if
you support copyleft, the only logically consistent position is to also
support enforcement
. The real disagreement here, thus, is one about
whether or not people like copyleft: that’s an age-old debate that we
just had again.

However, the anti-copyleft side used a more sophisticated political
strategy this time. Specifically, copyleft opponents are attempting to
scapegoat minor strategy disagreements among those who do GPL
enforcement. I’m grateful to Harald for cutting through that ruse.
Those of us that support copyleft may have minor disagreements about
enforcement strategy, but we all support GPL enforcement and want to see
it continue. Copyleft opponents will of course use political
maneuvering to portray such minor disagreements as serious policy
questions. Copyleft opponents just want to distract the debate away
from the only policy question that matters: Is copyleft a good force
in the world for software freedom?
I say yes, and thus I’m going to
keep enforcing it, until there are no developers left who want to
enforce it.

Cutting Through The Anti-Copyleft Political Ruse

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2012/02/11/harald-on-enforcement.html

I’d like to thank Harald Welte for
his reasoned
and clear blog post about GPL enforcement
which I hope helps to
clear up some of the confusions
that I
also wrote about recently
.

Harald and I appear to agree that all enforcement actions should
request, encourage, and pressure companies toward full FLOSS
compliance. Our only disagreement, therefore, is on a minor strategy
point. Specifically, Harald believes that the “reinstatement of
rights lever” shouldn’t be used to require compliance on all FLOSS
licenses when resolving a violation matter, and I believe such use of
that lever is acceptable in some cases. In other words, Harald and I
have only a minor disagreement on how aggressively a specific legal
tools should be utilized. (I’d also note that given Harald’s
interpretation of German law, he never had the opportunity to even
consider using that tool, whereas it’s always been a default tool in the
USA.) Anyway, other than this minor side point, Harald and I appear to
otherwise be in full in agreement on everything else regarding GPL
enforcement.

Specifically, one key place where Harald and I are in total agreement
is: copyright holders who enforce should approve all enforcement
strategies. In every GPL enforcement action that I’ve done in my life,
I’ve always made sure of that. Indeed, even while I’m a very minor
copyright holder in BusyBox
(just a
few patches
), I still nevertheless defer to
Erik Andersen
(who holds a plurality of the BusyBox copyrights)
and Denys
Vlasenko
(who is the current BusyBox maintainer) about enforcement
strategy for BusyBox.

I hope that Harald’s post helps to end this silly recent debate about
GPL enforcement. I think the overflowing comment pages can be
summarized quite succinctly: some people don’t like copyleft and don’t
want it enforced. Others disagree, and want to enforce. I’ve
written before that
if
you support copyleft, the only logically consistent position is to also
support enforcement
. The real disagreement here, thus, is one about
whether or not people like copyleft: that’s an age-old debate that we
just had again.

However, the anti-copyleft side used a more sophisticated political
strategy this time. Specifically, copyleft opponents are attempting to
scapegoat minor strategy disagreements among those who do GPL
enforcement. I’m grateful to Harald for cutting through that ruse.
Those of us that support copyleft may have minor disagreements about
enforcement strategy, but we all support GPL enforcement and want to see
it continue. Copyleft opponents will of course use political
maneuvering to portray such minor disagreements as serious policy
questions. Copyleft opponents just want to distract the debate away
from the only policy question that matters: Is copyleft a good force
in the world for software freedom?
I say yes, and thus I’m going to
keep enforcing it, until there are no developers left who want to
enforce it.