eclipse-jdt / eclipse-jdt/.github

Inactive committer cleanup 2026

Open
#34 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
1
Forks
5
PR merge metrics
No merged PRs in 30d

Description

The following JDT committers neither authored nor committed any change within the past two years to any of the JDT git repositories according to https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/actions/runs/32640175610/job/97195946790#logs

- `Jinbo Wang` -- @testforstephen
- `Sravan Kumar Lakkimsetti` -- @sravanlakkimsetti
- `Julian Honnen` -- @jhonnen
- `Fabrice Tiercelin` -- no Github handle!
- `Kenneth Styrberg` -- @styken
- `Kalyan Prasad Tatavarthi` -- @ktatavarthi
- `Vikas Chandra` -- @vik-chand
- `Sarika Sinha` -- @SarikaSinha
- `Thomas Mäder` -- @tsmaeder
- `Till Brychcy` -- @brychcy
- `Olivier Thomann` -- @othomann
- `Michael Rennie` -- @mrennie

Each person in the list is considered inactive in their role as committer.
In order to keep the list of committers healthy therefore each of you is a candidate to be retired as committer of this project.

Please state your will and plan to contribute to keep your committership here by 24th of September 2026.

The workflow only considers commits and might even has missed some. If any commit or any other form of involvement in this project was missed, please let me know to not terminate your committership.

Furthermore retired committers can be nominated again as committer much quicker than new candidates to regain their committer status.

Contributor guide

Open the contributing guide

Research direction

Start with the linked Eclipse Platform Releng workflow log and verify the activity information for each listed committer across the JDT repositories. Review any responses or evidence of missed involvement by the stated deadline; the cleanup is done when each committer's status is accurately resolved and the project can retire inactive committers where appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github
Domain
developer-experience
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.