1. 21
  1. 13

    Neat! I’m moving away from Github, but haven’t gone quite this far yet.

    I’ve been reluctant to post this as a top level submission to Lobsters, but I feel like it could be tangentially relevant here:


    I’m also slowly working on a command line tool to smooth the process of using the Gitea migration dialog over and over. I had thought to include a flag to archive migrated repositories, as an indicator that I had moved away from Git{hub,lab}. This post has me thinking it could be worthwhile to include a scrub flag to leave a more pointed message behind.

    1. 6

      Gitea is amazing. I use Codeberg and selfhost my own for private projects.

    2. 10

      Unless gitea or sr.ht solution provide a decentralized login system in a way that users shouldn’t have to sign up for an account to open issue or send MR to any random project they find interesting, I find moving away from GitHub actually detrimental to FOSS contributions at least for new-comers.

      1. 13

        I think it depends on what you consider the goals of “FOSS contributions” to be. Some people, myself included, are becoming a bit uncomfortable with the centralization and inertia that are locked up behind Github, on top of the fact that they have been pretty cavalier with releasing tools that enable people to violate established FLOSS licenses with ease.

        1. 11

          You don’t have to sign up for an account on sr.ht to open issues or send MRs.

          You should have an email client that you like though.

          1. 13

            You should have an email client that you like though.

            I hate git-send-email more than I hate GitHub. I reckon a lot of people are like me.

            1. 4

              I fear it because I’ve never used it.

              Its probably not a bad tool, depending on your setup for email. Everybody who contributes being at least technical enough to set up an email client might even help raise the value of contributions.

              At least that’s the hope.

              1. 5

                You don’t need an email client for git-send-email. It does everything. You just need to give it your SMTP details https://git-send-email.io

          2. 7

            Not for long! Gitea is actively developing federation using the ActivityPub-based Forgefed protocol so that you’ll be able to interact with users and repos on any Gitea instance using only a single Gitea account. Some federation features will be probably be included in the next major Gitea release, 1.18.

            Also, both Forgefriends and ForgeFlux are developing ForgeFed proxies for GitHub, GitLab, and sr.ht, so eventually (in a year?), you’ll even be able to use a single Gitea account to interact with GitHub repos.

            1. 5

              You’re right, but Github already has that problem. It’s just that by now everyone has a Github account.

              So what they really need is a big “login with your Github account” button? ‘Cause github sure doesn’t take account logins from other things.

              1. 4

                frankly I think github is the yahoo for developers. Sold once too often. And past it’s time. Hell, was it cool once.

              2. 6

                I really hope for stuff like Federated software forges

                1. 3

                  gitea does offer an OAuth2 provider and I believe has the capability of accepting logins from GitHub or GitLab, you just need to set it up. Personally, I don’t think projects like that will catch on the same way as GitHub just because they require a level of effort to maintain and keep running. For small personal projects, or niche stuff, sure go for it.

                  Also, I think Sourcehut (although I still like to call it “sir hat”) has a way to contribute via email alone, even bug reports. It does use git-send-email for mailing lists, but you can also email the project with an issue or bug report and converse with folks without ever needing an account. Generally, it feels like Sourcehut tries to stick to traditional collaboration techniques with Git, which works out well for personal projects and projects maintained/used by technical-oriented people. I like its compromise between fully owning your own project management tooling (and having to set up all those mailing lists, Git/web hosting, and IRC stuff yourself) and dealing with however GitHub decided to build their pull request UI, or force your users to create a GitHub account just to contribute.

                  1. 1


                    But honestly these days the kind of users you talk about will be ok with a log in with GitHub or log in with Google button

                  2. 2

                    Annoying. I wanted to see what else the guy has made on github, but his profile is empty