Eclipse OpenSmartCLIDE

The EMO is using this issue to track the progress of project creation. Help regarding the process can be found in the Eclipse Foundation Project Handbook.

The following image shows the workflow for Starting a Project at the Eclipse Foundation.

We are using scoped labels to identify where a project proposal is at any time during the onboarding process. These labels are mapped to the stages shown in the previous image. If you have doubts, just ask.

We'll use the due date of this issue to provide an estimation of the next date the EMO team will checkin with the project team. Sometimes, e.g. during the project creation time, the due date will coincide with the Project Creation date.

Project

• Project proposal: Eclipse OpenSmartCLIDE
• Creation review: https://projects.eclipse.org/reviews/eclipse-opensmartclide-creation-review
• Project: Eclipse OpenSmartCLIDE

Basic Information

• License: Eclipse Public License 2.0

Pre-creation Checklist

To be completed by the EMO

• Project scope is well-defined
• Top-level Project selected
• PMC accepts the project (PMC has replied with +1)
• License(s) approved
• Project name trademark approved. Trademark transfer agreement available here in case you need it.
• Project lead(s) identified
• Committers identified
• Committers have Eclipse Foundation Accounts
• Eclipse Architecture Council mentor identified
• Two weeks of community review completed

Project resources to be created

Project Lead involvement needed Open source projects at the Eclipse Foundation are required to make use of certain Eclipse Foundation services. See the Handbook for more information on this subject.

• The project lead has confirmed the project shortname: OpenSmartCLIDE

• The project lead has requested a project website repository in the comments

• The project lead has confirmed the following project resources are correct in the comment's section

• Dedicated GitHub organization

• Project mailing list: https://accounts.eclipse.org/mailing-list/OpenSmartCLIDE-dev

Post-creation Checklist

To be completed by the EMO

• Project created
• Project provisioned (including at least one committer)
• Project lead(s) designated (DB)
• Architecture Council mentor designated (DB)
• Domain Name agreement to be completed (to transfer the Domain)
• Committer orientation completed (upon request)

After creation

Once the project is created the provisioning process starts with an email message being sent to each of the committers listed on the project proposal with instructions on how to engage in the committer paperwork process.

Committers should check their emails and complete the paperwork at their earliest convenience. No project resources are created until at least one committer is fully provisioned.

After provisioning

Before pushing any code into an official Eclipse project repository, the project team must submit the project’s initial contribution of project code and wait for the Eclipse Intellectual Property (IP) Team to grant checkin of that contribution.

Project teams interact with the Eclipse IP Team via the IPZilla system using Contribution Questionnaires (CQs). More information is available in the Eclipse Handbook.

Approximately three months after successful completion of this creation review, the EMO will initiate a progress review.

Post-provisioning Checklist

To be completed by the EMO

These are the last few things needed to close this issue:

• Initial Contribution submitted for review by the IP Team
• IP team checkin granted

changed due date to October 05, 2022

added EDPCommunityReview License Approval Request Mentor Project Proposal Review Request Trademark Approval Request labels

assigned to @mdelgado624 and @wbeaton

removed License Approval Request label

@shmacdonald please initiate trademark search for the Eclipse Sky project.

cc/@pkriefrvi

marked the checklist item Committers have Eclipse Foundation Accounts as completed

changed the description

To be added as participant and to receive notifications

Hello all! I would also like to be added as participant and to receive notifications!

marked the checklist item PMC accepts the project (PMC has replied with +1) as completed

The name Sky is already widely used in various Trademarks. Please choose 3 new names and submit then in your order of preference and I will do a new search.

Thanks, Sharon

Hi @shmacdonald Here are the other names that the consortium had in mind in order of preference. HTH

Names	Score	Comment
Eclipse OpenSmartCLIDE	6
Eclipse SmartIDE	5	Used already https://smartide.cn/en/
Eclipse Nefos	5	Potential conflict with https://nefoscorp.com/ and https://www.nefosolutions.com/ ?
Eclipse KUMODAN	5
Eclipse KUMO	5	Might be an issue with https://www.kumo.com/
Eclipse Daramulum	5

The name Eclipse OpenSmartCLIDE is approved.

Thanks, Sharon

Great news !!! Thx a lot Sharon

@shmacdonald the project is currently using the name SmartCLIDE (repositories and European consortium). Is there anything name-wise the project team should do to comply with the new Eclipse OpenSmartCLIDE trademark?

Is the existing SmartClide project coming to the Eclipse Foundation? Or is OpenSmartCLIDE entirely new?

The existing SmartCLIDE project from Eclipse Research (here) will go to Eclipse Foundation

We will require a Trademark and Domain Name Transfer Agreement to be completed if an existing project name is coming over to us.

Sharon, I think there is a misunderstanding. The name of the Eclipse project will be "Eclipse OpenSmartCLIDE" which is not identically to SmartCLIDE, which is the H2020 project name.

So coming back to your earlier question, OpenSmartCLIDE will be entirely new. However, what we will use as initial contribution is already available in the SmartCLIDE repositories that are available under Eclipse Research (see above).

So I hope I could clarify it.

If it is entirely new then we do not need am agreement and we are good to proceed.

@shmacdonald the name is new, but very similar to the European Project name. Also, there is a domain smartclide.eu which is associated with the project that is owned by the project team. I'm assuming the project team would like to keep it. What are your recommendations in this case?

/cc @sscholze366 @pkriefrvi

What do you mean by "keep it"? If it, we can transfer the ownership to EF

@pkriefrvi I meant keep using it, and yes, transfer it to the EF. Apologies for the confusion.

Thx @mdelgado624 @sscholze366 do you own the domain name do we (Eclipse) own it? I can't recall this point. Thx

We generally will ask for the Domain Name agreement to be completed and then we will proceed to transfer the Domain to us.

@pkriefrvi I own the domain in the name of ATB and I do not see any problems in transfering the ownership of the domain. However, I will check tomorrow with my general manager.

@pkriefrvi I clarified it, ATB can and will transfer the domain to Eclipse if necessary

Great news!

Dear @mdelgado624 what is the next step to creating the project? Should we update the proposal and replace Eclipse Sky by Eclipse OpenSmartCLIDE? Thx

@pkriefrvi thanks for the ping! I've replaced all references to Sky and changed them for OpenSmartCLIDE and I've updated also this issue title. We only need a mentor and we should be ready for creation. I'll keep you posted as soon as we find one!

/cc @asalamanis

removed Trademark Approval Request label

marked the checklist item Project name trademark approved. Trademark transfer agreement available here in case you need it. as completed

changed title from Eclipse Sky to Eclipse OpenSmartCLIDE

changed the description

changed the description

@asalamanis @pkriefrvi please confirm the project shortname and the project resources that need to be created, specifying in you prefer a repository or a dedicated GitHub organization (i.e. eclipse-OpenSmartCLIDE)

• The project lead has confirmed the project shortname: OpenSmartCLIDE
• The project lead has requested a project website repository in the comments
• The project lead has confirmed the following project resources are correct in the comment's section
• Project repository: https://github.com/eclipse/OpenSmartCLIDE
• Project mailing list: https://accounts.eclipse.org/mailing-list/OpenSmartCLIDE-dev

Please see the handbook for more information.

I can confirm the project shortname and the project resources to be created. I have to check with @asalamanis and @pkriefrvi whether we would prefer an organization or a repository.

I agree with @sscholze366. We need to discuss internally about the best option.

Folks, in my opinion, knowing the number of repositories we have (37), a dedicated GitHub organization might make more sense, allowing us to group them together.

For the short name, @mdelgado624 originally suggested using "osc" for opensmartclide. In my opinion, it will be difficult to implement and others might confuse it with https://en.wikipedia.org/wiki/Open_Sound_Control. I was wondering if we could directly use "smartclide" instead to reduce refactoring as much as possible but I need to check with @wbeaton if this is feasible. If not, we can also keep the full name if it doesn't bother the team more than that.

Finally, Maria Teresa pointed me to https://www.eclipse.org/projects/handbook/#checklist which explains some naming rules we should apply in our repository. I will check to see if there are other rules for .py or .js code. Wayne, do you have any suggestions for non-java code?

@pkriefrvi I agree with the Github organization

Yes, I agree with @pkriefrvi that a GitHub org might be a better approach. We will also try to reduce the number of repos before the IP review.

marked the checklist item Two weeks of community review completed as completed

marked the checklist item Project lead(s) designated (DB) as completed

removed Mentor label

@ejiang has volunteered to mentor the project!

This creation review has concluded successfully! The project has been created and you'll soon receive the committer paperwork (all initial committers listed in the proposal). Please complete the paperwork at your earliest convenience. No project resources will be created until at least one committer has been fully provisioned.

@webmaster please initiate the provisioning process. Notice that the project has requested a dedicated GitHub organization.

I'll check in again with the project team in a week from now to review the status of the paperwork and the provisioning process.

@pkriefrvi @asalamanis please provide a list of the repositories that need to be created.

@mdelgado624 Do you need a full list of repositories, that we would like to create or will we be allowed to create our "own" repositories inside the github organisation?

@sscholze366 the requested GitHub organization will be maintained by the Eclipse Foundation. Any committer can open a Help Desk issue to request that the Eclipse IT Team create a new repository for their project on, or move an existing repository to, GitHub. Please see the Handbook for more details: https://www.eclipse.org/projects/handbook/#resources-github

Since we are in the bootstrapping phase of the project you can already request a list of the repositories you'll need. You can add others at any time during your project lifecycle by following the above mentioned process.

ok, thanks for clarification. I will provide you this list.

In principle it would be all repositories that we use in the Eclipse Research organisation: Smartclide at Eclipse Research

The paperwork for myself is completed.

added EDPProvisioning label and removed EDPCommunityReview label

assigned to @webmaster

added Successful label

marked the checklist item Eclipse Architecture Council mentor identified as completed

marked the checklist item Project created as completed

marked the checklist item Architecture Council mentor designated (DB) as completed

changed the description

changed the description

@asalamanis @pkriefrvi @sscholze366 please complete the domain transfer agreement at your earliest convenience.

/cc @shmacdonald

Please find attached the signed agreement for the domain transfer.Agreement_06102022.pdf

The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project:

Source Code Management:             Your projects existing repositories have been transferred into a new organization for your project: eclipse-opensmartclide . Committers that have added their Github IDs to their Eclipse.org accounts will receive access the next time our sync tooling runs.

Issue Tracker: 

Github issues will remain enabled for your project.

Outbound Communication:

Mailing list: https://accounts.eclipse.org/mailing-list/opensmartclide-dev

Downloads: http://download.eclipse.org/opensmartclide

Archives: http://archive.eclipse.org/opensmartclide

Builds: You can upload releases to opensmartclide via SFTP or SCP from a CI instance at Eclipse.org

Older builds should be moved to the archives area when they are no longer required.You can do this by visiting http://download.eclipse.org/opensmartclide in your favorite web browser and using the web ui.

@mward thank you very much. There are 5 more repositories that would need to be transferred:

• https://github.com/eclipse-researchlabs/smartclide-ide-front-end-theme
• https://github.com/eclipse-researchlabs/smartclide-design-pattern-selection-theia
• https://github.com/eclipse-researchlabs/smartclide-cicd
• https://github.com/eclipse-researchlabs/kie-wb-distributions
• https://github.com/eclipse-researchlabs/kie-wb-common

@mward I have another question regarding the container images:

• Currently the container images we built are still in the container registry of the eclipse-researchlabs organization. Is that OK or shall they be move to the eclipse-opensmartclide organisation
• Currently we cannot push new images to the eclipse-researchlabs container registry due to missing write access from eclipse-opensmartclide organisation. How shall we continue with this issue?

I've transferred the listed repos.

I would expect the container images to move to the eclipse-opensmartclide, however I don't see any obvious path to do that aside from updating your CI process to publish to the 'new' Github organization.

Thanks for transferring.

Yes, we updated / we are updating our CI process. However, I was wondering about the existing smartclide images under eclipse-researchlabs

Btw, @mdelgado624, what about a logo for OpenSmartCLIDE. Can we "reuse" by adapting the current logo of SmartCLIDE. i had such ideas in mind: or Thx for your help

@shmacdonald can you please check if this is possible and desirable from the trademark PoV?

It is not desirable from a Trademark PoV. A new logo should be created.

Thx @shmacdonald.

@webmaster Would it be possible to make the container registry public ((https://github.com/orgs/eclipse-opensmartclide/packages)) by default? /cc @pkriefrvi

I think this should now be set correctly.

Unfortunately the container images are all still private: It would be great if you could check this again and make the images we stored there and will store there public by default. Thank you!

The packages setting matches eclipse-researchlabs organization, so AFAICT things are set correctly. Perhaps the CI job needs to be poked to set these as 'public'?

No it seems that this is still not working and it has nothing to do with our CI jobs.

Within the organisations the settings should be set to "public"

Usually one can tweak the settings under packages. The default seems to be still "PRIVATE". However, as we have no rights for the organisation settings (allthough we have the role project leads), we cannot do this. So we are blocked here.

The package creation permissions on the org level have been changed to allow public packages. I still had to manually set the existing packages to public.

Thanks a lot. I think they needed manually be set to public because the packages were created while the default was still set to PRIVATE.

@mward it seems that we transferred a repository we should not. Actually, one of our partners doesn't want to push his code to Eclipse so we need to remove its unique repository and put in back in the Research Labs. https://github.com/eclipse-opensmartclide/smartclide-RMV Is it an issue and can you do it easily ? Very sorry for the trouble.

Thx a lot

Ok I've transferred the repo back, although someone may need to tweak the teams.

Thx a lot @mward. What do you mean by "although someone may need to tweak the teams"?

When the repo was transferred to the eclipse-opensmartclide organization the original team/committers should have been removed and updated to match the opensmartclide team. With the transfer back to eclipse-researchlabs the opensmartclide team would have been removed and so my expectation is that whoever originally had access will need to be 're-added'.

Since I don't happen to know who that was(or who set it up originally) someone else will either need to fix that, or tell me who should have access so I can fix it.

However if there is some automated process managing these permissions that I'm unaware of then the problem may have already fixed itself.

Hi @mward, Thx for your explaination.

The repo smartclide-RMV seems to be always under eclipse-opensmartclide: https://github.com/eclipse-opensmartclide/smartclide-RMV I would expect to see it back under the research lab https://github.com/eclipse-researchlabs/smartclide-RMV. Did I miss something? Thx

It is not yet transferred back

yes, @sscholze366, it is also my understanding.

Hmmm, not sure what happened there. I've re-transferred the repo back to eclipse-researchlabs.

Now it is back to eclipse-researchlabs and it seems that the contributors are still assign as it was orginally, so thanks!

@pkriefrvi A question related to the rights on the organisation and or repositores: Is it planned that even the project leads have no rights to tweak settings in "our" organisation and "our" repositories?

For example:

• We cannot change the logo (probably not that important for now, but a good example)
• We cannot tweak the "Branch protection rules" settings for any of the opensmartclide repositories.
• We cannot change the visibility settings for packages that we built (see [here])(#367 (comment 1027772)).
• ...probably many more...

mentioned in issue eclipsefdn/helpdesk#2093 (closed)

@sscholze366 I cannot answer these questions but one. May I recommend, as it has been recommended to me, to submit your question to the HelpDesk (https://gitlab.eclipse.org/eclipsefdn/helpdesk).

For the logo, we should be able to change it through the Eclipse project editor:

I suspect, it will change also on GitHub but I might be wrong

@pkriefrvi Yes would be nice if helpdesk can support us on this.

Created the eclipsefdn/helpdesk#2108 (closed) issue

I suspect, it will change also on GitHub but I might be wrong

It will not.

Thx. Good to know.

Dear @mdelgado624, for some reason we didn't use the same email as project leader and as committer for @asalamanis in the proposal Would you mind replacing Athanasios Salamanis (asal@iti.gr) by Athanasios Salamanis (athanasios.salamanis@gmail.com). The second email is known by eclipse.

Thx a lot for your help

@mdelgado624 I could change the email on the proposal but it didn't impact the project. So I guess you have to do something else to make it happen. Thx a lot

@pkriefrvi the paperwork is in the workflow. I'll check again in a couple of days, but I don't see any particular issue with it.

mentioned in issue eclipsefdn/helpdesk#2108 (closed)

Dear @mdelgado624, we still have some missing committers. I will send them in a separate email. Thx a lot for your understanding /cc: @asalamanis @sscholze366

@pkriefrvi sure! since we're still in the bootstrapping phase we can make an exception and add them as part of the initial committer pool. In the future, the project team will need to run a proper committer election based on merit. There is more information available in the EF handbook.

added EDPInitial Contribution label and removed EDPProvisioning label

changed due date to November 16, 2022

marked the checklist item Project provisioned (including at least one committer) as completed