Re: [Review request] Git forge requirements

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Feb 12, 2020 at 09:03:44 -0500,
 Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:

However, I think it's important that if we choose a hosted solution, we have
a clear migration path _out_, and that includes not just the bare git repo
but metadata and all the other features like issues and pull requests and
comments.

That's not strong enough. That wording seems to assume we get warning that a migration is necessary and have time to execute it before we can't any more. Really you'd want to have regular backups of all that, someplace controlled by the project so that in the case of a no warning shutdown, recovery is possible without losing much data.
_______________________________________________
council-discuss mailing list -- council-discuss@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to council-discuss-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/council-discuss@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Users]     [Fedora Outreach]     [Fedora Desktop]     [Fedora KDE]     [KDE Users]     [Fedora SELinux]     [Yosemite Forum]     [Linux Audio Users]

  Powered by Linux