Re: [ease-dev] Request for Subproject/Group Creation for CLI-focused EAS

[Christian Pontesegger <christian.pontesegger@xxxxxx>]

Hi Latha,

great that you are interested in supporting EASE! Let me try to answer
your questions below as best as I can:

> Our main motivation is to keep the codebase cleaner for CLI use
> cases, since we notice thatUI dependencies are currently included,
> even when building purely CLI-based products.

EASE plugins (at least the core ones) are separated into UI/non-UI
plugins. I guess what you should do first for your usecase is to find
out, which plugins of EASE you are interested to use.

Then we can scan these plguins for unwanted UI dependencies.

If there are any, we should consider splitting up plugins into a cli
part and an UI part - or probably to move around some classes between
plugins. Lets see if this is a practical way to fulfill your request.

>    1. Subproject/Group Creation
>          a. Is it possible for us to create agroup or subproject
> under Eclipse EASE to host this work, rather than relying only on a
> fork?

No, you cannot create subgroups.

>  
>    1. Eclipse CI Integration
>          a. Would it be possible for Eclipse CI builds
> (Jenkins/GitLab integration) to run for this subproject as well?

We are using Jenkins builds where eclipse is providing the resources
for. Additional Jobs - if needed - can be put there. Although you would
need my help on this.

>          b. If not, are there recommended alternatives to ensure
> continuous builds and artifact generation?
>  
>    1. Costs and Available Options

No costs involved from Eclipse when you are happy with the default
resources that any project gets. More power for builds would include
some costs, but if you are on the Steering Committee, you should get
better information on this topic from there.

> Currently, we can only fork the repository but not create a group. We
> would appreciate your advice on the right process to proceed.

If we can avoid a fork, that would benefit all users I guess and also
provide a cleaner way for further development.

As for myself, my focus shifted in the past year and I can only put
some maintenace effort into this project anymore. From a functional
point of view, it is also pretty mature and feature-complete (I hope)

cheers
Christian