Migration of openPASS to GitLab

In the future, the openPASS project should be managed over GitLab. Please trigger the migration as soon as possible.

Hi there, it would be helpful if you could list your Git repositories. Thank you.

Hi,

please migrate all branches in https://git.eclipse.org/c/simopenpass/simopenpass.git/. Thank you!

If you have further questions, feel free to contact me!

Hello,

I don't see you listed in the project committers or leaders list: https://projects.eclipse.org/projects/technology.simopenpass/who

Please ask the project lead approve the request (in this issue).

Hello, as one of the project leads I can approve the migration to GitLab. Thanks, Alex

We'll perform the migration in a few hours.

I've added a new blank repo to your project information at https://projects.eclipse.org/projects/technology.simopenpass

One that's created, I'll use it to import https://git.eclipse.org/c/simopenpass/simopenpass.git/

Once imported, I'll mark the git.eclipse.org repository as read-only, and delete it once you're satisfied with the contents on gitlab.

The group (and repository) have been created, waiting for teams to sync: https://gitlab.eclipse.org/eclipse/simopenpass

The team has been sync'ed. Can you see if everything is as it should be?

https://gitlab.eclipse.org/eclipse/simopenpass

Thank you @droy for the migration and your great work! I am just collecting feedback from the WG if everything is fine. Next week I will tell you about the feedback!

@droy , is it possible to migrate all the open and ongoing epics and user stories from Tuleap https://tuleap.eclipse.org/projects/openpass/ to GitLab?

I haven't seen any tuleap -> gitlab import tools or processes.

You have 10 open bugs in bugzilla: https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&list_id=20071303&order=Importance&product=Simopenpass&query_format=advanced

Would you like those imported as well?

Well spotted, @droy! Yes, please import those as well!

@droy What is the status here? To which place are you going to import the bugs?

Those 10 bugs can be imported as issues in the project (https://gitlab.eclipse.org/eclipse/simopenpass/simopenpass/-/issues). Or we can simply archive the Bugzilla bugs. Please confirm what you'd like to do.

@droy The current members on the GitLab consist of committers and project leads. It seems that they have more options than a non member user. Is it possible to add other Working Group Members to the member list such that they can work actively on the project?

That is all you should see. Everyone and anyone can work on the project (as a contributor) by forking the repository and submitting merge requests. There is a distinction between the Simopenpass Eclipse OSS project, and the Eclipse OpenPASS working group. Being in the WG doesn't grant automatic committer access to the repository. To become a committer, please see the handbook: https://www.eclipse.org/projects/handbook/#elections-committer

@droy There is another issue we have been confronted with while testing GitLab. Clicking on the "Operations" tab leads to a Error404 Page not found defect note https://gitlab.eclipse.org/eclipsefdn/gitlab/-/feature_flags. Can you please have a look on that issue?

I believe "Operations" requires elevated permissions. I believe the webdev team is working on a mechanism to give elevated permissions to project leans. Perhaps @malowe can comment and link to the issue where that work is being tracked?

Found it, here: https://gitlab.eclipse.org/eclipsefdn/gitlab/-/issues/17

I've responded on the thread of the issue that Denis just linked. TLDR, not in progress yet, and there are a few pieces to look into before we make the change that would give the permissions you likely need. Once we finish the investigation and any patches from that, the permissions change is quick and easy thankfully.

More info from Tuan: When it comes in editing the meta information such as due date, assignee, epic, etc. it is not feasible.

I agree this should be part of the default permissions for anyone with write access to the repo. I'll look into that separately.

@droy just to clarify some things:

We from the openPASS WG want to make a proper release planning. Therefore, we need some rights on GitLab to do so. Until now, as a non-member on the GitLab simopenpass project we are able to create issues. When it comes in editing the meta information such as due date, assignee, epic, etc. it is not feasible. As a product manager it is my duty and task to edit those issues. Furthermore, it is necessary that other partners in the project can edit those meta information, too.

a) create issues. I was able to create an issue by using a normal user account: https://gitlab.eclipse.org/eclipse/simopenpass/simopenpass/-/issues/6 You must be logged into GitLab to create an issue.

b) meta info can be changed be Committers on the project only. If you need to change these, please follow the elections process (outlined earlier). We do not allocate permissions to open-source projects based on a role inside a company.

@tduongquang Although "Manage Operations" requires Maintainer level (we place everyone at the Developer level) the items you've listed should be possible for the project developers:

https://docs.gitlab.com/ee/user/permissions.html

@droy Can you please make me as an owner of the simopenpass project in GitLab?

I need the right to delete issues and epics which is only possible as an owner.

After a Q&A session with Paul Buck and Wayne Beaton We still have some open issues and figured out some bugs. I am going to open new ones to get a better overview. I will close this one.

closed

mentioned in issue #456 (closed)

mentioned in issue #522 (moved)

added Migration ~16083 labels

added wg:OpenPASS label