1. Ideas for the SPDX™ WG 1

2. Onboarding New Participants SPDX™ WG need to have a plan for onboarding new participating companies. Example:  I am Company A that just joined SPDX™. How and where can I get involved? and doing what?  What resources are available to me to educate my 1) compliance team and 2) my developers?  What’s on the SPDX™ WG plate right now in terms of to-do list? What’s hot priority? Etc. 2

3. Identify to new comers where and how to get involved. Examples below. Contact the lead(s) of the team(s) you want to contribute to, get briefed on current state of affairs, and where help is needed the most. Join the mailing lists and participate in the discussions. Attend the calls as scheduled by the various teams. Submit feedback on the specifications following the process set in place. Submit bug reports/code contributions to the tools following the development process set in place. Submit new use cases, or feedback on existing ones Join SPDX™ track at Linux Foundation conferences. Create content for SPDX™: papers, web site improvements, blogs, etc. Create SPDX™ files for your favorite open source projects

4. Identify, Accommodate and Encourage Different User Scenarios Provide guidance for the various general users of SPDX™:  Users who generate SPDX™ files for downstream users  Users who request SPDX™ files from upstream suppliers  User who know how to use, update and maintain an SPDX file that comes in, and who passes that SPDX downstream How to provide guidance?  Documentation: How-to style to educate uses about using SPDX™ and also proper ways to submit feedback & questions or even request help for complex cases that the SPDX™ specs may have not covered yet.  Users 1-day Forum: Parallel to other SPDX™ or Linux Foundation events. The focus of such a forum is to provide tutorial/training style presentations on using SPDX™.  Hosted SPDX™ seminars: These seminars could be hosted at companies that are on their way to or have already adopted SPDX™ and they need to educate their (compliance) teams.

5. Open Source Community Reach-Out Getting community feedback on specs  Open source organization (Apache, Eclipse, Mozilla, etc.)  Linux Foundation Technical Advisory Board  Others ? Getting open source projects to start using SPDX™  Provide (updated) examples to follow (that applies to latest spec  SPDX™ participants volunteering to create SPDX™ files for open source projects they heavily use  Etc. Building developer community around existing SPDX™ tools  A way to engage open source developers in SPDX™

6. Your company is a member of SPDX™ WG A B C Your company is not a member of SPDX™ WG Participate in SPDX™ WG A B C Educating Developers

7. Educating Open Source Developers If you are a maintainer for an open source project and you want to use SPDX™:  A?  B?  C? If you are a contributor to an open source project:  Sending new code:  Updating existing code: If you want to contribute SPDX™ spec file for an open source project:  A?  B? If you are a user of an open source project that use SPDX™:  You discover an error:  B?

8. Create and Publish a Release Methodology for Specs and Tools (Example below) CURRENT 1.1 Release Date (1.1) NEXT 2.0 Release Date (2.0) FUTURE 3.0 All roadmap items that are not prioritized for 2.0 will be automatically pushed to the roadmap of future release All features/release are defined and tracked Example Prioritization Model: This requires a certain prioritization model for what gets into the roadmap, such as: P1 – To be included in this current. Necessary and pre-requisite for other features/use cases. P2 – To be included in current release only if certain conditions are met. P3 – Pushed to future release: Requires significant changes. Etc. 2.1 2.2 Dot releases would be reserved for minor updates to the specs often related to fixes and feedback received Release Date (3.0) Release Cadence: Between major releases: 12 months

9. 2012 Structure:  Finalize and approve governance  Finalize and publish charter (mission, goals, vision)  Publish roadmap Releases:  Specs  Tools Content:  New deck for recruitment purposes  New data sheet  SPDX.org F2F Meetings: Event Presence:  Open Compliance Summit (Tokyo, Oct 24-25)  Track and F2F at LinuxCon EU (Nov 5-7) Etc. 2013 Releases  ??/??: SPDX™ 2.0  ??/??: Updated tools Content:  New paper following 2.0 release  New webinar F2F Meetings:  Collaboration Summit  LinuxCon NA  LinuxCon EU Event Presence  Presentation at LinuxCon NA/EU/JP  Presentation at Auto Summit  Presentation at Open Compliance Summit  0.5 day seminar at “event A and B” Etc. Identify and Publish Major Milestones 2012- 2013 (example below)

10. Create a Visual Roadmap and Publish Online 2012-2013 – Example below ReleasesContentEventF2F 08/1209/1210/1211/1212/1201/1302/1303/1304/1305/1306/13 LinuxCon NA Aug 29-31 Compliance Summit Oct 24-25 LinuxCon EU Nov 5-7 Collaboration Summit SPDX F2F San Francisco SPDX™ 1.1 Paper on SPDX 1.1 Updated SPDX Tools SPDX F2F Data Sheet and PPT Deck Auto Summit Sep 19-20 Finalize Governance SPDX.org Completed Ongoing recruitment activities to get new members and increase adoption

11. Draft Roadmap 2013-2014 07/1308/1309/1310/1311/1312/1301/1402/1403/1404/1405/14 ReleasesContentEventF2F