Tracking issue for RFC 2044: dual-MIT/Apache2 licensing

This is a tracking issue for RFC 2044 (thread, rendered), to put the rust-lang/rfcs repo under dual MIT/Apache-2 licensing terms.

Necessary steps for execution:

Asking past contributors to agree with the licensing terms (with <=40 contributors each to bypass the github mention limit of 50):

And further:

PR to rust-lang/rfcs to add LICENSE-MIT and LICENSE-APACHE files, talk about the licensing situation in the README, and edit the template to include the header: Add note of the RFC 2044 licensing process to README and update template rfcs#2075
Asking first time contributors who opened PRs before the PR above got merged to agree with the terms: Licensing sign off issue for first time contributors rfcs#2096
PR to rust-lang/rfcs to signify the licensing change is complete. Doable once every (or almost every) contributor has signified consent with the licensing terms. Also, figure out what to do about the contributions by people who didn't give their consent: ~~Remove files with contributions from the people where no approval of the licensing terms was received rfcs#2193~~

In order to document my process, a short note on methodology on how I've obtained the list of github names. I can't use the "contributors" page for that (nor the corresponding github api call), as a) both have limits to only show the top 100 contributors, and b) both completely ignore people not registered on github, or people with git configurations that are not set up to be recognized by github.

So I did the following:

created a directory hashes
obtain a list of commits, ordered by author. git shortlog --format="%H" > shl
pipe that list to the bash script f.sh attached below and sort out dupes (where people used different emails or similar): cat shl | ./f.sh | sort | uniq. Note that I gave myself a github token and used it to authenticate, to get higher rate limits, so the curl command I used was also adjusted to send the token.
This gave me a list of github account names, and for broken configs, it gave me "null HASH" entries. Also one entry invalid-email-address which I found out by grepping for that string in the hashes directory

The bash script reads in the list of commits ordered by author, and for each author, it takes the first commit mentioned, and obtains information about the commit via the github api, and stores it in a json file in the hashes directory. Then it extracts author info from that json file and prints it on stdout.

#!/bin/bash

while read author; do
	read hash;
	[ -f hashes/$hash ] || \
	curl -f "https://github.com/proxy/api.github.com/repos/rust-lang/rfcs/commits/$hash" -o hashes/$hash || \
	echo "Error for commit $hash"
	[ -f hashes/$hash ] && cat hashes/$hash | jq -r -e '.author.login' | sed "s/^null$/null $hash/"
	while read hash; do
		[ -z "$hash" ] && break
	done
done

I don’t know if it legally matters, but all four sign-off issues have a typo: “to chose” instead of “to choose”.

I left a comment in the pull request, regarding the proposed license header for RFCs; please take a look at that before you start adding license headers to individual RFCs.

@pnkfelix

@pnkfelix I'm unlocking this issue since it seems to have been locked by accident. If it was intentional feel free to lock it again (and perhaps leave a comment as to why it is being locked).

@barosl

Status in Oct 2019: Most contributors has signified consent.

The remaining people and their merged PRs are:

Added links to above comment. Also added information about two another RFCs whose major authors are others but they have commits in them.

Tom's contribution isn't substantial (it's a link being changed) and doesn't need copyright assignment.

It's only barosl left at this point, and they've received recent contact. Whether or not that leads to a response remains to be seen, but I'm optimistic considering recent activity.
Jakub Bukaj, listed as deleted user, is now @ jakubadamw and he gave consent in tracking issue 4/4.

Navigation Menu

Repository navigation

Tracking issue for RFC 2044: dual-MIT/Apache2 licensing #43461

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Tracking issue for RFC 2044: dual-MIT/Apache2 licensing #43461

Description

Activity

est31 commented on Jul 25, 2017

dscorbett commented on Jul 25, 2017

joshtriplett commented on Jul 26, 2017

jonas-schievink commented on May 18, 2019

crlf0710 commented on Oct 11, 2019

crlf0710 commented on Jan 8, 2020

Manishearth commented on Jan 8, 2020

RivenSkaye commented on Apr 23, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions