sealion/help/contactUs.html

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
   <meta name="GENERATOR" content="Mozilla/4.75 [en] (X11; U; Linux 2.2.14-5.0 i686) [Netscape]">
   <meta name="Author" content="AJA@MIT">
   <title>Downloading MITgcm 1.0</title>
</head>
<body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#51188E" alink="#FF0000">

<center><h1>How to contact us!</h1></center>

The most productive way to sort out a problem is to check the various
<a href="sourceOfInfo.html">sources of in formation</a> first. Please.

<p>
OK, we give in. You can contact us in several ways:
<p>If you think you have found a bug or major unexpected feature in the
code please report it to <a href="mailto:bugs@mitgcm.org">bugs@mitgcm.org</a>.
This will enter your email into a <a href="http://mitgcm.org/cgi-bin/mitgcm-bugs">bug-tracking
system</a> 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.
<p>The developers recieve email at <a href="mailto:support@mitgcm.org">support@mitgcm.org</a>.
The email is also forwarded to the <a href="news://mitgcm.org/mitgcm.support">newsgroup</a>
for archiving. This is your
<br>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.
<p>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...
<p>
<hr WIDTH="100%">
<table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" NOSAVE >
<tr NOSAVE>
<td NOSAVE>Last modified on $Date: 2001/10/05 19:31:00 $</td>

<td>
<div align=right>CVS: $Source:&nbsp; $Revision: 1.1 $</div>
</td>
</tr>
</table>

</body>
</html>
1	<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
2	<html>
3	<head>
4	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
5	<meta name="GENERATOR" content="Mozilla/4.75 [en] (X11; U; Linux 2.2.14-5.0 i686) [Netscape]">
6	<meta name="Author" content="AJA@MIT">
7	<title>Downloading MITgcm 1.0</title>
8	</head>
9	<body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#51188E" alink="#FF0000">
10
11	<center><h1>How to contact us!</h1></center>
12
13	The most productive way to sort out a problem is to check the various
14	<a href="sourceOfInfo.html">sources of in formation</a> first. Please.
15
16	<p>
17	OK, we give in. You can contact us in several ways:
18	<p>If you think you have found a bug or major unexpected feature in the
19	code please report it to <a href="mailto:bugs@mitgcm.org">bugs@mitgcm.org</a>.
20	This will enter your email into a <a href="http://mitgcm.org/cgi-bin/mitgcm-bugs">bug-tracking
21	system</a> which means you have us over a barrel if we do nothing. The
22	system will assign you a report number and you can track our progress.
23	<p>The developers recieve email at <a href="mailto:support@mitgcm.org">support@mitgcm.org</a>.
24	The email is also forwarded to the <a href="news://mitgcm.org/mitgcm.support">newsgroup</a>
25	for archiving. This is your
26	<br>best chance of all of us seeing your message but the response my be
27	un-coordinated: we might all reply or we might all think someone else replied.
28	<p>Finally, you can contact us directly (ie. privately - our emails are
29	on the users list) but this prohibits others from learning from the process.
30	More over, you might contact the one of us who doesn't know anything...
31	<p>
32	<hr WIDTH="100%">
33	<table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" NOSAVE >
34	<tr NOSAVE>
35	<td NOSAVE>Last modified on $Date: 2001/10/05 19:31:00 $</td>
36
37	<td>
38	<div align=right>CVS: $Source:  $Revision: 1.1 $</div>
39	</td>
40	</tr>
41	</table>
42
43	</body>
44	</html>