[MITgcm-devel] update on mitgcm.org

[Jean-Michel Campin]

Hi,

As you probably noticed, mitgcm.org has been overloaded (and unusable) several
times recently, mostly because of web-related request from robots.
This is annoying since the same machine (still young, barely 10.yrs old 32-bit
hardware) is also serving the mitgcm email list and CVS access to the code.

In the short term, to facilitate the move to new machine and also to 
avoid that all 3 services go down when one is hit, we are starting to 
separate the different bits:

1) lighter web-site load on forge.csail.mit.edu:
 Chris started to isolate the cvs-web interface (ViewVC) and put it on different
 hardware. Since this was where search-engine robots spent most of their effort, 
 this might solve the overload problem. The switch is transparent; just one thing 
 to keep in mind is that we can expect up to 2 min delay for cvs-commit to show up
 on the cvs-web (ViewVC).

2) switching the MITgcm mailing list (support, devel & cvs) to mailman.mit.edu:
 mailman.mit.edu is already used successfully for the 2 ecco list:
  http://mailman.mit.edu/mailman/listinfo/ecco-support
  http://mailman.mit.edu/mailman/listinfo/ecco-devel
 The mailman setting is quite similar there (compared to our own mitgcm.org/mailman)
 so that it could be relatively easy to make the move (without asking users to
  subscribe again ?); we can test this with mitgcm-devel and if it works well,
 then move also the support list.

 Related to: 
 I am currently changing the email address that I use to send testreport results
 from "jmc at mitgcm.org" to "jmc at dev.mitgcm.org".
 In theory, it should not be necessary but in case we want to play with how 
 mitgcm.org receives emails, this might make thing easier. Anyway, no rush here.

Comments / suggestions are welcome.

Cheers,
Jean-Michel