PROJ Provenance Review

See the guidelines for the provenance review here: https://wiki.osgeo.org/wiki/Code_Provenance_Review

Project History

Summarise the history of the source code, including discussion about code ownership and license over time.

Libraries

List or reference a table of included libraries and/or components. Include:

• Library Name
• License
• Whether the library licence is compatible with the project
• Whether the library is compiled into the project's releases, or required as an external dependancy
• Whether the library is included in the project's code repository
• Issue? (link if issue if one exists)
• Ok? (Yes/No/Black - implies not checked yet)
• Comment(s)

Library	License	Compatible?	Included in core?	Issue(s)?	OK?	Comments
SQLite	Public Domain	Yes	No		Yes
nlohmann/json	MIT	Yes	Yes		Yes
lrucache11	BSD	Yes	Yes		Yes	License and author is attributed in the relevant source file

Source Files

List of source files, including code, documentation and data, including:

• File name
• License
• Copyright Holder (if known)
• License header included?
• Issue? (link if issue if one exists)
• Ok? (Yes/No/Black implies not checked yet)
• Comment(s)

The list of source files and their license status is maintained on Google Docs:

https://docs.google.com/spreadsheets/d/1Bdu73lw8I1iFX4cb7CIUF6yqWGDTcZKBfW0cUsEjCXk/edit?usp=sharing

Copyright Holders

List or reference all copyright holders of the project's source files. These are all the people that would need to be contacted if the license of the project is to be changed. List:

• Organisation or person
• Contact details for Organisation or person
• Issue? (link if issue if one exists)
• Comments

Copyright Holder	Contact details	Issue?	Comments

Committers

List or reference a table of committers, including:

• Committer name
• Commit username in code repository
• Committer's employer(s) (if applicable)
• Committer (or employer) has signed contribution agreement? (yes/no)

Committer	Username	Affiliation	Contribution Agreement Signed?	OK?
Frank Warmerdam	warmerdam		No	Yes
Even Rouault	rouault	Spatialys	No	Yes
Kristian Evers	kbevers	SDFE	No	Yes
Thomas Knudsen	busstoptaktik	SDFE	No	Yes
Howard Butler	hobu	Hobu Inc	No	Yes
Mike Taves	mwtoews	GNS Science	No	Yes
Kurt Schwehr	schwehr	Google	No	Yes
Charles Karney	cffk		No	Yes

The project has opted to not ask committers to sign a contribution agreement because 1) the MIT license is permissive which eliminates the desire to re-license the software, 2) it's an added layer of complexity to the project and 3) some developers has expressed that they will not sign such an agreement. An article on the problems with instating a contribution agreement can be found here

Further Issues

List or reference a list of any outstanding issues not already listed above. Typically link to issues in project's issue tracker.