Enhance documentation and actionability of license information

[cthoyt]

While an ontology can contain licensing information in its own metadata, that's not the typical place people look for license text while browsing repositories on GitHub - it's desirable to have a file called LICENSE in the root of the repository that has standard license text as well. This is so ubiquitous, that GitHub even parses these and structures the metadata so it's accessible through the GitHub API.

I'm going to write a script that scrapes the OBO Foundry ontologies' repos and auto-generates PRs with the appropriate license text. I'll refer back to this issue and update this text with more information.

The code I'm using to automate creating PRs

import pandas as pd
import webbrowser
from bioregistry.external.obofoundry import get_obofoundry

MAPPING = {
    "CC BY 4.0": "cc-by-4.0",
    "CC0 1.0": "cc0-1.0",
}


def main():
    df = pd.read_csv("data/data.tsv", sep='\t')
    prefixes = dict(df.loc[df.license.isna(), ["prefix", "default_branch"]].values)
    obo = get_obofoundry()
    for prefix, default_branch in prefixes.items():
        data = obo[prefix]
        repository = data["repository"].rstrip("/")
        if "github" not in repository:
            continue
        ontology_license = data["license"]
        key = MAPPING.get(ontology_license)
        if not key:
            continue
        url = f"{repository}/community/license/new?branch={default_branch}&template={key}"
        webbrowser.open_new_tab(url)


if __name__ == '__main__':
    main()

The standard text I'm using in the PRs:

This pull request is part of an initiative to make the licensing information about OBO Foundry ontologies more actionable.

While this ontology contains licensing information in its metadata, GitHub is not aware of the license unless you create a `LICENSE` file with standardized text. This PR creates a `LICENSE` file with the standard text for the CC BY 4.0 license. 

More information about this initiative and further discussion is taking place here: https://github.com/OBOFoundry/OBOFoundry.github.io/issues/1840.

[matentzn]

This is totally crazy and totally awesome, both at the same time.