Re: GitHub reliability
Seth via Boost <[email protected]>
| Newsgroups | gmane.comp.lib.boost.devel |
|---|---|
| Message-ID | <[email protected]> |
It seems you are referring to optional features. GitLab can even be self-hosted from official packages, or you can compile the community edition from source yourself # Clone GitLab repository sudo -u git -H git clone https://gitlab.com/gitlab-org/gitlab-foss.git -b <X-Y-stable> gitlab Full docs https://docs.gitlab.com/install/self_compiled/ I may not be fully aware of additional licensing constraints so I welcome anyone who has a comparison matrix of licensing/hosting/support options. I know several people who self-host GitLab for free. My $0.02 Seth On Wed, May 13, 2026, at 9:59 PM, Peter Taraba via Boost wrote: > they only have 30 day free trial... > > Get Started with GitLab > > Try our most advanced features, including GitLab Duo Agent Platform to automate development tasks with AI agents. After your 30-day trial, continue with free features or upgrade to unlock the full value of GitLab. > > > > well, we dont need ai, but if they start blocking other features? > > Best, > Peter > > https://randommathguy.blogspot.com/ > Ph.D. from Slovak University of Technology in Bratislava, Slovakia > Microsoft Research, J.W.Goethe University and ST Microelectronics Alumnus > > > *Sent:* Sunday, May 10, 2026 at 9:47 PM > *From:* "zweite Konto via Boost" <[email protected]> > *To:* "Boost developers' mailing list" <[email protected]> > *Cc:* "zweite Konto" <[email protected]> > *Subject:* [boost] Re: GitHub reliability > Any reason GitLab is not being considered? I think that is also a community > maintained platform? > > On Mon, 11 May 2026, 7:50 am Klemens Morgenstern via Boost, < > [email protected]> wrote: > > > 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/ > > > _______________________________________________ > 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/JSBFACOV7724MUCLGDUG5XQWKBBE3NOP/ > _______________________________________________ > 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/66NIDTFU6CDU7IGX35BWJEIF3NKOKIOV/ > _______________________________________________ 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/SVOGRMW4UW2TIQ6KLZFVSE5OV7AWUDMM/