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.74 [en]C-CCK-MCD   (Win98; U) [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 first check the various
<a href="sourcesOfInfo.html">sources
of in formation.</a>
<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="/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 receive 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 best chance of getting in contact with us all
simultaneously, but the response my be un-coordinated.
<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.
<p>
<hr WIDTH="100%">
<table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" NOSAVE >
<tr NOSAVE>
<td NOSAVE>Last modified on $Date: 2001/10/12 02:53:35 $</td>

<td>
<div align=right>CVS: $Source: /u/gcmpack/mitgcm.org/sealion/help/contactUs.html,v$Revision:
1.2 $</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.74 [en]C-CCK-MCD (Win98; U) [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>
12	<h1>
13	How to contact us!</h1></center>
14	The most productive way to sort out a problem is to first check the various
15	<a href="sourcesOfInfo.html">sources
16	of in formation.</a>
17	<p>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="/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 receive 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 best chance of getting in contact with us all
26	simultaneously, but the response my be un-coordinated.
27	<p>Finally, you can contact us directly (ie. privately - our emails are
28	on the users list) but this prohibits others from learning from the process.
29	<p>
30	<hr WIDTH="100%">
31	<table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" NOSAVE >
32	<tr NOSAVE>
33	<td NOSAVE>Last modified on $Date: 2001/10/12 02:53:35 $</td>
34
35	<td>
36	<div align=right>CVS: $Source: /u/gcmpack/mitgcm.org/sealion/help/contactUs.html,v$Revision:
37	1.2 $</div>
38	</td>
39	</tr>
40	</table>
41
42	</body>
43	</html>