LinuxQuestions.org
Visit the LQ Articles and Editorials section
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, 10:37 AM   #211
rinias
Member
 
Registered: May 2009
Distribution: Slackware64-14.0
Posts: 58

Rep: Reputation: 18

Quote:
Originally Posted by ponce View Post
it's the same license adopted for the material published on the wiki
Yes, yes. It's good.

My consternation was rather over the
Quote:
2012-08-17 New Slackbook, New License

We're progressing on the new slackbook
part which means my math was off. (For the record, I don't actually think 0 people are working on it).

But now I think I've gone a touch too far off track; this isn't the "Reincarnate the Slackbook" thread, after all. Apologies!
 
Old 08-22-2012, 12:28 PM   #212
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.0/14.1
Posts: 3,482

Rep: Reputation: 533Reputation: 533Reputation: 533Reputation: 533Reputation: 533Reputation: 533
Perhaps I missed this in the wiki, but as the goal of this project is to create a library of shared information about Slackware, I recommend using a Creative Commons license, specifically Attribution-ShareAlike (CC BY-SA).

Note: Copyright is strictly a statutory invention. Claiming copyright implies submitting to the jurisdiction of statutes. Using Creative Commons avoids that mess.

With respect to using Slackbook material, as of Aug. 17 the information is licensed under Creative Commons Attribution Share and Share-Alike license. That means the material can be used in the wiki without concern about copyright.
 
Old 08-22-2012, 12:39 PM   #213
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,223

Rep: Reputation: Disabled
Quote:
Originally Posted by Woodsman View Post
Perhaps I missed this in the wiki, but as the goal of this project is to create a library of shared information about Slackware, I recommend using a Creative Commons license, specifically Attribution-ShareAlike (CC BY-SA).

Note: Copyright is strictly a statutory invention. Claiming copyright implies submitting to the jurisdiction of statutes. Using Creative Commons avoids that mess.

With respect to using Slackbook material, as of Aug. 17 the information is licensed under Creative Commons Attribution Share and Share-Alike license. That means the material can be used in the wiki without concern about copyright.
Hi Woodsman

I added this from the start - it is shown in the footer of every page:
Code:
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 3.0 Unported
Alan and I discussed the SlackBook license in the past days, co´ncidentally he appears to have changed the license just a few days before that discussion because he has again started writing new content.

Eric
 
Old 08-22-2012, 12:46 PM   #214
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,561
Blog Entries: 1

Rep: Reputation: 1023Reputation: 1023Reputation: 1023Reputation: 1023Reputation: 1023Reputation: 1023Reputation: 1023Reputation: 1023
Eric, prepare your servers:
http://linux.slashdot.org/story/12/0...ins-in-earnest
 
Old 08-22-2012, 12:52 PM   #215
rinias
Member
 
Registered: May 2009
Distribution: Slackware64-14.0
Posts: 58

Rep: Reputation: 18
Quote:
Originally Posted by sycamorex View Post
O lawd!
 
Old 08-22-2012, 01:22 PM   #216
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,958
Blog Entries: 52

Rep: Reputation: Disabled
There's still quite a lot of ignorance regarding Slackware out there, from the comments:


Quote:
So what distinguishes Slackware from other distros? No public bug tracking. Closed development process. A primitive character-mode installer. All administration is done from the command line. No dependency tracking. Minimal feature set.

Could somebody who uses this thing explain why they prefer it to a more modern and open distro?
 
Old 08-22-2012, 02:08 PM   #217
akus
Member
 
Registered: May 2006
Location: Netherlands
Distribution: Slackware64-13.37
Posts: 52

Rep: Reputation: 17
Hi all,

I have a suggestion regarding Slackware Wiki.
To the main page a section called something like "Program-Specific Installation instructions / Application database" should be added. This section could have subsections like "Physical Sciences", "CAD" "Engineering" etc.
This would be somewhat similar to the application database for WINE (or Crossover). Of course, if an application can be installed and works on one distro, it can usually be installed on any distro . But there are often some distro specific dependencies and tricks one has to care about.

Here is an example.

There is a literature/citation management software RefDB, which I always install. There somewhat outdated installation instructions for Debian and generic linux. I have written down instructions which include explanations for particular configurations options, and which auxiliary Perl modules should be installed , and what are Slackware-specific things one must take care about (e.g. which SGML/Docbook engines are already onboard etc).

So, I keep a number of files with instructions for various programs. I might as well put this info into Slackware Wiki, share my experience, and learn from others.
Many of my programs are specially for natural sciences. They sometimes are close-source, and one has to install some dependencies.

Slackbuilds.org is not a right place for this kind of information, I think.
But this information is useful because applications, this is what's important for everyday work.
So, this kind of application database would help me and perhaps other people who use Linux for work.

Last edited by akus; 08-22-2012 at 02:15 PM.
 
1 members found this post helpful.
Old 08-22-2012, 02:32 PM   #218
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,958
Blog Entries: 52

Rep: Reputation: Disabled
We haven't sorted out how many sections (or namespaces), pages, subsections, or whatever, there will be. I should think that there will be somewhere to write about special cases like that.
 
Old 08-22-2012, 02:34 PM   #219
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,561
Blog Entries: 1

Rep: Reputation: 1023Reputation: 1023Reputation: 1023Reputation: 1023Reputation: 1023Reputation: 1023Reputation: 1023Reputation: 1023
There is a question about additional namespaces on the mailing list.
 
Old 08-22-2012, 02:37 PM   #220
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,958
Blog Entries: 52

Rep: Reputation: Disabled
Yeah, I've just read it and replied to it. About HOWTOS. Maybe unusual cases of installing software would fit in there? Don't know.
 
Old 08-22-2012, 02:42 PM   #221
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,223

Rep: Reputation: Disabled
Quote:
Originally Posted by vharishankar View Post
Why docs.slackware.com? Is this going to be merged as a (Semi-)/official project or will the community continue to be the main driving force?
It was my decision to ask Pat for a slackware.com hostname to connect it more naturally to the distro. This does not mean it will be a Slackware-driven or even Slackware-owned project.

Quote:
I ask, because if it is going to be an official project under official control of Slackware project, I would like to dissociate myself from the ongoing efforts in principle. In any case, I don't consider myself part of any official team in any project. My sincere apologies if this seems a bit rude, but really as a volunteer I am not interested in projects which are controlled by a corporate (legally speaking) or other statutory entity.
The only levels of "control" will be quality control, which was the goal from the beginning. Like slackbuilds.org we would like to see the community (you) contribute the content and get recognition for your contributions. There will be an admin team - like we have at slackbuilds.org - which will have the responsibility for keeping the site and the information contained therein accessible, legible but the admins should never dictate what that content must be! Proofreading, assistance with phrasing, connecting you to other people writing in the same topic area, that kind of activities. And of course maintenance of the servers and software.

Remember that people have been complaining about lack of proper Slackware documentation (a beginners's guide like the SlackBook is seriously outdated now) and also people have talked and talked endlessly about centralizing Slackware documentation... but such a project never took off. I decided to just start with kikinovak and see where it would end. Having a slackware.com hostname will most certainly give the wiki greater credibility. As such, we have even made slackdot today. But the real "name and fame" will only be established by you - the people who will (and have already started) populate the wiki with knowledge.

I have no desire at all to become a projectlead with dictatorial tendencies. But, the wiki is running on my virtual machine in a datacenter, the mailing list is hosted on my own server at home, and I have spent more time so far in setting up the infrastructure and configuring this wiki than you have spent editing... no offense. It's my puppy and I am just making sure it gets rooted and has a chance to gain enough momentum that it "runs itself".

Quote:
I perfectly understand the rationale behind the move to centralize this documentation, give it a leadership and appreciate it, but personally I feel less involved in a controlled project than in a pure community one.
Ultimately, only you control what you do with your time. I value your contributions, those you already did and all that may come in future.

If you (and/or others) feel that I should not have stepped up and taken the lead, then I will gladly upload the full content of the wiki (dokuwiki's great feature is that you can zip up one directory and unzip that on another server and your wiki will run there after modifying one file) so that "the community" can continue to grow it. It will not be under a slackware.com host then. And I will go back to doing my own thing. Take it or leave it.

One more thing. I don't know if you contribute to slackbuilds.org but there are far more Slackware coreteam members in that admin team than will ever be in this Wiki admin team. Did that ever give you the feeling that Slackware (the "legal entity") controls that site?

Eric
 
2 members found this post helpful.
Old 08-22-2012, 06:11 PM   #222
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.0/14.1
Posts: 3,482

Rep: Reputation: 533Reputation: 533Reputation: 533Reputation: 533Reputation: 533Reputation: 533
Quote:
I added this from the start - it is shown in the footer of every page:
Huh, right in front of my nose.

I expect that eventually this site will have some kind of submission guideline. Perhaps that guideline should include a similar disclosure statement?
 
Old 08-22-2012, 06:18 PM   #223
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,223

Rep: Reputation: Disabled
Quote:
Originally Posted by Woodsman View Post
Huh, right in front of my nose.

I expect that eventually this site will have some kind of submission guideline. Perhaps that guideline should include a similar disclosure statement?
Accidentally I edited http://docs.slackware.com/slackdocs:..._people_s_work a few hours ago to reflect exactly that :-)

Eric
 
Old 08-22-2012, 08:49 PM   #224
vwgtiturbo
LQ Newbie
 
Registered: Feb 2004
Location: Lincoln, CA
Distribution: openSuse 9-11, Ubuntu 10
Posts: 8

Rep: Reputation: 0
I just wanted to say 'Thanks' for this project, as I've been looking to get back into Slack for a few years now (haven't run it in 10), and documentation would be such a help.

In any case, if there is anything I can do to help, drop me a line, even if it's menial garbage, I'd be glad to lend a hand!
 
Old 08-23-2012, 03:23 AM   #225
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,223

Rep: Reputation: Disabled
Quote:
Originally Posted by vwgtiturbo View Post
I just wanted to say 'Thanks' for this project, as I've been looking to get back into Slack for a few years now (haven't run it in 10), and documentation would be such a help.

In any case, if there is anything I can do to help, drop me a line, even if it's menial garbage, I'd be glad to lend a hand!
Actually, since this project is contained in a Wiki, you can contribute any piece of Slackware related knowledge quite effortlessly. All you have to do in order to contribute is register an account on http://docs.slackware.com/ , create a new page and start documenting.

Eric
 
  


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


All times are GMT -5. The time now is 01:42 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration