[MITgcm-devel] Lists?

[Alistair Adcroft]

It sounds like we want the gforge machine, cvs server and web server to be
the same machine but you say that isn't easy? Vitual hosting should allow
something to be worked out but it's unfortunate if it's going to be a hack
rather than natural.

It might be simpler to call the lists support, devel, archive and cvs rather
than mitgcm-* ?

A.
--
Dr Alistair Adcroft              email: Alistair.Adcroft at noaa.gov
NOAA/GFDL, Princeton University               Tel: (609) 452-6538
Forrestal Campus, U.S. Route 1, P.O. Box 308, Princeton, NJ 08542


-----Original Message-----
From: mitgcm-devel-bounces at dev.mitgcm.org
[mailto:mitgcm-devel-bounces at dev.mitgcm.org] On Behalf Of Ed Hill
Sent: Wednesday, July 23, 2003 2:41 PM
To: MITgcm-devel at dev.mitgcm.org
Subject: RE: [MITgcm-devel] Lists?


On Wed, 2003-07-23 at 13:59, Alistair Adcroft wrote:
> I see devel at mit.edu as being just an alias for the MIT group to talk
> to each other about issues that don't need (or shouldn't) be in the 
> public domain.
> 
> The norm would be to use support at mitgcm.org for most things but it is
> nice to
> 
> The lists can act either as an email-list (news group) and/or as an
> archive.
> 
> Based on what Ed and Chris have said it seems we need four
> lists(archives):
> 
> Mitgcm-support at mitgcm.org:
>  purpose = general address for incoming messages and discussion (as
> used to
> date)
>  aliased as support at mitgcm.org
>  subscriptions allowed
>  advertized to public
> Mitgcm-archive at dev.mitgcm.org
>  purpose = archives everything from gforge (i.e. changes to tasks, bugs,
> etc...)
>  no alias
>  no subscriptions
>  not advertized
> Mitgcm-cvs at dev.mitgcm.org
>  purpose = archives CVS activity
>  no alias
>  subscriptions allowed
>  advertized
> Mitgcm-devel at dev.mitgcm.org
>  purpose = messages not for public consumption
>  aliased as devel at mitgcm.org
>  subscriptions allowed
>  not advertized


Hi Alistair,

OK, I can setup everything you've listed above and it will work smoothly
except for the aliases.

The problems are

  1) GForge is hard-coded to work with list names of the form
     "PROJECTNAME-LISTNAME at server.domain.name"

  2) mailman does not gracefully handle input from forwarders 
     such as the current support at mitgcm.org forwarder

  3) sendmail "canonicalizes" (RFC822/2822) mail so that, in spite 
     of any mailman configs, the mail will always appear to come 
     from "name at dev.mitgcm.org" instead of "name at mitgcm.org" since 
     its running on that machine

  4) GForge wants to be setup as the "DocumentRoot" for the machine 
     upon which it runs so it isn't easy (need virtual hosting?) 
     to make dev.mitgcm.org and mitgcm.org be the same machine

So would it be acceptable if I did all of the above except the aliases?

Ed

-- 
Edward H. Hill III, PhD
office:  MIT Dept. of EAPS;  Room 54-1424;  77 Massachusetts Ave.
            Cambridge, MA 02139-4307
email:   eh3 at mit.edu,  ed at eh3.com
URL:     http://web.mit.edu/eh3/
phone:   617-253-0098
fax:     617-253-4464