All of lore.kernel.org
 help / color / mirror / Atom feed
From: noc ops <aptgetd@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HOWTO unmaintained?
Date: Wed, 05 Oct 2005 23:18:24 +0000	[thread overview]
Message-ID: <43445F40.7010306@gmail.com> (raw)
In-Reply-To: <m3d5odyoom.fsf@reason.gnuhh-core>

Does anyone know where we stand with lartc howto?


regards,
/virendra

Stephen Hemminger wrote:
> On Thu, 18 Aug 2005 14:00:30 +0100
> Ed W <lists@wildgooses.com> wrote:
> 
> 
>>>>I wonder if someone would host a mediawiki and consider uploading the 
>>>>documentation there.  This would make it easier for people to 
>>>>contribute, and I think it shold be fairly easy to convert from it's 
>>>>current format to a wiki
>>>>
>>>>   
>>>>
>>>
>>>Good idea, I'll see if the OSDL will put up a wiki for it
>>>on developer.osdl.org, stay tuned.
>>> 
>>>
>>
>>Can I suggest that you look very hard at Mediawiki (ie as per 
>>wikipedia).  It's built for scalability, is really easy to edit, very 
>>actively maintained, and has all the distributed stuff built in if you 
>>really needed to spread the load over several machines.  All in all a 
>>very grown up documentation tool.  Oh and it's also multi-lingual so it 
>>might also be possible to use it to help with the translation issues
>>
>>I mainly mentioned it because I'm sure there are some tools for 
>>converting the current lartc faq up to the wiki format and obviously 
>>that's the first main step.
>>
>>If someone will host it then I have some experience maintaining a 
>>mediawiki site and could probably help out some
> 
> 
> Okay, if the lartc.org guys don't pick it up, I'll setup a mediawiki
> when I get back from holiday.  For an example see:
> 	http://wiki.linux-nfs.org
> 
> 	
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> 


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-10-05 23:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17  8:04 [LARTC] HOWTO unmaintained? Georg C. F. Greve
2005-08-17 10:19 ` Andreas Klauer
2005-08-17 10:40 ` Georg C. F. Greve
2005-08-17 11:28 ` Ed W
2005-08-17 12:26 ` Kenneth Kalmer
2005-08-17 12:27 ` Mike O
2005-08-17 13:38 ` Lee Sanders
2005-08-17 14:09 ` Andre D. Correa
2005-08-17 16:24 ` Stephen Hemminger
2005-08-17 16:28 ` Dariusz Dwornikowski
2005-08-17 17:05 ` Jonathan Day
2005-08-17 17:27 ` Andreas Klauer
2005-08-17 17:33 ` Carl-Daniel Hailfinger
2005-08-17 17:39 ` Carl-Daniel Hailfinger
2005-08-17 21:44 ` Taylor, Grant
2005-08-18  7:04 ` Stef Coene
2005-08-18 13:00 ` Ed W
2005-08-19 14:52 ` Stephen Hemminger
2005-08-20 11:17 ` Riccardo Losselli
2005-08-20 15:17 ` Alexander Reelsen
2005-10-05 23:18 ` noc ops [this message]
2005-10-06  2:41 ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43445F40.7010306@gmail.com \
    --to=aptgetd@gmail.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.