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/ripe-atlas@ripe.net/
[atlas] Survey results on Atlas open-sourcing
- Previous message (by thread): [atlas] Survey results on Atlas open-sourcing
- Next message (by thread): [atlas] Survey results on Atlas open-sourcing
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Simon Josefsson
simon at josefsson.org
Wed Jan 4 16:11:03 CET 2012
"Richard L. Barnes" <rbarnes at bbn.com> writes: > Analyze as you will :) One thing that strikes me from the discussion has been an absence of answers to this question: What would reasons be to _not_ release the source code? I believe that unless there is a strong reason not to release the source, it should be done because there is interest in it and there is potential to get improvements out of it. One reason could be that the current security architecture is based on obscurity, but that discussion wasn't conclusive if I remember correctly. In that case, releasing things gradually might be a good compromise, so that people can contribute a better security architecture. /Simon
- Previous message (by thread): [atlas] Survey results on Atlas open-sourcing
- Next message (by thread): [atlas] Survey results on Atlas open-sourcing
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]