Re: Where to put issues for "getting started with SPDX" documentation?

William Bartholomew (CELA)

I would put them in the spdx-spec repository, and we can label them as docs. One of the reasons for this is it allows us to address issues holistically, for example, the right thing to do might be to clarify the spec, create samples, and write new docs.


I was experimenting with some new getting started documentation, you can see some examples here:




William Bartholomew (he/him) – Let’s chat

Principal Security Strategist

Global Cybersecurity Policy – Microsoft


My working day may not be your working day. Please don’t feel obliged to reply to this e-mail outside of your normal working hours.


From: spdx@... <spdx@...> On Behalf Of VM (Vicky) Brasseur via
Sent: Tuesday, June 21, 2022 10:48 AM
To: spdx@...
Subject: [EXTERNAL] [spdx] Where to put issues for "getting started with SPDX" documentation?


Howdy, team.


In last week’s Outreach call we discussed the lack of “getting started with SPDX” documentation, info that could take someone from Zero to SPDX. Currently it’s really hard for new people to show up and use/generate/understand SPDX, but we can (with time) fix that.


We decided that step one of this would be to start collecting ideas for newbie questions that’ll need answering, etc. We’ll do this in issues to make it easier to keep track of them.


The next question is…where should those issues go? The -spec repo isn’t a good fit for them, neither is outreach. Do we perhaps need a new -docs repo…? I don’t know, but it’s worth considering. Or is this premature optimization and we should just pick a repo to log the issues in and then move them later if needed?


So what do y’all think? Where should these issues go for now?





VM (Vicky) Brasseur

Director, Senior Strategy Advisor

Open Source Program Office

Wipro Limited

Time Zone: Pacific/West Coast US


'The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.'

Internal to Wipro

Join to automatically receive all group messages.