Mastodon: @[email protected]
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.
I believe you can replace start
with the command that is suitable for your system (e.g., xdg-open
for linux).
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”.
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.