Technical Team/Minutes/2017/05/09¶
Archived page
Read-only copy of the SPDX wiki. The wiki is no longer active; its content has moved to https://github.com/spdx. Last edited 2017-05-16 by K.stewart.
April 4, 2017
Attendees¶
- Thomas Steenberger
- Alexios Zavros
- Yev
- Brad
- Uday Korlimarla
- Philippe Ombredanne
- Jack Manbeck
- Kate Stewart
Agenda¶
- Google of Summer of Code Approved Projects (Philippe)
- Tranfer of Specification to GitHub project (Thomas)
- Review of features for next revision of Specification (Kate & all)
Minutes¶
- GSoC
- GSoC - 4 students slotted and selected.
- license coverage grader
- online validation tool - server side. python.
- validation of license expressions. java
- github integration.
- Everything takes place in open. Define logistics.
- All communication should go through mailing list.
- Code developed in open in github, private repository, move over afterwards.
- Frequent online chat with students. use #SPDX channel?
- Spec Hosting --> Github
- Thomas demonstrated what he’s done with conversion. github.com/tsteenbe/specification.
- Finishing off License list expressions. Lot of links still need to be cleaned up.
- Building it with gitbook.io. Converting to version 4. Thomas waiting for repository on other side.
- Phillipe: Proposes prefix repo name with SPDX - so spdx-specification. Will relabel existing "spec" as spdx-vocabulary possibly tagging/noting as 1.2, all ok with it.
- Thomas: Writing in gitbook like plugins. So everyone can contribute.
- Next Spec
- Then transitioned to working on Topic list for next rev of specification.
- https://docs.google.com/document/d/1vJqWGU02ynzrJ5CvmX1z2mBssOSpuBvuKene8jVJGNI/edit
- Agreement on
- Deprecating SHA1 (implies next rev will be 3.0)
- Expanding relationship between elements
- Need further discussion with missing people on:
- Relationship between license list elements (Gary)
- Conditional License Expressions (Mark)