Re: GitHub reliability

On Mon, May 11, 2026 at 9:53 AM Vinnie Falco via Boost <
[email protected]> wrote:

> 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
>
>
> I've used Gitea a few years ago and it looks like Codeberg's Forgejo is a
clone.
Back then Drone CI worked great with Gitea.
It seems that drone has been forked into Woodpeckers CI as well, which
Forgejo is using by default.

Thus, the existing drone scripts should largely work.

So either Gitea + Drone or Forgejo + Woodpeckers sound great to me.


> 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?
>

I think the first attempt should be to spin up a mirror of either Forgejo
and/or Gitea
and see how it works.
And then we set a date, at which we disable issues and PRs on Github
and use github as a pure (and automated) mirror.


> 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).
>

Both have an "import from github" function, that allows you to import a
full project.
This is probably a good default, unless a maintainer wants to do it another
way (e.g. only transfer certains issues).




> 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/
>
_______________________________________________
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/JQFOILZOCBSZBSFDAPKC5MXU6OJYKHBT/