Re: [Maxlinux-devel] inceptionos.org

[Kelledin <kel...@sk...>]

On Tuesday 20 August 2002 03:54 am, Enrico Kern wrote:
> > OK - Sounds good to me. Who needs access? A list of web
> > developers along with email addresses & required username
> > would be good.

A list of all current developers is avaliable at=20
http://sourceforge.net/project/memberlist.php?group_id=3D21828

Some of the members on that list might be "dead=20
members"--basically people who have left off the project without=20
notifying anyone.  Michael and I will need to see what to do=20
about those people...the less people with shell access to the=20
RaQ, the better.

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

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

The archive on skarpsey.dyndns.org will be backed up regularly;=20
I'm planning on the following schedule:

1) Back up everything to tape on a weekly basis.  Capacity is not=20
really a problem here; a single tape cartridge holds 20GB=20
uncompressed.

2) Have the package archive backed up to a CD set whenever the=20
RPMS or SRPMS repository approaches 700MB.  Good CD-R media is=20
dirt-cheap these days, so this is no problem.

If it makes things more convenient, I can probably set up rsync=20
on skarpsey.dyndns.org.

> > OK, one last thing, could someone add me to the list of
> > developers on Sourceforge? (Doc_Linux). Since I'm new to
> > this project do we have a list of what needs doing? I'm
> > willing to write documentation (using Docbook) if it needs
> > doing - I'm not really a coder ;-)
>
> Kelledin can arrange this i think. Hmm i think there are many
> tasks. As i say, i work on the installation interface, but
> this takes time (compile, package, testing, compile package,
> testing ;)) But i can show you some screenshots if you want

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

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

Enrico, what's your SourceForge username (or do you have one,=20
yet)?  It doesn't look like you're on the developer list, and=20
I'd like to rectify that.

--=20
Kelledin
"If a server crashes in a server farm and no one pings it, does=20
it still cost four figures to fix?"