[Cluster-devel] Moving gfs2-utils away from fedorahosted.org

[Andrew Price]

On 19/09/16 17:48, Andrew Price wrote:
> Hi all,
>
> Re: https://communityblog.fedoraproject.org/fedorahosted-sunset-2017-02-28/
>
> We'll need to find a new host for the cluster projects that haven't
> migrated away from fedorahosted.org yet.
>
> The recommended successor to fedorahosted.org is pagure.io which is a
> Fedora project, open source, uses the same user account system, allows
> git hooks to be set up, and has the added advantage that we have a
> direct line to the admins and developers.
>
> I've investigated whether pagure.io has the features required to support
> our workflows (group push access) and I've had confirmation that it does
> from #fedora-admin. I've also tried out the test instance of Pagure
> <https://stg.pagure.io/> and it looks like it has everything we need.
>
> We have until Feb 28 to do this so there is time to discuss the
> migration if discussion is needed. Unless we find some good reasons to
> go elsewhere I'll aim to migrate the gfs2-related git repositories to
> Pagure by the end of January.

Progress on this:

- A new repository has been created at <https://pagure.io/gfs2-utils> 
and everything in the gfs2-utils Fedora Hosted repository has been 
pushed to it. This will be kept mirrored until the switch over.

- A gfs2-utils maintainers group 
<https://pagure.io/group/gfs2-utils-maint> has been set up and given 
push access to the repository.

- Filed a ticket <https://pagure.io/fedora-infrastructure/issue/5696> to 
get the release tarballs etc. migrated over (and hopefully a URL 
redirect set up).

- Disabled the issue tracker and pull request features for the project 
as we currently have no plans to move away from Bugzilla and email.


Left to do:

- Switch over. I think Feb 3 would be a good date for this as it gives 
us plenty of time to work out any issues, though I don't foresee any.

- Migrate over the current push access list. Pagure uses the Fedora 
accounts system like Fedora Hosted does so this should be simple.

- Set up commit notifications to the appropriate mailing list.

- Update URLs etc. in the git repository itself.

If there's anything I might have missed, do let me know.

Cheers,
Andy