Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.project > #9949

Re: Do we need embargoes for GPL compliance issues?

From Jonathan Carter <jcc@debian.org>
Newsgroups linux.debian.project
Subject Re: Do we need embargoes for GPL compliance issues?
Date 2018-09-12 22:40 +0200
Message-ID <wxk5A-3t1-7@gated-at.bofh.it> (permalink)
References <wxiZP-2Rt-3@gated-at.bofh.it>
Organization Debian

Show all headers | View raw


Hi Florian

On 12/09/2018 21:19, Florian Weimer wrote:
> Do you think Debian should welcome embargoes for GPL compliance
> issues?  Security embargoes are a huge pain, but one would hope that
> GPL violations by Linux distributions are much rarer events.

I'm only speaking on my own behalf here, but I find those really awkward.

Red Hat has launched a project[0] called GPL Cooperation Commitment
where developers could volunteer to promise that they would give
violators of their license a "fair chance" to correct problems with how
they use the software.

"Fair chance", is of course, not very well defined anywhere in there at all.

So, the expectation is that free software developers should be willing
and eager to trust large billion dollar companies on what is best for
free software.

Frankly, my response to that isn't suitable for this list.

Having said all of that, I don't know of any case where Debian has
specifically named and shamed anyone regarding such a violation, but I
also don't see a reason why Debian should explicitly try to keep those
secret for no good reason.

-Jonathan

-- 
  ⢀⣴⠾⠻⢶⣦⠀  Jonathan Carter (highvoltage) <jcc>
  ⣾⠁⢠⠒⠀⣿⡁  Debian Developer - https://wiki.debian.org/highvoltage
  ⢿⡄⠘⠷⠚⠋   https://debian.org | https://jonathancarter.org
  ⠈⠳⣄⠀⠀⠀⠀  Be Bold. Be brave. Debian has got your back.



Powered ByWebafricaFibre | LTE	 

Back to linux.debian.project | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Do we need embargoes for GPL compliance issues? Florian Weimer <fw@deneb.enyo.de> - 2018-09-12 21:30 +0200
  Re: Do we need embargoes for GPL compliance issues? Jonathan Carter <jcc@debian.org> - 2018-09-12 22:40 +0200
    Re: Do we need embargoes for GPL compliance issues? Florian Weimer <fw@deneb.enyo.de> - 2018-09-12 22:50 +0200
  Re: Do we need embargoes for GPL compliance issues? Ian Jackson <ijackson@chiark.greenend.org.uk> - 2018-09-13 01:00 +0200
    Re: Do we need embargoes for GPL compliance issues? Ian Jackson <ijackson@chiark.greenend.org.uk> - 2018-09-13 01:10 +0200
  Re: Do we need embargoes for GPL compliance issues? Russ Allbery <rra@debian.org> - 2018-09-13 04:00 +0200
    Re: Do we need embargoes for GPL compliance issues? Paul Wise <pabs@debian.org> - 2018-09-13 05:50 +0200
      Re: Do we need embargoes for GPL compliance issues? Russ Allbery <rra@debian.org> - 2018-09-13 06:40 +0200
        Re: Do we need embargoes for GPL compliance issues? Paul Wise <pabs@debian.org> - 2018-09-13 07:20 +0200
          Re: Do we need embargoes for GPL compliance issues? Russ Allbery <rra@debian.org> - 2018-09-13 07:50 +0200
    Re: Do we need embargoes for GPL compliance issues? Florian Weimer <fw@deneb.enyo.de> - 2018-09-13 08:00 +0200
      Re: Do we need embargoes for GPL compliance issues? Russ Allbery <rra@debian.org> - 2018-09-13 18:10 +0200
        Re: Do we need embargoes for GPL compliance issues? Florian Weimer <fw@deneb.enyo.de> - 2018-09-13 18:50 +0200
        Re: Do we need embargoes for GPL compliance issues? Ben Hutchings <ben@decadent.org.uk> - 2018-09-14 03:30 +0200
          Re: Do we need embargoes for GPL compliance issues? Ian Jackson <ijackson@chiark.greenend.org.uk> - 2018-09-17 13:50 +0200
            Re: Do we need embargoes for GPL compliance issues? Philip Hands <phil@hands.com> - 2018-09-17 22:00 +0200
              so-called "Common Cure" provision, GPL enforcement within Debian, Patrick McHardy's enforcement, etc. (was Re: Do we need embargoes for GPL compliance issues?) "Bradley M. Kuhn" <bkuhn@sfconservancy.org> - 2018-09-20 00:20 +0200

csiph-web