While I appreciate the sentiment and the generousity of Voltra, I think the attitude can lead to some problematic thinking.
"Free" as in Free Beer can be just as important for FLOSS than the "free as in free speech" is. "Faircode" was a license that attempted to set a line for annual revenue of an organisation, after which a fee was mandatory. Didn't end well.
Calling for donations, advocating for paid bounties and calling for contributions* is all very fair. Just keep in mind that "free" should stay "free".
^(* At that point, you might want to rethink the "MIT all the things"-approach)
I use git for everything. The odd one or two times I've had to collab with someone who doesn't even understand vcs I just clone the reop for them, put them on their own branch and ask them to commit everything and push when they're ready.
Projects like ungit are pretty cool for those people but you'll want to get used to the cli.
Can't wait for windows to get the 2.* branch to get a simple push-deploy going on.
Whatever vcs you like you should make sure its decentralized. Far superior model.
So glad to hear that you are going to try it out -- please make sure you let us know how you like it! The visualization of it all is a great characteristic of Ungit. If you have any suggestions, or changes you think can be made, be sure to contact: https://github.com/FredrikNoren/ungit. It's open-source, so if you want to jump in and contribute, that would be amazing.
No problem :) It's just what I've landed on over the years, but there has been (and still are) other apps, both on and off the Play Store, that are useful. Then when I see a comment like this, or feel disappointed in any of the tools, I'll go searching again. With that, over the last few days I've found ungit, which seems to work fine through UserLAnd on Android 8 and 10 without root. Runs a server with a simple webpage that handles at least the most basic Git client needs (as far as I can tell) and then the webpage is accessed in the native browser. I'm guessing this is similar to how code-server above works, but I haven't tried that with UserLAnd again yet.
The only one I recommend is ungit and that's mainly for people not familiar with git who are joining a project. Make them use regular git commands but have them watch the ungit visualization until they wrap their head around branching and merging.
I use the command line -- I find that it's more straightforward that way + that it's just generally easier to use.
However, whenever I get completely confused/completely screw up, I use a program called Ungit, which is the only visual/non-terminal git program I can tolerate. Unlike nearly every single other program out there, ungit will deliberately show me the underlying data structure (acyclic graph) that git uses instead of trying to hide things away.
It basically strips away features + exposes the skeletons + the underlying concept, and so makes it easier to debug.
However, I do find that it's a bit laggy + some features are slightly unintuitive, so it's not really worth having it open all the time -- I default to using the terminal.
I haven't tried it myself (I learned git through the command line, which probably wasn't ideal), but a friend of mine finds ungit quite helpful. It has a pretty nice visualisation of the commit graph, so you can get a good mental model of what's going on.
When I started using git this tool was invaluable. I still use it for the easier tasks where I want to quickly check diffs or look at my commit history, and use command line git for the more complex tasks.
Yeah, I'm still confused out of my mind. This is supposed to mean something to me? It's a bunch of weird folders and strange files.
How does this have anything to do with creating a repository of Visual Studio projects?