FYI, take action if you have projects in fedorahosted.org
---------- Forwarded message ----------
From: Kevin Fenzi <kevin(a)scrye.com>
Date: Thu, Sep 8, 2016 at 12:44 AM
Subject: Fedorahosted.org sunset: 2017-02-28
Fedora Infrastructure currently maintains two sites for general open
source code hosting: fedorahosted.org and pagure.io.
Fedorahosted.org was established in late 2007 using Trac for issues and
wiki pages, Fedora Account System groups for access control and source
uploads, and offering a variety of Source Control Management tools
(git, svn, hg, bzr). With the rise of new workflows and source
repositories fedorahosted.org has ceased to grow, adding just one new
project this year and a handful the year before.
Pagure.io was established in 2015, and is a modern Flask/Python based
application. It is under rapid development and supports git repos for
source code, docs, and tickets. The pull request model is used for
changes along with many options for projects. Access control is
standalone. New projects are self service and added all the time.
Given the lack of growth and continued maintenance burden, Fedora
Infrastructure would like to retire fedorahosted.org and encourage all
its active projects to move to pagure.io (or whatever other place they
feel best meets their needs). We have tenatively scheduled this
retirement for February 28th, 2017.
The Infrastructure team has already contacted owners of the top ten
projects on Fedora Hosted for input on their needs. If your project
has special needs, please contact the Infrastructure team (details
below) to discuss options.
After the sunset date, we will continue to provide raw data from public
projects previously hosted at fedorahosted.org, but the service itself
will be closed. We hope to provide this data for download for a few
years, but won't provide it forever.
A quick FAQ:
Question: pagure.io has some issues/problems that prevent me from
moving my project there. What can I do?
Answer: Please file these issues against pagure:
https://pagure.io/pagure/issues/ and we will try and address them as
best we can. Note that not every feature request can be accommodated
but the team will consider all requests.
Question: How can I migrate my data from fedorahosted to pagure.io?
Answer: You can use the https://pagure.io/pagure-importer tool to
migrate trac data to pagure.io issues. Git repositories should be
easily migrated with a push to the new pagure.io repo. Releases can be
uploaded to pagure.io.
Question: I want to test things out, but not migrate yet, how can I do
Answer: We have a https://stg.pagure.io/ test instance you are welcome
to create projects on and test importing data. Note that from time to
time we clear out this instance, so do not use it for any long term
Question: What happens if I ignore this/don't get around to migrating
my project by the 2017-02-28 deadline?
Answer: We hope to provide the raw data from projects for download for
a while, so you should be able to download a tar.xz of your old git
repo and trac files, but it will be up to you to extract what you need
from them, and we won't host them forever. The data sunset period would
be at least several additional months.
Question: Does pagure.io support hg, bzr, svn or cvs?
Question: I have more questions, where can I get more answers?
Answer: Feel free to ask on the infrastructure(a)lists.fedoraproject.org
list or #fedora-admin on IRC
announce mailing list