Difference between revisions of "Google Summer of Code 2023 Ideas"

Revision as of 13:59, 23 January 2023

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 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