Improve "Eclipse IDE for committers" package onboarding journey
-
Goal of this issue is to summarize and initialize first actions in order to improve Eclipse (new) contributors / committers user journey when they download the "Eclipse IDE for Committers" from: https://www.eclipse.org/downloads/packages/release/2024-03/r/eclipse-ide-eclipse-committers
-
First ideas coming from a working session with Olivier Prouvost (April 2024):
-
When installing the Eclipse package for committers, it would be good to ask which project(s) one wishes to contribute to.
-
Then ask if one is already a committer on this project (if not, it doesn't prevent one from making a PR, but it's an opportunity to explain to a new, inexperienced arrival what being a committer at Eclipse involves).
-
Next, one should be able to provide their GitHub (for example) and automatically fork.
-
Then, one should be able to specify which version of the project they wish to contribute to, and ideally, it should be easier to facilitate local testing of a contribution too
- Olivier mentions that today, he doesn’t even know how to launch tests on a project he is a committer on; he has to wait for the nightly builds without knowing how to launch them locally
- A target could be to have launch config targets named "Eclipse launcher" and "Eclipse TEST launcher" on ALL projects
-
Another element (probably a quick win) in a "committer" version would probably be wise to redirect and display the "contributing" file of the opened project,
-
or even allow starting a quiz that would ask a few questions to see if he has understood the rules of contribution.
-
-
DOD
- work with Community Member consultant and Community members on "new committer user journey" eclipse-wg/ide-wg/ide-wg-dev-funded-efforts/ide-wg-dev-funded-program-planning-council-top-issues#19
- Put in place a roadmap of Contributor onboarding improvements on Eclipse IDE for committers" package