Legal Team/Templatizing/ActionPlan

Action Items - Stage 1a: XML Conversion

Kris to put original "conversion" tool (to convert text files into XML format, to then be reviewed) in public repository so anyone else can use it or improve it (KRIS)
convert and add exceptions to repository (KRIS or someone from tech team using Kris' tool) and review exceptions to merge (ALL)
- note from Gary: tools don't care whether in same or different directory
convert and add deprecated licenses to repository (GARY) and review to merge (ALL)
- outcome: Proposed solution to add a boolean attribute named deprecated to the SPDX element with a default value of false. For the "+" deprecated licenses, we would copy the XML file, rename it to include the "+" and add deprecated=true to the SPDX attributed.
licenses tagged as "required acknowledgment" - were going to not merge and than add a tag to denote this --> decided to make this a future feature; keep labeling these for future update
- may need input from legal team at that point
true-up changes to existing licenses from 2.3 to current, 2.6 (ANYONE, see spreadsheet)
convert and add new licenses to repo from 2.4, 2.5. 2.6 (KRIS or someone from tech team using Kris' tool) and review to merge (ALL to review)
general clean-up of all licenses (once review is completed and all have been merged), e.g., remove body tag, fix lower case spdx tags, get rid of HTML &-; characters, and update tags as per tech team recommendations (someone from tech team) --> discuss at OSLS

Gary to bring to tech team for Sept 20 call, tech team to decide, with final review/sanity check by legal team - DONE
- process: build a table for existing field name (machine-readable name for these from current spec) and new XML tag - DONE
- Gary took to tech team, and had joint call with legal and tech team to finalize. Notes here: http://wiki.spdx.org/view/Technical_Team/Minutes/2016-10-25 and https://docs.google.com/document/d/1z9n44xLH2MxT576KS_AbTOBtecyl5cw6RsrrQHibQtg/edit
update tags as per tech team recommendations (see above)

As of Sept 16 call, Gary had done a first pass on tools to generate website and caught a bunch of validation errors, many of which were from lower case <spdx> tag. Gary to see what other validations were and fix and merge if simply or create pull request/submit to legal team if needs review
other updates to spdx-tools for new XML format (including website generation) - for 5 different formats? (Gary)
preview of website before release

Update info for README on Github for initial switch to Github from Git repo, prior to XML conversion (Dennis to draft, ALL review) - DONE
- completed - see here: https://docs.google.com/document/d/1kGSs3CXbtjF_uZmVsjhXMGChyP-pzlszktTr8t4PmmI/edit#
Review various webpages for updating (changes to be made now? or what until stage 2?) - Alan did first pass, which raised various questions and other things to address, need to revisit now that naming issue has been resolved with tech team
- license matching guidelines page
- license list overview page,
- info about XML tags (http://wiki.spdx.org/view/Legal_Team/Templatizing/tags-matching) - this may be more likely stage 2 and become part of spec as an appendix

update README (see above for link to text)
update any relevant webpages:
- links to master files
- page on requesting a new license - how to update, just point to README?
- what else?

to do so by hand is a bit tedious. Will still need human review before finalizing. Initial tool Kris used probably won't be applicable. Would be nice if this could be web-based
discuss with tech team, find someone to take this on?

i.e., how to request a new license, what kind of pull requests we want, underlying process etc.
included checking with Kate re: moving license list to Github primary (instead of LF Git and mirrored to Github)

revisions to current appendix in spec as to markup (e.g., var v. alt markup tag)
explanation of XML tags - to go in markup appendix or new appendix?