Hi Kris, Jilayne and legal team,
I'm seeing a lot of activity on the XML licenses, so I started looking into expanding the tools that generate the website to support the new XML format. Here's what I'm currently thinking: - write a new command line tool which takes three parameters, a tag name for the Git repo, a release date and the output directory. The tag name must also be the version name used on the website. The default for the tag is just the latest from master and the default for release date would be today's date. - The application would fetch the XML files from git and translate them into the different file formats including the files used to push to the website. A few questions: Would it make sense to have an XML file that describes the release date and version name in the repo? This would eliminate the second parameter to the application and provide better control over the release name. Another alternative would be to pull this info out of the git commit (use the date of the commit itself for the release date). Once I get this up and running, do you want me to post the results to spdx.org/licenses/preview? Also - Anything else you want me to fix while I'm in there (like the OSI text in the individual license pages)? Let me know your thoughts. Thanks, Gary ------------------------------------------------- Gary O'Neall Principal Consultant Source Auditor Inc. Mobile: 408.805.0586 Email: <mailto:g...@sourceauditor.com> g...@sourceauditor.com
_______________________________________________ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
