Editing Google Summer of Code 2019 Accepted projects

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 9: Line 9:
 
It is expected that the project will deliver a well-tested version of UMLGraph built around  the new jdk.javadoc.doclet Doclet API with support for Java features such as Lambdas and Generics.
 
It is expected that the project will deliver a well-tested version of UMLGraph built around  the new jdk.javadoc.doclet Doclet API with support for Java features such as Lambdas and Generics.
  
==== GSOC 2019 Project Repository ====
+
==== Related Repositories ====
https://github.com/eellak/gsoc2019-UMLGraph
+
https://github.com/dspinellis/UMLGraph
  
 
==== Knowledge Prerequisites ====
 
==== Knowledge Prerequisites ====
Line 17: Line 17:
 
==== Mentors:  ====
 
==== Mentors:  ====
 
[https://github.com/dspinellis Diomidis Spinellis], [https://www.csd.auth.gr/en/staff/faculty?view=user&ro=1&id=14 Stamelos Ioannis]
 
[https://github.com/dspinellis Diomidis Spinellis], [https://www.csd.auth.gr/en/staff/faculty?view=user&ro=1&id=14 Stamelos Ioannis]
 +
 +
 +
== <br>  API Design Tool ==
 +
 +
=== Mentor Organisation: National Bank Of Greece ===
 +
 +
==== Brief Explanation: ====
 +
In the new world of “API Design First Approach” there is a need for a tool that can be used from both business or developer people to design the APIs. There are tools/IDE in the market at the moment that claim to fit this need but none has all the features required for the job.
 +
                                               
 +
 +
==== Related GitHub repositories ====
 +
There is no project URL at the moment.
 +
 +
==== Expected Results ====
 +
 +
** The API Design tool should fulfill the following requirements:
 +
** A person with no developer skills to be able to design/create an API visually.
 +
** A developer to be able to design the API manually by writing/editing the swagger file.
 +
** To be able to sync bidirectional changes to the API swagger file between the tool and a GitHub repository.
 +
** To be able to download the API in a swagger yaml or json file (resolved or unresolved format).
 +
** To be able to generate the API server stub in c#.
 +
** To be able to preview the documentation of the API.
 +
** To be able to download the documentation of the API.
 +
** To be able to mock the API functionality.
 +
** To be able to organize the APIs in projects and Teams.
 +
** To be able to invite other people to collaborate with the API design.
 +
** To be able to assign specific rights/roles to the people designing/viewing the the API.
 +
** To be able to make public or private an API.
 +
** To be able to create OAS2 and OAS3 APIs or convert between them.
 +
** To be able to view at a glance what were the last changes and who made them.
 +
 +
==== Knowledge Prerequisites ====
 +
AngularJS or ReactJS (latest stable version)
 +
C#
 +
 +
==== Mentors:  ====
 +
[mailto:bogdos.nikos@nbg.gr Bogdos Nikos], 
 +
[mailto:gkozntari.stamatia@nbg.gr Gkozntari Stamatia],
 +
[mailto:dkoliar@nbg.gr Koliarmou Despina],
 +
[mailto:agapitou.flora@nbg.gr Agapitou Flora].
  
 
== Greek Government Gazette text mining, cross-linking, and codification - 3gm ==
 
== Greek Government Gazette text mining, cross-linking, and codification - 3gm ==
Line 50: Line 90:
 
6. Possibility of interactive corrections of the structure and responsibilities derived from the NER & Metadata Extraction of the Greek Government Gazette
 
6. Possibility of interactive corrections of the structure and responsibilities derived from the NER & Metadata Extraction of the Greek Government Gazette
  
==== GSOC 2019 Project Repository ====
+
==== Related Repositories ====
https://github.com/eellak/gsoc2019-3gm
+
Source Code: https://github.com/eellak/gsoc2018-3gm
 +
 
 +
<nowiki> </nowiki>Web application: http://3gm.ellak.gr/
  
 
==== Knowledge Prerequisites ====
 
==== Knowledge Prerequisites ====
Line 98: Line 140:
 
d) The development of assembly guidelines and the creation of demo scenarios for the class.
 
d) The development of assembly guidelines and the creation of demo scenarios for the class.
  
==== <br> GSOC 2019 Project Repository ====
+
 
https://github.com/eellak/gsoc2019-diyrobot
+
 
 +
==== Related Repositories ====
 +
https://hackaday.io/project/26007-versatile-educational-2wd-robot
  
 
==== Knowledge Prerequisites ====
 
==== Knowledge Prerequisites ====
Line 106: Line 150:
 
==== Mentors:  ====
 
==== Mentors:  ====
 
[https://www.dit.hua.gr/~varlamis/ Iraklis Varlamis], [https://github.com/tgkarounos Theodoros Karounos]
 
[https://www.dit.hua.gr/~varlamis/ Iraklis Varlamis], [https://github.com/tgkarounos Theodoros Karounos]
 
  
  
Line 122: Line 165:
 
Thesis subjects must fall under one or more topics, from a list that the department sets and the topic information along with the title, a description and a list of references is stored with each subject.
 
Thesis subjects must fall under one or more topics, from a list that the department sets and the topic information along with the title, a description and a list of references is stored with each subject.
  
When the professor finally decides on the student(s) that will carry out a project, he/she has to propose two more professors from the department or externals that will co-supervise the project.
+
When the profesor finally decides on the student(s) that will carry out a project, he/she has to propose two more professors from the department or externals that will co-supervise the project.
  
 
When all the assignments have been fixed by the administrator of the TMS, they can be exported in a document which can be published on the department web site.
 
When all the assignments have been fixed by the administrator of the TMS, they can be exported in a document which can be published on the department web site.
Line 135: Line 178:
 
In the three months of the project it is expected to have the whole functionality required to support the TMS lifecycle.
 
In the three months of the project it is expected to have the whole functionality required to support the TMS lifecycle.
  
==== GSOC 2019 Project Repository ====
+
==== Related Repositories ====
https://github.com/eellak/gsoc2019-tms
+
https://github.com/redhatcz/Thesis-management-system
  
 
==== Knowledge Prerequisites ====
 
==== Knowledge Prerequisites ====
Line 150: Line 193:
 
Git-issue is a minimalist decentralized issue management system based on Git. It has the following advantages over other systems.
 
Git-issue is a minimalist decentralized issue management system based on Git. It has the following advantages over other systems.
  
No backend, no dependencies: You can install and use git issue with a single shell script. There's no need for a server or a database back-end, and the corresponding problems and requirements for their administration.
+
    No backend, no dependencies: You can install and use git issue with a single shell script. There's no need for a server or a database back-end, and the corresponding problems and requirements for their administration.
  
Decentralized asynchronous management: Anyone can add, comment, and edit issues without requiring online access to a centralized server. There's no need for online connectivity; you can pull and push issues when you're online.Transparent text file format: Issues are stored as simple text files, which you can view, edit, share, and backup with any tool you like. There's no risk of loosing access to your issues because a server has failed.
+
    Decentralized asynchronous management: Anyone can add, comment, and edit issues without requiring online access to a centralized server. There's no need for online connectivity; you can pull and push issues when you're online.
  
Git-based: Issues are changed and shared through Git. This provides git issue with a robust, efficient, portable, and widely available infrastructure. It allows you to reuse your Git credentials and infrastructure, allows the efficient merging of work, and also provides a solid audit trail regarding any changes. You can even use Git and command-line tools directly to make sophisticated changes to your issue database.
+
    Transparent text file format: Issues are stored as simple text files, which you can view, edit, share, and backup with any tool you like. There's no risk of loosing access to your issues because a server has failed.
 +
 
 +
    Git-based: Issues are changed and shared through Git. This provides git issue with a robust, efficient, portable, and widely available infrastructure. It allows you to reuse your Git credentials and infrastructure, allows the efficient merging of work, and also provides a solid audit trail regarding any changes. You can even use Git and command-line tools directly to make sophisticated changes to your issue database.
  
 
Git-issue can currently import issues using the GitHub API.  The project's objective is to extend this functionality with a way to synchronize between GitHub/GitLab issues and the issues kept under git-issue.
 
Git-issue can currently import issues using the GitHub API.  The project's objective is to extend this functionality with a way to synchronize between GitHub/GitLab issues and the issues kept under git-issue.
Line 161: Line 206:
 
Git-issue extended for exporting its issues to GitHub/GitLab
 
Git-issue extended for exporting its issues to GitHub/GitLab
  
==== GSOC 2019 Project Repository ====
+
==== Related Repositories ====
https://github.com/eellak/gsoc2019-git-issue
+
https://github.com/dspinellis/git-issue
  
 
==== Knowledge Prerequisites ====
 
==== Knowledge Prerequisites ====
Line 183: Line 228:
 
A modern replacement of LTSP should be implemented, as outlined in http://wiki.ltsp.org/wiki/Dev:GSoC. It should be ready for inclusion in Debian/Ubuntu, for LTSP users to be able to slowly migrate to it.
 
A modern replacement of LTSP should be implemented, as outlined in http://wiki.ltsp.org/wiki/Dev:GSoC. It should be ready for inclusion in Debian/Ubuntu, for LTSP users to be able to slowly migrate to it.
  
==== GSOC 2019 Project Repository ====
+
==== Related  repositories ====
https://github.com/eellak/gsoc2019-ltsp
+
http://www.ltsp.org/
 +
http://wiki.ltsp.org/wiki/Dev:GSoC
  
 
==== Knowledge Prerequisites ====
 
==== Knowledge Prerequisites ====
  
 
Netbooting internals, shell, python, git, debian packaging
 
Netbooting internals, shell, python, git, debian packaging
 +
 +
 
==== Mentors ====
 
==== Mentors ====
  
Line 201: Line 249:
 
The Qt Calendar widget is updated, modified accordingly and ported into Qt 5.12 and Qt Quick Controls 2 current version. Ideally it will be upstreamed to Qt, contributing this way to the Qt ecosystem.
 
The Qt Calendar widget is updated, modified accordingly and ported into Qt 5.12 and Qt Quick Controls 2 current version. Ideally it will be upstreamed to Qt, contributing this way to the Qt ecosystem.
  
==== GSOC 2019 Project Repository ====
+
=== Related  repositories ===
https://github.com/eellak/gsoc2019-qtcontrols
+
https://github.com/extenly/qtqc2_calendar
  
 
=== Knowledge Prerequisites ===
 
=== Knowledge Prerequisites ===
Line 240: Line 288:
 
* Corpus management features using text metadata
 
* Corpus management features using text metadata
  
==== GSOC 2019 Project Repository ====
+
=== Related  repositories ===
https://github.com/eellak/gsoc2019-text-extraction
+
https://github.com/gmikros/Author_Multilevel_Ngram_Profiles
 +
 
 +
https://github.com/quanteda/quanteda
 +
 
 +
https://github.com/unDocUMeantIt/koRpus
 +
 
 +
https://miroslavkubat.webnode.cz/software/
 +
 
 +
https://github.com/bnosac/udpipe
 +
 
 +
https://github.com/explosion/spaCy
  
 
=== Knowledge Prerequisites ===
 
=== Knowledge Prerequisites ===
Line 258: Line 316:
 
A  [https://extensions.libreoffice.org/extensions LibreOffice Extension] and a Linux application with a web GUI that will  anonymize information in legal documents(odt and txt). Must have the ability to mass edit files, and to recognize through NLP and anonymize entities (such as Names, Addresses- ID numbers- VAT- social security numbers  or any other potentially sensitive information. The entities that will be anonymized through strong data encryption so that only people with access to a secret key or password can read the documents.
 
A  [https://extensions.libreoffice.org/extensions LibreOffice Extension] and a Linux application with a web GUI that will  anonymize information in legal documents(odt and txt). Must have the ability to mass edit files, and to recognize through NLP and anonymize entities (such as Names, Addresses- ID numbers- VAT- social security numbers  or any other potentially sensitive information. The entities that will be anonymized through strong data encryption so that only people with access to a secret key or password can read the documents.
  
==== GSOC 2019 Project Repository ====
+
=== Knowledge Prerequisites ===
 
Python, Spacy, Encryption algorithms
 
Python, Spacy, Encryption algorithms
  
 
=== Related repositories ===
 
=== Related repositories ===
https://github.com/eellak/gsoc2019-anonymization
+
https://pypi.org/project/bcrypt/
 +
 
 +
https://github.com/eellak/anonimos-amka/
 +
 
 +
https://github.com/eellak/gsoc2018-spacy
 +
 
 
=== Mentors ===
 
=== Mentors ===
 
[https://www.dit.hua.gr/~varlamis/ Iraklis Varlamis], [https://github.com/tgkarounos Theodoros Karounos]
 
[https://www.dit.hua.gr/~varlamis/ Iraklis Varlamis], [https://github.com/tgkarounos Theodoros Karounos]
 +
 +
== <span lang="en-US">OpenProject Work-Package #1 to support modeling of the PM<sup>2 </sup>methodology for project management</span> ==
 +
 +
==== <span lang="en-US">Brief Explanation:</span> ====
 +
<span lang="en-US">PM²
 +
is a Project Management Methodology developed by the European
 +
Commission. PM² is built on Project Management best practices and is
 +
supported by the following four (4) pillars: </span>
 +
 +
# <span lang="en-US">a project governance model(Roles & Responsibilities) </span>
 +
# <span lang="en-US">a project lifecycle (Project Phases) </span>
 +
# <span lang="en-US">a set of processes (Project Management activities) </span>
 +
# <span lang="en-US">a set of project artifacts (templates and guidelines). </span>
 +
 +
<span lang="en-US">For
 +
a full support of PM² Project Management Methodology by OpenProject,
 +
new modules should be developed on OpenProject that will allow
 +
modeling of the abovementioned four pillars of PM².</span>
 +
 +
==== <span lang="en-US">Expected Results:</span> ====
 +
<span lang="en-US">Support
 +
for the process of PM² itself in OpenProject: That is, development
 +
of  Open Project plug-ins which  should add support for defining and
 +
handling the roles, responsibilities, phases and activities (in terms
 +
of PM² governance, life-cycle and processes pillars) for every new
 +
project. </span>
 +
 +
<span lang="en-US">The
 +
work of this Work-Package includes:</span>
 +
* <span lang="en-US">the analysis of PM2 requirements </span>
 +
* <span lang="en-US">the setup of OpenProject development environment (Development VM)</span>
 +
* <span lang="en-US">the modeling of PM2 requirements in OpenProject environment via the development of one or more plug-ins. The plug-ins should follow the Open Project plug-in guidelines and be consistent with the OpenProject API (http://docs.openproject.org/apiv3-doc/). The plug-ins should add the required models, logic and DB tables in order to: </span>
 +
 +
** <span lang="en-US">Support the PM² Governance Model (Roles, Responsibilities) </span>
 +
** <span lang="en-US">Support the PM² Phases </span>
 +
** <span lang="en-US">Support the PM² Artifacts per Phase</span>
 +
** <span lang="en-US">Support all PM<sup>2 </sup>plans and logs such as Change Log, Communications, Issue, Project, Quality, Requirements, and Risk </span>
 +
* <span lang="en-US">The development of tests for all the requirements (e.g. initiate PM² project, initiate phases, add artifacts, generate reports).</span>
 +
 +
==== <span lang="en-US">'''Related GitHub repositories'''</span> ====
 +
<span lang="en-US">https://github.com/opf/openproject
 +
</span>
 +
 +
https://ec.europa.eu/isa2/solutions/open-pm2_en/
 +
 +
==== '''Knowledge Prerequisites''' ====
 +
* <span lang="en-US">R</span>uby
 +
 +
* <span lang="en-US">Ruby on Rails</span>
 +
 +
* <span lang="en-US">Postgres </span>
 +
 +
* <span lang="en-US">Problem Analysis & Modeling </span>
 +
 +
==== Mentors ====
 +
[http://users.ntua.gr/karounos/karounos.html Theodoros Karounos], [http://www.3-lab.eu/core-team/george-blanas/ George Blanas], [https://www.linkedin.com/in/nicoskourounakis/ Nicos Kourounakis]
 +
 +
== <span lang="en-US">OpenProject Work-Package #2 to support functionality of the PM<sup>2 </sup>methodology for project management</span> ==
 +
 +
==== <span lang="en-US">Brief Explanation:</span> ====
 +
<span lang="en-US">This
 +
work-package is based on and extends OpenProject Work-Package #1
 +
(Support modeling of the PM2 methodology for project management) by
 +
adding visual elements that will support for PM²project artifacts
 +
through templates, wizards, tools and guidelines.</span>
 +
 +
<span lang="en-US">'''Expected
 +
Results:'''</span>
 +
 +
<span lang="en-US">Integrate
 +
the outputs of Work-Package #1 in OpenProject UI. For this, developed
 +
plug-ins from Work_Package #1 will be extended and new plug-ins will
 +
be developed in order to provide a rich User interface for the user.
 +
The plug-ins should follow the Open Project plug-in guidelines and be
 +
consistent with the OpenProject API
 +
(http://docs.openproject.org/apiv3-doc/)
 +
.</span>
 +
 +
<span lang="en-US">The
 +
developed functionality should: </span>
 +
 +
* <span lang="en-US">Provide wizards allowing the PM² user to:</span>
 +
 +
** <span lang="en-US">create and initiate PM² based project Templates</span>
 +
** <span lang="en-US">Initiate Project phases </span>
 +
** <span lang="en-US">add PM² artifacts per phase</span>
 +
** <span lang="en-US">create reporting templates with visual content like Gantt and Pert charts </span>
 +
** <span lang="en-US">add PM² artifacts with textual content like Risk Logs.</span>
 +
* <span lang="en-US">Support all PM<sup>2 </sup>plans and logs such as Change Log, Communications, Issue, Project ,Quality , Requirements, Risk </span>
 +
* <span lang="en-US">Provide tools such as</span>
 +
 +
** <span lang="en-US">3-point estimation with triangular and/or beta distribution</span>
 +
** <span lang="en-US">Critical Path Method (CPM)</span>
 +
** <span lang="en-US">Monte-Carlo analysis/technique</span>
 +
** <span lang="en-US">Network Diagram (FS, SS, FF)</span>
 +
** <span lang="en-US">Work Breakdown Structure (WBS)</span>
 +
* <span lang="en-US">Support Agile Specific Artifacts and Tools, e.g. Iterations, Kanboards etc.</span>
 +
* <span lang="en-US">Support visual representation of PM² using standards like BPMN, STRATML, RDF etc</span>
 +
* <span lang="en-US">Allow connection with external systems (e.g. Open ID, Media-Wiki)</span>
 +
* <span lang="en-US">Allow for Export and import for/to other formats for data exchange (e.g. MS Project export/import, PDF, XLS etc.).</span>
 +
 +
==== <span lang="en-US">'''Related GitHub repositories'''</span> ====
 +
<span lang="en-US">https://github.com/opf/openproject
 +
</span>
 +
 +
<span lang="en-US">https://ec.europa.eu/isa2/solutions/open-pm2_en</span>
 +
 +
==== '''Knowledge Prerequisites''' ====
 +
*Ruby
 +
 +
* Ruby on Rails
 +
 +
* Angular
 +
 +
* <span lang="en-US">ES6</span>
 +
<nowiki>*</nowiki>
 +
 +
<span lang="en-US">statistical modeling methods for PM (Monte carlo , CPM etc)</span>
 +
 +
==== Mentors ====
 +
[http://users.ntua.gr/karounos/karounos.html Theodoros Karounos], [http://www.3-lab.eu/core-team/george-blanas/ George Blanas], [https://www.linkedin.com/in/nicoskourounakis/ Nicos Kourounakis]
  
  
Line 275: Line 459:
 
The expected outcome will be a standalone web page, via which automatic speech to text towards personalized mail dictation will be offered. The code will be opensource and provided by GitHub repositories. Our approach will offer A) improvements in the speech-to-text procedure by acoustic model adaptation to individual users and statistical text model adaptation based on already existent corpuses (the user’s mails) and B) a standalone tool for everyone to utilize.
 
The expected outcome will be a standalone web page, via which automatic speech to text towards personalized mail dictation will be offered. The code will be opensource and provided by GitHub repositories. Our approach will offer A) improvements in the speech-to-text procedure by acoustic model adaptation to individual users and statistical text model adaptation based on already existent corpuses (the user’s mails) and B) a standalone tool for everyone to utilize.
  
==== GSOC 2019 Project Repository ====
+
=== Related  repositories ===
https://github.com/eellak/gsoc2019-sphinx
+
https://github.com/cmusphinx
  
 
=== Knowledge Prerequisites ===
 
=== Knowledge Prerequisites ===
Line 299: Line 483:
  
 
in  (REST/JSON)
 
in  (REST/JSON)
 
==== GSOC 2019 Project Repository ====
 
https://github.com/eellak/gsoc2019-greekspell
 
  
 
==== Knowledge Prerequisites<br> ====
 
==== Knowledge Prerequisites<br> ====
Line 326: Line 507:
 
Ideally this would include in-line editing of identifiers.
 
Ideally this would include in-line editing of identifiers.
  
==== GSOC 2019 Project Repository ====
+
==== Related GitHub repository ====
https://github.com/eellak/gsoc2019-CScout
+
https://github.com/dspinellis/cscout
  
 
==== Knowledge Prerequisites ====
 
==== Knowledge Prerequisites ====
Line 336: Line 517:
  
 
==== Mentor:====
 
==== Mentor:====
[https://www.spinellis.gr Diomidis Spinellis] [http://www.csd.auth.gr/en/staff/faculty?view=user&ro=1&id=14 Stamelos Ioannis]  
+
[https://www.spinellis.gr Diomidis Spinellis] [http://www.csd.auth.gr/en/staff/faculty?view=user&ro=1&id=14 Stamelos Ioannis]  
  
  
Line 374: Line 555:
 
* Make contacts and calendar encrypted
 
* Make contacts and calendar encrypted
  
===== GSOC 2019 Project Repository =====
+
===== Related GitHub repositories =====
https://github.com/eellak/gsoc2019-NextCloudPi
+
https://github.com/nextcloud/nextcloudpi/
  
 
===== Knowledge Prerequisites =====
 
===== Knowledge Prerequisites =====

Please note that all contributions to Ελεύθερο Λογισμικό / Λογισμικό ανοιχτού κώδικα are considered to be released under the Creative Commons (see Ελεύθερο Λογισμικό / Λογισμικό ανοιχτού κώδικα:Πνευματικά Δικαιώματα for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)