Aslak Raanes#Fossil er distribuert forum, wiki, saksbehandler o.l. på toppen av #SQLite.
Nesten som en atproto-app som Eurosky-folka pusher 😜
Eks på oppsett for å kjøre greia på domeneshop:
Richard Holloway@henrik in my (not very significant) opinion; the only reason to use Git is the network effect - everyone already uses it. Fossil has a huge benefit with storing everything along with the application code, means that each commit is *complete* and in one place.
With the prevalence of Git, that competition space is dead. I have not managed to get any other Dev to even take a look at #fossilscm. Nearly every Dev I have worked with has never used or is even aware of any VCS other than Git.
With the prevalence of Git, that competition space is dead. I have not managed to get any other Dev to even take a look at #fossilscm. Nearly every Dev I have worked with has never used or is even aware of any VCS other than Git.
Colin MacleodFossil https://fossil-scm.org is forum, chat, bug tracker, wiki. And a distributed version control.
Robin Palotai
hardtech.fts
LFA 🇮🇨Oh man how cool Fossil is! I updated the Goophy devlog entry on my gopher hole and with just one command: ' fossil commit -m "Update Goophy Devlog" ', it commited the changes and synced them with my remote fossil server.
WuMing2@krille perhaps switching to platforms as the all-in-one #FossilSCM - easily self hosted on lowest tier vps - or #Codeberg would assuage who is annoyed at GitHub’s #softwareBloat. And boost participation.
offray@krisajenkins regarding the "Solving Git's Pain Points with Jujutsu" episode, for a little bit of a counter example about a "universal" technology I have been able to develop software mostly ignorant of #Git and use #FossilSCM instead. I'm an odd case, but a good example of how other tech stacks can reach non developers and being more aproachable by a general public.
Maybe you could consider Richard Hipp from #sqlite / #fossil fame?
As usual, excellent epidode:
Solving Git's Pain Points with Jujutsu (with Martin von Zweigbergk) by @Kris Jenkins
Git might be the most ubiquitous tool in software development, but that doesn't mean it's perfect. What if we could keep Git compatibility while fixing its most frustrating aspects—painful merges, scary rebases, being stuck in conflict states, and the confusing staging area? This week we're joined by Martin von Zweigbergk, creator of Jujutsu (JJ), a Git-compatible version control system that takes a fundamentally different approach. Starting from a simple idea—automatically snapshotting your working copy—Martin has built a tool that reimagines how we interact with version control. We explore the clever algebra behind Jujutsu's conflict handling that lets you store conflicts as commits and move freely through your repository even when things are broken. We discuss why there's no staging area, how the operation log gives you powerful undo/redo capabilities, and why rebasing becomes trivially easy when you can edit any commit in your history and have changes automatically propagate forward. Whether you're a Git power user frustrated by interactive rebases, someone who's lost work to a botched merge, or just curious about how version control could work differently, this conversation offers fresh perspectives on a tool we all take for granted. And if you're working with large monorepos or game development assets, Martin's vision for the future of Jujutsu might be exactly what you've been waiting for. --- Support Developer Voices on Patreon: https://patreon.com/DeveloperVoices Support Developer Voices on YouTube: https://www.youtube.com/@DeveloperVoices/join Jujutsu (JJ): https://github.com/martinvonz/jj Jujutsu Documentation: https://martinvonz.github.io/jj/ Git: https://git-scm.com/ Mercurial: https://www.mercurial-scm.org/ Rust: https://www.rust-lang.org/ Watchman: https://facebook.github.io/watchman/ Google Piper: https://research.google/pubs/why-google-stores-billions-of-lines-of-code-in-a-single-repository/ Kris on Bluesky: https://bsky.app/profile/krisajenkins.bsky.social Kris on Mastodon: http://mastodon.social/@krisajenkins Kris on LinkedIn: https://www.linkedin.com/in/krisjenkins/
🧊 freezr 🥶Hi guys, I know this risk to become the dumbest question ever made on the #fediverse but I must ask it not matter what…
For all the experts and non-experts… Is it possible, or would it possible, to have a plain text image format?
Something that can be diffable and you can track changes as for instance the #SVG format. It looks like all these control versions, like #git, aren't very suitable to handle format like #png, #jpg ,etc… They can only handle them as a binary blob and track if it has changed and re-upload or re-download fully.
Long-story short: handle the creation of catalog with #Fossil-scm hasn't been very good regarding managing the huge amount of pictures…