Migration to Github

Hello,

I want to migrate the entire project in the future to github, do you have any best practises how to do so? I saw that some projects are eclipse and under github, but i dont understand really how this fits in the gitlab usage.

regards

added IT-prioritylow IT-severitylow statetodo team:infra labels

added service:GitHub label

I'm not certain I understand the question, but I suspect the general workflow would be something like:

1. Agree on a transition time with the project
2. Create a Github org to hold the project
3. Import repositories
4. Clean up Gitlab

There are some details left out(ie:what happens to issues? do redirects occur? etc) simply because it's never been done.

Would you be willing to provide some details about why your considering this move?

Thanks for the answer:) Maybe the entire project migration has too much impact... Currently i have just concerns about the external gitlab runners/packages repos, and i asked myself, if it's somehow possible to use the github runners/packages registries for pipeline purposes, or reaching any sync of changes made there. Some people just forking the gitlab repos to github, working there, but never push code back to eclipse, because the governance is too hard for easy cooperation. So i was thinking about any bot structure which pushing the things backs by creating MRs. Or the otherway arround. I saw also other projects which are somehow connected to github, but registered in eclipse, and was curious how they made that. It's in the moment just an diffuse brainstorming about options:) I thought maybe you got such problems in the past already, and have maybe some best practises.

I have concerns about the external gitlab runners/packages repos

Our RelEng team is doing some work around Gitlab runners, so depending on your concerns they may have answers.

if it's somehow possible to use the github runners/packages registries >for pipeline purposes, or reaching any sync of changes made there.

I will defer to our RelEng team here.

the governance is too hard for easy cooperation.

I'm not sure this is 'fixable' simply by moving the project to Github as we enforce the same rules around contributions(ie: that the contributor has signed the ECA).

@wbeaton any thoughts here?

I saw also other projects which are somehow connected to github, but registered in eclipse,

Projects can choose to have their repositories on our Gitlab instance, or in an organisation on Github.

/cc @fgurr

The governance is the same on GitHub and on our GitLab instance. An EF account and ECA are required in all cases.

AFAICT, it's a technology problem/opportunity: to do a pull request from GitHub to GitLab, you'd have to create a fork on GitLab, push your GitHub changes to that fork, and then work the GitLab contribution process via MR (which I assume is a PITA for developers who are used to just working in GitHub). I assume that it's these extra steps that are blocking contribution.

Thanks for the answers:) @wbeaton would it be possible to create at least for the xfsc project one github organisation + a repo, so that we can setup a runner workflow which is triggered by gitlab webhooks? I think that can work to avoid external runner service:) So far i see i could easily setup here webhooks, which forward the necessary information for docker builds to the github runners. If yes how is the process to set up this github repos?

@schulzesttsi Matt can set up a GitHub org for the project.

/cc @mward

I've created the organisation and an initial repo so you can experiment.

Committers that have added their Github IDs to their Eclipse.org accounts will receive access when the sync tooling next runs.

marked this issue as related to #5202 (closed)

marked this issue as related to #5822

assigned to @jmazanek4ep