I am waiting for #gitea#forgejo to implement support for #ActivityPub. Once that is available and every ActivityPub account can open issues without needing to open a local gitea/forgejo account, I will spin up my own instance of forgejo to host my git repos. Moar #decentralisation :) (I have already moved my repos from GitHub to #CodeBerg a year ago)
Good points by @edward on how the git/GitHub/pull request monoculture is holding us back.
I have an account on Codeberg, the co-operative, fully open source, code hosting site, but it’s basically a GitHub clone—what if, freed from the monopoly, we found better ways to collaborate?
@graue I've used other version control software before (subversion, mercurial, etc.), and I believe Git has its own merits beyond GitHub for having become so dominant, but that is matter of another conversation.
So as long as Git remains opensource, embedded in a very active community and not controlled by any corporation, there is not a big risk about its dominance IMHO.
GitHub as the de-facto hosting for repos, collaboration and CI, I fully agree it is a massive risk, and that is why I've been personally shying away from for quite some time now. And the same applies to GitLab or Bitbucket or any other, I believe.
Running your own Git server for your team is trivial, so that should be the first step to make sure your code is always available regardless of whatever drama happens now or in the future with GitHub or her siblings. For this you can use a self-hosted Gitea, Forgejo or GitLab server, they all come with all of the bells and whistles you really need.
Now your code is safe... phew!... but you don't have the large community of GitHub to engage with any more.
In the short term, just push a mirror of your self-hosted repo to GitHub or GitLab and you will get back all the social interaction without the risk of losing your code. Yes, you are still subject to all the Microsoft sniffing of your code, but for opensource projects, you really don't care.
In the medium and long term, several of these self-hosted Git servers will implement support for federation via ActivityPub (or something else), which in practice will make our tiny Git servers capable of talking to each other and even other Fediverse applications such as Mastodon or Misskey.
Once this happens, we don't need GitHub at all any more, and I predict a massive migration in a very short time, because differently from Twitter or Instagram, the community of GitHub is made of tech savvy people, who will have no concern whatsoever for running a Gitea or Forgejo server.
We shall see the eventual demise of Microsoft GitHub following after.
Ever since I saw the requests from Lemmy and KBin devs to tread lightly on their issue trackers, I've been thinking about this. How can we, the people benefiting from the underpaid (often unpaid) specialist work of Free Code devs, manage our feedback (which can be very useful) in ways that help them to help us?
Anyone willing to volunteer? All necessary training and mentoring provided. You don't need any experience with anything but being a human who knows how to use a web browser.
@gregorni see if you can contribute to #Codeberg / #Forgejo Idk the degree to which the main project accept community contributions. Maybe something to look into?
Otherwise you may find that cloning the repo on device with termux and committing and pushing from your termux command line gets you a better experience. Plus you can access the files in termux from any external text editor using the system file picker. If you don't have termux already you can find it on f-droid.
@sugar_in_your_tea About "good time to jump in": the small size of the lemmy dev community gives you a chance to shift off Microsoft to a community git forge e.g. #Codeberg [1] that aims at forge federation [2] before there's too much #TyrannyOfConvenience inertia. Mastodon devs are reluctant to even discuss giving up Microsoft [3].
#NotOnGitHub: Tell us about your favourite #OpenSource / #FreeSoftware projects that are not available on mainstream platforms, whether on a self-hosted cgit or available as an archive download only.
Over the long term, proprietary services, like proprietary software, doesn't exist. There is no such thing as a durable proprietary community, and we can do better than consigning ourselves to the tides of rentier-nomadism.
OSS devs, please hear me: your installer is your product. It is the first, and an exactly correct, impression you give people of how much you care about, how much you've invested in, the human experience of working with your software, and with you.
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
NLnet awarded a grant to Forgejo to develop its release process and additional features, starting June 2023. User blocking was implemented to protect repositories you own from unwanted interactions, an essential self-service moderation tool. An extended installation section was added to the documentation as well as a user and admin documentation for Forgejo Actions.
Not blockchain based, but it uses a mechanism where it becomes increasingly more expensive to do automated actions. It is called PoW, as it works similarly.
But the intricate details are best eplained by the developer.
I dunno current status, but #mCaptcha is being considered for inclusion in #Forgejo and #Gitea and will then also be available in #Codeberg as the #captcha solution.
"In 2020, the community discovered that GitHub has a for-profit software services contract with the USA Immigration and Customs Enforcement (ICE). Activists, including some GitHub employees, have been calling on GitHub for two years to cancel that contract. GitHub's primary reply has been that their parent company, Microsoft, has sold Microsoft Word for years to ICE without any public complaints"
➥ @conservancy
@jbzfn This is exactly why #Forgejo is working on federation. So no matter what codeforge you choose, as long as it can speak Forgefed (a domain-specific ActivityPub extension!), you can send and accept PRs, file issues, etc.
Some repos accept email submissions. (Now that I know about them, git bundles are great for this.) If more repositories opened up to it, that could be a great step away from requiring GitHub for everyone and everything.
#gitea / #forgejo can store your containers. You should be able to use #codeberg if you don't want to host your own got server. Below are some examples
Update from Lemmy after the Reddit blackout (join-lemmy.org)