Yes, yes. It's good.

My consternation was rather over the 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!

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:
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

Eric, prepare your servers:
http://linux.slashdot.org/story/12/0...ins-in-earnest

O lawd!

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

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.

1 members found this post helpful.

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.

There is a question about additional namespaces on the mailing list.

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.

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.

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".

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.

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

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