From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] rfc: copyright attribution clarifications
Date: Sat, 24 Nov 2018 15:12:19 -0500 [thread overview]
Message-ID: <CAGfcS_my93gpqqBRBpS8nNgf6N0cT2x2YzHEzrAwJ5VwkCKF5w@mail.gmail.com> (raw)
In-Reply-To: <CAAr7Pr-8bZ2_qTKqfFv2mAwaP9J8Q-LRCf6opJ3_H8C_gWk8vA@mail.gmail.com>
On Sat, Nov 24, 2018 at 2:41 PM Alec Warner <antarus@gentoo.org> wrote:
>
> On Sat, Nov 24, 2018 at 12:47 PM William Hubbs <williamh@gentoo.org> wrote:
>>
>> This is what concerns me as well. All of the folks in this thread who
>> want to forbid multiline copyright notices have yet to convince me that
>> there is a technical argument for doing so.
>
> I don't believe the technical arguments have much basis; instead the argument is about community and humanpower.
I've yet to see any technical arguments. I certainly haven't made any.
There is no technical reason to allow multi-line notices, and there is
no technical reason to forbid them. This is entirely a non-technical
issue.
I think they should be forbidden for a number of non-technical reasons:
1. They add clutter to ebuilds. At the very least they should be put
at the bottom of ebuilds and not at the top, and anybody editing an
ebuild should be free to move a multiline notice to the bottom if they
see it at the top.
2. It strikes me as being fairly anti-community. Basically the
companies that give us the most trouble get to stick their names all
over ebuilds, while freely benefitting from hundreds of other ebuilds
that others have contributed without any care for sticking their names
on stuff. Sony should be contributing because they want to
contribute, not to stick their names on things. Or if they want to
sponsor us they should do so under the normal terms for doing so,
which generally involve more than contributing a couple of lines of
ebuild boilerplate.
3. It opens up a slippery slope. Once you say one person can stick
their names on something, how long until everybody and their uncle
starts doing it and an ebuild with a long history like glibc has three
pages of contributor names at the top (and IMO glibc is one of those
few ebuilds that actually seems non-trival)?
4. The people digging in to try to force this policy have no interest
in participating in the Gentoo community, or actually advocating for
their position. It seems that they simply consider their position
undebatable and expect us to just accept it because heaven forbid one
developer not be allowed to contribute during business hours, despite
many others having no issues with this at all since their employers
are more reasonable.
IMO Gentoo (and the members of its community) should be using this as
an opportunity to tarnish Sony's reputation, not bend over backwards
to cater to a random request of a company lawyer who seemingly isn't
interested in actually discussing their policy. This isn't Sony
contributing to open source, this is Sony interfering with what has
basically been routine practice in the community for 15-20 years.
--
Rich
next prev parent reply other threads:[~2018-11-24 20:12 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 [this message]
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
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_my93gpqqBRBpS8nNgf6N0cT2x2YzHEzrAwJ5VwkCKF5w@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