[Slackdocs] Introduction + first ideas

zithro (RabbiT) zithro at gmail.com
Mon Aug 20 17:43:42 CEST 2012

I also agree for a convention. I already have a few questions about this:

- to train myself to the Wiki syntax, I translated the start page in
french. Now "fr" is showing in the sitemap. Shouldn't there be a separate
sitemap for each language instead ? PS: thanks for the congrats Eric ;)

- which namespace will be the root of all docs (i mean, technical ones) ?
Will we use the Slackbook root ?
For example, I see that "security, cups, linux_howto_s, network, start,
user" are in the root, and IMHO they shouldn't. But I may go faster than
music here ;)
As per what you said in the contrib page, I could see a "General root"
(slack's philosophy, infos about the wiki, ...) and a "Technical root"
(how-to's, app-specific infos, install guide, ...). I'm really fond of
hierarchical namespace trees !
Does that make sense ?

2012/8/21 Kookie Monster <k00kiem0nster at ymail.com>

> I agree that a namespace convention has to be taken.
> I have been moving a few of the slackbook (beta) articles to the wiki, and
> will gladly accept any naming convention that will be decided. As for now,
> I'm sticking with AlienBob's slackbook: recommendation.
> Best regards,
> KookieMonster.
>   ------------------------------
> *From:* Eric Hameleers <eha at alienbase.nl>
> *To:* Nicolas Kovacs <info at microlinux.fr>
> *Cc:* slackdocs at alienbase.nl
> *Sent:* Monday, August 20, 2012 4:28 PM
> *Subject:* Re: [Slackdocs] Introduction + first ideas
> On Mon, 20 Aug 2012, Nicolas Kovacs wrote:
> > Nicolas Kovacs a écrit :
> >>
> >> As I've stated in a private mail to Eric, I think the most important
> >> point now is to setup a structure, a TOC, that has to be fleshed out
> >> with information. I think the existing Slackbook (3.0 beta) is an
> >> excellent starting point, and its TOC provides about two thirds of what
> >> can reasonable figure on a well-provided documentation site. So here's
> >> what I think could be a reasonable starting point.
> >
> > IMHO, someone has to step forward as a Temporary Benevolent Dictator to
> establish a rough first draft of the site structure. Just for this single
> problem, I sense a "Too Many Cooks Are Gonna Spoil The Soup" kind of
> problem.
> >
> > Eric? Anyone? Me?
> I'll see what I can do this week, but I do not want to run this as
> Slackware (with a single BDFL taking all decisions). For the time being, I
> made Nicci and myself admins of the wiki, and I think between the two of us
> we will not have many disagreements on how the Wiki should be structured.
> I will write a draft of the structure I would like to see in the Wiki and
> the ways people can contribute. I want to enforce the use of namespaces so
> that I can apply Access Control Lists to them in future. Watch
> http://taper.alienbase.nl/dokuwiki/start?idx=slackdocs for the appearance
> of articles which I will write about this.
> How does that sound?
> Eric
> _______________________________________________
> Slackdocs mailing list
> Slackdocs at alienbase.nl
> http://lists.alienbase.nl/mailman/listinfo/slackdocs
> _______________________________________________
> Slackdocs mailing list
> Slackdocs at alienbase.nl
> http://lists.alienbase.nl/mailman/listinfo/slackdocs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alienbase.nl/pipermail/slackdocs/attachments/20120821/28addbfa/attachment-0001.html>

More information about the Slackdocs mailing list