search

swaywm / wlroots

A modular Wayland compositor library
https://gitlab.freedesktop.org/wlroots/wlroots/
MIT License
2.15k stars 342 forks source link

Rehoming wlroots on gitlab.freedesktop.org #1858

Open ddevault opened 5 years ago

ddevault commented 5 years ago

Hi folks! I've been speaking to some of the wlroots maintainers and we're all in favor of moving wlroots from here on GitHub to gitlab.freedesktop.org. fd.o is the home to many other projects in this space, such as Wayland upstream, the X server, Mesa, libinput, and more. wlroots will be in good company there. It's also more socially responsible to host this project there than on GitHub, as fd.o is an open source organization and run by people in the community that we trust.

Anyone sitting on an open pull request here on GitHub is welcome to continue integrating it here, or to close it and re-open on Gitlab when the time comes.

wlr-protocols is coming with. The bindings for each language can join us at the maintainer's discretion.

wlroots has migrated to gitlab.freedesktop.org. This issue has been moved to:

https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/1858

ddevault commented 5 years ago

https://gitlab.freedesktop.org/wlroots/wlroots

https://gitlab.freedesktop.org/wlroots/wlr-protocols

Just for testing right now, until CI is rigged up we're not accepting MRs there yet.

ddevault commented 5 years ago

Pulling the plug on this for now until the following GitLab bug is addressed:

https://gitlab.com/gitlab-org/gitlab/issues/16491

The CI experience for merge requests will be worse than it is on GitHub under these constraints.

emersion commented 3 years ago

We now have a sensible plan for CI.

Assuming no objections from the core contributors, wlroots will migrate to gitlab.fdo on November 1st. The wlroots and wlr-protocols repositories will be migrated. Please create a gitlab.fdo account with the same e-mail as your GitHub account to allow comments to have the correct author.

cherti commented 3 years ago

As all PRs have to be reopened with the migration anyways, is the primary branch going to be renamed to adhere to git recommendations as I recently found out that git itself, while still creating the primary branch under the name master when issuing git init, shows a very explicit deprecation warning indicating that the default branch name is subject to change and fairly strongly implies it should be renamed?

The full deprecation warning as it is shown to me:

hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint: 
hint:   git config --global init.defaultBranch <name>
hint: 
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint: 
hint:   git branch -m <name>
emersion commented 3 years ago

The PRs won't need to be re-opened, they will be imported by GitLab. The master branch won't be renamed.

This warning appears when creating a new repository. For the GitLab migration a new repository won't be created, the old Git repository will be re-used. The deprecation isn't about existing repositories, it's just about Git defaults when creating a new repo which shouldn't be relied upon. The deprecation warning doesn't imply that existing master branches should be renamed.

If you feel like the default branch should be renamed, this can be discussed in a separate issue, but it's orthogonal to the migration.

emersion commented 3 years ago

We've migrated: https://gitlab.freedesktop.org/wlroots/wlroots