Once upon a time, the tor spec files and proposals were in the Tor tarball, so they clearly were covered under Tor's copyright license (3-clause BSD).
But now they're in their own git repository.
I think maybe they technically have no copyright license now?
We should pick one (I vote cc-by) and try to apply it. This plan could become tricky for proposals, because there are a lot of authors on proposals by now.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
Until this ticket is resolved, I am marking the I2P proposal process document (derived from 001-process.txt) as 3-clause BSD under the assumption that it retains that license from having been part of the Tor tarball. I will update the license once this has been clarified. Please contact me if there are any issues :)
Please consider licensing specs under public domain. CC-0 seems to be the most portable solution.
Though public domain may not run on some state architectures.
Speaking personally, I support placing the whole thing under the most permissive license possible, and I don't know anything more permissive than CC-0. We still need to get a lawyer or three to sign off on us doing that. This looks like it's gonna take some time.
(I hereby license 100% of the text that I wrote in the tor-spec repository under the CC-0 license, to the extent that I am able to do so.)