I would like to introduce you lovely OpenSource Lovers to a GIT-Alternative called FOSSIL that I also stumbled upon because of this Blog.<br> It’s basically opensource Github-in-a-box which means it’s an SCM with:
- Bug-tracker
- Ticketting-system
- Forum
- Wiki-system
- even a Chat-functionality
- Has built-in GUI
- Also has a Web-Server
- Self-Hostable like Gitea/Forgejo
& the best part it’s all in ONE STANDALONE FILE!!! which is extremely lightweight which you can copy to your $PATH & works even in crappy internet. how cool is that!!
However this tool supports a completely different style of development in FOSS called the “Cathedral-Style” whereas GIT suports a “Bazaar-Style”<br> The person behind Fossil is the creator of SQLite, <u>Dr.Richard Hipp</u> & they even made other projects to support Fossil like a PIC-Like language called PikChr<br> Well just in case; here’s a list of difference between Git vs Fossil<br> & guess what!! they even have a hosting service called CHISEL
Listen; Just check it out & use it for fun in your spare time even with the flaws it has (& Try out Darcs & Pijul as well)
Darcs does not require a central server, and works perfectly in offline mode.
Git can be used that way too. Am I missing something?
No, you are not. People regularly equate Git and GitHub, though.
no, this is exactly what git does
So GIT has a ticketting system, a Wiki, Bug-tracker built-into it along with a Version-tracker
It also has a Sync All command (I’m sure Git also has it Somewhere) ??
Why should git have a mediocre ticketing system instead of getting out of the way of dedicated ticketing systems?
Small personal projects just need a text file with a Todo list, large organisations might need something super heavy weight like Jira. If your VCS has a ticketing system it’s going to be dead weight for a large chunk of users, because there’s no one-size fits all solution.
Why shouldn’t git have one ? Why not avoid the bloat & Fossil was specifically made for get this small-medium size teams which can be scaled to bigger ones
I don’t think you understand what the word bloat means.
git add todo.mdNow do that without the markdown file
Darcs came out in 2003—Git in 2005. It was novel at the time compared to the alternatives. Darcs started as alternative to CSV & Subversion, not Git. Unlike Git it works on patches, not snapshots which has advantanges in merge conflicts.
Git uses
mergetools, which do whatever you make them to. Patches can be created from snapshots, but snapshots are not guaranteed to be creatable from patches - you might not have original state.EDIT: it uses merge drivers.
Patch Theory operates under the premise that patches commute & order should not matter until there is a conflict. Git will throw fits if you pull in a patch at the wrong order giving you a different snapshot.
Specific merge tool can throw fits. Git doesn’t care about specifics of how merge operation is done, it just tells to merge driver to merge three files(A, B and common ancestor) and stops if driver reports an error.
Also to correct myself: merge driver, not mergetool.
Am I missing something?
No and, in fact, this was (and still is) a selling point of Git over the alternatives (e.g. Subversion) available at the time that required you to “check out” some code and no one else could check out/modify that code while you had it checked out.
dont forget about jujutsu
Since jujutsu is Git-compatible it has very much replaced Git for me and is what I’m using for everything now. Its workflow is so good and miles ahead of Git.
I was trying out Pijul for a while before that and while it has a lot of great ideas and has a lot of potential due to the way its foundations work its interface is way too janky right now and missing features and nothing I’ve reported or the many changes I’ve submitted have been fixed/pulled since March. I’d really like it to be good but alas…
I ‘forgot’ it on purpose.
The compatibility with Git means it is ultimately shackled to the design decisions fundamental to Git which require hacky workarounds. The maker of Pijul has pointed out some of the fundamental ways it can never handle patches is the manner of Darcs/Pijul, but I am not in the position to pull some of these quotes.
I would rather see revolution over evolution, & the weird ties to Google & hosting the project Microsoft GitHub rub me wrong.
but they are working on their own vcs. I think git compatibility is not much more than a convenience in the long term.
Oh Yeah I like Pijul as well & I fully agree with your point of breaking the Git Hedgemony
BTW, tell me more about Darcs I want to know EDIT: Boy GIT-Fanboys are clearly mad about other VCSs existing😅
Darcs is sort of like Pijul before Pijul. It is a little slower, but might not even affect you at your project size, but what it has instead is a longer history with more tooling & support—on the CLI, support from package managers, forge options. It ends up being my preferred option just for this reason even if Pijul has better performance, handles binary files, & the identity server is novel.
Is there any good videos on Darcs that I can watch ?
Probably the most notable modern video https://www.youtube.com/watch?v=2XQz-x6wAWk
Thanks
Spent 5 minutes on the website and couldn’t get a peek at their code… The most fundamental thing, IMO.
fossil is made by the sqlite devs, for development of sqlite. this is not some amateur operation.
also, it’s by the sqlite people, so expect the code to be… odd.
& The code behind Linux isn’t ? People back then did some REAL sorcery with coding
back then? both codebases are fully modern. its more that sqlite uses a style that differs from the accepted norm quite a bit. that, and they don’t accept contributions.
Yeah it’s the cathedral-style, Opensource but closed contributions as in no PRs
Which is not really open now is it.
I would say its still open source. There is no requirement to be able to contribute modifications back. It is more about the availability of the code and what you can do with it.
PRs didn’t exist when open source was conceived.
You’ll actually have to talk to the devs to be included in the project This VCS favours a more horizontal organization where the devs know each other (so A <u>high-trust environment</u>)
Please don’t pretend as if OpenSource Devs don’t constantly complain about pesky PRs😅
Please don’t pretend as if OpenSource Devs don’t constantly complain about pesky PRs😅
<i>I</i>'ve <u>seen</u> much <b><u>more</u> complaints</b> about <a href=“https://0.0.0.0/random_img.tiff”>people</a> constantly <marquee>demanding</marquee> their specific <h1>annoyances</h1> to be fixed without ever <i>submitting <u>a single <b>line of code</b></u></i>. <i>Maintainers</i> are pretty much <b>universally</b> welcoming to code <h2>contributions</h2> <br><br><br><br><br><br>
I soooo hope this does something funky with someone’s Lemmy client
it’s not the most intuitive interface but there you go: https://fossil-scm.org/home/tree?name=src
Wow C, CSS and JS files at the same level. You don’t see this every day
There are tabs above like a browser
It’s in the code tab: https://fossil-scm.org/home/dir?ci=trunk
Look at the bottom
Learned fossil in college and I intensely disliked it
Why ? As in the intense dislike ?
Didn’t like mixing issue tracking with vcs. I also didn’t like any VCS hahaha, I was just writing shit in literally notepad
Oh ‽ well that I can relate to
This thread might be the fastest I’ve ever seen discussion devolve from “that could be interesting” to just incomprehensible screaming.
Yeah wtf it’s like there’s like a wolverine loose in the comments section
These people don’t even bother checking out the site & some can’t be bothered to scroll to the bottom of the site & can’t even read
They only recently were made aware of this tool & within a few seconds they literally go “Muh Bloated” etc…
It’s no wonder
This seems really cool!! And I love to see alternatives to git. But @MITM0@lemmy.world, you need to cool it on the replies. You’re making the Fossil community look hostile by association.
I’m not a part of the fossil community, also when none of the people here bother to properly check out the website & call it Ancient or see the why behind the tool & it’s development philosphy Yeah that pisses me off (So yeah I’ll “cool it” but it makes the GIT-community look like hostile hive)
Why don’t you tell me some more about what you like about Fossil… I’m assuming you’ve used other version control systems - how would you compare the feeling of actually using it in a collaborative workflow? How did you even come across Fossil in the first place?
This is my first time hearing about it, so would love to hear more straight from an actual user.
I imagine the creator envisioned something like a package wiki/docs mixed with direct access to the source code.
It can be carried around in your pocket & has the features of Github but open source Wiki, bug-tracker, ticketting, Forumn & even a chat for devs to use You can self-host it & it even runs on the most crappy internet Best part, it can track what you did in the past & stores in SQLite DB & can import & export to Git
Also I came across it via this blog
I like it even with the obvious flaws it has, plus it can be improved anyways
I really like the idea of using a relation db to track change history. It removes so much weirdness and quirkiness that git has. You just have regular SQL queries you can use to go through history and ask questions about the state of the repo. I also like that it’s immutable so you don’t have to worry about things like rebasing and other ways you can fuck up history in git. The problems solved by mucking with history largely go away when you can query the db with a rich syntax.
Same, really love the idea of backing history with a proper database, and the immutability. git rebasing was a mistake.
Rebasing is for advanced git users who knows what he’s doing. If one does not know how to use it or not feeling comfortable in general, he can happily take his own code and try to merge it into the latest version instead. No one is judging.
For the rest of the world where projects are open-source, more often than not, not those projects inside a corporation where only the team lead is making decisions, it’s a powerful tool to settle down conflicts sort out history.
One does not need to change the history again, if he’s not comfortable with it. Just use git as if it’s centralised VCS like SVN. No big deal. In fact, in corporations you do. There only needs to be one person who manages the repository.
I get why it exists, but yeah it’s more trouble than it’s worth in most cases.
How do you cleanly base your local changes against a new upstream version? Merges?
You merge from them. If you’re working on a PR, they can always squash merge your commits if you have a lot of them. No history rewriting required.
Tho we also got mercurial right?
I love Fossil and use it for all my personal projects! I use syncthing to keep my all my repositories updated across devices and it works great!
I do wish I better understood either self-hosting or that there were more web hosts though, it would make collaboration easier when I feel like sharing. A git(hub) bridge could do it too I guess…
Seems pretty cool! I have to try it out. Thanks for sharing.
