<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
hi<br>re: 'I think that there is maybe a bigger issue to start with though which<span style="text-decoration: underline;">
how are people supposed to be collecting the information to use in the
documentation? The only way i can think of doing this at the moment is
via Vms </span> which means people are going to need machines with enough
grunt to run a small vm networ or spare machines.'<br>
<br>a suggestion is something like this:-<br><br>http://uploadhosted.filefront.com/<br>http://www.huddle.net/<br>http://rapidshare.com/index.html<br><br>there are many free upload sites, it doesn't have to be any of these, rapidshare has ssl - most are at least 1/2gb/10hr upload limit [they aren't fast] with unlimited storage<br><br>all that's needed is for someone to set one up, & notify everyone of the site link, and ensure both upload/download status for users of a named friends group, rather than public access & if only docs or similar won't be large files, but they are free<br>just my 2 pen'orth<br><br>I'd favour a wiki on the klug server, though, then maybe blogspaces could be setup for demos/articles of interest/howtos etc<br><br>Aitch<br><hr>Date: Sun, 27 Jul 2008 11:33:13 +0100<br>From: danattwood@googlemail.com<br>To: kent@mailman.lug.org.uk<br>Subject: Re: [Klug-general] KLUG - Karoshi Doc Project<br><br><div dir="ltr">I know a bit about scribus and have used quark express in the past on which scribus is based. It is an extremely powerful desktop publishing program. Very good for setting up print publications and design work.<br>
<br>I could well be used for producing a final printed document, flyers, posters and the like. But it is not a collaborative program.<br><br>My personal feeling is that a wiki is the way to go to start with as it has a low barrier to entry, is easy to set up and will let people get cracking. The wiki can then be made available to the public and latter converted into a printed doc via latex or scribus if paper documentation is needed.<br>
<br>I think that there is maybe a bigger issue to start with though which how are people supposed to be collecting the information to use in the documentation? The only way i can think of doing this at the moment is via Vms which means people are going to need machines with enough grunt to run a small vm networ or spare machines.<br>
<br>Mikes suggestion of a virutal meeting is probably the best way to get cracking on this though. <br></div>
<br /><hr />Win £3000 to spend on whatever you want at Uni! <a href='http://clk.atdmt.com/UKM/go/101719803/direct/01/' target='_new'>Click here to WIN!</a></body>
</html>