Like usual I can provide various dns redirects or hosting. I've put up a
newer web server thats looks to be a bit mor epowerful than my current
one.... we could host the pages there or where ever.

   -Leif Hardison
    hardware.doa.org

On Fri, 29 Jan 1999, Roger Dingledine wrote:

> > > I can't host or mirror the home page, but i would be happy to maintain it. 
> 
> > How about setting up a cvs repository for the web site, and then setting
> > the web site to do an update every few hours? I can host the pages here no
> > problem, but offering others a login is more difficult.
>  
> It sounds like we've got several places that are willing to host the pages,
> and several people willing to do web work to get the pages more up to
> date. I've also noticed that the ELKS pages seem to be distributed pretty
> widely and randomly (a faq here, a mirror there, two (stale?) list archives,
> etc.)
> 
> I've gotten several personal mails offering help with getting the project
> "back on track". I propose we try to consolidate a bit more -- given the
> number of people around that want to put time into this, a good webpage
> would be very useful for keeping people informed of what's going on. I
> propose that this webpage should live on the same site as the cvs repository
> for the page, and ideally on the same site/domain as the main ftp site (or
> at least a complete mirror). It should have an elks group with logins for
> the developers, etc. Doesn't have to be extra-spiffy, but it needs to be
> functional, useful, and reliable.
> 
> I've seen some mentions of mirror sites (and redirects, eg elks.doa.org).
> doa: can you offer the above? I can set it up on the seul machines if
> nobody else has the infrastructure in place for it. Speak up now, else I'll
> try to deal.
> 
> A bigger question: there's a lot of discussion about web maintenance, but
> is anybody actually doing dev work on elks itself? I can't blame them for
> ignoring the list given its recent content, but getting a couple of status
> reports so they could go on the (future) website would be kind of useful.
> 
> --Roger
> 

Reply via email to