Gary O'Neall

Here's documentation on how to rename the branch: https://git-scm.com/book/en/v2/Git-Branching-Branch-Management It will also require an update to the Github actions. Also - everyone who has cloned the repo will likely need...

> do you foresee any changes needed to the License List Publisher itself, or just the branch name listed in the Github Actions config files Just the latter - no...

> do we need to discuss any aspects of what it means to make the XML files as a stable standard format (other than saying that)? Good question. I opened...

@zvr Good point - my last comment is definitely out of date. If we make the license XML official, all the fields should be documented. I'm still traveling for the...

Pinging @jlovejoy and @swinslow to review the above meeting proposal and discussion.

Reference https://github.com/spdx/license-list-XML/pull/1396#issuecomment-1112709802 Perhaps we should have a real-time discussion on this to finally decide what the solution is? I can support any reasonable solution with changes in the LicenseListPublisher.

Is the proposal to: A) maintain a separate repo which consumers would access directly B) maintain a separate repo which would be the source data for canonical text being which...

Just FYI - one of the recent GSoC projects implemented a license text scraper in the LicenseListPublisher for the purpose of verifying the license URL's. Some of that code could...

> hasn't this been done? Nope - still using a Makefile which I/we don't have much expertise to maintain.

@jlovejoy Is this really a technical issue? Someone(s) need to go through and make sure we are not miss-using the copyright field - not something that can be automated in...