Google Summer of Code 2023 Ideas

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

This year, projects should take ~175 hours or ~350 hours for GSoC contributors to complete.

Each project on the Ideas list should include:

• a project title/description
• more detailed description of the project (2-5 sentences)
• expected outcomes
• skills required/preferred
• possible mentors
• expected size of project (175 or 350 hour).
• And if possible, an easy, medium or hard rating of each project.

Project 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. This could include a list of specific objectives

Expected outcomes list of the results expected to be achieved after completing of the project.

Skills required/preferred list of skill set required to be able to complete the project in the proposed time.

Project size 175/350 hours

Possible mentors: Somebody Mentor

Rating Easy, medium or hard rating of each project.

Eclipse Hara (DDI Client for Eclipse hawbkBit™)

Topic 1: Improve Automatic Testing

Description: Hara-ddiclient (https://github.com/eclipse/hara-ddiclient/) is a Kotlin library that facilitates and speeds up the development of DDI API clients for devices connecting to hawkBit servers. This project aims to modernize and extend the existing test suite to improve the release process. Currently, the test cases implemented are limited and the test env uses a hawkbit-server launched via docker, which must be replaced with a mock.

Expected outcomes: a mock implementation of the hawkbit-server easily configurable at run time, and new test cases which cover the prominent use cases of the hara-ddiclient.

Skills required/preferred: Programming skills required, preferably one or more of the following technologies: Kotlin/Java, TestNG/JUnit

Project size: 175 or 350 hours (scope can be adjusted, e.g., by including test cases)

Possible mentors: Daniele Sergio

Rating: Medium

Topic 2: Native implementation in Rust

Description: Hara-ddiclient is a Kotlin library that facilitates and speeds up the development of DDI API clients for devices connecting to hawkBit servers. This project will implement a native ddi-client in Rust following the Hara-ddiclient architecture. This project's benefit is providing a DDI client implementation applicable in those crucial contexts where a native approach is required. The native implementation of the DDI client can then be used by different frameworks (i.e Qt) and tools to include their integration with the hawkBit update server.

Expected outcomes: a first version of the hara-ddiclient written in rust which covers one of the primary use cases of ddi-client which is to download and apply an update.

Skills required: Students should understand Kotlin, Rust, and possibly Actor model (https://en.wikipedia.org/wiki/Actor_model).

Project size: 350 hours

Possible mentors: Daniele Sergio Diego Rondini

Rating: Hard

Eclipse 4diac™ (Domain-specific modelling environment)

Topic 1: Testing software developed in a graphical DSL

Description The Eclipse 4diac project provides an open source infrastructure for distributed Industrial Process Measurement and Control Systems (IPMCS) based on the IEC 61499 standard. This project will add infrastructure for domain experts to test software components (so-called Function Blocks) based on behavior models. Currently, the tool environment has limited tool support for (semi-)automated testing of Function Blocks. A framework for the test execution and a basic user interface are available, partly developed by earlier GSoC projects.

Expected outcomes: A user interface for generating tests for FB Networks and executing them must be available (including documentation). It should be furthermore possible to record such scenarios, which can be later used as test cases.

Skills required/preferred: Programming skills required, preferably one or more of the following technologies: Java, SWT, Eclipse, RCP

Project size: 175 or 350 hours (scope can be adjusted, e.g., by including a graphical user interface)

Possible mentors: Bianca Wiesmayr

Rating: Medium

Topic 2: Refactoring graphical software automatically

Description The Eclipse 4diac project provides an open source infrastructure for distributed Industrial Process Measurement and Control Systems (IPMCS) based on the IEC 61499 standard. This project will add automatic refactoring operations to improve the software developed in the graphical modeling language.

Expected outcomes: A concept for fixing problems in the software has to be developed and implemented. The results should be presented to the user.

Skills required/preferred: Programming skills required, preferably one or more of the following technologies: Java, Eclipse, RCP

Project size: 175 or 350 hours (scope can be adjusted, e.g., by including a graphical user interface)

Possible mentors: Bianca Wiesmayr

Rating: Medium

Eclipse Vert.x client for Apache Pinot

Description Vert.x is a toolkit to build reactive applications on the Java virtual machine. It provides asynchronous and non-blocking clients for different types of databases. Apache Pinot is a realtime distributed datastore for analytics workloads. The project consists in creating a Vert.x client for Pinot, based on the Apache Pinot Java Client.

Expected outcomes At the end of the project, we should be able to execute Pinot queries using Vert.x supported APIs (Future, RxJava, or SmallRye Mutiny). The client transport shall be implemented with the Vert.x Web Client. It is expected that the student creates a sample application and a blog post to present it.

Skills required/preferred Students should have a good understanding of the Java programming language and be able to learn and experiment with the Apache Pinot Java Client.

Project size 175/350 hours (scope can be adjusted to reflect the desired length)

Possible mentors: Thomas Segismont

Rating Medium/Hard

Eclipse JKube™

Topic 1: Improve JKube user experience

Description Eclipse JKube™ is a collection of plugins and libraries that are used for building container images using Docker, JIB or S2I build strategies. Eclipse JKube generates and deploys Kubernetes/OpenShift manifests at compile time too.

This project focuses on providing compile-time plugins and libraries for the Java ecosystem for:

• Building container images
• Creating Kubernetes and OpenShift resource descriptors
• Deploying resources descriptors

The goal of this proposal is to improve the user experience of JKube for a better adoption. Basically to work on the issues with the label ‘UX’ https://github.com/eclipse/jkube/labels/UX . Students could also propose issues that would help JKube to be well/better adopted.

Expected outcomes are of course contributions in terms of code. But it could also involve the website or the documentation or videos.

Skills required/preferred.

• Basic knowledge of Kubernetes
• Good knowledge of Java

Project size 350

Possible mentors: Sun Tan (CET/CEST)

Rating medium

Eclipse Epsilon Kernel for Jupyter Notebooks

Description Eclipse Epsilon is a family of Java-based scripting languages for automating common model-based software engineering tasks, such as code generation, model-to-model transformation and model validation. This project would consist in the implementation of a kernel to allow executing these languages in a Jupyter Notebook. Eclipse Epsilon already provides several features that might help during this project: (1) Epsilon programs can be executed from Java code or vía Ant, Maven or Gradle; (2) textual syntaxes for models and metamodels (Flexmi and Eclipse Emfatic respectively) that fit well in the cell-based workflow of Jupyter Notebooks; (3) a browser-based playground for fiddling with Epsilon’s languages; and (4) examples of how to work with Epsilon in different development environments.

Expected outcomes A baseline could be implementing a Jupyter kernel that allows executing EOL (Epsilon Object Language) snippets contained in notebook cells. The kernel should be able to maintain the state of the environment, which will be updated with each notebook cell execution. From there, other model-based tasks could be added incrementally, such as editing models and metamodels, supporting other Eclipse Epsilon languages, and visualising models, among others.

Skills required/preferred Object-Oriented Programming skills required, preferably Java. Knowledge in how to use Jupyter Notebooks is preferred but not required.

Project size 175/350 hours (scope can be adjusted e.g. by determining which of the Epsilon languages/tools is supported)

Possible mentors: Alfonso de la Vega, Dimitris Kolovos

Rating Medium/Hard

Eclipse Adoptium

Topic 1: Optimize Eclipse Adoptium Pipelines (Techniques for Reducing Test Node Usage)

Description adoptium.net Eclipse Adoptium has a large inventory of infrastructure to support builds and tests. We gather metrics on machine utilization and store that in an application written as part of the Eclipse AQAvit project (TRSS/Test Results Summary Service, a live instance found here: https://trss.adoptium.net/, source code within: https://github.com/adoptium/aqa-test-tools). We want to extend the information that we gather and put in the TRSS database (to include queue times and machine idleness), and assess various approaches to optimize our use of the limited nodes we have, including the use of dynamic agents, trialing different parallelism strategies, and different scheduling tactics to minimize idle times). This project will have aspects of data gathering, analysis and hands-on pipeline changes to trial and measure new variations of node usage.

Expected outcomes We expect that this project will provide us with metrics to be able to refine our build and test pipelines to more optimally use our limited machine resources. An assessment of current CI/CD best practices and comparative analysis with several variations should be one of the concrete outcomes of this work. Outcomes from this project will also be valuable for sharing with other projects. Another outcome will be a dynamic map of our infrastructure network, or other visualizations of the data (represented in the TRSS application). Ideally the findings will allow us to reduce our infrastructure costs and maintenance requirements.

Skills required/preferred Successful candidates should have a good understanding of the Java, JavaScript and shell script programming and be prepared to gather and analyze large amounts of data and present regularly on findings. Skills in data visualization are also helpful.

Project size 175/350 hours (scope can be adjusted to reflect the desired length) 350 hours

Possible mentors: Shelley Lambert Scott Fryer

Rating Medium

Topic 2: Eclipse AQAvit Assessment and Prioritization

Description The Eclipse AQAvit project curates and runs an extremely large set of tests. The AQAvit manifesto includes a clause to introduce and use metrics to ensure the test material is assessed regularly for its effectiveness. This project is geared to developing a repeatable approach to measure the effectiveness of our large set of tests to be used regularly to assess and adjust our testing to be most useful and relevant. Details at this aqa-tests wiki page.

Expected outcomes We hope that this project will have the following outcomes: - A survey of the best in class open source tools/approaches that measure test effectiveness - A set of KPIs used to assess the test material on a regular cadence - Tools that assist in the running of this assessment - If time permits, automated report generation.

Skills required/preferred Successful candidates should have a good understanding of the Java, JavaScript and shell script programming.

Project size 175/350 hours (scope can be adjusted to reflect the desired length) 350 hours

Possible mentors: Lan Xia Renfei Wang Shelley Lambert

Rating Medium

Eclipse Cargo Tracker: Improvements and Updates

Description The Eclipse Cargo Tracker project demonstrates how you can develop applications with Jakarta EE using widely adopted architectural best practices like Domain-Driven Design (DDD). It is a realistic, non-trivial Jakarta EE sample application. The project is a key part of the EE4J/Jakarta EE umbrella at the Eclipse Foundation. The project is mature but needs a number of important enhancements ranging from improving look/feel, upgrading to Jakarta EE 10/Payara 6/Java SE 11, adding more JUnit tests, adding JMeter tests, adding support for more IDEs such as VS Code/IntelliJ and supporting more runtimes such as GlassFish/Open Liberty/WildFly. Here is a complete list of issues where contribution is needed: https://github.com/eclipse-ee4j/cargotracker/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22. The Eclipse Cargo Tracker website is here: https://eclipse-ee4j.github.io/cargotracker/.

Expected outcomes The contributor(s) will successfully merge the enhancement(s) they elect to work on into the main branch of the project and close the corresponding issues. Their work will be included in a subsequent Eclipse Cargo Tracker release. They will be recognized as a project contributor and possibly a qualified committer.

Skills required/preferred Java, Jakarta EE, JUnit, JMeter, HTML, CSS, JavaScript

Project size 175/350 hours

Possible mentors: Reza Rahman (Reza.Rahman@microsoft.com)

Rating There are easy, medium and hard tasks in the project.