Eclipse Dataspace Connector Restructuring review

PMI link: Eclipse Dataspace Connector

The project is evaluating changing the scope and project name.

New project name is Eclipse Dataspace Components.

We'll use this issue to keep track of the restructuring review that will cover these aspect.

Background

The project scope has expanded from implementing a Connector to also implementing other components that are required for setting up a data space. New name should (very probably) be Eclipse Dataspace Components.

Some corresponding questions are: Rename a project Register a domain name for an external website Register a trademark for name and logo

Scope change

In order to implement the required scope and name change, we need to complete the following:

• EMO (ED) approval
• PMC notified by the PLs
• Trademark approval of the new name
• Inform the Eclipse Dataspace Connector community using the project communication channels.

changed due date to September 07, 2022

assigned to @mdelgado624

changed the description

We discussed the project name, corresponding short names, and identifiers. The group of committers would like to have the project named Eclipse Dataspace Components as mentioned above.

What we want to clarify are the possibilities for setting the shortname as identifier within the EF infrastructure and our namespace, as well as possible naming of the Github-organization.

A proposal would be to have the GH-Org named Eclipse Dataspace Components. Would that be possible, or do we need something like eclipse-dataspacecomponents for the GH-Org?

Using the shortname edc the namespaces, e.g. in Java would result in org.eclipse.edc.component.*

What we want to clarify are the possibilities for setting the shortname as identifier within the EF infrastructure and our namespace, as well as possible naming of the Github-organization.

Changing the short name is possible. edc makes sense to me, and it's not currently taken. The short name is used a lot of places... by way of expectation management, in the process of changing the short name, some things might break and require follow up. To change the short name, @mspiekermann... once we've completed this review successfully, you can open a help desk issue and coordinate the timing of the change with the IT Team (it's better if you open the issue since you need to be involved in the coordination of the timing).

A proposal would be to have the GH-Org named Eclipse Dataspace Components. Would that be possible, or do we need something like eclipse-dataspacecomponents for the GH-Org?

The text of the org can be "Eclipse Dataspace Components", but the technical namespace (that is the url) can/should use the short name, would be eclipse-edc (https://github.com/eclipse-edc)

Using the shortname edc the namespaces, e.g. in Java would result in org.eclipse.edc.component.*

If you believe that it will not be too disruptive to your current adopters, you can change the Java namespace. There is precedent, however, for keeping the namespace stable if that makes more sense to you. I defer to your judgment.

I would like to mention, that task 3 is nothing we need to track as mandatory in my opinion. Since registering project name trademarks is generally not done, we can decouple that from the restructuring process. I will address that as a follow-up, because Fraunhofer right now has no trademark to be transferred as the task suggests.

added restructuring label

added Trademark Approval Request label

changed the description

@shmacdonald please initiate trademark search for the new name of the project: Eclipse Dataspace Components

changed the description

marked the checklist item Trademark approval of the new name as completed

New Trademark name is approved.

Thanks, Sharon

@mdelgado624 since there are no comments on https://projects.eclipse.org/projects/technology.dataspaceconnector/reviews/restructuring-review we are allowed to move on to the next steps? Is it a task for me to inform the EMO and PMC using a mailing list or something else? Next step for me would be to make a list what needs to be renamed in terms of repositories and so on. What about the project and shortname? Do we "just" give a sign to the webmasters and they will change it on an aligned date?

@mspiekermann please inform the PMC using the public mailing list and your community using the project mailing list. In the meantime I've requested approval of our ED (executive director).

Regarding the shortname, please see Wayne's comment below:

once we've completed this review successfully, you can open a help desk issue and coordinate the timing of the change with the IT Team (it's better if you open the issue since you need to be involved in the coordination of the timing).

removed Trademark Approval Request label

@mmilinkovich we need your approval to change the project name of the Eclipse Dataspace Connector project to "Eclipse Dataspace Components".

approved

changed due date to September 14, 2022

changed due date to September 21, 2022

@mdelgado624 If I see it right, we have pass all preparatory issues and have all approvals, right?

• trademark
• community-review
• EMO approval

Right now we are discussing about a suitable date for the rebranding, since this include also changes in our codebase. We aligned within our committer group to schedule it with our next release, which would be end October. This would allow us a clear communication (community, press, etc.) as well as (impotant to us) give downstream projects the change to prepare as well. Would it be possible to align on a schedule (day not exact time)? Who should be involved for this? The group of webmaster?

@mspiekermann yes we should have all the approvals needed to conclude the review at this point. The project still needs to send a note to the PMC.

If I understood correctly you would like to make the re-branding at the end of October, together with your next release. This would mean that all changes in the EF infrastructure (PMI, DB, and GitHub repositories) should not be implemented until then.

Please confirm that this is the case. If so, we can keep this ticket open until then and notify webmaster when you're ready. Take into consideration that some of these changes can take a couple of days to be implemented, so I would suggest you request them one week before you're ready to advertise it to the community.

@mdelgado624 Yes, exactly as you said. We want to re-brand end of October and I will contact the webmasters a couple of days before we want to "switch". I will send the mail to PMC after my vacation 4/5 October and make a note within this issue.

marked the checklist item EMO (ED) approval as completed

changed the description

changed due date to October 19, 2022

PMC was notified via mailing list.

@mspiekermann thanks for letting me know!

Shall we ask @webmaster to start implementing the changes in the EF infrastructure?

@webmaster Any chance to have a call this week to clarify and align the next steps to avoid problems?

The biggest issue with a move like this is that we can't rename the mailing list(s). That's a well known(to us) limitation and our solution is to create new lists(with the correct name) and then post a 'list is over there now' message to the old list(s) before archiving them.

I'm a little uncertain about the CI instance, but I think it should be reasonably straight forward, @fgurr can you confirm?

We can handle the project website with some static redirects(www.eclipse.org/dataspaceconnector -> www.eclipse.org/edc).

Outside of that I think the rest of the redirections required are created automagically by Github.

So it really come down to when you'd like this to happen, and if you have a preference for the order in which things happen.

We have a check list for renaming projects, that should cover most of the issues that we found in the past. So yes, it should be mostly straight-forward.

If we can make a wish, we would like to happen this on Friday the 25th of November. We could do some checks on the weekend then, while not expecting users to work with the EDC and also prepare some information. Would that fit your schedules?

I think we can work with that timing. I'll talk to the RelEng team and report back if that date doesn't work

marked the checklist item PMC notified by the PLs as completed

mentioned in issue eclipsefdn/helpdesk#2133 (closed)

mentioned in issue eclipsefdn/helpdesk#2141 (closed)

assigned to @webmaster

changed due date to November 15, 2022

changed due date to November 25, 2022

changed due date to November 21, 2022

mentioned in issue #416 (moved)

Most of the rename work has been completed, but there are a few loose ends(ossrh,npmjs, etc) we'll wrap up on Monday.

Committers will need to update their remote URLs in any local copies of the repos to reflect the change in organization name to eclipse-dataspacecomponents .

In our old (?) CI environment (ci.eclipse.org/dataspaceconnector) I seem to not have any rights anymore, e.g. to start build jobs. Is that expected? Will our CI also get moved? If so, what will be the URL? Thanks

In our old (?) CI environment (ci.eclipse.org/dataspaceconnector) I seem to not have any rights anymore, e.g. to start build jobs. Is that expected?

Yes. I simply forgot to shut it down.

Will our CI also get moved? If so, what will be the URL?

=> https://ci.eclipse.org/edc/

Thanks for the info. However, seems like Setup isn’t quite complete, e.g. gpg credentials: https://ci.eclipse.org/edc/job/EDC-Nightly-Snapshot/112/console

Or is there anything we need to Update/change on our end?

quick update: on other builds i've witnessed bad passphrases. are they not bound yet, or do I need to update the GPG Key ID? https://ci.eclipse.org/edc/job/GradlePlugins-Snapshot/47/console

First of all, thanks for all the work over the weekend!

Not as important as the CI, but please also update the project's name on Github or grant me temporarily the required rights to do it myself.

In addition to the comment of @mspiekermann: We agreed on renaming the DataSpaceConnector repo to Connector to prevent name duplications.

On top of that, descriptions need to be updated:

• Publications: "Eclipse Dataspace Connector - Publications" --> "EDC publications"
• Collateral: "Eclipse Dataspace Connector - Communication Collateral" --> "EDC Presentations and Working Documents"
• Connector: "DataspaceConnector project" --> "EDC core services including data plane and control plane"

Do we need to create a separate issue for these requests?

Or is there anything we need to Update/change on our end?

I'm still in the process of cleaning up. Will comment here once everything is done.

In addition to the comment of @mspiekermann: We agreed on renaming the DataSpaceConnector repo to Connector to prevent name duplications.

On top of that, descriptions need to be updated:

• Publications: "Eclipse Dataspace Connector - Publications" --> "EDC publications"
• Collateral: "Eclipse Dataspace Connector - Communication Collateral" --> "EDC Presentations and Working Documents"
• Connector: "DataspaceConnector project" --> "EDC core services including data plane and control plane"

Do we need to create a separate issue for these requests?

No. I've applied the requested changes.

Thanks! @fgurr I am sry but I forgot the docs repo: "Eclipse Dataspace Connector - Documentation" should also not name the old branding --> "EDC documentation"

OK. Done.

The GitHub org has been renamed to https://github.com/eclipse-edc/ to be in line with the project ID.

@platzel I've re-added the ossrh-account GitHub credentials that were set up in eclipsefdn/helpdesk#1341 (closed) and the gpg-passphrase credentials. Both are non-standard credentials and therefore required additional effort.

The builds still show:

gpg: signing failed: Bad passphrase

I will have to dig deeper.

If it helps we could hop on a call tomorrow and keep feedback loops short.

@fgurr I noticed that there was a misconfiguration in the job, possibly due to the migration: the PASSPHRASE variable was bound to the Bot Credentials secret (???). Anyway, changed it to be bound to GPG Passphrase, but now I get a 401 when communicating with the Sonatype repo: https://ci.eclipse.org/edc/job/GradlePlugins-Snapshot/50/console. We're getting there.

...same thing happened for the OSSRH account username/password - they were simply bound to the wrong credentials object. @fgurr with that, I believe we can assume this to be working again.

Let me know if anything else is still missing.

@mdelgado624 "Inform the Eclipse Dataspace Connector community using the project communication channels." is done and can be marked accordingly.

Thanks for the update @mspiekermann. At this point I believe we're done and we can now close this ticket!

marked the checklist item Inform the Eclipse Dataspace Connector community using the project communication channels. as completed

closed

added Successful label

mentioned in issue emo-services#5 (closed)