LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-22-2012, 02:50 AM   #196
vharishankar
Senior Member
 
Registered: Dec 2003
Distribution: Debian
Posts: 3,178
Blog Entries: 4

Rep: Reputation: 138Reputation: 138

deleted.

Last edited by vharishankar; 11-02-2012 at 12:36 PM.
 
Old 08-22-2012, 03:08 AM   #197
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453

Original Poster
Rep: Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154
Quote:
Originally Posted by vharishankar View Post
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.
It's more "Quality Assurance" than "centralized".
 
Old 08-22-2012, 04:33 AM   #198
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; Slackware64-current (VM); Debian 12 (VM)
Posts: 8,290
Blog Entries: 61

Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post
please excuse the syntactic and orthographic mistakes as English is not my native language.
Sorry, I didn't notice any.

Quote:
Originally Posted by vtel57 View Post
Don't apologize for your English, Didier. You communicate more proficiently in that language than many Americans I know.
And many English that I know. Me, for instance. And I'm monolingual. Je ne parle pas d'autres langues, seul l'anglais mauvaises. (Merci, Google)
 
Old 08-22-2012, 04:40 AM   #199
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; Slackware64-current (VM); Debian 12 (VM)
Posts: 8,290
Blog Entries: 61

Rep: Reputation: Disabled
Quote:
Originally Posted by vharishankar View Post
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.
 
Old 08-22-2012, 05:25 AM   #200
vharishankar
Senior Member
 
Registered: Dec 2003
Distribution: Debian
Posts: 3,178
Blog Entries: 4

Rep: Reputation: 138Reputation: 138
deleted.

Last edited by vharishankar; 11-02-2012 at 12:35 PM.
 
Old 08-22-2012, 07:11 AM   #201
rinias
Member
 
Registered: May 2009
Distribution: Slackware64-14.0
Posts: 58

Rep: Reputation: 18
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!
 
Old 08-22-2012, 08:14 AM   #202
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453

Original Poster
Rep: Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154
Quote:
Originally Posted by rinias View Post
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...)
 
Old 08-22-2012, 08:38 AM   #203
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,836
Blog Entries: 1

Rep: Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251
Quote:
Originally Posted by vharishankar View Post
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.
 
Old 08-22-2012, 08:39 AM   #204
vharishankar
Senior Member
 
Registered: Dec 2003
Distribution: Debian
Posts: 3,178
Blog Entries: 4

Rep: Reputation: 138Reputation: 138
deleted.

Last edited by vharishankar; 11-02-2012 at 12:35 PM.
 
Old 08-22-2012, 09:30 AM   #205
vharishankar
Senior Member
 
Registered: Dec 2003
Distribution: Debian
Posts: 3,178
Blog Entries: 4

Rep: Reputation: 138Reputation: 138
deleted.

Last edited by vharishankar; 11-02-2012 at 12:35 PM.
 
Old 08-22-2012, 09:32 AM   #206
rinias
Member
 
Registered: May 2009
Distribution: Slackware64-14.0
Posts: 58

Rep: Reputation: 18
Quote:
Originally Posted by vharishankar View Post
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
 
Old 08-22-2012, 09:34 AM   #207
rinias
Member
 
Registered: May 2009
Distribution: Slackware64-14.0
Posts: 58

Rep: Reputation: 18
Quote:
Originally Posted by vharishankar View Post
Already, the Wiki is beginning to take some shape.
Here, here! You (and others) have been doing a great job!
 
Old 08-22-2012, 09:40 AM   #208
vharishankar
Senior Member
 
Registered: Dec 2003
Distribution: Debian
Posts: 3,178
Blog Entries: 4

Rep: Reputation: 138Reputation: 138
deleted.

Last edited by vharishankar; 11-02-2012 at 12:35 PM.
 
Old 08-22-2012, 09:44 AM   #209
rinias
Member
 
Registered: May 2009
Distribution: Slackware64-14.0
Posts: 58

Rep: Reputation: 18
Hmm.. Now, I don't know :

Quote:
2012-08-17 New Slackbook, New License

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:

darkstar:~$ git clone git://slackbook.org/slackbook
from http://slackbook.org/
Attached Files
File Type: txt COPYING.txt (21.7 KB, 27 views)
 
Old 08-22-2012, 10:05 AM   #210
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,068

Rep: Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145
it's the same license adopted for the material published on the wiki
 
  


Reply

Tags
documentation, slackware


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Linux Documentation Project ask for Help jdd Linux - News 0 09-15-2008 01:37 AM
beginners documentation project? ichrispa LQ Suggestions & Feedback 1 01-13-2006 05:19 AM
The Windows Documentation Project CoolAJ86 General 3 08-29-2005 08:05 PM
The Fedora Documentation Project the shadows Fedora 0 03-21-2004 11:01 PM
Documentation project paradoxlight General 1 10-16-2003 10:24 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:29 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration