Difference between revisions of "General Meeting/Minutes/2014-02-13"

Revision as of 17:27, 13 February 2014

v2.0 overview and requirements are near final
- Still open to comments
- Will run through our tech doc process
Working on agenda for Collaboration Summit
- Tech Team will have a full day meeting on v2.0 at the venue on the Tuesday before
- We will have a track during the conference
  - Mix of presentations and working sessions
The search for a new co-lead is nearing completion

On going
- Some new license requests
- Marking up licenses
Fedora list resolution is somewhat stalled and needs a jumpstart
FOSDEM report
- There was a presentation on SPDX in the legal track
  - The presenter showed up late
  - Conference organizers were not happy with that and there were some issues with content
  - Did not reflect well on SPDX, so we need some quality control for conference presence.

OSI
- Phil has reached out to initiate more collaboration
- Hoping to initiate a meeting to discuss how we might cooperate in the OSI projects
  - License Chooser
  - License Compatibility Tools
  - Machine readable license text
- Aiming for a small joint meeting to kick off
Phil posted language describing direction in 2.0 spec section of SPDX.org
License Expression Syntax - MarkG
- Cross functional effort between Tech and Legal Teams to define formal but simple and flexible mechanism for expressing complex licensing of some packages (multiple licensing, exceptions, etc)
- Will essentially use Boolean operators and parentheses.
- Productive kick off meeting yesterday; agreement on the issue and reasonable alignment on the approach
- One more meeting before Collab Summit with the goal of having a draft for discussion at the Summit

@@ Line 45: / Line 45: @@
 ** Aiming for a small joint meeting to kick off
 * Phil posted [http://spdx.org/SPDX-specifications/spdx-version-2.0 language describing direction in 2.0 spec section of SPDX.org]
-* [[License_Expression_Review_1|License Expression Syntax]] - MarkG
+* [[Legal Team/License Expression Review 1|License Expression Syntax]] - MarkG
 ** Cross functional effort between Tech and Legal Teams to define formal but simple and flexible mechanism for expressing complex licensing of some packages (multiple licensing, exceptions, etc)
 ** Will essentially use Boolean operators and parentheses.