| Yes, Denis’s blog post earlier this week https://blogs.eclipse.org/post/denis-roy/moving-eclipse-projects-github-and-gitlab had me thinking about the situation again. I agree that it’s preferable to be proactive about the move, rather than force ourselves into it down the road. Normally I’d say let’s do this after the Java 11 work is finished, but since you’ve been taking that on yourself, you’re in a better position to say how that’s going.
* Do we want to do a Java 11 based Wikitext release ahead of Github migration? * If so, should we bump up the version to 3.1 (as this will break compatibility with Java 8/9 runtimes).
Regardless of these choices, I vote positively that we take on the Github migration next.
- Leo
Hey everyone, * many devs already have github accounts so no need to learn new tool as much as GitLab is similar, even having one less account is worth it * dependabot and other GH bots and actions
If there is agreement, I can drive the move.
Interesting development. I can’t say I was very fond of the Github reviews feature last time I used it, but that was admittedly a few years ago and hopefully it has improved.
--- license-tool-plugin:0.0.1-SNAPSHOT:license-check (default-cli) @ parent ---
[INFO] Querying Eclipse Foundation for license data for 166 items.
[INFO] Found 166 items.
[INFO] Vetted license information was found for all content. No further investigation is required.
[INFO] Summary file was written to: /home/jenkins/agent/workspace/lsp4e-github_master/target/dash/summary
From https://ci.eclipse.org/lsp4e/job/lsp4e-github/job/master/18/console .
Having these updates handled for us is smth totally impossible on gerrit infrastructure now but saves so much time.
Aleksandar, how much friction was there in the migration process for the other projects you were on? Migrating the git repo will obviously require updating our builds. One of our release builds does some git repo tagging (I think through mvn-release plugin) that required some assistance from the Eclipse CI/Jenkins team to initially help set up, and then again to migrate to the JIPP infrastructure. I think a ci-bot specific to the project needed to be set up with write access to the repo. Do you know if this is still supported on Github? As long as we can port our builds quickly, I don’t have issues moving to Github.
Migration was pretty straightforward e.g. for lsp4e it literally costed a day to do minor changes to jenkins. Foundation provides a bot to do tagging too as per https://wiki.eclipse.org/CBI#GitHub_and_Bot_Accounts so I assume that should be pretty straightforward but haven't used it yet.
I’m also curious about how Github hosted contributions tie into the ECA? Will contributors need to have both an Eclipse.org account, and a Github account that’s linked to the Eclipse account? I find that Eclipse.org registration seems to be a point of friction for some of our newer contributors at Tasktop, but I imagine that step still a requirement even when the contribution is coming from Github.
Thanks, Leo
-- Leo Dos Santos Senior Software Engineer, Tasktop Integrations
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mylyn-docs-dev
-- Aleksandar Kurtakov
Red Hat Eclipse Team
-- Aleksandar Kurtakov
Red Hat Eclipse Team
_______________________________________________ mylyn-docs-dev mailing list mylyn-docs-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mylyn-docs-dev
-- Leo Dos Santos Senior Software Engineer, Tasktop Integrations
|
