forgefed
killed-by-microsoft
forgefed | killed-by-microsoft | |
---|---|---|
20 | 42 | |
983 | 165 | |
0.2% | - | |
5.5 | 5.6 | |
7 days ago | 18 days ago | |
Bikeshed | JavaScript | |
Creative Commons Zero v1.0 Universal | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
forgefed
- Gitlab's ActivityPub architecture blueprint
- PyPy has moved to Git, GitHub
-
Harness launches Gitness, an open-source GitHub competitor
If you don't mind me asking since you're here: will you be implementing ForgeFed in Gitness [0]? My sense is that federation is our best hope for breaking GitHub's network effects, and I'd love to see more projects like yours join the protocol.
[0] https://forgefed.org/
- ForgeFed
-
Gitlab's plan to support ActivityPub for merge requests
From the comments, Forgejo is also already working on implementing ForgeFed, an ActivityPub extension specifically designed for software forges [0]. Judging from the issue, it looks like they're well on their way [1].
I have to say, I'm not super into the idea of social media, but this is a use for federation I approve of wholeheartedly. The friction of having to create accounts on X forges (where X is the number of projects that self-host GitLab) is a huge moat for GitHub, and federation could solve that very handily and create an environment where FOSS projects can feasibly host their own code away from Microsoft's control without horribly inconveniencing everyone who wants to participate.
[0] https://forgefed.org/
[1] https://codeberg.org/forgejo/forgejo/issues/59
-
git-appraise – Distributed Code Review for Git
> I agree that e-mail is not perfect, but... how is GitHub better?
Please look at my comment again. I prefer email to locked in forges.
> Devs like new shiny toys, and e-mails are old technology
There is one aspect where such forges have an advantage over email - a better user experience. Aerc and the likes all good - but Github and others provide a good user experience over a tool that everyone uses - the web browser.
> we should have something better than e-mail in 2023
We really should have something better than email. I'm saying this as someone who operates a personal mail server and a bunch of desktop services for it. It's really hard to get the setup correct.
In that context, it's worth looking at forgefed (https://forgefed.org/). It's a protocol for federating forges like Gitea and Gitlab. It's built on top of ActivityPub - which behaves a bit like email (it has inboxes and outboxes for every user). From the spec, it seems like pull requests happen by sending patches to the destination forge.
> Nobody takes the time to try the e-mail workflow (even though it's really two git commands)
Email workflow seems simple. But there are two things that make it complicated:
1. The patches don't specify the commits they apply to. It's simply assumed that they apply to the head of the main branch. The commits have to be carefully rebased on the main branch before sending the patches. It could otherwise lead to conflicts and a lot of wasted time.
2. Each commit/patch is send as a single email. Developers usually make frequent commits when they develop. Such patches can be confusing and hellish to review. A sane patchset requires the developers to edit the commit history, usually using interactive rebases. Each commit should contain a single feature and shouldn't break the build.
I consider both the above to be good development practices and follow them even on my personal projects. However, this is an additional barrier to entry. In fact, this may be a bigger problem for many than setting up git for email.
-
Leveling Up Your Git Server: Sharing Repos with a Friend
Another interesting topic to look into is forge federation. Forgejo [0], the code forge on which Codeberg is based is one forge software that intends to federate their repositories between server instances over the network using ActivityPub protocol extensions such as ForgeFed [1] and F3 [2] specifications.
[0] https://forgejo.org
[1] https://forgefed.org
[2] https://lab.forgefriends.org/friendlyforgeformat
- Sono Moreno di Morrolinux. AMA!
-
Let's Make Sure Github Doesn't Become the only Option
> If you want to look into people who disagree with you: https://forgefed.org/
killed-by-microsoft
-
Microsoft is ending support for the Windows Subsystem for Android (WSA)
> P.S. Do we make "jokes" about Microsoft killing things off like we do with Google?
Well someone went ahead and made https://killedbymicrosoft.info/
-
Microsoft Announces the End of Windows Mixed Reality
There is https://killedbymicrosoft.info/, though it seems to be missing a lot of older examples like MSN Explorer. They also don't seem to include product renames like the Google one does.
- Killed by Microsoft
-
Stability of the Neovim ecosystem
You might want to check https://killedbymicrosoft.info/
- Microsoft explored buying Sega, Bungie, Niantic, and IO Interactive, wanted to "spend Sony out of business" | Zynga and Supergiant Games were also targets
-
Google Domains shutting down, assets sold to Squarespace
Without a source mentioned, I assume you refer to this[1]?
A comparison shows most products that should be dead are on that list.
G, on the other hand, has products actively used and loved by users.
[1] https://killedbymicrosoft.info/
-
Microsoft aiming to challenge Apple Silicon with custom ARM chips
Inb4 new entry in killedbymicrosoft.info. /s
-
BREAKING: Microsoft’s $69 Billion Activision Deal Blocked by UK Watchdog
Saved by Microsoft, like Nokia, Skype, Rare etc.pp.
-
Google CEO Sundar Pichai Received $226M Compensation While Firing Thousands
> They have a tendency to simply discard products left and right.
I guess this site could be of interest to some, to have a look at some of the products: https://killedby.tech/
Google has a separate site here as well: https://killedbygoogle.com/
Microsoft also has a site like that: https://killedbymicrosoft.info/
I tried looking up one for Amazon or AWS projects, but only unrelated news articles came up.
I don't really have a horse in the race, though, since all three of the big platforms (and others like Oracle Cloud) are outside of my price point and all my personal projects run on smaller simple VPS providers. From what I can tell, there is not a single large corporation out there with the commitment to never kill a product of theirs and support everything in perpetuity.
-
Google wants you to uninstall Meet so you can use Meet
Someone made https://killedbymicrosoft.info/
What are some alternatives?
kyoto - Golang SSR-first Frontend Library
Killed by Google - Part guillotine, part graveyard for Google's doomed apps, services, and hardware.
gitness - Gitness is an Open Source developer platform with Source Control management, Continuous Integration and Continuous Delivery.
ccls - C/C++/ObjC language server supporting cross references, hierarchies, completion and semantic highlighting
cicada - A FOSS, cross-platform version of GitHub Actions and Gitlab CI
git-appraise - Distributed code review system for Git repos
Windows10Debloater - Script to remove Windows 10 bloatware.
gitlab
redux-undo - :recycle: higher order reducer to add undo/redo functionality to redux state containers
linux - Linux kernel source tree
Mind-Expanding-Books - :books: Find your next book to read!