Re: [Maxlinux-devel] inceptionos.org

[Terry C. <te...@do...>]

Kelledin <kel...@sk...> Said:

> A list of all current developers is avaliable at 
> http://sourceforge.net/project/memberlist.php?group_id=21828
> 
> Some of the members on that list might be "dead 
> members"--basically people who have left off the project without 
> notifying anyone.  Michael and I will need to see what to do 
> about those people...the less people with shell access to the 
> RaQ, the better.

Agreed.

> I say we have SSH/SFTP set up on the RaQ, with support for 
> ssh2-publickey authentication, and no other authentication.  
> Then, simply tell all developers where to send their SSH public 
> keys if they want access.

Good idea. FYI this host is also used by a few close friends so we may
need to leave password access enabled, but only I'll know it & it'll
be completely random...

I'll set up a webmasters user for those who need access to update
webpages. I'll then add the keys of those who need access to this user.

> As far as FTP hosting, it's a good idea to start hosting the 
> archive on the RaQ.  If another offer comes along, well, we'll 
> have more mirrors.  This never hurts. ;)

Indeed :) How do you want to do it? rsync is fine for now if you want to mail
me the details.

> The archive on skarpsey.dyndns.org will be backed up regularly; 
> I'm planning on the following schedule:
> 
> 1) Back up everything to tape on a weekly basis.  Capacity is not 
> really a problem here; a single tape cartridge holds 20GB 
> uncompressed.
> 
> 2) Have the package archive backed up to a CD set whenever the 
> RPMS or SRPMS repository approaches 700MB.  Good CD-R media is 
> dirt-cheap these days, so this is no problem.
> 
> If it makes things more convenient, I can probably set up rsync 
> on skarpsey.dyndns.org.

This RaQ will also be backed up around 4am Sunday (GMT) to a tape robot.

> Done. :)  Terry, you're listed as a "Doc Writer", which we could 
> certainly use.  One of the first things I'll need is a set of 
> documentation for package maintainers (the people who do my 
> primary job)--basically a set of guidelines for how packages 
> should be built.  I'm fervently hoping I don't end up being the 
> only package maintainer!  I've got a partial rough-draft of the 
> guide in text format; I'll probably post it in a few days for 
> you to convert to DocBook format.

OK, I'll work out my plan of attack when I get home (working ATM).

> We'll also need some sort of end-user manual; we can probably get 
> started on that once Enrico's got some shots of what the install 
> procedure will look like, and how it will behave.

Excellent, I'll get on ASAP.

I'll try and sort out access for people and other related stuff today, but
it does depend on how busy it gets at work...
-- 
Terry Churchill	:	http://www.doc-linux.co.uk/

One distinguishing characteristic of BOFHen is attention deficit disorder.
Put me in front of something boring and I can find a near-infinite number
of really creative ways to bugger off.