[pulseaudio-discuss] Moving to GitLab

[Arun Raghavan]

Hi folks,
The freedesktop admins have now started helping projects move to GitLab (http://gitlab.freedesktop.org/) on a pilot basis. I'm quite excited about this as it would mean a better way to track patches, as well as a more familiar interface for new contributors coming from the Github world.

The choices are to move piecemeal (git + merge requests first, bugs later), or just do it all at one shot. I favour the latter, in the spirit of absorbing all the migration pain at one shot. This is probably a good time in the release cycle to do this as well. There's a tracker bug for getting this done at:

https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/49

Thoughts? Questions?

As a first step, I would request everyone with commit access to set up your account and populate your key(s).

Cheers,
Arun

p.s.: Once this is done, I also want to move our CI over.

[Arun Raghavan]

Post by Arun Raghavan
Hi folks,
The freedesktop admins have now started helping projects move to GitLab
(http://gitlab.freedesktop.org/) on a pilot basis. I'm quite excited
about this as it would mean a better way to track patches, as well as a
more familiar interface for new contributors coming from the Github
world.
The choices are to move piecemeal (git + merge requests first, bugs
later), or just do it all at one shot. I favour the latter, in the
spirit of absorbing all the migration pain at one shot. This is probably
a good time in the release cycle to do this as well. There's a tracker
https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/49
Thoughts? Questions?
As a first step, I would request everyone with commit access to set up
your account and populate your key(s).

We're moving ahead with this. Subscribe to the bug above to keep track of progress, and I'll send out an update as the big changes happen.

Cheers,
Arun

[Arun Raghavan]

Post by Arun Raghavan

Post by Arun Raghavan
Hi folks,
The freedesktop admins have now started helping projects move to GitLab
(http://gitlab.freedesktop.org/) on a pilot basis. I'm quite excited
about this as it would mean a better way to track patches, as well as a
more familiar interface for new contributors coming from the Github
world.
The choices are to move piecemeal (git + merge requests first, bugs
later), or just do it all at one shot. I favour the latter, in the
spirit of absorbing all the migration pain at one shot. This is probably
a good time in the release cycle to do this as well. There's a tracker
https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/49
Thoughts? Questions?
As a first step, I would request everyone with commit access to set up
your account and populate your key(s).

We're moving ahead with this. Subscribe to the bug above to keep track
of progress, and I'll send out an update as the big changes happen.

And this is done!

The organisation is at: https://gitlab.freedesktop.org/pulseaudio

Existing open bugs have been migrated, and new issues should be filed against the relevant project (for example https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues)

We are also transitioning from patches sent to the mailing list to MRs (merge requests). The simple description of the workflow is that you create a fork using the GitLab UI, create a branch, push your changes, and then get back to the web UI which will let you create a merge request from your fork/branch. (more details at https://docs.gitlab.com/ee/gitlab-basics/add-merge-request.html)

That's it. Please chime in if you have questions/comments.

Cheers,
Arun

p.s.: My heartfelt thanks to Daniel Stone and the freedesktop.org admin team for the super quick migration.

[Arun Raghavan]

Post by Arun Raghavan

Post by Arun Raghavan

Post by Arun Raghavan
Hi folks,
The freedesktop admins have now started helping projects move to GitLab
(http://gitlab.freedesktop.org/) on a pilot basis. I'm quite excited
about this as it would mean a better way to track patches, as well as a
more familiar interface for new contributors coming from the Github
world.
The choices are to move piecemeal (git + merge requests first, bugs
later), or just do it all at one shot. I favour the latter, in the
spirit of absorbing all the migration pain at one shot. This is probably
a good time in the release cycle to do this as well. There's a tracker
https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/49
Thoughts? Questions?
As a first step, I would request everyone with commit access to set up
your account and populate your key(s).

We're moving ahead with this. Subscribe to the bug above to keep track
of progress, and I'll send out an update as the big changes happen.

And this is done!
The organisation is at: https://gitlab.freedesktop.org/pulseaudio
Existing open bugs have been migrated, and new issues should be filed
against the relevant project (for example
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues)
We are also transitioning from patches sent to the mailing list to MRs
(merge requests). The simple description of the workflow is that you
create a fork using the GitLab UI, create a branch, push your changes,
and then get back to the web UI which will let you create a merge
request from your fork/branch. (more details at
https://docs.gitlab.com/ee/gitlab-basics/add-merge-request.html)
That's it. Please chime in if you have questions/comments.

Please note that while pulseaudio-commits will continue to get commit emails, pulseaudio-bugs will no longer be functional. You can just go and to the GitLab UI and "Watch" the PulseAudio group (or any repo / issue within it) to get the same effeect.

-- Arun