It’s actually quite worrisome, many projects exclusively have their troubleshooting or support on Discord now what’s going to happen years down the road when all those Discord servers have closed or no longer active and the invite links expire this is going to be a vast knowledge base that’s just lost to the world
No, there was MSN in the 70s but communication was made through a machine called Microtron. They are largely lost to the world due to being made from degradable PCB plates.
Another way to think about this is that those projects that have a more structured approach to documentation have a better chance at lasting longer, attracting more contributors, and making more lasting impacts
If it’s open source and the license allows it, I wouldn’t consider that stealing. If a fork gets more popular than the original, then it either addresses a major missing feature of the original or is simply more active. If this displeases the original dev, they can hopefully work it out with the maintainers of the fork. This is a feature of FOSS, not a bug.
The problem is the fact that the documentation exists solely as a series of what are effectively chat messages, not what platform those chat messages are hosted on. Markdown files or bust.
Yep, Debian was (is) a disaster to configure graphics with modern hardware. It was pure open source (even blocked firefox as the logo was copyright protected). They opened up with a non-free repo for hardware support, but already lost the ‘market share’ on the desktop to Ubuntu (and the load of forks with just a different windoemanager as default… instead of adding a desktop selection on install). Also Ubuntu is offered a lot as option on new hardware.
With snap I’m guessing users migrate back… (a very few at least)
Honestly Debian was one of the few that still kept a strong stance on freedom. Its sad that they went the opposite direction. I wish that they would of just broke the non-free into firmware and apps like they have now and then provided two isos. They could have a simple paragraph explaining free software with two links.
Hahaha ended up with different “Chromium” is that the joke? :D I don’t know if the collective understood but boy can I relate to searching the repo and getting way different stuff than I started looking for! XD
There are so many tools to make documentation for your project. LATEX is a great one, and you can use it to easily host your documentation online. And it’s really not difficult at all to do by hand. If you can have it on discord you can certainly have it in a repo.
Maybe it’s a cynical ploy to increase community engagement with their project by getting them into the discord. Regardless, it gives me The Ick. Very gross.
I personally don’t like LaTeX for documentation because it doesn’t benefit much from advanced features of LaTeX, while being more difficult to read/write than Markdown.
Discord is great for building a community because it’s the defacto chat service for communities. It replaced IRC and does that quite well. Having a place to casually chat with people more invested in the project has its advantages.
Now I really dislike it if they think discord can replace a wiki. Iirc discord added a wiki-like feature a while ago and it’s terrible because it’s not indexable by search engines.
I think you give Discord too much credit even with that. They’re closed source and have very little openness with their data. We have no clue how they store and archive our data and conversations, or what they do with it. I don’t think the open source community should trust Discord an inch.
I’m really hoping an open source alternative starts gaining traction.
A agree with everything you just wrote. Discord is the platform of choice for many projects because most people are already there, so it increases engagement (and often enough some people actually ask for an official discord).
I personally prefer projects to use matrix, despite all it’s faults. Some already do.
LaTeX is great, but I prefer Markdown for software documentation (bonus points if your flavor of markdown supports LaTeX-style math). Standard LaTeX is geared towards typesetting and formatting, which is great for reports and journals, but not so much for software documentation, so you end up with a lot of boilerplate. Markdown syntax is also more accessible to beginners, I feel. And if you have a really big project that requires features like cross-references, there’s things like myst markdown.
Both are powerful tools, though with different strengths as you describe. I was thinking more with automation in mind. But regardless, anything is better than a discord server. Even .txt documentation!
It’s not really about the tools, we have plenty of tools, plain text, markdown, latex, web pages. Putting content to readable format is the easy part.
The hard part is knowing what to put down and how to organize it, and making sure that your documented explanations are actually understandable.
Particularly when you want to get traction going you might really want conversations to help you understand where the project needs fixing versus how documentation needs fixing and get a sense for what documentation might be helpful.
best I can do is please react to the #roles channel with a ❤️ to unlock the channel. what’s that? you’re looking for a fix to an issue you’re having in an older and supported version of the app? well sucks for you and suck my d*** we’ve already deleted that channel a long time ago who needs that old info anyway
I think we fixed that for someone a few months ago, maybe you can scroll back and find it. I think the guys handle was user-something, might have been around May…
linuxmemes
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.