I’m not complaining, but any of us involved in SPDX have learned how long and time-consuming standards work can be. Luckily we’ve got a great team and the work does have its rewards. We’ll all pop the corks when Version 1 is finalized, but there’s reason for a little celebration now, as well: The Open Source Initiative (OSI) has just adopted the SPDX short form license names, yippee!
podence's blog
Celebrate small victories (and cheers to the Open Source Initiative)
SPDX in International Free and Open Source Software Law Review
Paper by Kate, Esteban and Phil in IFOSSLR
Evolving the SPDX Group
As the SPDX group has evolved, it's been clear that the range of threads and moving parts are a lot for most participants. Three distinct work streams have emerged--technical, business and legal--and so we are evolving the organization in that direction with three different teams.
Technical Team- Primarily responsible for drafting the specification and providing documentation, samples, templates and tools.
Business Team- Initially focused on making sure that SPDX is successfully rolled out and responsible for the beta program, outreach, training, and everything else that surrounds the spec and makes it useable.
Legal Team- Responsible for the license list, coordinating with the Linux Foundation Member Counsel, trademarks and any other legal issues for SPDX.
SPDX and LF's Open Compliance Program
The SPDX Group is incredibly pleased to have the specification adopted as one of the key elements of the Linux Foundation’s Open Compliance Program. The Foundation has been supportive from the outset, but this is a huge step beyond. It was at LinuxCon in the fall of 2009 that I first met Kate Stewart chirping about for other birds of her feather, folks who shared the pain and were up for tackling the industry problem of exchanging package data. A number of us expressed interest, but it was Jim Zemlin and the Linux Foundation that gave the effort the home it needed as part of FOSSBazaar.
