From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Derrick Stolee <stolee@gmail.com>, KOLANICH <kolan_n@mail.ru>,
git@vger.kernel.org, Derrick Stolee <dstolee@microsoft.com>,
Elijah Newren <newren@gmail.com>
Subject: Re: Could /Documentation/technical/commit-graph.txt be relicensed under a permissive license?
Date: Tue, 10 Dec 2019 14:20:21 -0800 [thread overview]
Message-ID: <xmqqeexbrffe.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20191210205056.GA14079@coredump.intra.peff.net> (Jeff King's message of "Tue, 10 Dec 2019 15:50:56 -0500")
Jeff King <peff@peff.net> writes:
>> What _could_ be problematic is repeating the documentation directly
>> in another permissive-licensed repository.
>
> That's my understanding as well. That said, I would not be opposed to
> some kind of statement in the documentation making our view explicit.
In principle, I do not mind that either.
But quite honestly, I cannot say that I am (or "want to be") all
that sympathetic.
It takes me some effort to convince myself that it is worth for us
to spend extra brain cycles even thinking about making such
statements, when those who would benefit the most from such an
effort are the ones who call the software we work on "contamination"
and proclaim that they cannot be bothered to spend the necessary
effort to comply with the license as a waste of time.
I'd be more receptive to those who are more friendly and
respectful---these things tend to be mutual.
next prev parent reply other threads:[~2019-12-10 22:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 19:31 Could /Documentation/technical/commit-graph.txt be relicensed under a permissive license? KOLANICH
2019-12-10 20:10 ` Junio C Hamano
2019-12-10 20:38 ` Derrick Stolee
2019-12-10 20:50 ` Jeff King
2019-12-10 17:18 ` Ed Maste
2019-12-10 20:58 ` Derrick Stolee
2019-12-10 22:20 ` Junio C Hamano [this message]
2019-12-11 0:36 ` KOLANICH
2019-12-11 12:57 ` Johannes Schindelin
2019-12-13 0:58 ` brian m. carlson
2019-12-15 2:29 ` Jakub Narebski
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=xmqqeexbrffe.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=kolan_n@mail.ru \
--cc=newren@gmail.com \
--cc=peff@peff.net \
--cc=stolee@gmail.com \
/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 NNTP newsgroup(s).