SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have no other issues with a centralized Slackware-led documentation project except that I am uncomfortable to play any role in it. Purely a personal thing with me.
I have no other issues with a centralized Slackware-led documentation project except that I am uncomfortable to play any role in it. Purely a personal thing with me.
Well, it will be our loss if you leave the project. I think you did a pretty good job on the Slackware philosophy page.
I think the "copy the Slackbook" effort was started for (at least) two reasons:
1 - it would provide a bunch of Slackware content quickly
2 - (and more importantly, at least in my eyes) it would allow the Slackbook to be updated quickly
That being said, I don't personally feel that it really fits into a wiki setup in direct book form. I do, however, still support the idea. It would be easy enough to get the information in there, community edited and up-to-date, and brought together in it's own page or series (just like how Wikipedia can do 'Series,' these articles could have a 'This article is part of a series called Slackbook.' Or it could be a portal. Didier's ideas could also be portals...) If broken down into subsections, those articles could fit nicely into the wiki scheme while also being linked via a Slackbook series/portal/wiki-generated-ToC (using slackbook tag?)
As for the actual text, it seems inevitable that much of it will be revised and rewritten over time. I wouldn't sweat it, just like I won't sweat it when anything I write gets heavily edited. I just hope I'm not make more work for someone!
I think the "copy the Slackbook" effort was started for (at least) two reasons:
1 - it would provide a bunch of Slackware content quickly
2 - (and more importantly, at least in my eyes) it would allow the Slackbook to be updated quickly
I follow rinias on this idea. The Slackbook is a great project, but it's currently in a coma in some virtual no-man's-land. Placing it onto the wiki - all licence considerations taken, of course - would quickly revive it and significantly accelerate its completion. L'Union fait la force, as we say here. (But here in the South we also say "Ne remets pas à demain ce que tu peux faire après-demain", which is another story...)
Rather I am perfectly ready to participate in community projects where no single person takes the decisions.
I think, a Wiki should be a community project. There is far too much background thinking behind this. I see too many efforts to structurize and control this effort which will only stifle the contribution in the long run.
I agree that there seems to be too much background thinking behind this but that's exactly my point. We can't seem to be able to agree on one line of action. Lots of people are willing and eager to contribute, which is great but it brings some problems with it. There will always be someone who is not completely satisfied with the shape of things. I have my own idea of how *I* would organise it (my sketch of TOC) but I am more than happy to give it up as long as we agree on something.
If SlackBook has to be ported to wiki, it has to be edited to change references to chapter numbers or sections to appropriate internal links. Also the markup may need some tuning. It is more than just copy/paste work.
Definitely. Still, it would give rather rough drafts which could be expanded upon, which isn't such a bad thing.
Quote:
I still think it's somewhat of a duplication of effort. Best to leave it to the choice of the contributors and the original authors.
I don't know if it's duplication of effort. That would imply that it is currently being worked on by at least two people. As much as we are grateful to Alan, I haven't been seeing any *cough* chew his ass out *cough* recently, so that might imply that there is a grand total of 0 people working on it. Unless we port it into the wiki.
Quote:
Problem with Dokuwiki is that it's not as advanced as Mediawiki in terms of categorization features. Probably needs a plugin.
Here I defer entirely to you, as I understand you installed it on your server to play with it.
The Slackbook may or may not be brought to the wiki, depending on the mood of the community. Personally, I won't see it as a big loss or big gain either way, as long as people find Slackdocs easy and informative. Once a typical response on the forum is "Check out the Slackdocs page," I think we'll be successful. Until then, I think it's best that we - especially forum trollers like myself - set ourselves about creating content instead of answering the same old questions.
Last edited by rinias; 08-22-2012 at 09:33 AM.
Reason: Tag oops
We're progressing on the new slackbook and have finally settled on a license, the Creative Commons Attribution Share and Share-Alike license. You can find a copy of it in the COPYING file once you've pulled our latest git tree. Additionally, the beta has been updated. Feel free to browse it and send in any patches.
In order to tide you over a little bit and to solicit feedback on improvements from the community, I've posted a beta online here. Please send all comments, criticisms, suggestions, fixes, additions, and the like to me via e-mail. The book currently does not have an official license, but will likely be CC Non-commercial (with a commercial exception for Slackware Inc. of course).
If you want to take a look at the Docbook source code and send in some patches, you can grab the latest version from git with:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.