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]/
Re-homing of RAToolSet to RIPE NCC
- Previous message (by thread): Re-homing of RAToolSet to RIPE NCC
- Next message (by thread): Re-homing of RAToolSet to RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Bill Manning
bmanning at ISI.EDU
Thu Oct 4 14:13:36 CEST 2001
% Like I said, most (techie) people don't give a hoot, but legal % departments at largish outfits can seriously halt Progress(tm). Although % RIPE and the RIPE NCC are non-profit organisations, most of the members % are most definitely out to make a (euro-)buck. It's only proper that if % these tools are to be hosted/provided/maintained by the RIPE NCC, that % the restrictive license is removed. Replacing it with a RIPE/RIPE NCC % copyright may make non-RIPE members nervous, so I still think a GNU-like % license is the safest and fairest option. I spect that the USC tag still claims that it needs to stay w/ the code so RIPE would need to do a "clean-room" reimplementation to expunge the USC tag. Of course RIPE could also cut a deal w/ USC on broad commercial use of the tools. That has often proved to be the cheapest/easiest course. % % Cheers, % Steven % -- --bill
- Previous message (by thread): Re-homing of RAToolSet to RIPE NCC
- Next message (by thread): Re-homing of RAToolSet to RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]