Opened 3 years ago

Last modified 18 months ago

#18788 accepted enhancement

Make the copyright license clear for torspec and proposals

Reported by: arma Owned by: nickm
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: license, copyright, 034-triage-20180328, 034-removed-20180328
Cc: wseltzer Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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.

Child Tickets

Change History (15)

comment:1 Changed 3 years ago by arma

Cc: wseltzer added

comment:2 Changed 3 years ago by str4d

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 :)

comment:3 Changed 3 years ago by nickm

Milestone: Tor: 0.2.9.x-final

comment:4 Changed 3 years ago by nickm

Keywords: license copyright nickm-deferred-20160905 added
Milestone: Tor: 0.2.9.x-finalTor: 0.3.0.x-final

We need a license person to look at this. Moving out of 0.2.9 for now since I don't know when somebody will be available.

comment:5 Changed 3 years ago by twim

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.

comment:6 Changed 3 years ago by nickm

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.)

comment:7 Changed 3 years ago by dgoulet

Keywords: triage-out-030-201612 added
Milestone: Tor: 0.3.0.x-finalTor: unspecified

Triaged out on December 2016 from 030 to Unspecified.

comment:8 Changed 2 years ago by nickm

Keywords: triage-out-030-201612 removed

comment:9 Changed 2 years ago by nickm

Keywords: nickm-deferred-20160905 removed

comment:10 Changed 2 years ago by nickm

Milestone: Tor: unspecifiedTor: 0.3.2.x-final
Priority: MediumHigh

comment:11 Changed 2 years ago by nickm

Owner: set to nickm
Status: newaccepted

comment:12 Changed 2 years ago by nickm

Milestone: Tor: 0.3.2.x-finalTor: 0.3.4.x-final

comment:13 Changed 18 months ago by nickm

Keywords: 034-triage-20180328 added

comment:14 Changed 18 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:15 Changed 18 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

Note: See TracTickets for help on using tickets.