4 ms·
> The authors of the good manuals had written them for O'Reilly Associates, I see the bar is relatively... low. That being said, I expect the reason authors w
by musicale 6y ago
> The authors of the good manuals had written them for O'Reilly Associates,
I see the bar is relatively... low.
That being said, I expect the reason authors wrote for O'Reilly was so they could actually get paid.
> The obstacle is that many users think that a proprietary manual is good enough—so they don't see the need to write a free manual. They do not see that the free operating system has a gap that needs filling.
The biggest obstacle is probably either a) finding money to pay a good writer or b) finding a good writer who is happy to work without pay.
- PaulDavisThe1st 6y ago(c) finding a good writer able and willing to do the work under any conditions.
- cycloptic 6y agoI think you may have missed this part: >The problem with these manuals was not that O'Reilly Associates charged a price for printed copies—that in itself is fine.
- Uehreka 6y agoIf you’re saying people need to make their content available for free with an option to pay for a printed copy, then you’re telling them they can’t make money from their work, which is the thing at issue. And we can argue about whether authors of books about FOSS tools should embrace the same ethos as those tools’ developers, but it seems silly to hide the ball or act like there’s a win-win solution hiding in plain sight.
- lelandbatey 6y agoI think what's being pointed out is more just a problem, no concrete solution (like "make their content available for free with an option to pay for a printed copy") is being prescribed. But if we are talking about prescriptive solutions, what I'd want that does all this is a pay-to-access documentation Wiki, where I and other users of the software can make changes (or at least propose changes) to those docs that we read and rely on.
- cycloptic 6y agoI'm not saying that and the article doesn't say that either. If anything it says the opposite, but the real focus of is asking for documentation writers to publish their source files. (odt/doc files, latex/rst/md sources, etc...) My personal opinion is that open source projects should probably do this, when a project is taking patches to the source and contributors can't also contribute to the docs then the docs will lag behind.
- setr 6y agoThe problem listed in the article is specifically “freedom to copy, modify and redistribute”, not “free to have” O’Reilly would be fine, if they allowed you to modify the book as you please — but they don’t; like licensed software, you’ve only paid to access the content, but you don’t really own it. Basically every argument for FOSS is now being applied to the manual(s) as well
- warkdarrior 6y agoWe really need an AGPL3 for documentation. If you read that documentation and then provide (consulting) services based on that knowledge, you really need to feed the profits back to the documentation authors.
- duskwuff 6y agoWhat you're proposing amounts to "if you read this, you must give us money". That's way outside the scope of a license and is completely unenforceable. It's also a great way to convince consultants to avoid your software entirely.
- setr 6y agoThe documentation AGPL equivalent would simply be that if you provide a modified copy of the docs remotely (eg online), you must still provide the documentation source and all rights to modify & redistribute further. The AGPL just extends the GPL to apply in SaaS contexts — I don’t know how the documentation equivalent that would go anything close to modifying profit flow for consulting services
- musicale 6y ago> The problem listed in the article is specifically “freedom to copy, modify and redistribute”, not “free to have” If O'Reilly were to sell books on those terms, say in PDF+source form, what exactly would prevent "freedom to copy... and redistribute" from quickly turning into "free to have?"
- setr 6y ago