-OK, we give in. You can contact us in several ways: -
If you think you have found a bug or major unexpected feature in the -code please report it to bugs@mitgcm.org. -This will enter your email into a bug-tracking -system which means you have us over a barrel if we do nothing. The -system will assign you a report number and you can track our progress. -
The developers recieve email at support@mitgcm.org.
-The email is also forwarded to the newsgroup
-for archiving. This is your
-
best chance of all of us seeing your message but the response my be
-un-coordinated: we might all reply or we might all think someone else replied.
-
Finally, you can contact us directly (ie. privately - our emails are -on the users list) but this prohibits others from learning from the process. -More over, you might contact the one of us who doesn't know anything... -
-
| Last modified on $Date: 2001/10/12 02:53:35 $ | - -
- CVS: $Source: /home/ubuntu/mnt/e9_copy/mitgcm.org/sealion/help/Attic/contactUs.html,v $Revision: 1.1 $
- |
-
OK, we give in. You can contact us in several ways: +
If you think you have found a bug or major unexpected feature in the +code please report it to bugs@mitgcm.org. +This will enter your email into a bug-tracking +system which means you have us over a barrel if we do nothing. The +system will assign you a report number and you can track our progress. +
The developers receive email at support@mitgcm.org. +The email is also forwarded to the newsgroup +for archiving. This is your best chance of getting in contact with us all +simultaneously, but the response my be un-coordinated. +
Finally, you can contact us directly (ie. privately - our emails are +on the users list) but this prohibits others from learning from the process. +
+
| Last modified on $Date: 2001/10/22 02:54:43 $ | + +
+ CVS: $Source: /home/ubuntu/mnt/e9_copy/mitgcm.org/sealion/help/Attic/contactUs.html,v $Revision:
+1.2 $
+ |
+