Dear EASE Development Team,
I hope you are doing well.
We are exploring the possibility of creating and maintaining a variant of the Eclipse EASE repository that focuses on
CLI product development.
Our main motivation is to keep the codebase cleaner for CLI use cases, since we notice that
UI dependencies are currently included, even when building purely CLI-based products.
For this, we would like your guidance on:
- Subproject/Group Creation
- Is it possible for us to create a
group or subproject under Eclipse EASE to host this work, rather than relying only on a fork?
- What is the correct process to initiate such a request?
- Eclipse CI Integration
- Would it be possible for Eclipse CI builds (Jenkins/GitLab integration) to run for this subproject as well?
- If not, are there recommended alternatives to ensure continuous builds and artifact generation?
- Costs and Available Options
- Does setting up such a subproject and builds under Eclipse incur any cost for contributors/maintainers?
- Are there existing shared runners or build resources provided by the Eclipse Foundation that we could leverage?
Currently, we can only fork the repository but not create a group. We would appreciate your advice on the right process to proceed.
For context, I also serve on the
Eclipse IDE Steering Committee, and this request is aligned with our interest in enabling cleaner CLI usage of EASE while staying within Eclipse Foundation practices.
Thank you very much for your support and guidance.
Best regards,
Patil Latha
Bosch Global Software Technologies Private Limited
(CIN: U72400KA1997PTC023164) | 360 Degree Business Park - Tower 2 | Neeladri Road | Electronics City Phase 1 | Bengaluru (Electronic City) |
INDIA | www.bosch-softwaretechnologies.com
Patil.Latha@xxxxxxxxxxxx
