User Tools

Site Tools


gsoc-2018

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
gsoc-2018 [2018/01/22 22:26]
Michael Jaeger created
gsoc-2018 [2018/01/23 17:45] (current)
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.
  
-== Mentors ==+==== Mentors ​====
  
-* Maximilian: Maximilian Huber, mail@maximilian-huber.de  +  ​* Maximilian: Maximilian Huber, mail@maximilian-huber.de  
-* Kate: Kate Stewart, kstewart@linuxofundation.org +  * Kate: Kate Stewart, kstewart@linuxofundation.org 
-* Michael: Michael C. Jaeger, mcj@mcj.de+  * Michael: Michael C. Jaeger, mcj@mcj.de
  
-== Project #1: Lightweight ​Scanner ==+==== Project #1: Artifacts ​Scanner ​====
  
-Description: Add a new lightweight Scanner which is able find licenses. e.gby taking ​the SPDX license ​list as input and figure out by itself how to detect them in source code+== Skills Needed == 
-Possible Mentor(s)Maximilian, Michael+ 
 +  * PHP and / or C/C++ programming 
 +  * Database programming 
 +  * Software development on Linux 
 + 
 +== Description ​== 
 + 
 +Current scanners search for regular expressions or text similarity of license textsHowever, this can lead to interpretations issues when it comes to conclude ​the actual condition of licensing of files. Opposed to genuine ​license ​texts, open source software authors use prosaic descriptions referring to licensing. If scanning understands different licensing artifacts, conclusions can be automated at higher precision. 
 + 
 +== Tasks == 
 + 
 +From an existing database of licensing texts and descriptions a model needs to createdBased on that model a the existing scanner is extended. With distinguishing recognition by types of licensing artifacts, conclusions can be automated more efficiently. 
 + 
 +== Possible Mentor(s) ​== 
 + 
 +Maximilian, Michael 
 + 
 +==== Project #2: Get SPDX file by command line and REST API ==== 
 + 
 +== Skills Needed == 
 + 
 +  * PHP and / or C/C++ programming 
 +  * Database programming 
 +  * Software development on Linux 
 + 
 +== 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 resource. A similar interface could be implemented as command line tool. 
 + 
 +  * SPDX license information standard https://​spdx.org 
 + 
 +== Tasks == 
 + 
 +Create a REST endpoint when FOSSology is deploying, allowing for exchanging license information for file hashes. 
 + 
 +https://​github.com/​fossology/​fossology/​issues/​592
  
-== Project #2:  get SPDX file by command line and REST API ==+== Possible Mentor(s) ​==
  
-Description:​ https://​github.com/​fossology/​fossology/​issues/​592 +Kate, Michael
-Possible Mentor(s):  ​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:​
Line 33: Line 67:
 More project Ideas: More project Ideas:
  
-* REST, throwing a SHA for upload there and get SPDX back (in case it is there already) +  ​A new REST API, throwing a SHA for upload there and get SPDX back (in case it is there already) 
-(Programming Language Analysis plugin) +  * A Programming Language Analysis plugin) 
-* Work on new clean-field implementation / ideas for new central hub +  * Cool search ​of files, currently the search is like 80ies style Web page 
-* Make scanners modular / independent +  * More intelligent / configurable decider
-* Cool search +
-* More intelligent / configurable decider+
gsoc-2018.1516660015.txt.gz · Last modified: 2018/01/22 22:26 by Michael Jaeger