From: Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Derrick Stolee" <derrickstolee@github.com>,
"Junio C Hamano" <gitster@pobox.com>, git <git@vger.kernel.org>,
"Taylor Blau" <me@ttaylorr.com>,
"Kaartic Sivaraam" <kaartic.sivaraam@gmail.com>,
"Jakub Narębski" <jnareb@gmail.com>
Subject: Re: Can I use CRoaring library in Git?
Date: Thu, 21 Jul 2022 20:27:43 +0530 [thread overview]
Message-ID: <CAPOJW5zA1FnLDWXgRza3WLCHK0ER7ZUkdyq-kcPm4-TsW9U2nA@mail.gmail.com> (raw)
In-Reply-To: <220721.86r12etvly.gmgdl@evledraar.gmail.com>
On Thu, Jul 21, 2022 at 7:29 PM Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
>
> It's great that the primary author of the library wants to release it
> under a compatible license.
>
> But I feel like I'm missing something here, don't we still need the
> other contributors to that code to sign off on such a license change,
> and for us to be comfortable with integrating such code?
As far as I see their commits, they don't use sign-off in any of their commits.
I know what you want to mean but the license text uses "The CRoaring
authors" rather than "Daniel Lemire". Below is the text -
/*
* MIT License
*
* Copyright 2016-2022 The CRoaring authors
*
* Permission is hereby granted, free of charge, to any
* person obtaining a copy of this software and associated
...
*/
So, isn't it enough for us?
> My understanding (again, not a lawyer and all that) is that such
> transitions happen one of a few ways:
>
> A. One entity had been assigned copyright in the first place, and can
> re-license the work. E.g. the FSF requiring copyright assignments
> for anything non-trivial.
>
> B. The license itself has an "upgrade" clause (e.g. GPLv2 "or later"
> projects being GPLv3 compatible).
>
> C. All copyright holders (or near enough) agree to
> relicense. E.g. OpenStreetMap went through this process at some
> point.
I got your point here. I am sure that "All copyright holders" have no
problem with this relicensing.
Daniel already said in his comment[1] that they do not have any problem with it.
[1] https://groups.google.com/g/roaring-bitmaps/c/0d7KoA79k3A/m/t8e09-wPAgAJ
Thanks :)
next prev parent reply other threads:[~2022-07-21 14:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 13:50 Can I use CRoaring library in Git? Abhradeep Chakraborty
2022-07-16 14:16 ` Ævar Arnfjörð Bjarmason
2022-07-16 16:26 ` Abhradeep Chakraborty
2022-07-17 12:25 ` Kaartic Sivaraam
2022-07-17 22:00 ` Junio C Hamano
2022-07-17 22:25 ` Taylor Blau
2022-07-18 8:57 ` Abhradeep Chakraborty
2022-07-25 22:11 ` Taylor Blau
2022-07-17 14:43 ` Derrick Stolee
2022-07-18 11:13 ` Jakub Narębski
2022-07-18 11:38 ` Abhradeep Chakraborty
2022-07-18 13:38 ` Ævar Arnfjörð Bjarmason
2022-07-18 11:48 ` Abhradeep Chakraborty
2022-07-18 12:18 ` Derrick Stolee
2022-07-18 13:15 ` Abhradeep Chakraborty
2022-07-18 21:48 ` brian m. carlson
2022-07-25 22:14 ` Taylor Blau
2022-07-25 22:35 ` rsbecker
2022-07-25 23:37 ` Taylor Blau
2022-07-21 4:07 ` Abhradeep Chakraborty
2022-07-21 6:12 ` Junio C Hamano
2022-07-21 12:14 ` Derrick Stolee
2022-07-21 13:51 ` Ævar Arnfjörð Bjarmason
2022-07-21 14:57 ` Abhradeep Chakraborty [this message]
2022-07-22 11:07 ` Ævar Arnfjörð Bjarmason
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPOJW5zA1FnLDWXgRza3WLCHK0ER7ZUkdyq-kcPm4-TsW9U2nA@mail.gmail.com \
--to=chakrabortyabhradeep79@gmail.com \
--cc=avarab@gmail.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=me@ttaylorr.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).