public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] rfc: copyright attribution clarifications
Date: Sun, 25 Nov 2018 17:58:21 -0500	[thread overview]
Message-ID: <CAGfcS_m0FnBKZ0+fxXZRTCLNCN5ZXE6Le07mv=L75xgoCW4ObQ@mail.gmail.com> (raw)
In-Reply-To: <20181125205224.GA720@linux1.home>

On Sun, Nov 25, 2018 at 3:52 PM William Hubbs <williamh@gentoo.org> wrote:
>
> Regardless of anything that is said in this thread, I do not agree, as
> a council member, with the idea of the Gentoo community actively
> tarnishing anyone's reputation.
>
> I have added the proctors to this email, because I think they should
> determine whether your behavior is a CoC violation.
>

The opinions below are my own.

IMO advocating for what Gentoo should or shouldn't do isn't a CoC
violation.  I certainly haven't said anything intended to tarnish
Sony's reputation in the email above.

I do think that antarus's suggestion of leaving the policy as-is for
now and seeking further clarification from Sony as to why they feel it
is necessary to change it would be more constructive.

That said, I don't like the idea that corporations can basically
dictate policy changes under the threat of withdrawing contributions.
This has created a lot of churn mostly involving the most senior
members of the community, and a moderate amount of division.  While
one developer getting to spend a few hours per week on company time on
Gentoo commits is certainly helpful, many other companies seem to be
able to provide this to Gentoo without requiring policy changes, and
far more hours get donated by volunteers without any demands for
concessions.

I'll admit that my post was a bit emotional, and as such perhaps not a
great example for a dev to set.  However, I'm not sure that passive
acceptance of a change like this is going to be any less harmful to
Gentoo than active defiance.  These two are of course not the only
alternatives, and we should seek a better way.

-- 
Rich


  reply	other threads:[~2018-11-25 22:58 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 18:32 [gentoo-project] rfc: copyright attribution clarifications William Hubbs
2018-11-13 18:47 ` M. J. Everitt
2018-11-14  2:17 ` Rich Freeman
2018-11-14  2:46   ` William Hubbs
2018-11-14  7:18     ` Sarah White
2018-11-14 15:58       ` Rich Freeman
2018-11-14 19:38         ` Patrick McLean
2018-11-14 23:23           ` Rich Freeman
2018-11-15  0:00             ` Patrick McLean
2018-11-15 15:03               ` Rich Freeman
2018-11-15 15:28                 ` William Hubbs
2018-11-15 15:52                 ` Ian Stakenvicius
2018-11-14  8:24     ` Ulrich Mueller
2018-11-14  8:28       ` Raymond Jennings
2018-11-14 19:47       ` Patrick McLean
2018-11-14 20:09         ` Patrick McLean
2018-11-15 13:38           ` Thomas Deutschmann
2018-11-15 22:25             ` Kristian Fiskerstrand
2018-11-15  6:49         ` Ulrich Mueller
2018-11-15 15:35           ` William Hubbs
2018-11-15 17:50             ` Ulrich Mueller
2018-11-15 18:50               ` William Hubbs
2018-11-15 21:31                 ` M. J. Everitt
2018-11-15 21:56                   ` Andrew Savchenko
2018-11-16  9:16                 ` Ulrich Mueller
2018-11-14 15:50     ` Rich Freeman
2018-11-14 14:45       ` Andrew Savchenko
2018-11-14 15:24         ` Rich Freeman
2018-11-14 15:53           ` Andrew Savchenko
2018-11-23 19:21             ` Sarah White
2018-11-23 19:46               ` Rich Freeman
2018-11-23 20:23                 ` Sarah White
2018-11-23 20:25                   ` Ian Stakenvicius
2018-11-23 20:40                     ` Sarah White
2018-11-24 17:47                       ` William Hubbs
2018-11-24 18:15                         ` Sarah White
2018-11-24 19:41                         ` Alec Warner
2018-11-24 20:12                           ` Rich Freeman
2018-11-24 20:32                             ` Alec Warner
2018-11-24 21:21                               ` Rich Freeman
2018-11-26 12:01                               ` Ulrich Mueller
2018-11-26 13:36                                 ` Alec Warner
2018-11-25 20:36                             ` Matt Turner
2018-11-25 20:52                               ` William Hubbs
2018-11-25 22:58                                 ` Rich Freeman [this message]
2018-11-24 23:11                           ` Ulrich Mueller
2018-11-25  1:09                             ` Sarah White
2018-11-25  1:37                               ` Rich Freeman
2018-11-25  2:04                                 ` Sarah White
2018-11-25  2:22                                   ` Rich Freeman
2018-11-25  3:21                                     ` Sarah White
2018-11-25  6:53                                     ` Joonas Niilola
2018-11-25  2:04                         ` Matt Turner
2018-11-26 15:20                           ` William Hubbs
2018-11-26 23:12                             ` William Hubbs
2018-11-27  0:05                               ` Raymond Jennings
2018-11-27  2:38                               ` Matt Turner
2018-11-27  4:51                                 ` William Hubbs
2018-11-27  6:20                                   ` Matt Turner
2018-11-23 20:42                   ` Rich Freeman
2018-11-23 20:51                     ` Sarah White
2018-11-23 21:11                       ` Rich Freeman
2018-11-24 17:49                         ` Sarah White
2018-11-23 20:57                   ` Rich Freeman
2018-11-14 14:36   ` Andrew Savchenko
2018-11-14 15:31     ` Rich Freeman
2018-11-14 16:19       ` Andrew Savchenko
2018-11-14 18:59       ` Ian Stakenvicius
2018-11-14 19:38         ` William Hubbs
2018-11-14 20:02         ` Patrick McLean
2018-11-14 20:11           ` M. J. Everitt
2018-11-15 13:16         ` Thomas Deutschmann
2018-11-15 15:51       ` Brian Dolbec
2018-11-15 16:25         ` Thomas Deutschmann
2018-11-15 16:47           ` William Hubbs

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='CAGfcS_m0FnBKZ0+fxXZRTCLNCN5ZXE6Le07mv=L75xgoCW4ObQ@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-project@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