Skip to main content
Jump to: navigation, search

Google Summer of Code 2019 Ideas

Revision as of 05:26, 28 February 2019 by (Talk | contribs) (Topic 2: Usability improvements for the Eclipse IDE)

Please see our main Google Summer of Code page for participation information.

Any issue listed as helpwanted is a potential GSoC project idea.

Here are some of the most recently identified helpwanted issues:

  • bug 543787 TreeMasterValidationInitiator deletes siblings of the notifier on remove
  • bug 543663 Ctrl+E popup should use dialog font
  • bug 543623 Correct indentation slow for very large files (> 10k lines)
  • bug 543402 Use Objects.equals(...) and Objects.hashCode(...)
  • bug 543360 "Finding differences" message should be on editor and not be a popup
  • bug 543293 Deprecate org.eclipse.jface.util.Util#hashCode in favor of Objects.hashCode
  • bug 543283 toCamelCase command
  • bug 543263 Update API Tools icons to png files instead of Gifs
  • bug 543217 Feature view - Allow to see all plug-ins included in a feature
  • bug 542987 Replace 'http' with 'https' for all Eclipse links in code base
  • bug 542790 Copy/Paste (CTRL+C/CTRL+V) on the tree does not match user expectation
  • bug 542762 Use less margins in MANIFEST.MF editor

A complete list is available here.

Other ideas

Project team member and potential mentors, add your content here. The format suggested below is just an idea. Play with the layout, but please don't mess with content provided by other projects. Please be sure to follow branding guidelines (e.g. "Eclipse Dash", not "Dash"). Putting things in alphabetical order seems like a fair thing to do. Links to content hosted elsewhere are fine, but bear in mind that this page will likely be the main point of contact for people who are not already inside your community.

Example Project idea

Description of the Example Project idea with links to more information, bugs, and other useful content.

Specific work that this could involve includes:

  • Bullet list of specific
  • objectives

Possible mentors: Somebody Mentor

Eclipse 4diac

Eclipse 4diac is an environment for programming distributed industrial process measurement and control systems according to the IEC 61499 standard.

Topic 1: Investigate how Eclipse 4diac can migrate to GEF 5

The modeling language defined in IEC 61499 is highly graphical language. Currently we are using GEF legacy for implementing our graphical editors. As GEF legacy is not maintained any more, we need a migration path to the new GEF 5. As part of this topic a first editor could be implemented. A good candidate could be the system configuration editor. Based on the results of this experiment we can better estimate and plan for a full migration to GEF5.

Skills required: Java

Possible mentor: Alois Zoitl

Topic 2: Improve Dynamic Code Loading

Eclipse 4diac allows to program a wide variety of devices (e.g., PLCs from different vendors, RaspberryPI, BeagleBone Black, Lego Mindstorms). In order to address this we have a feature that deploys user programs utilizing the Lua programming language and the Lua virtual machine. However this is feature is highly experimental. It would require further testing, stabilization and some features are missing. A starting point can be these open bugs:

  • bug 510941 support DurationLiteral in Lua
  • bug 510956 support DurationLiteral in Lua export
  • bug 529609 support re-implemented FBs of the IEC 61131-3 standard lib for lua export
  • bug 529610 create documentation for the use of dynamicTypeLoad
  • bug 529611 update of existing function block types (without any instance in use)

Skills required: C/C++, Lua, Java beneficial

Possible mentor: Alois Zoitl

Topic 3: Add OCL for Detecting Model Inconsistencies in 4diac Models

Eclipse provides a OCL (Object Constraint Language) infrastructure. This allows to specify generic constraints a model has to fulfill. This can be utilized in Eclipse 4diac to add checks for issues and inconsistencies in the models developed in 4diac.

Skills required: Java, eCore, OCL beneficial

Possible mentor: Alois Zoitl

If you have any questions, feel free to ask them on to the 4diac mailing list.

Eclipse APP4MC

Eclipse APP4MC is a platform for engineering embedded multi- and many-core software systems. The platform enables the creation and management of complex tool chains including simulation and validation. As an open platform, proven in the automotive sector by Bosch and their partners, it supports interoperability and extensibility and unifies data exchange in cross-organizational projects. APP4MC is one of the results of the ITEA3 Amalthea and Amalthea4Public research projects.

What is APP4MC?

Click here to get a quick overview of how APP4MC and Capra can help you manage timing, scheduling and traceability in a multi-core environment.

Topics and how to apply

If you are interested in one of the topics, please...

  • Download and extract APP4MC
  • Open the Tools-Examples (File -> New -> Example -> APP4MC Tools Examples -> Java Example)
  • Modify the file so it will output some information about the model, e.g. the number and name of tasks
  • Create a GitHub account (in case you don't yet have one) and upload your results
  • Contact us via the APP4MC mailing list. Don't forget to attach the Link to your GitHub repository.

If you have any questions, feel free to ask them on to the APP4MC mailing list.

Topic 1: Code-Generator for Raspberry Pi

Eclipse APP4MC integrates the Amalthea System Model that allows, among others, to describe the structure of software. In order to verify the timing behavior of software, your task is to generate code out of models that is compileable and executable on e.g. a Raspberry Pi.

(Skills required: Java, C/C++ beneficial)

Specific work that this could involve includes:

  • create a C or C++ file based on the content of an AMALTHEA model
  • generate C-functions out of tasks and runnables
  • annotate these with waiting methods that delay execution according to their execution time
  • implement inter-task communication

In case you have no access to a Raspberry Pi, we can provide you with SSH-Access to one located in our facilities.


Let us assume we have a model with one Task t1 and two Runnables r1 and r2. If Runnables r1 and r2 are executed as part of task t1, the generated C-Code could look similar to the following listing:

 #include <stdio.h>
 void r1() {
   printf("Executing r1\n");
 void r2() {
   printf("Executing r2\n");
 void t1() {
 int main() {
   return 0;

Possible mentor: Lukas Krawczyk

Topic 2: Real-Time application on the Adapteva Parallella

The Adapteva Parallella is a heterogeneous MPSoC with 18 cores. We want to execute real-time applications using e.g. FreeRTOS on this board and compare the results with APP4MC. Your task is to create such an application.

(Skills required: C/C++, FreeRTOS)

Specific work that this could involve includes:

  • Get an understanding on how FreeRTOS works
  • Create a simple application based on FreeRTOS on the Adapteva that utilizes all 16 Epiphany cores
  • Extend the application to use both ARM cores
  • Convert an industrial example to FreeRTOS on the Adapteva
  • Compare the examples

Possible mentor: Lukas Krawczyk

Topic 3: Progress visualization

The Amalthea platform tools in Eclipse APP4MC allow users to distribute data and tasks to the target hardware platforms, with the focus on optimization of timing and scheduling. Your task is to extend these tools with an visualization of the progress along with (preliminary) results.

(Skills required: Java)

Specific work that this could involve includes:

  • Extract metrics from APP4MC, e.g. the number of tasks, runnables, min/avg/max communications per task/label/runnable, the best quality of the partitioning/mapping tool, ...
  • Select a library that is suitable for visualizing these metrics e.g. Eclipse SWTChart
  • Create an own extension for the APP4MC tools that implements the visualization of the current progress resp. the quality metrics.

Possible mentor: Lukas Krawczyk

Topic 4: Task Visualizer

In order to simulate the execution of tasks on a specific hardware platform, APP4MC contains a Task Visualizer. Your task is to extend the Task Visualizer by communication dependencies.

(Skills required: Java, JavaFX)

Specific work that this could involve includes:

  • Extract communications from APP4MC models
  • Add communication dependencies to the Task Visualizers Gantt View
  • Add support for large models (e.g. with +10000 communications)

Possible mentor: Lukas Krawczyk

Eclipse CBI

Eclipse CBI (Common Build Infrastructure) is a set of tools and best practices for building projects at the Eclipse Foundation.

Topic 1: Improve Eclipse Digital signature services

The Eclipse Foundation provides Digital Signature services for various kind of artifacts (Java Jar, Windows executable (PE Authenticode), macOS .app and .dmg). Those services are implemented as web services ( with a REST endpoint to sign a file.

Topic 1.1 Add authentication

The web services are currently not authenticated, they rely on the network topology to implement access restriction. The goal is to add authentication to those webservices. An OAuth2 service will be used to provide the authentication service.

Topic 1.2: Add asynchronous endpoints

Currently, the endpoints are synchronous: one POSTs a file to be signed, the server signs the file and returns the result in the response body. This is a naive implementation and should be augmented with an asynchronous variant: one POSTs a file to be signed and gets a token from the server. The server signs the file in the background. User can then poll the server with the token to query whether the file is ready or not. Instead of polling, the initial POST could also open a WebSocket waiting to be notified by the server when the file is ready. The endpoint main client (maven plugins: will need to be updated to benefit from the new asynchronous endpoints.

Skills required: Java, REST, Maven

Possible mentor: Mikaël Barbero

Topic 2: Implement a Dashboard about apps running in a Kubernetes cluster

CBI is currently in the process of migrating all the Jenkins instances it manages ( to a Kubernetes (OpenShift) cluster. The goal of this topic is to implement a dashboard listing all Jenkins instances running in the Kubernetes cluster (similar to but with live data from the cluster (pod status, resource usage, Jenkins queue size etc...). The dashboard will run itself in the cluster. Server side implementation will preferably be in Java, Rust or Go while the dashboard client will preferably be implemented as a set of reusable React JS components.

Skills required: Kubernetes, (Java|Rust|Go), Javascript, React

Possible mentor: Mikaël Barbero

Eclipse SUMO: Simulation of Urban Mobility

SUMO is a free and open traffic simulation suite. SUMO allows modelling of intermodal traffic systems including road vehicles, public transport and pedestrians. Included with SUMO is a wealth of supporting tools which handle tasks such as route finding, visualization, network import and emission calculation. SUMO can be enhanced with custom models and provides various APIs to remotely control the simulation.

The goal of our GSoC project is to make SUMO more accessible for users of graphical user interfaces and facilitate alternative ways of setting up and interacting with the simulation. Specific work that this could involve includes:

  • Development of a "Replay" functionality for trajectories of vehicles
  • Development of SUMO-as-a-WebService functionalities / WebWizard / WebGL prototyping
  • Development of GUI-elements to visualize critical situations and locations in a traffic simulation
  • Development of interfaces and connections to external (live) data, e.g., General Transit Feed Specification (GTFS) for public transport
  • Development of GUI-elements to visualize public transport timetables and public transport networks
  • Initial concept and development for a model describing the dynamics of (container) ships
  • Development of 3D visualization components for SUMO (open scene graph, Web3D, HTC Vive)

Possible mentors: Michael Behrisch, Jakob Erdmann

Eclipse Hono

Eclipse Hono™ provides remote service interfaces for connecting large numbers of IoT devices to a back end and interacting with them in a uniform way regardless of the device communication protocol.

If you have any questions you may contact us on the mailing list.

Topic 1: Create a new protocol adapter

Eclipse Hono is all about abstracting protocols for IoT. We already have MQTT, plain HTTP, Coap, and last year's GSoC brought us AMQP 1.0. So it only makes sense to pick another protocol this year and do an implementation for Eclipse Hono.

This topic requires you to:

  • Pick a protocol you want to add (as part of your proposal)
  • Define mappings between the Hono telemetry, event, and command & control API and the chosen protocol
  • Implement the protocol adapter in Java, using your mapping definition, re-using the existing infrastructure, and maybe re-using an exiting protocol implementation
  • Provide unit and integration tests
  • Add the new protocol adapter to the existing deployment scripts
  • Amend the documentation to cover the new protocol adapter

The task here is not to write a new protocol implementation, but rather to use an existing protocol implementation and create a mapping to the Hono system (aka protocol adapter). For example, in last year's GSoC the task was to implement an AMQP protocol adapter, by re-using the existing Proton AMQP library.

Skills required: Java

Possible mentor: Jens Reimann

Eclipse SWTChart

SWTChart is a powerful library to create charts and display data using SWT. So, it can be easily used in Java desktop applications. Only a few lines of code are necessary to create interactive and feature rich charts:

public class MyChart extends MassSpectrumChart {
	public MyChart(Composite parent) {
		super(parent, SWT.NONE);
	private void initialize() {
		IChartSettings chartSettings = getChartSettings();
		List<IBarSeriesData> barSeriesDataList = new ArrayList<IBarSeriesData>();
		IBarSeriesData barSeriesData = new BarSeriesData(SeriesConverter.getSeriesXY(SeriesConverter.BAR_SERIES_1));

The source code is located here and can easily be cloned:

If you are interested in one of the topics you have to apply on the mailing list.

Topic 1: Extending the export options

Many export options are contained already, e.g. to export to bitmaps as well as to scripts. The R script option is really helpful, especially when preparing scientific charts for publication. As the data is stored in a generic way, many different export options can be implemented. The task of topic 1 would be to add/extend the options: *.svg, *.eps, *.pdf and to put a pre-configured LaTeX table into the clipboard.

Possible Mentor: Philip Wenig

Topic 2: Handling of large data sets

SWTChart already contains a function to compress the data and reduce the time to plot series. This is important especially when handling > 100,000 data points. Compressing large data sets could be improved, e.g. to lazily load just the data that is needed, depending on the resolution of the screen. Even when handling large data sets, details should be displayed when zooming in.

Possible Mentor: Philip Wenig

Topic 3: Create default charts

This topic contains to add default charts, which could be easily re-used, e.g. a PCA chart or others.

Possible Mentor: Philip Wenig

Eclipse Vert.x

Topic 1: Reactive relational database client

Eclipse Vert.x currently supports relational database using JDBC and a PostgreSQL Client. The PostgreSQL client can be extended to supports other relational databases, reusing the current client API and internal architecture.

A student willing to work on this project should have some basic knowledge in relational databases and be capable of reading and understanding database access protocols which are publicly available such as the PostgreSQL, MySQL or SQLServer protocols.

The student should also be able to use networking tools such as Wireshark or TCP dump which can be useful for developing such protocols in a client.

Finally the student must also have a good pro-efficiency with the Java language, event driven architectures and Java concurrency in general.

The goal is to implement the Service Provider Interface of a non-blocking database client for the MSSQL database which are openly and clearly documented:

  • develop the set of command to authenticate and close a connection to an SQL Server database
  • develop query execution (also known as simple queries) and retrieve results from the database
  • implement value mapping between SQL types and Java types
  • develop prepared queries creation and retrieve prepared query metadata for performing client slide validation and decoding
  • develop prepared queries execution and retrieve results from the database
  • develop unit tests

Possible mentors: Julien Viet

Topic 2: Full polyglot support of TypeScript (outside vert.x APIs)

Eclipse Vert.x is a polyglot reactive runtime that fully supports TypeScript in the form of ES4X. Support is currently provider in the form of:

  • proper type hinting
  • compile time validation
  • generated type definitions

However if libraries are used that were not specifically written for use with vert.x no help is available. This project would be to enhance/extend the current tooling to extract basic class metadata to generate a bare type definition file(s) for non vert.x API jars.

A student willing to work on this project should have some basic knowledge in TypeScript and be capable of using tools available with any JDK such as:

  • jar
  • javap

The goal is to implement a tool, that given a random jar file, will generate a set of TypeScript definition files for each public class/interface. The format is already well defined in the vert.x project, which makes the task of the student a bit simpler:

1. identify a way to read a random jar 2. list all public APIs in the given jar 3. map the public APIs to a JavaScript import file 4. map the generated import file to a TypeScript .d.ts file 5. package the generated code into a npm package 6. automate all the steps into a simple CLI tool

Possible mentors: Paulo Lopes

Eclipse Che

Topic 1: Co Editing

Explore and implement a first skeleton to enable CoEditing in Che and Theia. There are several options

Then explore how live-synchronisation could solve issues like when several Language servers and Editors share the same buffer.

Possible mentors: Sun Tan

Eclipse SW360

Eclipse SW360 supports software development by managing a component inventory for products and projects. The component inventory will be fed by build tool chains using a REST API and the inventory can help for a number of tasks: license compliance, vulnerability management, export control for "interesting" technologies, statistics about component usage, and so forth. Imagine a person in an organisation asking "I would like to know which products have commons-collections-3.2.1.jar?" (referring to the vulnerability that was reported once in 2017) - using SW360 as central component inventory can answer this question.

We from the Eclipse SW360 team would like to offer GOSC topics, if you are interested in the topic or technology. The SW360 technology stack is:

  • Java, Tomcat, Maven
  • Liferay as Web UI front end and Spring as REST front end
  • Couchdb for storing open source component source code (for scanning) and metadata, using Ektorp as Java POJO translator.

More information about SW360

Please do not hesitate to ask questions to:

Topic 1: Make Eclipse SW360 Fit for OSS Foundations

SW360 can be used for organizations in general: However, currently, the main input for use cases was coming from commercial organizations, companies. However, since SW360 is entirely open source software, how would use looks like for OSS foundations? Main use cases of foundations are about license compliance as well - for example ensuring license compatibility of involved OSS in the software project hosted by a foundation. The GSOC project proposes to implement an integration of Eclipse SW360 into the operations of the Eclipse Foundation. As such, as for the preparations, the relevant use cases and interaction with existing build hardware needs to be determined. Then, the project shall focus on three main use cases:

  • Component inventory feed by ci/cd chains using the SW360 REST API: an eclipse project uploads all dependencies
  • Automated license check for uploaded components which are dependencies of the projects
  • Support project view of all dependencies, if they are approved.

Possible mentors: t.b.d., candidate: Michael C. Jaeger

Topic 2: Create a cool statistics dashboard

Currently, there is some overview as of tables, and users can export spreadsheets for drawing pie charts, but the latter requires export. SW360 users would greatly take advantage from charting that allows to select from predefined values:

  • Metric (for example, no. of components, no. of projects, avg. components per project, etc.)
  • Group (selecting data for a group or for all groups on the server)
  • Time frame (1 day, 1 week, 1 month, 1 year, 10 years) where time frame could present the interval by using the step below (one day shows data at the interval of hours, one week shows the interval of days)

That is for the basics, another area of charting is interesting for license compliance metrics, where the charting mode can vary (not necessarily using bar charts, but pie charts):

  • which licenses do appear
  • what is their distribution
  • list components by license

This part could be displayed as separate portlet.

For users, a statistics dashboard allows for displaying charts based on selectable metrics. The metrics could be predefined queries in terms of metric and time frame and interval.

Possible mentors: t.b.d.

Eclipse IDE

Topic 1: Eclipse Dart Support

Help developing and testing Dart support for the Eclipse IDE.


Possible mentors: Lars Vogel

Topic 2: Usability improvements for the Eclipse IDE

Help improving the usability of the Eclipse IDE. This can for example include contributing and testing the platform notification API, simplifying Git operations, moving blocking dialogs to non-blocking, migrating code minings from Github implemtations to standard.


Possible mentors: Lars Vogel

Back to the top