This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[routing-wg] Open-sourcing of the RIPE NCC’s RPKI core software
- Previous message (by thread): [routing-wg] Open-sourcing of the RIPE NCC???s RPKI core software
- Next message (by thread): [routing-wg] rsync://rpki.ripe.net rsyncd limits set too low?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Cynthia Revström
me at cynthia.re
Wed Feb 16 15:50:49 CET 2022
Hi, On Thu, Feb 10, 2022 at 6:35 PM Shane Kerr <shane at time-travellers.org> wrote: > > I'm a little disappointed that you didn't choose a copyleft style > license, like with the RIPE Atlas Software Probe, which uses GPLv3. That > would help ensure that the work of the RIPE NCC employees is not used by > a proprietary product or service by a company unwilling or unable to > share their changes. Probably in the presentation at RIPE 84 there will > be a bit of explanation about the choice of using a license so easy to > convert back to closed source. 😉 There are issues regardless of what license you pick and remember that there are proprietary HSM dependencies used, which could potentially cause issues with GPLv3 for the NCC itself as far as I understand it. -Cynthia
- Previous message (by thread): [routing-wg] Open-sourcing of the RIPE NCC???s RPKI core software
- Next message (by thread): [routing-wg] rsync://rpki.ripe.net rsyncd limits set too low?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]