git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Can I use CRoaring library in Git?

From
Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
Date
Jul 21, 2022, 14:57 UTC
Message-ID
<CAPOJW5zA1FnLDWXgRza3WLCHK0ER7ZUkdyq-kcPm4-TsW9U2nA@mail.gmail.com>
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:

Show 7 quoted lines
>
> 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?
Show 13 quoted lines
> 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 :)
Previous: Ævar Arnfjörð BjarmasonNext: Ævar Arnfjörð Bjarmason
Message 24 of 25 in “Can I use CRoaring library in Git?”
  1. Abhradeep ChakrabortyJul 16, 2022
  2. Ævar Arnfjörð BjarmasonJul 16, 2022
  3. Abhradeep ChakrabortyJul 16, 2022
  4. Kaartic SivaraamJul 17, 2022
  5. Junio C HamanoJul 17, 2022
  6. Taylor BlauJul 17, 2022
  7. Abhradeep ChakrabortyJul 18, 2022
  8. Taylor BlauJul 25, 2022
  9. Derrick StoleeJul 17, 2022
  10. Jakub NarębskiJul 18, 2022
  11. Abhradeep ChakrabortyJul 18, 2022
  12. Ævar Arnfjörð BjarmasonJul 18, 2022
  13. Abhradeep ChakrabortyJul 18, 2022
  14. Derrick StoleeJul 18, 2022
  15. Abhradeep ChakrabortyJul 18, 2022
  16. brian m. carlsonJul 18, 2022
  17. Taylor BlauJul 25, 2022
  18. rsbecker@nexbridge.comJul 25, 2022
  19. Taylor BlauJul 25, 2022
  20. Abhradeep ChakrabortyJul 21, 2022
  21. Junio C HamanoJul 21, 2022
  22. Derrick StoleeJul 21, 2022
  23. Ævar Arnfjörð BjarmasonJul 21, 2022
  24. Abhradeep ChakrabortyJul 21, 2022
  25. Ævar Arnfjörð BjarmasonJul 22, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.