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)

  • nimpnin@sopuli.xyz
    1·
    18 days ago

    Darcs does not require a central server, and works perfectly in offline mode.

    Git can be used that way too. Am I missing something?

    • toastal@lemmy.ml
      1·
      18 days ago

      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.

      • uis@lemm.ee
        0·
        16 days ago

        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.

        • toastal@lemmy.ml
          1·
          16 days ago

          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.

      • ZeroOne@lemmy.worldOP
        0·
        17 days ago

        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) ??

        • jmcs@discuss.tchncs.de
          1·
          18 days ago

          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.