From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: libc-alpha@sourceware.org
Subject: Re: Seeking input from developers: glibc copyright assignment policy.
Date: Fri, 25 Jun 2021 12:17:57 +0530 [thread overview]
Message-ID: <3e0c8f21-422b-ffd6-d939-49f88f09cac7@gotplt.org> (raw)
In-Reply-To: <83k0misbni.fsf@gnu.org>
On 6/25/21 11:56 AM, Eli Zaretskii wrote:
> I don't follow. You said:
>
>> (2) contributors who prefer to retain ownership of their content for
>> various reasons
>
> I'm showing text from the assignment agreement that IMO clearly says
> the developer retains all the rights. IOW, as long as the developer
> doesn't prevent the FSF from using the changes as they see fit, the
> developer can do anything with the changes, including distributing
> them under any license the developer wants. Why doesn't this satisfy
> your point (2)?
Sorry I should have been clearer, I meant to say that an assignment with
a grant back implies a shared ownership, which is different from wanting
exclusive ownership. It's perfectly reasonable for someone to be picky
about who they share ownership with.
>> It still needs trust in the organization to represent my values.
>
> I think this is (3), not (2).
>
> And I don't really understand what values are being alluded to here.
> The FSF is an organization whose only purpose is supporting and
> promoting Free Software; as such, the only relevant values (or should
> I say "value", singular) is the support and promotion of Free
> Software. Anything else is not relevant to the FSF and our relations
> with it, and can only be some private values or views of some FSF
> members. What does this have to do with the copyright assignment for
> a contribution to a GNU project such as glibc?
That's for me to decide, no? :) Different people take a different view
of the kinds of values they would attach to an engagement and it may
differ with the nature of engagement.
> The DCO text practically tells the developer not to worry about "this
> nonsense", and just say things "to the best of his/her knowledge". It
> doesn't even explain the purpose of the declarations in the DCO and
> how they will be used by the project. For example, the crucial
> importance of the information veracity for a possible future
> litigation is never mentioned. So even if the developer wants to
> DTRT, they won't know what is and isn't important in their
> declaration, and thus will not be able to make sure the important
> information is verified and correct.
I don't think that difference matters in practice, definitely not enough
to create an elaborate mechanism that is similarly leaky.
> Oh, and talking about dishonest contributors is not useful. I'm
> talking about the honest ones. If someone wants to lie about the
Agreed, I mentioned that case only for completeness.
Siddhesh
next prev parent reply other threads:[~2021-06-25 6:48 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 1:04 Bruno Haible
2021-06-23 3:19 ` Siddhesh Poyarekar
2021-06-24 19:30 ` Eli Zaretskii
2021-06-25 2:23 ` Siddhesh Poyarekar
2021-06-25 6:26 ` Eli Zaretskii
2021-06-25 6:47 ` Siddhesh Poyarekar [this message]
2021-06-25 7:06 ` Eli Zaretskii
2021-06-25 8:57 ` Siddhesh Poyarekar
2021-06-25 9:43 ` Siddhesh Poyarekar
2021-06-25 11:32 ` Eli Zaretskii
2021-06-25 12:07 ` Florian Weimer
2021-06-25 12:11 ` Siddhesh Poyarekar
2021-06-25 12:14 ` Florian Weimer
2021-06-25 12:25 ` Siddhesh Poyarekar
2021-06-25 12:33 ` Florian Weimer
2021-06-25 12:48 ` Siddhesh Poyarekar
2021-06-25 13:44 ` Eli Zaretskii
2021-06-25 14:06 ` Siddhesh Poyarekar
2021-06-26 6:31 ` Eli Zaretskii
2021-06-28 4:11 ` Siddhesh Poyarekar
2021-06-28 12:01 ` Eli Zaretskii
2021-06-28 13:06 ` Siddhesh Poyarekar
2021-06-28 14:04 ` Phil Blundell
2021-06-28 14:57 ` Eli Zaretskii
2021-06-25 11:30 ` Eli Zaretskii
2021-06-25 12:24 ` Siddhesh Poyarekar
2021-06-25 7:24 ` Florian Weimer
2021-06-25 7:52 ` Eli Zaretskii
2021-06-25 8:23 ` Florian Weimer
2021-06-25 11:03 ` Eli Zaretskii
2021-06-25 6:30 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2021-07-02 22:23 Craig Topham
2021-07-05 14:59 ` Szabolcs Nagy
2021-07-05 16:48 ` Eli Zaretskii
2021-07-05 18:52 ` Paul Eggert
2021-06-14 18:52 Carlos O'Donell
2021-06-14 19:08 ` Rich Felker
2021-06-14 19:25 ` Khem Raj
2021-06-14 20:05 ` Florian Weimer
2021-06-14 20:22 ` Matt Turner
2021-06-15 20:28 ` Carlos O'Donell
2021-06-14 21:16 ` Paul Eggert
2021-06-14 20:18 ` Matt Turner
2021-06-14 20:22 ` Adhemerval Zanella
2021-06-15 2:48 ` Siddhesh Poyarekar
2021-06-15 3:18 ` DJ Delorie
2021-06-15 17:41 ` Paul Eggert
2021-06-15 18:43 ` DJ Delorie
2021-06-15 19:05 ` Paul Eggert
2021-06-15 19:12 ` DJ Delorie
2021-06-15 19:35 ` Paul Eggert
2021-06-15 19:42 ` DJ Delorie
2021-06-15 20:08 ` Carlos O'Donell
2021-07-02 22:33 ` Carlos O'Donell
2021-07-03 1:59 ` Paul Eggert
2021-07-04 0:40 ` Paul Eggert
2021-07-04 11:55 ` Florian Weimer
2021-07-04 18:32 ` Paul Eggert
2021-07-04 23:25 ` Bradley M. Kuhn
2021-07-05 15:26 ` Christoph Hellwig
2021-07-06 18:02 ` Bradley M. Kuhn
2021-07-05 5:28 ` Carlos O'Donell
2021-07-05 20:21 ` Paul Eggert
2021-07-06 18:05 ` Bradley M. Kuhn
2021-07-06 19:42 ` Paul Eggert
[not found] ` <YOTTfm12jac/NYe5@ebb.org>
2021-07-07 8:51 ` Florian Weimer
2021-07-07 15:01 ` Joseph Myers
2021-07-05 5:00 ` Carlos O'Donell
2021-07-05 5:28 ` Florian Weimer
2021-07-05 20:37 ` Joseph Myers
2021-07-03 3:24 ` Bruno Haible
2021-07-05 5:53 ` Carlos O'Donell
2021-06-15 3:39 ` Daniel Black
2021-06-15 16:09 ` Josh Triplett
2021-06-16 13:01 ` Alyssa Ross
2021-06-16 14:08 ` Adam Sampson
2021-06-16 19:33 ` Joseph Myers
2021-06-16 19:45 ` Phil Blundell
2021-06-30 21:54 ` Bradley M. Kuhn
2021-07-01 5:24 ` Siddhesh Poyarekar
2021-07-01 19:33 ` Bradley M. Kuhn
2021-07-02 3:29 ` Siddhesh Poyarekar
2021-07-03 6:03 ` Eli Zaretskii
2021-07-01 8:19 ` Alexandre Oliva
2021-07-02 8:59 ` Florian Weimer
2021-06-30 22:21 ` Mark Wielaard
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=3e0c8f21-422b-ffd6-d939-49f88f09cac7@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=eliz@gnu.org \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).