public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark David Dumlao <madumlao@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Trouble on the horizon!
Date: Tue, 25 Sep 2018 12:49:44 +0800	[thread overview]
Message-ID: <CAG2nJkM_xUaZrvoCL85Du1XCc9Fg3pHhd5vDGsUnPcTzT=Z2dw@mail.gmail.com> (raw)
In-Reply-To: <poaedf$qqi$1@blaine.gmane.org>

On Mon, Sep 24, 2018 at 6:34 PM Nikos Chantziaras <realnc@gmail.com> wrote:
>
> On 24/09/2018 13:11, R0b0t1 wrote:
> > On Mon, Sep 24, 2018 at 11:01 AM, Nikos Chantziaras <realnc@gmail.com> wrote:
> >>
> >> To me it looks like youtubers and some sites trying to make money through
> >> clickbait?
> >>
> >
> > If you had not heard of it elsewhere the Linux code of conduct was
> > amended. It makes the CoC similar to those of other projects where
> > there are a number of (usually nontechnical) contributors who identify
> > as a champion of social justice.
> > [...]
> Well, if kernel developers are fine with that, then I don't see how
> that's relevant to anyone who isn't a kernel dev. If they want to adopt
> social justice politics, that's really their prerogative.
>

Actually, social justice politics didn't seem to have anything to do
with the CoC
adoption. It was more of Linus taking a backseat (due to how he self-assessed
his vacation behavior) and pretty soon after, they adopted CoC, most likely as
some kind of "standardization"

Barely a week has passed since the CoC though, and already there are political
manuevers to oust high-profile kernel devs to the point that some contributors
have started talks on exercising their copyright privileges and
withholding their
code. Which they have a right to do, by the way, if they feel the foundation
has betrayed them.

So as esr has put it:
> First, let me confirm that this threat has teeth. I researched the relevant law
> when I was founding the Open Source Initiative. In the U.S. there is case law
> confirming that reputational losses relating to conversion of the rights of a
> contributor to a GPLed project are judicable in law. I do not know the case law
> outside the U.S., but in countries observing the Berne Convention without the
> U.S.’s opt-out of the “moral rights” clause, that clause probably gives the
> objectors an even stronger case.

(http://esr.ibiblio.org/?p=8139)

This is not a little online trollfest that only affects kernel devs.
This can affect
literally everything. Biblical proportions, dogs and cats living together, etc.
-- 
This email is:    [ ] actionable   [x] fyi        [x] social
Response needed:  [ ] yes          [ ] up to you  [x] no
Time-sensitive:   [ ] immediate    [ ] soon       [x] none


  parent reply	other threads:[~2018-09-25  4:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24  7:02 [gentoo-user] Trouble on the horizon! Alan Grimes
2018-09-24  9:00 ` Adam Carter
2018-09-24  9:01 ` [gentoo-user] " Nikos Chantziaras
2018-09-24 10:11   ` R0b0t1
2018-09-24 10:33     ` Nikos Chantziaras
2018-09-24 11:39       ` R0b0t1
2018-09-25  4:49       ` Mark David Dumlao [this message]
2018-09-25 20:26         ` Wols Lists
2018-09-24 12:42 ` [gentoo-user] " Philip Webb
2018-09-24 12:59   ` Rich Freeman
2018-09-24 16:27     ` Jack
2018-09-24 18:25     ` J. Roeleveld
2018-09-24 18:24   ` J. Roeleveld
2018-09-24 22:55     ` [gentoo-user] Re : kernel delay Philip Webb
2018-09-25  7:34       ` Peter Humphrey
2018-10-04  9:35         ` [gentoo-user] [Even further OT] " Peter Humphrey
2018-09-25  4:36     ` [gentoo-user] Trouble on the horizon! gevisz
2018-09-25  6:14       ` J. Roeleveld
2018-09-25  6:23         ` gevisz
2018-09-25  7:12           ` J. Roeleveld
2018-09-25  7:28             ` gevisz
2018-09-26 12:17               ` Bill Kenworthy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAG2nJkM_xUaZrvoCL85Du1XCc9Fg3pHhd5vDGsUnPcTzT=Z2dw@mail.gmail.com' \
    --to=madumlao@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox