gsoc-2018
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
gsoc-2018 [2018/01/22 23:32] Michael Jaeger |
gsoc-2018 [2018/01/22 23:35] Michael Jaeger |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Google Summer of Code ===== | + | ===== Google Summer of Code 2018 ===== |
| We have applied for the Google Summer of Code 2018 as organization. This lists the topics so far we heve collected for this application. | We have applied for the Google Summer of Code 2018 as organization. This lists the topics so far we heve collected for this application. | ||
| Line 9: | Line 9: | ||
| * Michael: Michael C. Jaeger, mcj@mcj.de | * Michael: Michael C. Jaeger, mcj@mcj.de | ||
| - | === Project #1: Artifacts Scanner === | + | ==== Project #1: Artifacts Scanner ==== |
| == Skills Needed == | == Skills Needed == | ||
| Line 39: | Line 39: | ||
| == Description == | == Description == | ||
| - | A REST API in the straight forward sense of FOSSology would be about handling uploads or triggering scanners. However, a REST API in the sense of the SPDX standard, an XML format for expressing license compliance would be different than the traditional endpoints of the FOSSology application. For working in the sense of the SPDX standard it would be about file or source package centric endpoints for exchanging license and copyright, making hash sums of files or packages queryable as ressource, | + | A REST API in the straight forward sense of FOSSology would be about handling uploads or triggering scanners. However, a REST API in the sense of the SPDX standard, an XML format for expressing license compliance would be different than the traditional endpoints of the FOSSology application. For working in the sense of the SPDX standard it would be about file or source package centric endpoints for exchanging license and copyright, making hash sums of files or packages queryable as resource. A similar interface could be implemented as command line tool. |
| * SPDX license information standard https://spdx.org | * SPDX license information standard https://spdx.org | ||
| Line 53: | Line 53: | ||
| Kate, Michael | Kate, Michael | ||
| - | == Project #3: Graphical representation of license contents / graphical statistics == | + | ==== Project #3: Graphical representation of license contents / graphical statistics ==== |
| Description: It would be nice to see the the overall contents of a project at one glance. | Description: It would be nice to see the the overall contents of a project at one glance. | ||
| Possible Mentor(s): Maximilian, Michael | Possible Mentor(s): Maximilian, Michael | ||
| - | == Project #4: Fields for SPDX metadata, update to latest SPDX 2.1 and license list 3.0 == | + | ==== Project #4: Fields for SPDX metadata, update to latest SPDX 2.1 and license list 3.0 ==== |
| Description: | Description: | ||
gsoc-2018.txt ยท Last modified: 2022/11/18 12:46 by Gaurav Mishra
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
