https://wiki.spdx.org/api.php?action=feedcontributions&feedformat=atom&user=Zvr 2026-05-07T11:48:36Z User contributions MediaWiki 1.23.13 https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2022-03-01T16:50:35Z

<p>Zvr: /* Ideas for 2022 Projects */</p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2022 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> = Ideas for 2022 Projects =<br /> <br /> == SBOM Conformance Checker ==<br /> The goal of this project is to create a simple tool that<br /> checks whether an SBOM (in SPDX format)<br /> conforms to NTIA's minimum elements guidance.<br /> === Description ===<br /> The SPDX Specification defines a number of fields (elements) that may appear in an SBOM (Software Bill of Materials).<br /> Not all of them are mandatory, however, so SBOMs in SPDX format can vary greatly.<br /> <br /> While researching the attributes that have to be present in an SBOM,<br /> NTIA came up with a guidance about the minimum elements that must appear therein:<br /> https://www.ntia.doc.gov/files/ntia/publications/sbom_minimum_elements_report.pdf<br /> <br /> It would, therefore, be useful to have a tool that can determine whether an SBOM stored in SPDX format<br /> fulfills all such minimum obligations.<br /> <br /> The tool should make use of the already existing libraries for reading SPDX documents<br /> === Technologies ===<br /> Python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> It might be extended to a long (350 hours) project if integration<br /> with the existing SPDX handling tools (e.g., the Validation tool)<br /> is also implemented.<br /> === Mentors ===<br /> Dick Brooks, Kate Stewart<br /> <br /> == Private license management system ==<br /> A web-based system for managing license texts; similar to the SPDX License List but oriented towards other private collections of licenses.<br /> === Description ===<br /> The goal of the project would be to create a simple web application<br /> for people to upload license texts<br /> and automatically create a license repository.<br /> The initial rough &quot;functional specifications&quot; describe it as<br /> mainly an input form, where the information is entered.<br /> There will be some automatic processing (e.g., canonicalization, duplicate avoidance, etc.),<br /> a review/approval (and naming) step,<br /> and then publishing in a specified format.<br /> <br /> It should be noted that the specification is not yet finalized<br /> regarding naming namespaces, way to publish licenses, etc.<br /> If the SPDX project has already advanced in these definitions,<br /> this project will obviously implement the decisions taken.<br /> === Technologies ===<br /> Python (any framework) for the back-end; JavaScript (any framework) for the minimal front-end.<br /> === Duration ===<br /> This can be either a short (175 hours) project, implementing only the basic functionality;<br /> or a long (350 hours) one, implementing more functionality and automation.<br /> === Mentors ===<br /> Alexios Zavras; more TBD<br /> <br /> == SBOM combiner ==<br /> The project will result in a simple command-line tool that will be able to “combine” information from a number of SBOMs into a comprehensive SBOM that includes all the information of the provided ones.<br /> An actual use case would be the generation of an SBOM for an actual software delivery that is comprised by a number of components, each one of which has its own correct SBOM.<br /> === Description ===<br /> The primary purpose of this tool would be<br /> to stitch together smaller component-level SPDX documents<br /> and amalgamate them into one top-level SPDX document<br /> representing a &quot;sum of parts&quot; piece of software.<br /> As an initial pass for implementation, the component-level SBOMs would have to be provided by the caller<br /> until the tool was advanced enough to fetch SPDX Documents referenced by ExternalDocumenRef reliably. <br /> === Technologies ===<br /> Python (preferably); or Go.<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> Rose Judge; others TBD<br /> <br /> == Update of Java SPDX libraries to handle latest spec ==<br /> === Description ===<br /> The SPDX Project maintains a library, written in Java, for working with SPDX data.<br /> The development of the library does not always follow the development of the specification immediately.<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Java libraries<br /> capable of handling the latest spec.<br /> <br /> The project will involve obviously understanding deeply<br /> the existing libraries<br /> and extending them to handle the latest additions<br /> of the specification (to the point of the published version).<br /> === Technologies ===<br /> Java; see https://github.com/spdx/Spdx-Java-Library<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> == Update of Go SPDX libraries to handle latest spec ==<br /> === Description ===<br /> The SPDX Project maintains a library, written in Go, for working with SPDX data.<br /> The development of the library does not always follow the development of the specification immediately.<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Go libraries<br /> capable of handling the latest spec.<br /> <br /> The project will involve obviously understanding deeply<br /> the existing libraries<br /> and extending them to handle the latest additions<br /> of the specification (to the point of the published version).<br /> === Technologies ===<br /> Go; see https://github.com/spdx/tools-golang<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Update of Python SPDX libraries to handle latest spec ==<br /> === Description ===<br /> The SPDX Project maintains a library, written in Python, for working with SPDX data.<br /> The development of the library does not always follow the development of the specification immediately.<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Python libraries<br /> capable of handling the latest spec.<br /> <br /> The project will involve obviously understanding deeply<br /> the existing libraries<br /> and extending them to handle the latest additions<br /> of the specification (to the point of the published version).<br /> === Technologies ===<br /> Python; see https://github.com/spdx/tools-python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == More to come... ==<br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Duration===<br /> whether this is a short or a long project<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal.<br /> <br /> = Historical info =<br /> <br /> [[GSOC/PastProjectIdeas]]</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2022-02-28T15:49:04Z

<p>Zvr: /* Description */</p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2022 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> = Ideas for 2022 Projects =<br /> <br /> == SBOM Conformance Checker ==<br /> The goal of this project is to create a simple tool that<br /> checks whether an SBOM (in SPDX format)<br /> conforms to NTIA's minimum elements guidance.<br /> === Description ===<br /> The SPDX Specification defines a number of fields (elements) that may appear in an SBOM (Software Bill of Materials).<br /> Not all of them are mandatory, however, so SBOMs in SPDX format can vary greatly.<br /> <br /> While researching the attributes that have to be present in an SBOM,<br /> NTIA came up with a guidance about the minimum elements that must appear therein:<br /> https://www.ntia.doc.gov/files/ntia/publications/sbom_minimum_elements_report.pdf<br /> <br /> It would, therefore, be useful to have a tool that can determine whether an SBOM stored in SPDX format<br /> fulfills all such minimum obligations.<br /> <br /> The tool should make use of the already existing libraries for reading SPDX documents<br /> === Technologies ===<br /> Python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> It might be extended to a long (350 hours) project if integration<br /> with the existing SPDX handling tools (e.g., the Validation tool)<br /> is also implemented.<br /> === Mentors ===<br /> Dick Brooks, Kate Stewart<br /> <br /> == Private license management system ==<br /> A web-based system for managing license texts; similar to the SPDX License List but oriented towards other private collections of licenses.<br /> === Description ===<br /> The goal of the project would be to create a simple web application<br /> for people to upload license texts<br /> and automatically create a license repository.<br /> The initial rough &quot;functional specifications&quot; describe it as<br /> mainly an input form, where the information is entered.<br /> There will be some automatic processing (e.g., canonicalization, duplicate avoidance, etc.),<br /> a review/approval (and naming) step,<br /> and then publishing in a specified format.<br /> <br /> It should be noted that the specification is not yet finalized<br /> regarding naming namespaces, way to publish licenses, etc.<br /> If the SPDX project has already advanced in these definitions,<br /> this project will obviously implement the decisions taken.<br /> === Technologies ===<br /> Python (any framework) for the back-end; JavaScript (any framework) for the minimal front-end.<br /> === Duration ===<br /> This can be either a short (175 hours) project, implementing only the basic functionality;<br /> or a long (350 hours) one, implementing more functionality and automation.<br /> === Mentors ===<br /> Alexios Zavras; more TBD<br /> <br /> == SBOM combiner ==<br /> The project will result in a simple command-line tool that will be able to “combine” information from a number of SBOMs into a comprehensive SBOM that includes all the information of the provided ones.<br /> An actual use case would be the generation of an SBOM for an actual software delivery that is comprised by a number of components, each one of which has its own correct SBOM.<br /> === Description ===<br /> The primary purpose of this tool would be<br /> to stitch together smaller component-level SPDX documents<br /> and amalgamate them into one top-level SPDX document<br /> representing a &quot;sum of parts&quot; piece of software.<br /> As an initial pass for implementation, the component-level SBOMs would have to be provided by the caller<br /> until the tool was advanced enough to fetch SPDX Documents referenced by ExternalDocumenRef reliably. <br /> === Technologies ===<br /> Python (preferably); or Go.<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> Rose Judge; others TBD<br /> <br /> == Update of Java SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Java libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Java; see https://github.com/spdx/Spdx-Java-Library<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> == Update of Go SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Go libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Go; see https://github.com/spdx/tools-golang<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Update of Python SPDX libraries to handle latest spec ==<br /> === Description ===<br /> The SPDX Project maintains a library, written in Python, for working with SPDX data.<br /> The development of the library does not always follow the development of the specification immediately.<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Python libraries<br /> capable of handling the latest spec.<br /> <br /> The project will involve obviously understanding deeply<br /> the existing libraries<br /> and extending them to handle the latest additions<br /> of the specification (to the point of the published version).<br /> === Technologies ===<br /> Python; see https://github.com/spdx/tools-python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == More to come... ==<br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Duration===<br /> whether this is a short or a long project<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal.<br /> <br /> = Historical info =<br /> <br /> [[GSOC/PastProjectIdeas]]</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2022-02-28T15:48:17Z

<p>Zvr: /* Ideas for 2022 Projects */</p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2022 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> = Ideas for 2022 Projects =<br /> <br /> == SBOM Conformance Checker ==<br /> The goal of this project is to create a simple tool that<br /> checks whether an SBOM (in SPDX format)<br /> conforms to NTIA's minimum elements guidance.<br /> == Description ==<br /> The SPDX Specification defines a number of fields (elements) that may appear in an SBOM (Software Bill of Materials).<br /> Not all of them are mandatory, however, so SBOMs in SPDX format can vary greatly.<br /> <br /> While researching the attributes that have to be present in an SBOM,<br /> NTIA came up with a guidance about the minimum elements that must appear therein:<br /> https://www.ntia.doc.gov/files/ntia/publications/sbom_minimum_elements_report.pdf<br /> <br /> It would, therefore, be useful to have a tool that can determine whether an SBOM stored in SPDX format<br /> fulfills all such minimum obligations.<br /> <br /> The tool should make use of the already existing libraries for reading SPDX documents<br /> === Technologies ===<br /> Python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> It might be extended to a long (350 hours) project if integration<br /> with the existing SPDX handling tools (e.g., the Validation tool)<br /> is also implemented.<br /> === Mentors ===<br /> Dick Brooks, Kate Stewart<br /> <br /> == Private license management system ==<br /> A web-based system for managing license texts; similar to the SPDX License List but oriented towards other private collections of licenses.<br /> === Description ===<br /> The goal of the project would be to create a simple web application<br /> for people to upload license texts<br /> and automatically create a license repository.<br /> The initial rough &quot;functional specifications&quot; describe it as<br /> mainly an input form, where the information is entered.<br /> There will be some automatic processing (e.g., canonicalization, duplicate avoidance, etc.),<br /> a review/approval (and naming) step,<br /> and then publishing in a specified format.<br /> <br /> It should be noted that the specification is not yet finalized<br /> regarding naming namespaces, way to publish licenses, etc.<br /> If the SPDX project has already advanced in these definitions,<br /> this project will obviously implement the decisions taken.<br /> === Technologies ===<br /> Python (any framework) for the back-end; JavaScript (any framework) for the minimal front-end.<br /> === Duration ===<br /> This can be either a short (175 hours) project, implementing only the basic functionality;<br /> or a long (350 hours) one, implementing more functionality and automation.<br /> === Mentors ===<br /> Alexios Zavras; more TBD<br /> <br /> == SBOM combiner ==<br /> The project will result in a simple command-line tool that will be able to “combine” information from a number of SBOMs into a comprehensive SBOM that includes all the information of the provided ones.<br /> An actual use case would be the generation of an SBOM for an actual software delivery that is comprised by a number of components, each one of which has its own correct SBOM.<br /> === Description ===<br /> The primary purpose of this tool would be<br /> to stitch together smaller component-level SPDX documents<br /> and amalgamate them into one top-level SPDX document<br /> representing a &quot;sum of parts&quot; piece of software.<br /> As an initial pass for implementation, the component-level SBOMs would have to be provided by the caller<br /> until the tool was advanced enough to fetch SPDX Documents referenced by ExternalDocumenRef reliably. <br /> === Technologies ===<br /> Python (preferably); or Go.<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> Rose Judge; others TBD<br /> <br /> == Update of Java SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Java libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Java; see https://github.com/spdx/Spdx-Java-Library<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> == Update of Go SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Go libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Go; see https://github.com/spdx/tools-golang<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Update of Python SPDX libraries to handle latest spec ==<br /> === Description ===<br /> The SPDX Project maintains a library, written in Python, for working with SPDX data.<br /> The development of the library does not always follow the development of the specification immediately.<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Python libraries<br /> capable of handling the latest spec.<br /> <br /> The project will involve obviously understanding deeply<br /> the existing libraries<br /> and extending them to handle the latest additions<br /> of the specification (to the point of the published version).<br /> === Technologies ===<br /> Python; see https://github.com/spdx/tools-python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == More to come... ==<br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Duration===<br /> whether this is a short or a long project<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal.<br /> <br /> = Historical info =<br /> <br /> [[GSOC/PastProjectIdeas]]</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2022-02-28T15:39:54Z

<p>Zvr: /* SBOM combiner */</p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2022 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> = Ideas for 2022 Projects =<br /> <br /> == SBOM Conformance Checker ==<br /> The goal of this project is to create a simple tool that<br /> checks whether an SBOM (in SPDX format)<br /> conforms to the minimum elements guidance from NTIA for an SBOM<br /> (https://www.ntia.doc.gov/files/ntia/publications/sbom_minimum_elements_report.pdf).<br /> === Technologies ===<br /> Python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> It might be extended to a long (350 hours) project if integration<br /> with the existing SPDX handling tools (e.g., the Validation tool)<br /> is also implemented.<br /> === Mentors ===<br /> Dick Brooks, Kate Stewart<br /> <br /> == Update of Java SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Java libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Java; see https://github.com/spdx/Spdx-Java-Library<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> == Update of Go SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Go libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Go; see https://github.com/spdx/tools-golang<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Update of Python SPDX libraries to handle latest spec ==<br /> === Description ===<br /> The SPDX Project maintains a library, written in Python, for working with SPDX data.<br /> The development of the library does not always follow the development of the specification immediately.<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Python libraries<br /> capable of handling the latest spec.<br /> <br /> The project will involve obviously understanding deeply<br /> the existing libraries<br /> and extending them to handle the latest additions<br /> of the specification (to the point of the published version).<br /> === Technologies ===<br /> Python; see https://github.com/spdx/tools-python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> == Private license management system ==<br /> A web-based system for managing license texts; similar to the SPDX License List but oriented towards other private collections of licenses.<br /> === Description ===<br /> The goal of the project would be to create a simple web application<br /> for people to upload license texts<br /> and automatically create a license repository.<br /> The initial rough &quot;functional specifications&quot; describe it as<br /> mainly an input form, where the information is entered.<br /> There will be some automatic processing (e.g., canonicalization, duplicate avoidance, etc.),<br /> a review/approval (and naming) step,<br /> and then publishing in a specified format.<br /> <br /> It should be noted that the specification is not yet finalized<br /> regarding naming namespaces, way to publish licenses, etc.<br /> If the SPDX project has already advanced in these definitions,<br /> this project will obviously implement the decisions taken.<br /> === Technologies ===<br /> Python (any framework) for the back-end; JavaScript (any framework) for the minimal front-end.<br /> === Duration ===<br /> This can be either a short (175 hours) project, implementing only the basic functionality;<br /> or a long (350 hours) one, implementing more functionality and automation.<br /> === Mentors ===<br /> Alexios Zavras; more TBD<br /> <br /> == SBOM combiner ==<br /> The project will result in a simple command-line tool that will be able to “combine” information from a number of SBOMs into a comprehensive SBOM that includes all the information of the provided ones.<br /> An actual use case would be the generation of an SBOM for an actual software delivery that is comprised by a number of components, each one of which has its own correct SBOM.<br /> === Description ===<br /> The primary purpose of this tool would be<br /> to stitch together smaller component-level SPDX documents<br /> and amalgamate them into one top-level SPDX document<br /> representing a &quot;sum of parts&quot; piece of software.<br /> As an initial pass for implementation, the component-level SBOMs would have to be provided by the caller<br /> until the tool was advanced enough to fetch SPDX Documents referenced by ExternalDocumenRef reliably. <br /> === Technologies ===<br /> Python (preferably); or Go.<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> Rose Judge; others TBD<br /> <br /> == More to come... ==<br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Duration===<br /> whether this is a short or a long project<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal.<br /> <br /> = Historical info =<br /> <br /> [[GSOC/PastProjectIdeas]]</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2022-02-28T14:44:58Z

<p>Zvr: /* Private license management system */</p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2022 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> = Ideas for 2022 Projects =<br /> <br /> == SBOM Conformance Checker ==<br /> The goal of this project is to create a simple tool that<br /> checks whether an SBOM (in SPDX format)<br /> conforms to the minimum elements guidance from NTIA for an SBOM<br /> (https://www.ntia.doc.gov/files/ntia/publications/sbom_minimum_elements_report.pdf).<br /> === Technologies ===<br /> Python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> It might be extended to a long (350 hours) project if integration<br /> with the existing SPDX handling tools (e.g., the Validation tool)<br /> is also implemented.<br /> === Mentors ===<br /> Dick Brooks, Kate Stewart<br /> <br /> == Update of Java SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Java libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Java; see https://github.com/spdx/Spdx-Java-Library<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> == Update of Go SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Go libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Go; see https://github.com/spdx/tools-golang<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Update of Python SPDX libraries to handle latest spec ==<br /> === Description ===<br /> The SPDX Project maintains a library, written in Python, for working with SPDX data.<br /> The development of the library does not always follow the development of the specification immediately.<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Python libraries<br /> capable of handling the latest spec.<br /> <br /> The project will involve obviously understanding deeply<br /> the existing libraries<br /> and extending them to handle the latest additions<br /> of the specification (to the point of the published version).<br /> === Technologies ===<br /> Python; see https://github.com/spdx/tools-python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> == Private license management system ==<br /> A web-based system for managing license texts; similar to the SPDX License List but oriented towards other private collections of licenses.<br /> === Description ===<br /> The goal of the project would be to create a simple web application<br /> for people to upload license texts<br /> and automatically create a license repository.<br /> The initial rough &quot;functional specifications&quot; describe it as<br /> mainly an input form, where the information is entered.<br /> There will be some automatic processing (e.g., canonicalization, duplicate avoidance, etc.),<br /> a review/approval (and naming) step,<br /> and then publishing in a specified format.<br /> <br /> It should be noted that the specification is not yet finalized<br /> regarding naming namespaces, way to publish licenses, etc.<br /> If the SPDX project has already advanced in these definitions,<br /> this project will obviously implement the decisions taken.<br /> === Technologies ===<br /> Python (any framework) for the back-end; JavaScript (any framework) for the minimal front-end.<br /> === Duration ===<br /> This can be either a short (175 hours) project, implementing only the basic functionality;<br /> or a long (350 hours) one, implementing more functionality and automation.<br /> === Mentors ===<br /> Alexios Zavras; more TBD<br /> <br /> == SBOM combiner ==<br /> The project will result in a simple command-line tool that will be able to “combine” information from a number of SBOMs into a comprehensive SBOM that includes all the information of the provided ones.<br /> An actual use case would be the generation of an SBOM for an actual software delivery that is comprised by a number of components, each one of which has its own correct SBOM.<br /> === Technologies ===<br /> Python (preferably); or Go.<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> == More to come... ==<br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Duration===<br /> whether this is a short or a long project<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal.<br /> <br /> = Historical info =<br /> <br /> [[GSOC/PastProjectIdeas]]</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2022-02-28T14:43:28Z

<p>Zvr: /* Update of Python SPDX libraries to handle latest spec */</p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2022 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> = Ideas for 2022 Projects =<br /> <br /> == SBOM Conformance Checker ==<br /> The goal of this project is to create a simple tool that<br /> checks whether an SBOM (in SPDX format)<br /> conforms to the minimum elements guidance from NTIA for an SBOM<br /> (https://www.ntia.doc.gov/files/ntia/publications/sbom_minimum_elements_report.pdf).<br /> === Technologies ===<br /> Python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> It might be extended to a long (350 hours) project if integration<br /> with the existing SPDX handling tools (e.g., the Validation tool)<br /> is also implemented.<br /> === Mentors ===<br /> Dick Brooks, Kate Stewart<br /> <br /> == Update of Java SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Java libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Java; see https://github.com/spdx/Spdx-Java-Library<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> == Update of Go SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Go libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Go; see https://github.com/spdx/tools-golang<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Update of Python SPDX libraries to handle latest spec ==<br /> === Description ===<br /> The SPDX Project maintains a library, written in Python, for working with SPDX data.<br /> The development of the library does not always follow the development of the specification immediately.<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Python libraries<br /> capable of handling the latest spec.<br /> <br /> The project will involve obviously understanding deeply<br /> the existing libraries<br /> and extending them to handle the latest additions<br /> of the specification (to the point of the published version).<br /> === Technologies ===<br /> Python; see https://github.com/spdx/tools-python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> == Private license management system ==<br /> A web-based system for managing license texts; similar to the SPDX License List but oriented towards other private collections of licenses.<br /> === Technologies ===<br /> Python (any framework) for the back-end; JavaScript (any framework) for the minimal front-end.<br /> === Duration ===<br /> This can be either a short (175 hours) project, implementing only the basic functionality;<br /> or a long (350 hours) one, extending the functionality and automation.<br /> === Mentors ===<br /> Alexios Zavras; more TBD<br /> === More Information ===<br /> The goal of the project would be to create a simple web application<br /> for people to upload license texts<br /> and automatically create a license repository.<br /> The initial rough &quot;functional specifications&quot; describe it as<br /> mainly an input form, where the information is entered.<br /> There will be some automatic processing (e.g., canonicalization, duplicate avoidance, etc.),<br /> a review/approval (and naming) step,<br /> and then publishing in a specified format.<br /> <br /> It should be noted that the specification is not yet finalized<br /> regarding naming namespaces, way to publish licenses, etc.<br /> If the SPDX project has already advanced in these definitions,<br /> this project will obviously implement the decisions taken.<br /> <br /> == SBOM combiner ==<br /> The project will result in a simple command-line tool that will be able to “combine” information from a number of SBOMs into a comprehensive SBOM that includes all the information of the provided ones.<br /> An actual use case would be the generation of an SBOM for an actual software delivery that is comprised by a number of components, each one of which has its own correct SBOM.<br /> === Technologies ===<br /> Python (preferably); or Go.<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> == More to come... ==<br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Duration===<br /> whether this is a short or a long project<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal.<br /> <br /> = Historical info =<br /> <br /> [[GSOC/PastProjectIdeas]]</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2022-02-28T14:40:05Z

<p>Zvr: /* Ideas for 2022 Projects */</p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2022 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> = Ideas for 2022 Projects =<br /> <br /> == SBOM Conformance Checker ==<br /> The goal of this project is to create a simple tool that<br /> checks whether an SBOM (in SPDX format)<br /> conforms to the minimum elements guidance from NTIA for an SBOM<br /> (https://www.ntia.doc.gov/files/ntia/publications/sbom_minimum_elements_report.pdf).<br /> === Technologies ===<br /> Python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> It might be extended to a long (350 hours) project if integration<br /> with the existing SPDX handling tools (e.g., the Validation tool)<br /> is also implemented.<br /> === Mentors ===<br /> Dick Brooks, Kate Stewart<br /> <br /> == Update of Java SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Java libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Java; see https://github.com/spdx/Spdx-Java-Library<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> == Update of Go SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Go libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Go; see https://github.com/spdx/tools-golang<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Update of Python SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Python libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Python; see https://github.com/spdx/tools-python<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Private license management system ==<br /> A web-based system for managing license texts; similar to the SPDX License List but oriented towards other private collections of licenses.<br /> === Technologies ===<br /> Python (any framework) for the back-end; JavaScript (any framework) for the minimal front-end.<br /> === Duration ===<br /> This can be either a short (175 hours) project, implementing only the basic functionality;<br /> or a long (350 hours) one, extending the functionality and automation.<br /> === Mentors ===<br /> Alexios Zavras; more TBD<br /> === More Information ===<br /> The goal of the project would be to create a simple web application<br /> for people to upload license texts<br /> and automatically create a license repository.<br /> The initial rough &quot;functional specifications&quot; describe it as<br /> mainly an input form, where the information is entered.<br /> There will be some automatic processing (e.g., canonicalization, duplicate avoidance, etc.),<br /> a review/approval (and naming) step,<br /> and then publishing in a specified format.<br /> <br /> It should be noted that the specification is not yet finalized<br /> regarding naming namespaces, way to publish licenses, etc.<br /> If the SPDX project has already advanced in these definitions,<br /> this project will obviously implement the decisions taken.<br /> <br /> == SBOM combiner ==<br /> The project will result in a simple command-line tool that will be able to “combine” information from a number of SBOMs into a comprehensive SBOM that includes all the information of the provided ones.<br /> An actual use case would be the generation of an SBOM for an actual software delivery that is comprised by a number of components, each one of which has its own correct SBOM.<br /> === Technologies ===<br /> Python (preferably); or Go.<br /> === Duration ===<br /> This will be a short (175 hours) project.<br /> === Mentors ===<br /> TBD<br /> <br /> == More to come... ==<br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Duration===<br /> whether this is a short or a long project<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal.<br /> <br /> = Historical info =<br /> <br /> [[GSOC/PastProjectIdeas]]</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2022-02-23T15:04:34Z

<p>Zvr: /* Ideas for 2022 Projects */</p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2022 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> = Ideas for 2022 Projects =<br /> <br /> == SBOM Conformance Checker ==<br /> The goal of this project is to create a simple tool that<br /> checks whether an SBOM (in SPDX format)<br /> conforms to the minimum elements guidance from NTIA for an SBOM<br /> (https://www.ntia.doc.gov/files/ntia/publications/sbom_minimum_elements_report.pdf).<br /> === Technologies ===<br /> Python<br /> === Duration ===<br /> This will probably be a short project.<br /> It might be extended to a long project if it's integrated<br /> with the existing SPDX handling tools (e.g., the Validation tool).<br /> === Mentors ===<br /> Dick Brooks, Kate Stewart<br /> <br /> == Update of Java SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Java libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Java; see https://github.com/spdx/Spdx-Java-Library<br /> === Duration ===<br /> This will probably be a short project.<br /> === Mentors ===<br /> TBD<br /> <br /> == Update of Go SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Go libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Go; see https://github.com/spdx/tools-golang<br /> === Duration ===<br /> This will probably be a short project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Update of Python SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Python libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Python; see https://github.com/spdx/tools-python<br /> === Duration ===<br /> This will probably be a short project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Private license management system ==<br /> A web-based system for managing license texts; similar to the SPDX License List but oriented towards other private collections of licenses.<br /> === Technologies ===<br /> Python (any framework) for the back-end; JavaScript (any framework) for the minimal front-end.<br /> === Duration ===<br /> This can be either a short project, implementing only the basic functionality; or a long one, extending the functionality and automation.<br /> === Mentors ===<br /> Alexios Zavras; more TBD<br /> === More Information ===<br /> The goal of the project would be to create a simple web application<br /> for people to upload license texts<br /> and automatically create a license repository.<br /> The initial rough &quot;functional specifications&quot; describe it as<br /> mainly an input form, where the information is entered.<br /> There will be some automatic processing (e.g., canonicalization, duplicate avoidance, etc.),<br /> a review/approval (and naming) step,<br /> and then publishing in a specified format.<br /> <br /> It should be noted that the specification is not yet finalized<br /> regarding naming namespaces, way to publish licenses, etc.<br /> If the SPDX project has already advanced in these definitions,<br /> this project will obviously implement the decisions taken.<br /> <br /> == SBOM combiner ==<br /> The project will result in a simple command-line tool that will be able to “combine” information from a number of SBOMs into a comprehensive SBOM that includes all the information of the provided ones.<br /> An actual use case would be the generation of an SBOM for an actual software delivery that is comprised by a number of components, each one of which has its own correct SBOM.<br /> === Technologies ===<br /> Python (preferably); or Go.<br /> === Duration ===<br /> This will probably be a short project.<br /> === Mentors ===<br /> TBD<br /> <br /> == More to come... ==<br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Duration===<br /> whether this is a short or a long project<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal.<br /> <br /> = Historical info =<br /> <br /> [[GSOC/PastProjectIdeas]]</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2022-02-15T17:15:31Z

<p>Zvr: /* SBOM Conformance Checker */</p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2022 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> = Ideas for 2022 Projects =<br /> <br /> == SBOM Conformance Checker ==<br /> The goal of this project is to create a simple tool that<br /> checks whether an SBOM (in SPDX format)<br /> conforms to the minimum elements guidance from NTIA for an SBOM<br /> (https://www.ntia.doc.gov/files/ntia/publications/sbom_minimum_elements_report.pdf).<br /> === Technologies ===<br /> Python<br /> === Duration ===<br /> This will probably be a short project.<br /> It might be extended to a long project if it's integrated<br /> with the existing SPDX handling tools (e.g., the Validation tool).<br /> === Mentors ===<br /> Dick Brooks, Kate Stewart<br /> <br /> == Update of Java SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Java libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Java; see https://github.com/spdx/Spdx-Java-Library<br /> === Duration ===<br /> This will probably be a short project.<br /> === Mentors ===<br /> TBD<br /> <br /> == Update of Go SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Go libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Go; see https://github.com/spdx/tools-golang<br /> === Duration ===<br /> This will probably be a short project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Update of Python SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Python libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Python; see https://github.com/spdx/tools-python<br /> === Duration ===<br /> This will probably be a short project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Private license management system ==<br /> A web-based system for managing license texts; similar to the SPDX License List but oriented towards other private collections of licenses.<br /> === Technologies ===<br /> Python (any framework) for the back-end; JavaScript (any framework) for the minimal front-end.<br /> === Duration ===<br /> This can be either a short project, implementing only the basic functionality; or a long one, extending the functionality and automation.<br /> === Mentors ===<br /> Alexios Zavras; more TBD<br /> === More Information ===<br /> The goal of the project would be to create a simple web application<br /> for people to upload license texts<br /> and automatically create a license repository.<br /> The initial rough &quot;functional specifications&quot; describe it as<br /> mainly an input form, where the information is entered.<br /> There will be some automatic processing (e.g., canonicalization, duplicate avoidance, etc.),<br /> a review/approval (and naming) step,<br /> and then publishing in a specified format.<br /> <br /> It should be noted that the specification is not yet finalized<br /> regarding naming namespaces, way to publish licenses, etc.<br /> If the SPDX project has already advanced in these definitions,<br /> this project will obviously implement the decisions taken.<br /> <br /> == SBOM combiner ==<br /> Details to be added later.<br /> <br /> <br /> == More to come... ==<br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Duration===<br /> whether this is a short or a long project<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal.<br /> <br /> = Historical info =<br /> <br /> [[GSOC/PastProjectIdeas]]</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2022-02-15T14:57:12Z

<p>Zvr: /* Ideas for 2022 Projects */</p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2022 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> = Ideas for 2022 Projects =<br /> <br /> == SBOM Conformance Checker ==<br /> The goal of this project is to create a simple tool that<br /> checks whether an SBOM (in SPDX format)<br /> conforms to the minimum elements guidance from NTIA for an SBOM<br /> (https://www.ntia.doc.gov/files/ntia/publications/sbom_minimum_elements_report.pdf).<br /> === Technologies ===<br /> TBD<br /> === Duration ===<br /> This will probably be a short project.<br /> It might be extended to a long project if it's integrated<br /> with the existing SPDX handling tools (e.g., the Validation tool).<br /> === Mentors ===<br /> TBD<br /> <br /> == Update of Java SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Java libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Java; see https://github.com/spdx/Spdx-Java-Library<br /> === Duration ===<br /> This will probably be a short project.<br /> === Mentors ===<br /> TBD<br /> <br /> == Update of Go SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Go libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Go; see https://github.com/spdx/tools-golang<br /> === Duration ===<br /> This will probably be a short project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Update of Python SPDX libraries to handle latest spec ==<br /> Since the specification has evolved<br /> and a newer version is expected to be published<br /> right before the timeframe of the project,<br /> it would be useful to have the standard Python libraries<br /> capable of handling the latest spec.<br /> === Technologies ===<br /> Python; see https://github.com/spdx/tools-python<br /> === Duration ===<br /> This will probably be a short project.<br /> === Mentors ===<br /> TBD<br /> <br /> <br /> == Private license management system ==<br /> A web-based system for managing license texts; similar to the SPDX License List but oriented towards other private collections of licenses.<br /> === Technologies ===<br /> Python (any framework) for the back-end; JavaScript (any framework) for the minimal front-end.<br /> === Duration ===<br /> This can be either a short project, implementing only the basic functionality; or a long one, extending the functionality and automation.<br /> === Mentors ===<br /> Alexios Zavras; more TBD<br /> === More Information ===<br /> The goal of the project would be to create a simple web application<br /> for people to upload license texts<br /> and automatically create a license repository.<br /> The initial rough &quot;functional specifications&quot; describe it as<br /> mainly an input form, where the information is entered.<br /> There will be some automatic processing (e.g., canonicalization, duplicate avoidance, etc.),<br /> a review/approval (and naming) step,<br /> and then publishing in a specified format.<br /> <br /> It should be noted that the specification is not yet finalized<br /> regarding naming namespaces, way to publish licenses, etc.<br /> If the SPDX project has already advanced in these definitions,<br /> this project will obviously implement the decisions taken.<br /> <br /> == SBOM combiner ==<br /> Details to be added later.<br /> <br /> <br /> == More to come... ==<br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Duration===<br /> whether this is a short or a long project<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal.<br /> <br /> = Historical info =<br /> <br /> [[GSOC/PastProjectIdeas]]</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2022-02-07T14:36:56Z

<p>Zvr: </p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2022 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> = Ideas for 2022 Projects =<br /> <br /> <br /> <br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal. <br /> <br /> = Historical info =<br /> <br /> [[GSOC/PastProjectIdeas]]</div>

Zvr https://wiki.spdx.org/view/GSOC/PastProjectIdeas 2022-02-07T14:36:12Z

<p>Zvr: Created page with &quot;Past year Project Ideas for GSoC projects = 2021 = ==SPDX Workgroup Tooling Projects== These projects are aimed at contributing to the SPDX tools to help reduce the effort...&quot;</p> <hr /> <div>Past year Project Ideas for GSoC projects<br /> <br /> = 2021 =<br /> <br /> ==SPDX Workgroup Tooling Projects== <br /> These projects are aimed at contributing to the SPDX tools to help reduce the effort to create SPDX documents and increase the accuracy of them.<br /> <br /> === Migrate SPDX Online Tools to DJango3 ===<br /> Migrate the SPDX online tools to later versions of Django and upgrade dependencies (such as Django Social Auth) to later version to support better / more secure authentication to Github. In addition to migrating to DJango 3, additional issues can be taken on to create a full GSoC project (see the list below).<br /> <br /> ====Skills Needed====<br /> * Experience with Python3 programming<br /> * Familiar with Django framework<br /> <br /> ====Background Information====<br /> The SPDX Online Tools are currently being migrated to Python3. Several libraries can now be upgraded to more supportable versions including DJango. There are some known issues with the current version of Django Social Auth which would be resolved by upgrading the versions. There may be additional libraries which can be upgraded. There is also an opportunity to improve the structure and unit tests for the online tools if time allows. See the [https://github.com/spdx/spdx-online-tools/tree/rtgdk_python3 Python3 Branch] of the SPDX online tools for the current state of the Python3 migration.<br /> <br /> Additional tasks and issues can can be included in a project (in priority order):<br /> * Migrate project to python3 and Django3 [https://github.com/spdx/spdx-online-tools/issues/58 issue 50] and [https://github.com/spdx/spdx-online-tools/issues/24 issue 24]<br /> * [https://github.com/spdx/spdx-online-tools/issues/287 Merge app and api code]<br /> * Fix and improve test [https://github.com/spdx/spdx-online-tools/issues/201 issue 201] [https://github.com/spdx/spdx-online-tools/issues/282 issue 282], [https://github.com/spdx/spdx-online-tools/issues/202 issue 202] + others<br /> * [https://github.com/spdx/spdx-online-tools/issues/299 Add a submit via mail functionality to license submittal]<br /> * [https://github.com/spdx/spdx-online-tools/issues/218 Store license diff screenshot in database instead of uploading to github]<br /> * [https://github.com/spdx/spdx-online-tools/issues/157 Improve error message when error received from the Java code]<br /> * [https://github.com/spdx/spdx-online-tools/issues/186 Add a License Diff section to the SPDX Online Tool]<br /> * [https://github.com/spdx/spdx-online-tools/issues/91 API documentation tool]<br /> * API for license namespace <br /> * [https://github.com/spdx/spdx-online-tools/issues/204 Move to Github Apps and improvement for production]<br /> <br /> ====Available Mentors====<br /> [mailto:rohit.lodhartg@gmail.com Rohit Lodha] [mailto:anshuldutt21@gmail.com Anshul Dutt Sharma] [mailto:gary@sourceauditor.com Gary O'Neall]<br /> <br /> === Migrate Python Tools to Python 3 ===<br /> Migrate the [https://github.com/spdx/tools-python SPDX Python Tools] to Python 3 including all unit testing. In addition, additional known issues raised on GitHub may be tackled.<br /> <br /> ====Skills Needed====<br /> * Experience with Python3 programming<br /> * Knowledge of parsing algorithms<br /> <br /> ====Background Information====<br /> The Python tools are command-line tools and a library that implement reading and writing of SPDX files in different formats, as well as converting and validating SPDX files.<br /> The current implementation uses Python 2, which is no longer supported.<br /> In addition to migration, some additional tasks may be taken on to improve the supportability of the library. In particular, restructuring the code to separate out the different serialization formats (see [https://github.com/spdx/tools-python/issues/147 issue 147]).<br /> <br /> ====Available Mentors====<br /> [mailto:santiago@nyu.edu Santiago Torres Arias] [mailto:alexios.zavras@intel.com Alexios Zavras] [mailto:anshuldutt21@gmail.com Anshul Dutt Sharma]<br /> <br /> === RDF Writer for Golang ===<br /> Gordf supports writing rdf triples to rdf file. Create an interface that would take in a SPDX document and generate RDF triples out of it. Which will then be consumed by the gordf to generate a RDF/xml file.<br /> <br /> ====Skills Needed====<br /> * Knowledge of RDF<br /> * Skills in XML parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> RDF/XML is one of the supported formats for SPDX documents. Creating an RDFWriter would create a generally useful facility for Golang and provide a more modular structure for the SPDX Golang tools.<br /> <br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar]<br /> <br /> === YAML Support for Golang libraries ===<br /> YAML is one of the supported formats for SPDX. This project is to add support for reading and writing YAML to the Golang libraries.<br /> <br /> ====Skills Needed====<br /> * Knowledge of YAML<br /> * Skills in YAML parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar] [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> <br /> === JSON Support for Golang libraries ===<br /> JSON is one of the supported formats for SPDX. This project is to add support for reading and writing JSON to the Golang libraries.<br /> <br /> ====Skills Needed====<br /> * Knowledge of JSON<br /> * Skills in JSON parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar] [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> <br /> ==SPDX Specification Projects==<br /> The following projects contribute directly to the creation or validation of the SPDX specification.<br /> <br /> === Generate a JSON Representation of the Specification from Structured Markdown ===<br /> Convert a consistently structured Markdown file into a JSON structure following a well defined schema. Changes to an existing Markdown file should update the JSON files. The Markdown will have a well defined structure to allow for translation of the text in Markdown to the properties of the JSON file. The conversion will also validate that the Markdown follows the required specification. The conversion would be run as part of a Github action for the SPDX specification.<br /> <br /> ====Skills Needed====<br /> * Skills in writing parsing algorithms (e.g. working with [https://en.wikipedia.org/wiki/Abstract_syntax_tree Abstract Syntax Tree])<br /> * Knowledge and experience in the programming language chosen for the project (e.g. Java, JavaScript, Python)<br /> * Knowledge of Markdown and JSON syntax<br /> <br /> ====Background Information====<br /> The SPDX tech team works very collaboratively on the specification updates using markdown pages in GitHub as the primary documentation for the specification. RDF/OWL is used as the primary technical specification for the object model including relationships, cardinality, class structure, and other restrictions. There is a lot of overlap between the information in the Markdown and the information in the OWL document. To improve the quality and productivity of the specification work, the SPDX technical team has decided to add tooling for verification of the Markdown and conversion of any common information to the OWL document. The conversion will be in 2 stages:<br /> * Convert from Markdown to an intermediate JSON format<br /> * Convert from the JSON format to RDF/OWL<br /> <br /> The specific schema for the JSON format is under development and planned to be available before the start of GSoC.<br /> <br /> Below are some additional resources for this project:<br /> * [https://github.github.com/gfm/ GitHub flavored Markdown]<br /> * [https://json-schema.org/ JSON Schema] information site and its [https://tools.ietf.org/html/draft-bhutton-json-schema-00 current draft]<br /> * [https://docs.google.com/document/d/13PojpaFPdoKZ9Gyh_DEY-Rp7lldyMbSiGE3vCRQhR9M/edit# Results of process discussion]<br /> * [https://docs.google.com/document/d/1EGoAmKxPfmmlF3XV6fXwNmsCiFKLH83Bhh8_xrmGhko Analysis of RDF/OWL fields relative to Markdown] (work in progress)<br /> * [https://docs.google.com/document/d/1LN5CepVVOu38w4pXeLpw_3BDNn2CKAWUyTVdlh8C2WM/edit?usp=sharing Template for Spec Markdown] (work in progress)<br /> * [https://docs.google.com/document/d/1J6P3q6wcP0c1xquTIfMfIBJCa8S1xtkhDs6dD1hSf4Y/edit?usp=sharing Example spec JSON file] (work in progress)<br /> * [https://docs.google.com/document/d/1OF_EqfU4tLPF-oGheEZ1aCzsnGIJHyRptzQ_U7AA-wY/edit?usp=sharing Draft JSON schema] (work in progress)<br /> <br /> ====Available Mentors====<br /> [mailto:gary@sourceauditor.com Gary O'Neall] [mailto:alexios.zavras@intel.com Alexios Zavras]<br /> <br /> === Generate RDF/OWL from from JSON specification format ===<br /> Convert a set of JSON files into a Web Ontology Language XML document. The JSON file will map to the elements and attributes of the RDF/OWL XML file. The JSON schema will be defined prior to the project start and will be consistent with the &quot;Generate a JSON Representation of the Specification from Structured Markdown&quot; project described above.<br /> <br /> ====Skills Needed====<br /> * Knowledge and experience in the programming language chosen for the project (e.g. Java, JavaScript, Python)<br /> * Knowledge of RDF/OWL/XML formats<br /> * Knowledge of JSON parsers<br /> <br /> ====Background Information====<br /> The SPDX tech team works very collaboratively on the specification updates using markdown pages in GitHub as the primary documentation for the specification. RDF/OWL is used as the primary technical specification for the object model including relationships, cardinality, class structure, and other restrictions. There is a lot of overlap between the information in the Markdown and the information in the OWL document. To improve the quality and productivity of the specification work, the SPDX technical team has decided to add tooling for verification of the Markdown and conversion of any common information to the OWL document. The conversion will be in 2 stages:<br /> * Convert from Markdown to an intermediate JSON format<br /> * Convert from the JSON format to RDF/OWL<br /> <br /> The specific schema for the JSON format is under development and planned to be available before the start of GSoC.<br /> <br /> Below are some additional resources for this project:<br /> * [https://www.w3.org/TR/2004/NOTE-owl-parsing-20040121/ RDF OWL parsing notes from the W3C]<br /> * [https://json-schema.org/ JSON Schema] information site and its [https://tools.ietf.org/html/draft-bhutton-json-schema-00 current draft]<br /> * [https://docs.google.com/document/d/13PojpaFPdoKZ9Gyh_DEY-Rp7lldyMbSiGE3vCRQhR9M/edit# Results of process discussion]<br /> * [https://docs.google.com/document/d/1EGoAmKxPfmmlF3XV6fXwNmsCiFKLH83Bhh8_xrmGhko Analysis of RDF/OWL fields relative to Markdown] (work in progress)<br /> * [https://github.com/spdx/spdx-spec/blob/development/v2.2.1/ontology/spdx-ontology.owl.xml Current RDF/OWL document for SPDX spec]<br /> * [https://docs.google.com/document/d/1LN5CepVVOu38w4pXeLpw_3BDNn2CKAWUyTVdlh8C2WM/edit?usp=sharing Template for Spec Markdown] (work in progress)<br /> * [https://docs.google.com/document/d/1J6P3q6wcP0c1xquTIfMfIBJCa8S1xtkhDs6dD1hSf4Y/edit?usp=sharing Example spec JSON file] (work in progress)<br /> * [https://docs.google.com/document/d/1OF_EqfU4tLPF-oGheEZ1aCzsnGIJHyRptzQ_U7AA-wY/edit?usp=sharing Draft JSON schema] (work in progress)<br /> <br /> ====Available Mentors====<br /> [mailto:gary@sourceauditor.com Gary O'Neall] [mailto:alexios.zavras@intel.com Alexios Zavras]<br /> <br /> === SPDX Specification Views for legal counsels and developers ===<br /> The proposal is to see if it possible to deduct large SPDX documents into a small subset SPDX document providing a specific reduced &quot;views&quot; on larger data.<br /> ====Skills Needed====<br /> * Understanding of compliance needs of legal counsels and developers so we can remove friction to adopt SPDX<br /> ====Background Information====<br /> SPDX documents commonly contain 100s, if not 1000s of entries making it hard for a human to make manual corrections or draw conclusions. No scanner can provide 100% complete data human corrections are usual needed. The aim from this proposal is twofold:<br /> 1. Enable developers with a &quot;code view&quot; of tool-generated SPDX document close to the code they work on to enable them to make corrections to the SPDX data. For instance amend SPDX package tag values or model package dependencies not detected by used scanner.<br /> 2. Provide legal counsels with a &quot;package and limited file view&quot; to enable legal conclusions<br /> ====Available Mentors====<br /> [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> [mailto:thomas.steenbergen@here.com Thomas Steenbergen]<br /> <br /> === ClearlyDefined exporting and importing SPDX documents ===<br /> The goal of this GSoC project would be to add support in the [https://https://github.com/clearlydefined ClearlyDefined project] to export curated data into SPDX 2.2 documents. Once that is accomplished, being able to import SPDX documents into the curated database would be the next step.<br /> <br /> ====Skills Needed====<br /> * Experience with JSON and YAML (XML a plus)<br /> * Ability to interpret and implement the SPDX specification and related ClearlyDefined community documentation<br /> * Ability to work with the community in integrating results with other projects<br /> * Willingness to learn about open source licensing and related technical matters<br /> <br /> ====Background Information====<br /> Export a ClearlyDefined workspace as a SPDX document:<br /> * user to navigate to https://clearlydefined.io/workspace<br /> * Add one or more components to the workspace through any of the existing means, <br /> * then click Share, and then slick SPDX (choice of 2.2 supported output formats).<br /> which would result in an SPDX document is exported containing all of the components that were in the workspace.<br /> Note: If there is mandatory information required by SPDX that ClearlyDefined does not have we will need to determine how to accommodate that.<br /> <br /> To populate a workspace from a SPDX document:<br /> * user to navigate to https://clearlydefined.io/workspace<br /> * drag a SPDX document into the workspace and then all of the components in the SPDX document are added to the workspace.<br /> <br /> There are some discrepancies between the content in ClearlyDefined and that SPDX documents, so work would be needed with both communities to figure out: what to do if license information in the SPDX disagrees with what ClearlyDefined has and how to handle pending curations?<br /> <br /> ====Available Mentors====<br /> [mailto:kstewart@linuxfoundation.org Kate Stewart]<br /> [mailto:IAMWILLBAR@github.com William Bartholomew]<br /> <br /> = 2019 =<br /> <br /> The projects from 2019 can be found on the [https://summerofcode.withgoogle.com/organizations/4532099550281728/#5727887162867712 2019 Google Summer of Code projects page for SPDX].</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2022-02-07T14:33:35Z

<p>Zvr: /* Historical info */</p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2022 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> = Ideas for 2022 Projects =<br /> <br /> <br /> <br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal. <br /> <br /> = Historical info =<br /> <br /> [[GSOC/PastProjectIdeas]]<br /> <br /> (The projects from 2019 can be found on the [https://summerofcode.withgoogle.com/organizations/4532099550281728/#5727887162867712 2019 Google Summer of Code projects page for SPDX] ).<br /> <br /> ==SPDX Workgroup Tooling Projects== <br /> These projects are aimed at contributing to the SPDX tools to help reduce the effort to create SPDX documents and increase the accuracy of them.<br /> <br /> === Migrate SPDX Online Tools to DJango3 ===<br /> Migrate the SPDX online tools to later versions of Django and upgrade dependencies (such as Django Social Auth) to later version to support better / more secure authentication to Github. In addition to migrating to DJango 3, additional issues can be taken on to create a full GSoC project (see the list below).<br /> <br /> ====Skills Needed====<br /> * Experience with Python3 programming<br /> * Familiar with Django framework<br /> <br /> ====Background Information====<br /> The SPDX Online Tools are currently being migrated to Python3. Several libraries can now be upgraded to more supportable versions including DJango. There are some known issues with the current version of Django Social Auth which would be resolved by upgrading the versions. There may be additional libraries which can be upgraded. There is also an opportunity to improve the structure and unit tests for the online tools if time allows. See the [https://github.com/spdx/spdx-online-tools/tree/rtgdk_python3 Python3 Branch] of the SPDX online tools for the current state of the Python3 migration.<br /> <br /> Additional tasks and issues can can be included in a project (in priority order):<br /> * Migrate project to python3 and Django3 [https://github.com/spdx/spdx-online-tools/issues/58 issue 50] and [https://github.com/spdx/spdx-online-tools/issues/24 issue 24]<br /> * [https://github.com/spdx/spdx-online-tools/issues/287 Merge app and api code]<br /> * Fix and improve test [https://github.com/spdx/spdx-online-tools/issues/201 issue 201] [https://github.com/spdx/spdx-online-tools/issues/282 issue 282], [https://github.com/spdx/spdx-online-tools/issues/202 issue 202] + others<br /> * [https://github.com/spdx/spdx-online-tools/issues/299 Add a submit via mail functionality to license submittal]<br /> * [https://github.com/spdx/spdx-online-tools/issues/218 Store license diff screenshot in database instead of uploading to github]<br /> * [https://github.com/spdx/spdx-online-tools/issues/157 Improve error message when error received from the Java code]<br /> * [https://github.com/spdx/spdx-online-tools/issues/186 Add a License Diff section to the SPDX Online Tool]<br /> * [https://github.com/spdx/spdx-online-tools/issues/91 API documentation tool]<br /> * API for license namespace <br /> * [https://github.com/spdx/spdx-online-tools/issues/204 Move to Github Apps and improvement for production]<br /> <br /> ====Available Mentors====<br /> [mailto:rohit.lodhartg@gmail.com Rohit Lodha] [mailto:anshuldutt21@gmail.com Anshul Dutt Sharma] [mailto:gary@sourceauditor.com Gary O'Neall]<br /> <br /> === Migrate Python Tools to Python 3 ===<br /> Migrate the [https://github.com/spdx/tools-python SPDX Python Tools] to Python 3 including all unit testing. In addition, additional known issues raised on GitHub may be tackled.<br /> <br /> ====Skills Needed====<br /> * Experience with Python3 programming<br /> * Knowledge of parsing algorithms<br /> <br /> ====Background Information====<br /> The Python tools are command-line tools and a library that implement reading and writing of SPDX files in different formats, as well as converting and validating SPDX files.<br /> The current implementation uses Python 2, which is no longer supported.<br /> In addition to migration, some additional tasks may be taken on to improve the supportability of the library. In particular, restructuring the code to separate out the different serialization formats (see [https://github.com/spdx/tools-python/issues/147 issue 147]).<br /> <br /> ====Available Mentors====<br /> [mailto:santiago@nyu.edu Santiago Torres Arias] [mailto:alexios.zavras@intel.com Alexios Zavras] [mailto:anshuldutt21@gmail.com Anshul Dutt Sharma]<br /> <br /> === RDF Writer for Golang ===<br /> Gordf supports writing rdf triples to rdf file. Create an interface that would take in a SPDX document and generate RDF triples out of it. Which will then be consumed by the gordf to generate a RDF/xml file.<br /> <br /> ====Skills Needed====<br /> * Knowledge of RDF<br /> * Skills in XML parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> RDF/XML is one of the supported formats for SPDX documents. Creating an RDFWriter would create a generally useful facility for Golang and provide a more modular structure for the SPDX Golang tools.<br /> <br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar]<br /> <br /> === YAML Support for Golang libraries ===<br /> YAML is one of the supported formats for SPDX. This project is to add support for reading and writing YAML to the Golang libraries.<br /> <br /> ====Skills Needed====<br /> * Knowledge of YAML<br /> * Skills in YAML parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar] [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> <br /> === JSON Support for Golang libraries ===<br /> JSON is one of the supported formats for SPDX. This project is to add support for reading and writing JSON to the Golang libraries.<br /> <br /> ====Skills Needed====<br /> * Knowledge of JSON<br /> * Skills in JSON parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar] [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> <br /> ==SPDX Specification Projects==<br /> The following projects contribute directly to the creation or validation of the SPDX specification.<br /> <br /> === Generate a JSON Representation of the Specification from Structured Markdown ===<br /> Convert a consistently structured Markdown file into a JSON structure following a well defined schema. Changes to an existing Markdown file should update the JSON files. The Markdown will have a well defined structure to allow for translation of the text in Markdown to the properties of the JSON file. The conversion will also validate that the Markdown follows the required specification. The conversion would be run as part of a Github action for the SPDX specification.<br /> <br /> ====Skills Needed====<br /> * Skills in writing parsing algorithms (e.g. working with [https://en.wikipedia.org/wiki/Abstract_syntax_tree Abstract Syntax Tree])<br /> * Knowledge and experience in the programming language chosen for the project (e.g. Java, JavaScript, Python)<br /> * Knowledge of Markdown and JSON syntax<br /> <br /> ====Background Information====<br /> The SPDX tech team works very collaboratively on the specification updates using markdown pages in GitHub as the primary documentation for the specification. RDF/OWL is used as the primary technical specification for the object model including relationships, cardinality, class structure, and other restrictions. There is a lot of overlap between the information in the Markdown and the information in the OWL document. To improve the quality and productivity of the specification work, the SPDX technical team has decided to add tooling for verification of the Markdown and conversion of any common information to the OWL document. The conversion will be in 2 stages:<br /> * Convert from Markdown to an intermediate JSON format<br /> * Convert from the JSON format to RDF/OWL<br /> <br /> The specific schema for the JSON format is under development and planned to be available before the start of GSoC.<br /> <br /> Below are some additional resources for this project:<br /> * [https://github.github.com/gfm/ GitHub flavored Markdown]<br /> * [https://json-schema.org/ JSON Schema] information site and its [https://tools.ietf.org/html/draft-bhutton-json-schema-00 current draft]<br /> * [https://docs.google.com/document/d/13PojpaFPdoKZ9Gyh_DEY-Rp7lldyMbSiGE3vCRQhR9M/edit# Results of process discussion]<br /> * [https://docs.google.com/document/d/1EGoAmKxPfmmlF3XV6fXwNmsCiFKLH83Bhh8_xrmGhko Analysis of RDF/OWL fields relative to Markdown] (work in progress)<br /> * [https://docs.google.com/document/d/1LN5CepVVOu38w4pXeLpw_3BDNn2CKAWUyTVdlh8C2WM/edit?usp=sharing Template for Spec Markdown] (work in progress)<br /> * [https://docs.google.com/document/d/1J6P3q6wcP0c1xquTIfMfIBJCa8S1xtkhDs6dD1hSf4Y/edit?usp=sharing Example spec JSON file] (work in progress)<br /> * [https://docs.google.com/document/d/1OF_EqfU4tLPF-oGheEZ1aCzsnGIJHyRptzQ_U7AA-wY/edit?usp=sharing Draft JSON schema] (work in progress)<br /> <br /> ====Available Mentors====<br /> [mailto:gary@sourceauditor.com Gary O'Neall] [mailto:alexios.zavras@intel.com Alexios Zavras]<br /> <br /> === Generate RDF/OWL from from JSON specification format ===<br /> Convert a set of JSON files into a Web Ontology Language XML document. The JSON file will map to the elements and attributes of the RDF/OWL XML file. The JSON schema will be defined prior to the project start and will be consistent with the &quot;Generate a JSON Representation of the Specification from Structured Markdown&quot; project described above.<br /> <br /> ====Skills Needed====<br /> * Knowledge and experience in the programming language chosen for the project (e.g. Java, JavaScript, Python)<br /> * Knowledge of RDF/OWL/XML formats<br /> * Knowledge of JSON parsers<br /> <br /> ====Background Information====<br /> The SPDX tech team works very collaboratively on the specification updates using markdown pages in GitHub as the primary documentation for the specification. RDF/OWL is used as the primary technical specification for the object model including relationships, cardinality, class structure, and other restrictions. There is a lot of overlap between the information in the Markdown and the information in the OWL document. To improve the quality and productivity of the specification work, the SPDX technical team has decided to add tooling for verification of the Markdown and conversion of any common information to the OWL document. The conversion will be in 2 stages:<br /> * Convert from Markdown to an intermediate JSON format<br /> * Convert from the JSON format to RDF/OWL<br /> <br /> The specific schema for the JSON format is under development and planned to be available before the start of GSoC.<br /> <br /> Below are some additional resources for this project:<br /> * [https://www.w3.org/TR/2004/NOTE-owl-parsing-20040121/ RDF OWL parsing notes from the W3C]<br /> * [https://json-schema.org/ JSON Schema] information site and its [https://tools.ietf.org/html/draft-bhutton-json-schema-00 current draft]<br /> * [https://docs.google.com/document/d/13PojpaFPdoKZ9Gyh_DEY-Rp7lldyMbSiGE3vCRQhR9M/edit# Results of process discussion]<br /> * [https://docs.google.com/document/d/1EGoAmKxPfmmlF3XV6fXwNmsCiFKLH83Bhh8_xrmGhko Analysis of RDF/OWL fields relative to Markdown] (work in progress)<br /> * [https://github.com/spdx/spdx-spec/blob/development/v2.2.1/ontology/spdx-ontology.owl.xml Current RDF/OWL document for SPDX spec]<br /> * [https://docs.google.com/document/d/1LN5CepVVOu38w4pXeLpw_3BDNn2CKAWUyTVdlh8C2WM/edit?usp=sharing Template for Spec Markdown] (work in progress)<br /> * [https://docs.google.com/document/d/1J6P3q6wcP0c1xquTIfMfIBJCa8S1xtkhDs6dD1hSf4Y/edit?usp=sharing Example spec JSON file] (work in progress)<br /> * [https://docs.google.com/document/d/1OF_EqfU4tLPF-oGheEZ1aCzsnGIJHyRptzQ_U7AA-wY/edit?usp=sharing Draft JSON schema] (work in progress)<br /> <br /> ====Available Mentors====<br /> [mailto:gary@sourceauditor.com Gary O'Neall] [mailto:alexios.zavras@intel.com Alexios Zavras]<br /> <br /> === SPDX Specification Views for legal counsels and developers ===<br /> The proposal is to see if it possible to deduct large SPDX documents into a small subset SPDX document providing a specific reduced &quot;views&quot; on larger data.<br /> ====Skills Needed====<br /> * Understanding of compliance needs of legal counsels and developers so we can remove friction to adopt SPDX<br /> ====Background Information====<br /> SPDX documents commonly contain 100s, if not 1000s of entries making it hard for a human to make manual corrections or draw conclusions. No scanner can provide 100% complete data human corrections are usual needed. The aim from this proposal is twofold:<br /> 1. Enable developers with a &quot;code view&quot; of tool-generated SPDX document close to the code they work on to enable them to make corrections to the SPDX data. For instance amend SPDX package tag values or model package dependencies not detected by used scanner.<br /> 2. Provide legal counsels with a &quot;package and limited file view&quot; to enable legal conclusions<br /> ====Available Mentors====<br /> [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> [mailto:thomas.steenbergen@here.com Thomas Steenbergen]<br /> <br /> === ClearlyDefined exporting and importing SPDX documents ===<br /> The goal of this GSoC project would be to add support in the [https://https://github.com/clearlydefined ClearlyDefined project] to export curated data into SPDX 2.2 documents. Once that is accomplished, being able to import SPDX documents into the curated database would be the next step.<br /> <br /> ====Skills Needed====<br /> * Experience with JSON and YAML (XML a plus)<br /> * Ability to interpret and implement the SPDX specification and related ClearlyDefined community documentation<br /> * Ability to work with the community in integrating results with other projects<br /> * Willingness to learn about open source licensing and related technical matters<br /> <br /> ====Background Information====<br /> Export a ClearlyDefined workspace as a SPDX document:<br /> * user to navigate to https://clearlydefined.io/workspace<br /> * Add one or more components to the workspace through any of the existing means, <br /> * then click Share, and then slick SPDX (choice of 2.2 supported output formats).<br /> which would result in an SPDX document is exported containing all of the components that were in the workspace.<br /> Note: If there is mandatory information required by SPDX that ClearlyDefined does not have we will need to determine how to accommodate that.<br /> <br /> To populate a workspace from a SPDX document:<br /> * user to navigate to https://clearlydefined.io/workspace<br /> * drag a SPDX document into the workspace and then all of the components in the SPDX document are added to the workspace.<br /> <br /> There are some discrepancies between the content in ClearlyDefined and that SPDX documents, so work would be needed with both communities to figure out: what to do if license information in the SPDX disagrees with what ClearlyDefined has and how to handle pending curations?<br /> <br /> ====Available Mentors====<br /> [mailto:kstewart@linuxfoundation.org Kate Stewart]<br /> [mailto:IAMWILLBAR@github.com William Bartholomew]</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2022-02-07T14:31:57Z

<p>Zvr: </p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2022 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> = Ideas for 2022 Projects =<br /> <br /> <br /> <br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal. <br /> <br /> = Historical info =<br /> <br /> [GSOC/PastProjectIdeas]<br /> <br /> (The projects from 2019 can be found on the [https://summerofcode.withgoogle.com/organizations/4532099550281728/#5727887162867712 2019 Google Summer of Code projects page for SPDX] ).<br /> <br /> ==SPDX Workgroup Tooling Projects== <br /> These projects are aimed at contributing to the SPDX tools to help reduce the effort to create SPDX documents and increase the accuracy of them.<br /> <br /> === Migrate SPDX Online Tools to DJango3 ===<br /> Migrate the SPDX online tools to later versions of Django and upgrade dependencies (such as Django Social Auth) to later version to support better / more secure authentication to Github. In addition to migrating to DJango 3, additional issues can be taken on to create a full GSoC project (see the list below).<br /> <br /> ====Skills Needed====<br /> * Experience with Python3 programming<br /> * Familiar with Django framework<br /> <br /> ====Background Information====<br /> The SPDX Online Tools are currently being migrated to Python3. Several libraries can now be upgraded to more supportable versions including DJango. There are some known issues with the current version of Django Social Auth which would be resolved by upgrading the versions. There may be additional libraries which can be upgraded. There is also an opportunity to improve the structure and unit tests for the online tools if time allows. See the [https://github.com/spdx/spdx-online-tools/tree/rtgdk_python3 Python3 Branch] of the SPDX online tools for the current state of the Python3 migration.<br /> <br /> Additional tasks and issues can can be included in a project (in priority order):<br /> * Migrate project to python3 and Django3 [https://github.com/spdx/spdx-online-tools/issues/58 issue 50] and [https://github.com/spdx/spdx-online-tools/issues/24 issue 24]<br /> * [https://github.com/spdx/spdx-online-tools/issues/287 Merge app and api code]<br /> * Fix and improve test [https://github.com/spdx/spdx-online-tools/issues/201 issue 201] [https://github.com/spdx/spdx-online-tools/issues/282 issue 282], [https://github.com/spdx/spdx-online-tools/issues/202 issue 202] + others<br /> * [https://github.com/spdx/spdx-online-tools/issues/299 Add a submit via mail functionality to license submittal]<br /> * [https://github.com/spdx/spdx-online-tools/issues/218 Store license diff screenshot in database instead of uploading to github]<br /> * [https://github.com/spdx/spdx-online-tools/issues/157 Improve error message when error received from the Java code]<br /> * [https://github.com/spdx/spdx-online-tools/issues/186 Add a License Diff section to the SPDX Online Tool]<br /> * [https://github.com/spdx/spdx-online-tools/issues/91 API documentation tool]<br /> * API for license namespace <br /> * [https://github.com/spdx/spdx-online-tools/issues/204 Move to Github Apps and improvement for production]<br /> <br /> ====Available Mentors====<br /> [mailto:rohit.lodhartg@gmail.com Rohit Lodha] [mailto:anshuldutt21@gmail.com Anshul Dutt Sharma] [mailto:gary@sourceauditor.com Gary O'Neall]<br /> <br /> === Migrate Python Tools to Python 3 ===<br /> Migrate the [https://github.com/spdx/tools-python SPDX Python Tools] to Python 3 including all unit testing. In addition, additional known issues raised on GitHub may be tackled.<br /> <br /> ====Skills Needed====<br /> * Experience with Python3 programming<br /> * Knowledge of parsing algorithms<br /> <br /> ====Background Information====<br /> The Python tools are command-line tools and a library that implement reading and writing of SPDX files in different formats, as well as converting and validating SPDX files.<br /> The current implementation uses Python 2, which is no longer supported.<br /> In addition to migration, some additional tasks may be taken on to improve the supportability of the library. In particular, restructuring the code to separate out the different serialization formats (see [https://github.com/spdx/tools-python/issues/147 issue 147]).<br /> <br /> ====Available Mentors====<br /> [mailto:santiago@nyu.edu Santiago Torres Arias] [mailto:alexios.zavras@intel.com Alexios Zavras] [mailto:anshuldutt21@gmail.com Anshul Dutt Sharma]<br /> <br /> === RDF Writer for Golang ===<br /> Gordf supports writing rdf triples to rdf file. Create an interface that would take in a SPDX document and generate RDF triples out of it. Which will then be consumed by the gordf to generate a RDF/xml file.<br /> <br /> ====Skills Needed====<br /> * Knowledge of RDF<br /> * Skills in XML parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> RDF/XML is one of the supported formats for SPDX documents. Creating an RDFWriter would create a generally useful facility for Golang and provide a more modular structure for the SPDX Golang tools.<br /> <br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar]<br /> <br /> === YAML Support for Golang libraries ===<br /> YAML is one of the supported formats for SPDX. This project is to add support for reading and writing YAML to the Golang libraries.<br /> <br /> ====Skills Needed====<br /> * Knowledge of YAML<br /> * Skills in YAML parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar] [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> <br /> === JSON Support for Golang libraries ===<br /> JSON is one of the supported formats for SPDX. This project is to add support for reading and writing JSON to the Golang libraries.<br /> <br /> ====Skills Needed====<br /> * Knowledge of JSON<br /> * Skills in JSON parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar] [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> <br /> ==SPDX Specification Projects==<br /> The following projects contribute directly to the creation or validation of the SPDX specification.<br /> <br /> === Generate a JSON Representation of the Specification from Structured Markdown ===<br /> Convert a consistently structured Markdown file into a JSON structure following a well defined schema. Changes to an existing Markdown file should update the JSON files. The Markdown will have a well defined structure to allow for translation of the text in Markdown to the properties of the JSON file. The conversion will also validate that the Markdown follows the required specification. The conversion would be run as part of a Github action for the SPDX specification.<br /> <br /> ====Skills Needed====<br /> * Skills in writing parsing algorithms (e.g. working with [https://en.wikipedia.org/wiki/Abstract_syntax_tree Abstract Syntax Tree])<br /> * Knowledge and experience in the programming language chosen for the project (e.g. Java, JavaScript, Python)<br /> * Knowledge of Markdown and JSON syntax<br /> <br /> ====Background Information====<br /> The SPDX tech team works very collaboratively on the specification updates using markdown pages in GitHub as the primary documentation for the specification. RDF/OWL is used as the primary technical specification for the object model including relationships, cardinality, class structure, and other restrictions. There is a lot of overlap between the information in the Markdown and the information in the OWL document. To improve the quality and productivity of the specification work, the SPDX technical team has decided to add tooling for verification of the Markdown and conversion of any common information to the OWL document. The conversion will be in 2 stages:<br /> * Convert from Markdown to an intermediate JSON format<br /> * Convert from the JSON format to RDF/OWL<br /> <br /> The specific schema for the JSON format is under development and planned to be available before the start of GSoC.<br /> <br /> Below are some additional resources for this project:<br /> * [https://github.github.com/gfm/ GitHub flavored Markdown]<br /> * [https://json-schema.org/ JSON Schema] information site and its [https://tools.ietf.org/html/draft-bhutton-json-schema-00 current draft]<br /> * [https://docs.google.com/document/d/13PojpaFPdoKZ9Gyh_DEY-Rp7lldyMbSiGE3vCRQhR9M/edit# Results of process discussion]<br /> * [https://docs.google.com/document/d/1EGoAmKxPfmmlF3XV6fXwNmsCiFKLH83Bhh8_xrmGhko Analysis of RDF/OWL fields relative to Markdown] (work in progress)<br /> * [https://docs.google.com/document/d/1LN5CepVVOu38w4pXeLpw_3BDNn2CKAWUyTVdlh8C2WM/edit?usp=sharing Template for Spec Markdown] (work in progress)<br /> * [https://docs.google.com/document/d/1J6P3q6wcP0c1xquTIfMfIBJCa8S1xtkhDs6dD1hSf4Y/edit?usp=sharing Example spec JSON file] (work in progress)<br /> * [https://docs.google.com/document/d/1OF_EqfU4tLPF-oGheEZ1aCzsnGIJHyRptzQ_U7AA-wY/edit?usp=sharing Draft JSON schema] (work in progress)<br /> <br /> ====Available Mentors====<br /> [mailto:gary@sourceauditor.com Gary O'Neall] [mailto:alexios.zavras@intel.com Alexios Zavras]<br /> <br /> === Generate RDF/OWL from from JSON specification format ===<br /> Convert a set of JSON files into a Web Ontology Language XML document. The JSON file will map to the elements and attributes of the RDF/OWL XML file. The JSON schema will be defined prior to the project start and will be consistent with the &quot;Generate a JSON Representation of the Specification from Structured Markdown&quot; project described above.<br /> <br /> ====Skills Needed====<br /> * Knowledge and experience in the programming language chosen for the project (e.g. Java, JavaScript, Python)<br /> * Knowledge of RDF/OWL/XML formats<br /> * Knowledge of JSON parsers<br /> <br /> ====Background Information====<br /> The SPDX tech team works very collaboratively on the specification updates using markdown pages in GitHub as the primary documentation for the specification. RDF/OWL is used as the primary technical specification for the object model including relationships, cardinality, class structure, and other restrictions. There is a lot of overlap between the information in the Markdown and the information in the OWL document. To improve the quality and productivity of the specification work, the SPDX technical team has decided to add tooling for verification of the Markdown and conversion of any common information to the OWL document. The conversion will be in 2 stages:<br /> * Convert from Markdown to an intermediate JSON format<br /> * Convert from the JSON format to RDF/OWL<br /> <br /> The specific schema for the JSON format is under development and planned to be available before the start of GSoC.<br /> <br /> Below are some additional resources for this project:<br /> * [https://www.w3.org/TR/2004/NOTE-owl-parsing-20040121/ RDF OWL parsing notes from the W3C]<br /> * [https://json-schema.org/ JSON Schema] information site and its [https://tools.ietf.org/html/draft-bhutton-json-schema-00 current draft]<br /> * [https://docs.google.com/document/d/13PojpaFPdoKZ9Gyh_DEY-Rp7lldyMbSiGE3vCRQhR9M/edit# Results of process discussion]<br /> * [https://docs.google.com/document/d/1EGoAmKxPfmmlF3XV6fXwNmsCiFKLH83Bhh8_xrmGhko Analysis of RDF/OWL fields relative to Markdown] (work in progress)<br /> * [https://github.com/spdx/spdx-spec/blob/development/v2.2.1/ontology/spdx-ontology.owl.xml Current RDF/OWL document for SPDX spec]<br /> * [https://docs.google.com/document/d/1LN5CepVVOu38w4pXeLpw_3BDNn2CKAWUyTVdlh8C2WM/edit?usp=sharing Template for Spec Markdown] (work in progress)<br /> * [https://docs.google.com/document/d/1J6P3q6wcP0c1xquTIfMfIBJCa8S1xtkhDs6dD1hSf4Y/edit?usp=sharing Example spec JSON file] (work in progress)<br /> * [https://docs.google.com/document/d/1OF_EqfU4tLPF-oGheEZ1aCzsnGIJHyRptzQ_U7AA-wY/edit?usp=sharing Draft JSON schema] (work in progress)<br /> <br /> ====Available Mentors====<br /> [mailto:gary@sourceauditor.com Gary O'Neall] [mailto:alexios.zavras@intel.com Alexios Zavras]<br /> <br /> === SPDX Specification Views for legal counsels and developers ===<br /> The proposal is to see if it possible to deduct large SPDX documents into a small subset SPDX document providing a specific reduced &quot;views&quot; on larger data.<br /> ====Skills Needed====<br /> * Understanding of compliance needs of legal counsels and developers so we can remove friction to adopt SPDX<br /> ====Background Information====<br /> SPDX documents commonly contain 100s, if not 1000s of entries making it hard for a human to make manual corrections or draw conclusions. No scanner can provide 100% complete data human corrections are usual needed. The aim from this proposal is twofold:<br /> 1. Enable developers with a &quot;code view&quot; of tool-generated SPDX document close to the code they work on to enable them to make corrections to the SPDX data. For instance amend SPDX package tag values or model package dependencies not detected by used scanner.<br /> 2. Provide legal counsels with a &quot;package and limited file view&quot; to enable legal conclusions<br /> ====Available Mentors====<br /> [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> [mailto:thomas.steenbergen@here.com Thomas Steenbergen]<br /> <br /> === ClearlyDefined exporting and importing SPDX documents ===<br /> The goal of this GSoC project would be to add support in the [https://https://github.com/clearlydefined ClearlyDefined project] to export curated data into SPDX 2.2 documents. Once that is accomplished, being able to import SPDX documents into the curated database would be the next step.<br /> <br /> ====Skills Needed====<br /> * Experience with JSON and YAML (XML a plus)<br /> * Ability to interpret and implement the SPDX specification and related ClearlyDefined community documentation<br /> * Ability to work with the community in integrating results with other projects<br /> * Willingness to learn about open source licensing and related technical matters<br /> <br /> ====Background Information====<br /> Export a ClearlyDefined workspace as a SPDX document:<br /> * user to navigate to https://clearlydefined.io/workspace<br /> * Add one or more components to the workspace through any of the existing means, <br /> * then click Share, and then slick SPDX (choice of 2.2 supported output formats).<br /> which would result in an SPDX document is exported containing all of the components that were in the workspace.<br /> Note: If there is mandatory information required by SPDX that ClearlyDefined does not have we will need to determine how to accommodate that.<br /> <br /> To populate a workspace from a SPDX document:<br /> * user to navigate to https://clearlydefined.io/workspace<br /> * drag a SPDX document into the workspace and then all of the components in the SPDX document are added to the workspace.<br /> <br /> There are some discrepancies between the content in ClearlyDefined and that SPDX documents, so work would be needed with both communities to figure out: what to do if license information in the SPDX disagrees with what ClearlyDefined has and how to handle pending curations?<br /> <br /> ====Available Mentors====<br /> [mailto:kstewart@linuxfoundation.org Kate Stewart]<br /> [mailto:IAMWILLBAR@github.com William Bartholomew]</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2021-03-25T11:00:49Z

<p>Zvr: /* Migrate Python Tools to Python 3 */</p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2021 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> =Proposed 2021 Projects=<br /> <br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal. <br /> <br /> (The projects from 2019 can be found on the [https://summerofcode.withgoogle.com/organizations/4532099550281728/#5727887162867712 2019 Google Summer of Code projects page for SPDX] ).<br /> <br /> ==SPDX Workgroup Tooling Projects== <br /> These projects are aimed at contributing to the SPDX tools to help reduce the effort to create SPDX documents and increase the accuracy of them.<br /> <br /> === Migrate SPDX Online Tools to DJango3 ===<br /> Migrate the SPDX online tools to later versions of Django and upgrade dependencies (such as Django Social Auth) to later version to support better / more secure authentication to Github. In addition to migrating to DJango 3, additional issues can be taken on to create a full GSoC project (see the list below).<br /> <br /> ====Skills Needed====<br /> * Experience with Python3 programming<br /> * Familiar with Django framework<br /> <br /> ====Background Information====<br /> The SPDX Online Tools are currently being migrated to Python3. Several libraries can now be upgraded to more supportable versions including DJango. There are some known issues with the current version of Django Social Auth which would be resolved by upgrading the versions. There may be additional libraries which can be upgraded. There is also an opportunity to improve the structure and unit tests for the online tools if time allows. See the [https://github.com/spdx/spdx-online-tools/tree/rtgdk_python3 Python3 Branch] of the SPDX online tools for the current state of the Python3 migration.<br /> <br /> Additional tasks and issues can can be included in a project (in priority order):<br /> * Migrate project to python3 and Django3 [https://github.com/spdx/spdx-online-tools/issues/58 issue 50] and [https://github.com/spdx/spdx-online-tools/issues/24 issue 24]<br /> * [https://github.com/spdx/spdx-online-tools/issues/287 Merge app and api code]<br /> * Fix and improve test [https://github.com/spdx/spdx-online-tools/issues/201 issue 201] [https://github.com/spdx/spdx-online-tools/issues/282 issue 282], [https://github.com/spdx/spdx-online-tools/issues/202 issue 202] + others<br /> * [https://github.com/spdx/spdx-online-tools/issues/299 Add a submit via mail functionality to license submittal]<br /> * [https://github.com/spdx/spdx-online-tools/issues/218 Store license diff screenshot in database instead of uploading to github]<br /> * [https://github.com/spdx/spdx-online-tools/issues/157 Improve error message when error received from the Java code]<br /> * [https://github.com/spdx/spdx-online-tools/issues/186 Add a License Diff section to the SPDX Online Tool]<br /> * [https://github.com/spdx/spdx-online-tools/issues/91 API documentation tool]<br /> * API for license namespace <br /> * [https://github.com/spdx/spdx-online-tools/issues/204 Move to Github Apps and improvement for production]<br /> <br /> ====Available Mentors====<br /> [mailto:rohit.lodhartg@gmail.com Rohit Lodha] [mailto:gary@sourceauditor.com Gary O'Neall]<br /> <br /> === Migrate Python Tools to Python 3 ===<br /> Migrate the [https://github.com/spdx/tools-python SPDX Python Tools] to Python 3 including all unit testing. In addition, additional known issues raised on GitHub may be tackled.<br /> <br /> ====Skills Needed====<br /> * Experience with Python3 programming<br /> * Knowledge of parsing algorithms<br /> <br /> ====Background Information====<br /> The Python tools are command-line tools and a library that implement reading and writing of SPDX files in different formats, as well as converting and validating SPDX files.<br /> The current implementation uses Python 2, which is no longer supported.<br /> In addition to migration, some additional tasks may be taken on to improve the supportability of the library. In particular, restructuring the code to separate out the different serialization formats (see [https://github.com/spdx/tools-python/issues/147 issue 147]).<br /> <br /> ====Available Mentors====<br /> [mailto:santiago@nyu.edu Santiago Torres Arias] [mailto:alexios.zavras@intel.com Alexios Zavras]<br /> <br /> === RDF Writer for Golang ===<br /> Gordf supports writing rdf triples to rdf file. Create an interface that would take in a SPDX document and generate RDF triples out of it. Which will then be consumed by the gordf to generate a RDF/xml file.<br /> <br /> ====Skills Needed====<br /> * Knowledge of RDF<br /> * Skills in XML parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> RDF/XML is one of the supported formats for SPDX documents. Creating an RDFWriter would create a generally useful facility for Golang and provide a more modular structure for the SPDX Golang tools.<br /> <br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar]<br /> <br /> === YAML Support for Golang libraries ===<br /> YAML is one of the supported formats for SPDX. This project is to add support for reading and writing YAML to the Golang libraries.<br /> <br /> ====Skills Needed====<br /> * Knowledge of YAML<br /> * Skills in YAML parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar] [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> <br /> === JSON Support for Golang libraries ===<br /> JSON is one of the supported formats for SPDX. This project is to add support for reading and writing JSON to the Golang libraries.<br /> <br /> ====Skills Needed====<br /> * Knowledge of JSON<br /> * Skills in JSON parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar] [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> <br /> ==SPDX Specification Projects==<br /> The following projects contribute directly to the creation or validation of the SPDX specification.<br /> <br /> === Generate a JSON Representation of the Specification from Structured Markdown ===<br /> Convert a consistently structured Markdown file into a JSON structure following a well defined schema. Changes to an existing Markdown file should update the JSON files. The Markdown will have a well defined structure to allow for translation of the text in Markdown to the properties of the JSON file. The conversion will also validate that the Markdown follows the required specification. The conversion would be run as part of a Github action for the SPDX specification.<br /> <br /> ====Skills Needed====<br /> * Skills in writing parsing algorithms (e.g. working with [https://en.wikipedia.org/wiki/Abstract_syntax_tree Abstract Syntax Tree])<br /> * Knowledge and experience in the programming language chosen for the project (e.g. Java, JavaScript, Python)<br /> * Knowledge of Markdown and JSON syntax<br /> <br /> ====Background Information====<br /> The SPDX tech team works very collaboratively on the specification updates using markdown pages in GitHub as the primary documentation for the specification. RDF/OWL is used as the primary technical specification for the object model including relationships, cardinality, class structure, and other restrictions. There is a lot of overlap between the information in the Markdown and the information in the OWL document. To improve the quality and productivity of the specification work, the SPDX technical team has decided to add tooling for verification of the Markdown and conversion of any common information to the OWL document. The conversion will be in 2 stages:<br /> * Convert from Markdown to an intermediate JSON format<br /> * Convert from the JSON format to RDF/OWL<br /> <br /> The specific schema for the JSON format is under development and planned to be available before the start of GSoC.<br /> <br /> Below are some additional resources for this project:<br /> * [https://github.github.com/gfm/ GitHub flavored Markdown]<br /> * [https://json-schema.org/ JSON Schema] information site and its [https://tools.ietf.org/html/draft-bhutton-json-schema-00 current draft]<br /> * [https://docs.google.com/document/d/13PojpaFPdoKZ9Gyh_DEY-Rp7lldyMbSiGE3vCRQhR9M/edit# Results of process discussion]<br /> * [https://docs.google.com/document/d/1EGoAmKxPfmmlF3XV6fXwNmsCiFKLH83Bhh8_xrmGhko Analysis of RDF/OWL fields relative to Markdown] (work in progress)<br /> * [https://docs.google.com/document/d/1LN5CepVVOu38w4pXeLpw_3BDNn2CKAWUyTVdlh8C2WM/edit?usp=sharing Template for Spec Markdown] (work in progress)<br /> * [https://docs.google.com/document/d/1J6P3q6wcP0c1xquTIfMfIBJCa8S1xtkhDs6dD1hSf4Y/edit?usp=sharing Example spec JSON file] (work in progress)<br /> * [https://docs.google.com/document/d/1OF_EqfU4tLPF-oGheEZ1aCzsnGIJHyRptzQ_U7AA-wY/edit?usp=sharing Draft JSON schema] (work in progress)<br /> <br /> ====Available Mentors====<br /> [mailto:gary@sourceauditor.com Gary O'Neall] [mailto:alexios.zavras@intel.com Alexios Zavras]<br /> <br /> === Generate RDF/OWL from from JSON specification format ===<br /> Convert a set of JSON files into a Web Ontology Language XML document. The JSON file will map to the elements and attributes of the RDF/OWL XML file. The JSON schema will be defined prior to the project start and will be consistent with the &quot;Generate a JSON Representation of the Specification from Structured Markdown&quot; project described above.<br /> <br /> ====Skills Needed====<br /> * Knowledge and experience in the programming language chosen for the project (e.g. Java, JavaScript, Python)<br /> * Knowledge of RDF/OWL/XML formats<br /> * Knowledge of JSON parsers<br /> <br /> ====Background Information====<br /> The SPDX tech team works very collaboratively on the specification updates using markdown pages in GitHub as the primary documentation for the specification. RDF/OWL is used as the primary technical specification for the object model including relationships, cardinality, class structure, and other restrictions. There is a lot of overlap between the information in the Markdown and the information in the OWL document. To improve the quality and productivity of the specification work, the SPDX technical team has decided to add tooling for verification of the Markdown and conversion of any common information to the OWL document. The conversion will be in 2 stages:<br /> * Convert from Markdown to an intermediate JSON format<br /> * Convert from the JSON format to RDF/OWL<br /> <br /> The specific schema for the JSON format is under development and planned to be available before the start of GSoC.<br /> <br /> Below are some additional resources for this project:<br /> * [https://www.w3.org/TR/2004/NOTE-owl-parsing-20040121/ RDF OWL parsing notes from the W3C]<br /> * [https://json-schema.org/ JSON Schema] information site and its [https://tools.ietf.org/html/draft-bhutton-json-schema-00 current draft]<br /> * [https://docs.google.com/document/d/13PojpaFPdoKZ9Gyh_DEY-Rp7lldyMbSiGE3vCRQhR9M/edit# Results of process discussion]<br /> * [https://docs.google.com/document/d/1EGoAmKxPfmmlF3XV6fXwNmsCiFKLH83Bhh8_xrmGhko Analysis of RDF/OWL fields relative to Markdown] (work in progress)<br /> * [https://github.com/spdx/spdx-spec/blob/development/v2.2.1/ontology/spdx-ontology.owl.xml Current RDF/OWL document for SPDX spec]<br /> * [https://docs.google.com/document/d/1LN5CepVVOu38w4pXeLpw_3BDNn2CKAWUyTVdlh8C2WM/edit?usp=sharing Template for Spec Markdown] (work in progress)<br /> * [https://docs.google.com/document/d/1J6P3q6wcP0c1xquTIfMfIBJCa8S1xtkhDs6dD1hSf4Y/edit?usp=sharing Example spec JSON file] (work in progress)<br /> * [https://docs.google.com/document/d/1OF_EqfU4tLPF-oGheEZ1aCzsnGIJHyRptzQ_U7AA-wY/edit?usp=sharing Draft JSON schema] (work in progress)<br /> <br /> ====Available Mentors====<br /> [mailto:gary@sourceauditor.com Gary O'Neall] [mailto:alexios.zavras@intel.com Alexios Zavras]<br /> <br /> === SPDX Specification Views for legal counsels and developers ===<br /> The proposal is to see if it possible to deduct large SPDX documents into a small subset SPDX document providing a specific reduced &quot;views&quot; on larger data.<br /> ====Skills Needed====<br /> * Understanding of compliance needs of legal counsels and developers so we can remove friction to adopt SPDX<br /> ====Background Information====<br /> SPDX documents commonly contain 100s, if not 1000s of entries making it hard for a human to make manual corrections or draw conclusions. No scanner can provide 100% complete data human corrections are usual needed. The aim from this proposal is twofold:<br /> 1. Enable developers with a &quot;code view&quot; of tool-generated SPDX document close to the code they work on to enable them to make corrections to the SPDX data. For instance amend SPDX package tag values or model package dependencies not detected by used scanner.<br /> 2. Provide legal counsels with a &quot;package and limited file view&quot; to enable legal conclusions<br /> ====Available Mentors====<br /> [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> [mailto:thomas.steenbergen@here.com Thomas Steenbergen]<br /> <br /> === ClearlyDefined exporting and importing SPDX documents ===<br /> The goal of this GSoC project would be to add support in the [https://https://github.com/clearlydefined ClearlyDefined project] to export curated data into SPDX 2.2 documents. Once that is accomplished, being able to import SPDX documents into the curated database would be the next step.<br /> <br /> ====Skills Needed====<br /> * Experience with JSON and YAML (XML a plus)<br /> * Ability to interpret and implement the SPDX specification and related ClearlyDefined community documentation<br /> * Ability to work with the community in integrating results with other projects<br /> * Willingness to learn about open source licensing and related technical matters<br /> <br /> ====Background Information====<br /> Export a ClearlyDefined workspace as a SPDX document:<br /> * user to navigate to https://clearlydefined.io/workspace<br /> * Add one or more components to the workspace through any of the existing means, <br /> * then click Share, and then slick SPDX (choice of 2.2 supported output formats).<br /> which would result in an SPDX document is exported containing all of the components that were in the workspace.<br /> Note: If there is mandatory information required by SPDX that ClearlyDefined does not have we will need to determine how to accommodate that.<br /> <br /> To populate a workspace from a SPDX document:<br /> * user to navigate to https://clearlydefined.io/workspace<br /> * drag a SPDX document into the workspace and then all of the components in the SPDX document are added to the workspace.<br /> <br /> There are some discrepancies between the content in ClearlyDefined and that SPDX documents, so work would be needed with both communities to figure out: what to do if license information in the SPDX disagrees with what ClearlyDefined has and how to handle pending curations?<br /> <br /> ====Available Mentors====<br /> [mailto:kstewart@linuxfoundation.org Kate Stewart]<br /> [mailto:IAMWILLBAR@github.com William Bartholomew]</div>

Zvr https://wiki.spdx.org/view/Technical_Team 2021-03-23T17:04:51Z

<p>Zvr: </p> <hr /> <div>This is the working area for the technical team. This team has primary responsibility for drafting the specification and developing documentation, templates, samples and tools.<br /> <br /> The Technical Team meets weekly on <br /> <br /> Tuesdays at 16:00 UTC (and best guess for local time – 9:00AM PDT, 10:00 AM MDT, 11:00 AM CDT, 12:00PM EDT, 18:00 CEST).<br /> <br /> Canada +1 647 558 0588<br /> Germany +49 30 3080 6188<br /> Japan +81 3 4578 1488<br /> US Toll-free 877 369 0926<br /> Find your local number: https://zoom.us/u/ac9KKJWzJT<br /> <br /> Zoom meeting:<br /> https://zoom.us/j/663426859<br /> Meeting ID: 663 426 859<br /> <br /> <br /> <br /> * [[Technical_Team/SPDX_Upcoming_Meetings|SPDX Upcoming Meeting Agenda]]<br /> * [[Technical_Team/SPDX_Specification_Versions|SPDX Specification Versions]]<br /> * [[Technical_Team/SPDX_RDF_Vocabularies_and_Terms|SPDX RDF Vocabularies and Terms]]<br /> * [[Technical_Team/Minutes|Meeting Minutes for the Technical Team]]<br /> * [[Technical_Team/Priorities|Current Priorities and Work in Progress for the Technical Team]]<br /> * [[Technical_Team/Old|Older Items for the Technical Team]]<br /> * [[Technical_Team/Field_Names|Field Names]]<br /> * [[Technical_Team/Spreadsheet_Template|Spreadsheet Template]]<br /> <br /> [[Category:Technical]] [[Category:TestCategory]]</div>

Zvr https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas 2021-02-04T09:51:29Z

<p>Zvr: /* SPDX Specification Projects */</p> <hr /> <div>&lt;br /&gt;<br /> <br /> &lt;span style=&quot;font-size:150%&quot;&gt;'''Welcome to the 2021 SPDX Google Summer of Code Project Page'''&lt;/span&gt;<br /> <br /> See the [https://rtgdk.github.io/spdx-gsoc-proposal.html proposal template] if you are interested in submitting a Google Summer of Code proposal.<br /> <br /> Should you have questions please do not hesitate to contact one of the mentors directly.<br /> <br /> &lt;br /&gt;<br /> <br /> __TOC__<br /> <br /> &lt;br /&gt;<br /> <br /> == What is SPDX ? ==<br /> <br /> First and foremost we are a community dedicated to solving the issues and problems around Open Source licensing and compliance. The SPDX work group (part of the Linux Foundation) consists of individuals, community members, and representatives from companies, foundations and organizations who use or are considering using the SPDX standard. The work group operates much like a meritocratic, consensus-based community project; that is, anyone with an interest in the project can join the community, contribute to the specification, and participate in the decision-making process. We come from many different backgrounds including open source developers, lawyers, consultants and business professionals, many of who have been involved with license compliance and identification for years.<br /> <br /> As part of this effort we have developed a set of collateral that can be used:<br /> <br /> * [https://spdx.org/using-spdx License List and Short Identifiers]<br /> * [https://spdx.org/using-spdx SPDX Specification for generating SPDX Documents in multiple formats]<br /> * [https://spdx.org/tools A set of basic tools for working with SPDX Documents]<br /> * [https://spdx.org/using-spdx License Identifiers in source]<br /> <br /> == Why choose an SPDX Project? ==<br /> <br /> Contributing to one of the SPDX projects below will provide a valuable contribution to developers and/or users of open source software. We believe you will find the projects both technically challenging and rewarding. In essence we believe you will be able to look back one day and I say I was part of that effort.<br /> <br /> &lt;br/&gt;<br /> <br /> = Getting Involved =<br /> <br /> Beyond working with your mentor(s) we highly encourage students who select one of these projects to get involved with the SPDX community via our technical working group. Interaction with the technical team is primarily done via its mailing list and on gitter (see resources). There is however a weekly call you could join as well. .<br /> <br /> == Resources ==<br /> <br /> * [http://spdx.org SPDX website]<br /> * [https://spdx.org/specifications SPDX Specification]<br /> * [https://spdx.org/tools SPDX Workgroup Tools webpage]<br /> * [https://lists.spdx.org/mailman/listinfo/spdx-tech SPDX tech mailing list]<br /> <br /> =Proposed 2021 Projects=<br /> <br /> Mentors: please fill out the following template for any projects you wish to propose. <br /> <br /> === Project Name ===<br /> add overview of project here<br /> ====Skills Needed====<br /> what skills should the student have to do the coding exercises<br /> ====Background Information====<br /> context for the project and references to be studied<br /> ====Available Mentors====<br /> list individuals who are willing to mentor and provide information about the project proposal. <br /> <br /> (The projects from 2019 can be found on the [https://summerofcode.withgoogle.com/organizations/4532099550281728/#5727887162867712 2019 Google Summer of Code projects page for SPDX] ).<br /> <br /> ==SPDX Workgroup Tooling Projects== <br /> These projects are aimed at contributing to the SPDX tools to help reduce the effort to create SPDX documents and increase the accuracy of them.<br /> <br /> === Migrate SPDX Online Tools to DJango3 ===<br /> Migrate the SPDX online tools to later versions of Django and upgrade dependencies (such as Django Social Auth) to later version to support better / more secure authentication to Github.<br /> <br /> ====Skills Needed====<br /> * Experience with Python3 programming<br /> * Familiar with Django framework<br /> <br /> ====Background Information====<br /> The SPDX Online Tools are currently being migrated to Python3. Several libraries can now be upgraded to more supportable versions including DJango. There are some known issues with the current version of Django Social Auth which would be resolved by upgrading the versions. There may be additional libraries which can be upgraded. There is also an opportunity to improve the structure and unit tests for the online tools if time allows. See the [Python3 Branch https://github.com/spdx/spdx-online-tools/tree/rtgdk_python3] of the SPDX online tools for the current state of the Python3 migration.<br /> <br /> ====Available Mentors====<br /> [mailto:rohit.lodhartg@gmail.com Rohit Lodha] [mailto:gary@sourceauditor.com Gary O'Neall]<br /> <br /> === RDF Writer for Golang ===<br /> Gordf supports writing rdf triples to rdf file. Create an interface that would take in a SPDX document and generate RDF triples out of it. Which will then be consumed by the gordf to generate a RDF/xml file.<br /> <br /> ====Skills Needed====<br /> * Knowledge of RDF<br /> * Skills in XML parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> RDF/XML is one of the supported formats for SPDX documents. Creating an RDFWriter would create a generally useful facility for Golang and provide a more modular structure for the SPDX Golang tools.<br /> <br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar]<br /> <br /> === YAML Support for Golang libraries ===<br /> YAML is one of the supported formats for SPDX. This project is to add support for reading and writing YAML to the Golang libraries.<br /> <br /> ====Skills Needed====<br /> * Knowledge of YAML<br /> * Skills in YAML parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar] [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> <br /> === JSON Support for Golang libraries ===<br /> JSON is one of the supported formats for SPDX. This project is to add support for reading and writing JSON to the Golang libraries.<br /> <br /> ====Skills Needed====<br /> * Knowledge of JSON<br /> * Skills in JSON parsing<br /> * Knowledge and experience in Golang<br /> <br /> ====Background Information====<br /> See the [https://github.com/spdx/tools-golang SPDX Golang tools repo] and the [https://github.com/spdx/gordf gordf library] for more details on the current implementations.<br /> <br /> ====Available Mentors====<br /> [mailto:bhatnagarrishabh4@gmail.com Rishabh Bhatnagar] [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> <br /> ==SPDX Specification Projects==<br /> The following projects contribute directly to the creation or validation of the SPDX specification.<br /> <br /> === Generate a JSON Representation of the Specification from Structured Markdown ===<br /> Convert a consistently structured Markdown file into a JSON structure following a well defined schema. Changes to an existing Markdown file should update the JSON files. The Markdown will have a well defined structure to allow for translation of the text in Markdown to the properties of the JSON file. The conversion will also validate that the Markdown follows the required specification. The conversion would be run as part of a Github action for the SPDX specification.<br /> <br /> ====Skills Needed====<br /> * Skills in writing parsing algorithms (e.g. working with [https://en.wikipedia.org/wiki/Abstract_syntax_tree Abstract Syntax Tree])<br /> * Knowledge and experience in the programming language chosen for the project (e.g. Java, JavaScript, Python)<br /> * Knowledge of Markdown and JSON syntax<br /> <br /> ====Background Information====<br /> The SPDX tech team works very collaboratively on the specification updates using markdown pages in GitHub as the primary documentation for the specification. RDF/OWL is used as the primary technical specification for the object model including relationships, cardinality, class structure, and other restrictions. There is a lot of overlap between the information in the Markdown and the information in the OWL document. To improve the quality and productivity of the specification work, the SPDX technical team has decided to add tooling for verification of the Markdown and conversion of any common information to the OWL document. The conversion will be in 2 stages:<br /> * Convert from Markdown to an intermediate JSON format<br /> * Convert from the JSON format to RDF/OWL<br /> <br /> The specific schema for the JSON format is under development and planned to be available before the start of GSoC.<br /> <br /> Below are some additional resources for this project:<br /> * [https://github.github.com/gfm/ GitHub flavored Markdown]<br /> * [https://json-schema.org/ JSON Schema] information site and its [https://tools.ietf.org/html/draft-bhutton-json-schema-00 current draft]<br /> * [https://docs.google.com/document/d/13PojpaFPdoKZ9Gyh_DEY-Rp7lldyMbSiGE3vCRQhR9M/edit# Results of process discussion]<br /> * [https://docs.google.com/document/d/1EGoAmKxPfmmlF3XV6fXwNmsCiFKLH83Bhh8_xrmGhko Analysis of RDF/OWL fields relative to Markdown] (work in progress)<br /> * [https://github.com/spdx/spdx-spec/tree/development/v3.0/chapters Markdown for version 3.0] - subject to change as we specify the markdown constraints for this project<br /> <br /> ====Available Mentors====<br /> [mailto:gary@sourceauditor.com Gary O'Neall] [mailto:alexios.zavras@intel.com Alexios Zavras]<br /> <br /> === Generate RDF/OWL from from JSON specification format ===<br /> Convert a set of JSON files into a Web Ontology Language XML document. The JSON file will map to the elements and attributes of the RDF/OWL XML file. The JSON schema will be defined prior to the project start and will be consistent with the &quot;Generate a JSON Representation of the Specification from Structured Markdown&quot; project described above.<br /> <br /> ====Skills Needed====<br /> * Knowledge and experience in the programming language chosen for the project (e.g. Java, JavaScript, Python)<br /> * Knowledge of RDF/OWL/XML formats<br /> * Knowledge of JSON parsers<br /> <br /> ====Background Information====<br /> The SPDX tech team works very collaboratively on the specification updates using markdown pages in GitHub as the primary documentation for the specification. RDF/OWL is used as the primary technical specification for the object model including relationships, cardinality, class structure, and other restrictions. There is a lot of overlap between the information in the Markdown and the information in the OWL document. To improve the quality and productivity of the specification work, the SPDX technical team has decided to add tooling for verification of the Markdown and conversion of any common information to the OWL document. The conversion will be in 2 stages:<br /> * Convert from Markdown to an intermediate JSON format<br /> * Convert from the JSON format to RDF/OWL<br /> <br /> The specific schema for the JSON format is under development and planned to be available before the start of GSoC.<br /> <br /> Below are some additional resources for this project:<br /> * [https://www.w3.org/TR/2004/NOTE-owl-parsing-20040121/ RDF OWL parsing notes from the W3C]<br /> * [https://json-schema.org/ JSON Schema] information site and its [https://tools.ietf.org/html/draft-bhutton-json-schema-00 current draft]<br /> * [https://docs.google.com/document/d/13PojpaFPdoKZ9Gyh_DEY-Rp7lldyMbSiGE3vCRQhR9M/edit# Results of process discussion]<br /> * [https://docs.google.com/document/d/1EGoAmKxPfmmlF3XV6fXwNmsCiFKLH83Bhh8_xrmGhko Analysis of RDF/OWL fields relative to Markdown] (work in progress)<br /> * [https://github.com/spdx/spdx-spec/blob/development/v2.2.1/ontology/spdx-ontology.owl.xml Current RDF/OWL document for SPDX spec]<br /> * [https://github.com/spdx/spdx-spec/tree/development/v3.0/chapters Markdown for version 3.0] - subject to change as we specify the markdown constraints for this project<br /> <br /> ====Available Mentors====<br /> [mailto:gary@sourceauditor.com Gary O'Neall] [mailto:alexios.zavras@intel.com Alexios Zavras]<br /> <br /> === SPDX Specification Views for legal counsels and developers ===<br /> The proposal is to see if it possible to deduct large SPDX documents into a small subset SPDX document providing a specific reduced &quot;views&quot; on larger data.<br /> ====Skills Needed====<br /> * Understanding of compliance needs of legal counsels and developers so we can remove friction to adopt SPDX<br /> ====Background Information====<br /> SPDX documents commonly contain 100s, if not 1000s of entries making it hard for a human to make manual corrections or draw conclusions. No scanner can provide 100% complete data human corrections are usual needed. The aim from this proposal is twofold:<br /> 1. Enable developers with a &quot;code view&quot; of tool-generated SPDX document close to the code they work on to enable them to make corrections to the SPDX data. For instance amend SPDX package tag values or model package dependencies not detected by used scanner.<br /> 2. Provide legal counsels with a &quot;package and limited file view&quot; to enable legal conclusions<br /> ====Available Mentors====<br /> [mailto:swinslow@linuxfoundation.org Steve Winslow]<br /> [mailto:thomas.steenbergen@here.com Thomas Steenbergen]<br /> <br /> === ClearlyDefined exporting and importing SPDX documents ===<br /> The goal of this GSoC project would be to add support in the [https://https://github.com/clearlydefined ClearlyDefined project] to export curated data into SPDX 2.2 documents. Once that is accomplished, being able to import SPDX documents into the curated database would be the next step.<br /> <br /> ====Skills Needed====<br /> * Experience with JSON and YAML (XML a plus)<br /> * Ability to interpret and implement the SPDX specification and related ClearlyDefined community documentation<br /> * Ability to work with the community in integrating results with other projects<br /> * Willingness to learn about open source licensing and related technical matters<br /> <br /> ====Background Information====<br /> Export a ClearlyDefined workspace as a SPDX document:<br /> * user to navigate to https://clearlydefined.io/workspace<br /> * Add one or more components to the workspace through any of the existing means, <br /> * then click Share, and then slick SPDX (choice of 2.2 supported output formats).<br /> which would result in an SPDX document is exported containing all of the components that were in the workspace.<br /> Note: If there is mandatory information required by SPDX that ClearlyDefined does not have we will need to determine how to accommodate that.<br /> <br /> To populate a workspace from a SPDX document:<br /> * user to navigate to https://clearlydefined.io/workspace<br /> * drag a SPDX document into the workspace and then all of the components in the SPDX document are added to the workspace.<br /> <br /> There are some discrepancies between the content in ClearlyDefined and that SPDX documents, so work would be needed with both communities to figure out: what to do if license information in the SPDX disagrees with what ClearlyDefined has and how to handle pending curations?<br /> <br /> ====Available Mentors====<br /> [mailto:kstewart@linuxfoundation.org Kate Stewart]<br /> [mailto:IAMWILLBAR@github.com William Bartholomew]</div>

Zvr