As Alien Bob pointed out the other night... the name of the operating system is Slackware Linux... and so should be the doc project's name.

I'm the one on the right.

At the top of the page your link points to it says:

Welcome to the Slackware Documentation Project

The word Linux doesn't appear in that phrase. Does it need to be edited?

Either title is OK by me.

I mentioned this to Alien Bob on the talk page for the Main page at the wiki. I don't think he's had the chance to see it yet.

Personally, I think SlackDocs fits a pattern, with SlackBuilds and SlackWiki.
But I'm not saying it should be changed.

Well, bottom line is...

I'm only making suggestions. It's really not my call.

Yeah, it's up to the admins.

The name of the distro is "Slackware Linux". It is often colloquially abbbreviated to "Slackware".
The name of the documentation project is "Slackware Documentation Project".

There is no friction in that.

Eric

Note to self: edit sigline.

Edit: There we go.

The wiki is really coming along in terms of content well. I am very happy to be part of the team and my thanks to the contributors who've spent their valuable time in developing content.

We have a long way to go and a lot to do to get there. We have time, though. There's no hurry.

deleted.

It will get easier as we go along, though. The initial period of a project like this is always chaotic. I sent a link to the list about The Five Stages of Project Team Development. Alien Bob mentioned somewhere today that they covered this in his training class recently. I have done project management work (in residential development). That process of team development is very interesting. It's all psychology 101, basically, but very accurate. Knowing how a team will develop helps the members to recognize what stages they are in and what they need to do personally and as a team member to proceed to the next stage.

I am offering articles from my web site:

http://humanreadable.nfshost.com/

Slackware is my primary operating system, therefore be sure to check the generic how-tos and journal entries too, which can be revised to focus on Slackware.

I don't have the time to join the wiki project, and won't in the foreseeable future, so others will need to grab them.

All I ask is any article used is credited to me as the original author. As stated at the web site, any associated scripts are free/libre software. I understand the creative commons license used at the wiki.

By the end of the year I expect either to shut down the web site or overhaul with a serious reduction. So grab now while you can.

2 members found this post helpful.

I just want to say that I think what you're doing is great. I'm very grateful for all the effort you put in to helping us newbies.
Thank you!

1 members found this post helpful.