Re: GitHub reliability
Vinnie Falco via Boost <[email protected]>
| Newsgroups | gmane.comp.lib.boost.devel |
|---|---|
| Message-ID | <CA+EzHGe3VOgM9SpU0D_BW5N3cDAAcAShzRHKfYMq59HKU-yQDQ@mail.gmail.com> |
On Sun, May 10, 2026 at 9:07 PM Marshall Clow via Boost < [email protected]> wrote: > On May 10, 2026, at 5:02 PM, Peter Taraba via Boost <[email protected]> > wrote: > Then they showed that they could no longer run it well Yep. So, there is no urgency, and we should start thinking about what a migration plan might look like. How do we extract the open issues and transfer them? What do we do with the CI system? Release packages? Open pull requests? If for example we want to transfer the open issues then we should start collecting them now, because of rate limits (it could take weeks or months to collect all the data which is not stored in the repo). We also might think about the libraries which are not actively maintained (if any?) we could reach out to authors and make sure everyone is aware and involved in planning a migration. If we prepare now, we can be ready ahead of time, instead of having the issue forced on us when things become untenable at GitHub. Thanks _______________________________________________ Boost mailing list -- [email protected] To unsubscribe send an email to [email protected] https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/[email protected]/message/3SYG4QWSU6MV5U7WYQDJMPMIXFPZG5VD/