Hi Varshak, Welcome! Glad you're interested in participating in our community. I am copying the spdx-tech mail list where we discuss the GSoC efforts. Ideas we've come up with so far are listed on: ht

#spdx

Hi Varshak, Are you looking to work on a google summer of code project for SPDX or help contribute to the SPDX tools or specification, etc.,. (not google summer of code)? Thanks Jack

#spdx

Hello ! I have been following spdx and would love to contribute to the python tools. I would need some guidance as to how to get started with my first task . Thanks !

#spdx

Hi , I, Kumar Saurabh, a final year student at IIIT Bhubaneswar, majoring in Computer Science and engineering. Being passionate about product development, I find developing application development exc

#spdx

66391666391

#spdx

Hi, Have just finished setting up a #spdx IRC channel on freenode, to be used for ongoing SPDX project communication and collaboration. Was just going to send this to the tech list, but realized its m

#spdx

Hi I am Hardik and I am very much interested to begin my GSoC journey. I wish to be an aid to grow and add up to SPDX and in the process, I would enhance my skills and grow as well. However, this is s

#spdx

Hi, my name is Stratu Catalin. I have completed my GSOC proposal, how can I get feedback? The project I am applying for is Update of Go SPDX libraries to handle latest spec. Thanks.

#spdx

Hi Sandeep – Moving the conversation over to the SPDX-tech mailing list. Unfortunately, adding in a CPE ID or pURL would include characters disallowed in the SPDX ID. Fortunately, there is a way to ex

#spdx

Hi Chris, I think this is a valid use case and one I’ve thought about as well. Using the URI’s for listed licenses in RDF format would still be a valid SPDX document and much more compact. The changes

#spdx