Re: 3.3 release update, meeting minutes
I took a look at the automated build failures under #1 below.
I think it would be good for the tooling to generate the license text, but it currently does not do this (we didn’t think about that need until just now). I’m struggling with the workflow/user interface for how this can be accomplished.
For this release, we can manually upload the license text.
I just updated the workflow document to include a suggested approach. Jilayne – if you could test this out and see if it works.
I also noticed that the branch used for these pull requests are behind the commits in the license-list-XML repo. I think if you check the “update “ box in the tool, it will update the repository for you.
As far as the stale files - I’m not sure this is the best approach (in fact, I’m pretty sure it is not the best approach) you can the files you don’t want to change from the license-list-XML repo master branch and they should show up as unchanged in your PR. Others more github savvy than me can advise on the better approaches.
From: Spdx-legal@... <Spdx-legal@...> On Behalf Of Steve Winslow
Sent: Thursday, October 11, 2018 4:00 PM
To: J Lovejoy <opensource@...>
Cc: SPDX-legal <spdx-legal@...>
Subject: Re: 3.3 release update, meeting minutes
Hi Jilayne, for #1 I'll take a look at the XML files and will add comments in the PRs.
But, someone else with more Git / Github skills than me may need to weigh in on separating out files per your second bullet point in #1, I'm not sure how to handle that...
On Wed, Oct 10, 2018 at 6:00 PM J Lovejoy <opensource@...> wrote: