forgefed
git-appraise
forgefed | git-appraise | |
---|---|---|
20 | 10 | |
983 | 5,097 | |
0.2% | 0.1% | |
5.5 | 2.3 | |
9 days ago | 9 months ago | |
Bikeshed | Go | |
Creative Commons Zero v1.0 Universal | Apache License 2.0 |
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/
git-appraise
-
Gitlab's ActivityPub architecture blueprint
git-appraise[1] implements that concept. From Google, no less.
I've never used it, or seen it used in the wild, but it always seemed intriguing, and like the obvious approach. The web UI traction is far greater for this to have any serious usage, but I wonder if Git had that ability from the start, if the web UI concept would've taken off as it did.
[1]: https://github.com/google/git-appraise
- Git-appraise – Distributed Code Review for Git
-
git-appraise – Distributed Code Review for Git
I believe their docs cover the scenario of reviewing someone's code by pushing your review to the git repo, and others can use `git appraise list` to see open pull requests.
https://github.com/google/git-appraise/blob/master/docs/tuto...
A trivial git-hook could be setup for automating email notifications.
- Commit comments no longer appear in the pull request timeline
-
Show HN: OneDev – A Lightweight Gitlab Alternative
I know about Google’s gerrit. I now found https://github.com/google/git-appraise, there seems to be a plethora on the issue and pr tracking side.
Then the other day there was a generic/abstraction layer to write CI that abstracte over gitlab, circle ci, and GitHub actions (maybe more). I suppose all that’s left is to get some api tokens somewhere and go?
- Show HN: Crocodile Code Review
-
The Return of Fancy Tools
Experimenting with distributed issue trackers in git was popular in the early 2010s, there were a whole bunch of different implementations people came up with for git. Most of them died out though, there were typically a few problems - this is what I remember offhand from experimenting with a whole bunch of them:
* Some of them make a mess of some part of git; one of them put its info in separate git branches to ensure changes were always pushed/pulled even without a special push/pull command for the issue tracker.
* At least one of them kept their info in the repo in a dot-prefixed directory and auto added/committed the file as changes were made; this meant a single issue could be in different statuses depending on which branch you were on and there was no overarching view.
* The rest effectively ran in parallel to the git repo, pushing and pulling their data within it but requiring their own commands to do so, so it was totally possible to clone the repo and not get the issues.
* Most of them didn't have a non-repo way to track issues, for project managers and such. One did have a webview that ran from a repo, but it was up to you to figure out how to keep it in sync with the comments/etc devs were putting in their copies of the issue tracker.
Sibling mentions git-bug, a few others:
https://github.com/aaiyer/bugseverywhere (I think this is one of the original ones)
https://github.com/dspinellis/git-issue
https://github.com/neithernut/git-dit
https://github.com/google/git-appraise (I think this one is newest and I probably never tried it)
What are some alternatives?
kyoto - Golang SSR-first Frontend Library
fsv - fsv is a file system visualizer in cyberspace. It lays out files and directories in three dimensions, geometrically representing the file system hierarchy to allow visual overview and analysis.
gitness - Gitness is an Open Source developer platform with Source Control management, Continuous Integration and Continuous Delivery.
git-dit - Decentralized Issue Tracking for git
cicada - A FOSS, cross-platform version of GitHub Actions and Gitlab CI
onedev - Git Server with CI/CD, Kanban, and Packages. Seamless integration. Unparalleled experience.
killed-by-microsoft - Part guillotine, part graveyard for Microsoft's doomed apps, services, and hardware.
pull-request-stats - Github action to print relevant stats about Pull Request reviewers
gitlab
git-from-the-bottom-up - An introduction to the architecture and design of the Git content manager
linux - Linux kernel source tree
git-bug - Distributed, offline-first bug tracker embedded in git, with bridges