This problem is now solved for me. I didn’t do anything. Either a Firefox (current version 137.0.2 on mobile) or a Lemmy update (current version BE: 0.19.11) seems to have solved it.

I would stay away from YAML (almost at all costs).

For us to be able to help you, I think you need to give us some more details about the organization of your work. If each chapter is a separate text file, then you don’t really need to do any branching at all (assuming people will only make changes on their own files and not touch others’ work). If it is a single text file, branching (or anything else, to be honest) will not help much.

I assume chapters will have their separate files. As long as you can control who touches which file, everybody can work on the same branch (also referred to as “trunk based”). But if you fear that people may interfere with each other’s work (willingly or by accident), then it makes sense to create a branch per chapter to keep contributors at a distance from each other. But working on a single repository requires some sort of an agreement on the workflow.

Don’t they already have the names Leap and Tumbleweed? Changing the name to Leap would make sense since it’s the name of the “official LTS” version. At this point it sounds like “openSUSE” is the name of the project and not the distro. But I haven’t been following them closely, so perhaps I’m wrong.

Not sure but that sounds like you have a problem with your Git installation (or a dependency of Git). Maybe a reinstallation can solve that.

I understand the “why would I pay for this” reaction. I think crowdsourcing is a better approach for these kinds of content. Once you reach certain level of financial commitment from the crowd, you can give away the PDF and sell the print copy.

git branches are just homeomorphic endofunctors mapping submanifolds of a Hilbert space

Yeah, once you realize that everything falls into place.

The shape of that bottle is creepier than the text.

I believe you can replace start with the command that is suitable for your system (e.g., xdg-open for linux).

That’s an unnecessarily strong reaction. Money clearly matters for some things. But that’s not all that matters. There are many people releasing FOSS without any financial expectations. Clearly, money doesn’t matter to those people on that context. Trying to argue that “money should matter also for those people on that context” doesn’t make too much sense to me. Nobody is forcing anybody to release FOSS.

Sorry, I don’t follow your reasoning. Why would a company not making money be a relevant problem for the advocates of FOSS? FOSS is about freedom. It never had an opinion about money. Money has always been irrelevant. Some people may not like it, and they are free to not use non-free licenses. And FOSS advocates will warn users about that (as they did in the past). FOSS doesn’t have an obligation to offer a solution to every problem in the software industry.

I don’t think that is relevant from author’s (and OSI’s) point of view.

Here is my understanding of author’s position: Stay away from companies like Redis and ElasticSearch. They are building software with a proprietary mindset (the fact that they have tight control over product strategy and development demonstrates this) only to realize that they are being devoured by bigger fish. It’s a business model problem, not an open source problem.

Here is the link to the original website (an NGO that monitors blocked websites in Turkey): https://ifade.org.tr/engelliweb/distrowatch-erisime-engelledi/

And here is the Google translation of the text on that page:

The IP address of the DistroWatch platform, which provides news, reviews, rankings and general information about Linux distributions, was blocked by the National Cyber ​​Incident Response Center (USOM) on the grounds of “IP hosting/spreading malware”.

I think you are highlighting an important point that are missed by other commenters emphasizing the developer. I prefer GPL over MIT license. But this is a possible fallback if Redis decides to change its licensing (like several others did).

I think these kind of products have strategic significance for MS for their Azure offering. They are probably preparing to offer this there (in addition to and as an alternative to Redis). So, it makes sense for Microsoft to release this with an OSS license (otherwise no one will adopt it).

What checkout actually does. Here is a past comment with links to the courses (they are pay-walled, unfortunately)

I don’t think I read that one. I created a separate link-post for that one. Thanks.

Mine happened when I watched Paolo Perrota’s Git courses on Pluralsight. That’s when it clicked for me.

Who is this particular developer

As far as I understand from the discussions about the topic, Maxim Dounin was one of the few core developers of nginx. Looks like Wikipedia has already been updated.

The URL seems to have a typo. Correct URL is https://github.com/presslabs/gitfs