One such project is the Gitless initiative which has a Python wrapper around Git proper providing far-simpler workflows based on some solid research. Unfortunately it doesn't look like Gitless' Python codebase has had active development recently, which doesn't inspire much confidence. - Source: dev.to / about 2 years ago

You and me both. Git's interface has been very hard for me to understand (especially coming from Mercurial). I ended up finding Gitless (https://gitless.com), a wrapper around Git with a better interface, and loving it. - Source: Hacker News / almost 2 years ago

> > To differentiate from Git Pijul should focus on usability... If Pijul has an easy to use interface like Mercurial did then that will massively help adoption. > I don't think the goal or differentiation of pijul is to be popular via good UI, though. If the theory of patches is good, it doesn't matter if pijul "wins" or not, as long as whatever does can integrate it. If the theory of patches is bad, I... - Source: Hacker News / over 2 years ago

I'd like to think it was my project (https://github.com/martinvonz/jj), but other possibilities include Gitless (https://gitless.com/) or Bazaar (https://bazaar.canonical.com/). - Source: Hacker News / over 2 years ago

Gitless [1] has already been mentioned in another comment here. [2] That makes it easier to use hit for those who are not as experienced or haven’t learned about the internals of git. For a different model (and other types of workflows), consider Fossil SCM. [3] Here’s a comparison of fossil with git, and what these tools are a good fit for. [4] I found fossil easier to understand, relatively speaking, and it... - Source: Hacker News / over 2 years ago

Feedback to author: The diagram and explanation took a beat longer than normal to scan, since this buries a bit that it's not about the beautiful source control system called fossil shipped as a composition of modules: https://fossil-scm.org/home/doc/trunk/www/index.wiki Great diagrams, so of course that's the first thing a reader will skim. People biuld things based on git all the time, the diagram looks like... - Source: Hacker News / 5 months ago

There are (all too rare) tools that back those objects with git as well. And there's always fossil ... https://fossil-scm.org/home/doc/trunk/www/index.wiki But it's not git. :-(. - Source: Hacker News / 8 months ago

I don't think git should be the infrastructure of collaboration. It's good for long-lived artifacts, but isn't good for discussion, for rights management, ... Fossil (https://fossil-scm.org/home/doc/trunk/www/index.wiki) is of course better, but if git must remain, I believe the base infrastructure should be the mailing list. Patches, branches and releases can live inside a mailing list, it is naturally built for... - Source: Hacker News / 9 months ago

Have you spent much time using Fossil? https://fossil-scm.org/home/doc/trunk/www/index.wiki. - Source: Hacker News / 11 months ago

> To make things more complicated, they also use their a relatively niche version management system instead of git. Which would complicate making contributions (if they accepted them). The Fossil VCS actually has a page explaining why it was created, instead of just using Git: https://sqlite.org/whynotgit.html Honestly, a lot of those points make sense, especially how Git is perhaps a little bit more complex and... - Source: Hacker News / about 1 year ago