head	1.3;
access;
symbols
	TIGRIS_1_1_0RC2:1.3
	TIGRIS_1_1_0RC1:1.3
	TIGRIS_1_1:1.3.0.14
	TIGRIS_1_0_8:1.3
	TIGRIS_1_0_8RC3:1.3
	TIGRIS_1_0_8RC2:1.3
	TIGRIS_1_0_8RC1:1.3
	TIGRIS_1_0_7:1.3
	TIGRIS_1_0_7RC3:1.3
	TIGRIS_1_0_7RC2:1.3
	TIGRIS_1_0_7RC1:1.3
	TIGRIS_1_0_6:1.3
	TIGRIS_1_0_6RC5:1.3
	TIGRIS_1_0_6RC4:1.3
	TIGRIS_1_0_6RC3:1.3
	TIGRIS_1_0_6RC2:1.3
	TIGRIS_1_0_6RC1:1.3
	TIGRIS_1_0_5:1.3
	TIGRIS_1_0_5RC6:1.3
	TIGRIS_1_0_5RC5:1.3
	TIGRIS_1_0_5RC4:1.3
	TIGRIS_1_0_5RC3:1.3
	TIGRIS_1_0_5RC2:1.3
	TIGRIS_1_0_5RC1:1.3
	TIGRIS_1_0_4:1.3
	TIGRIS_1_0_3:1.3
	TIGRIS_1_0_2:1.3
	TIGRIS_1_0_1:1.3
	TIGRIS_1_0:1.3.0.16
	TIGRIS_1_0_0:1.3
	TIGRIS_1_0_0_RC1:1.3.0.12
	dlr:1.1.1
	TIGRIS_0_9_2_4:1.3
	TIGRIS_0_9_2_3:1.3
	HELM_PEER_PORT_BRANCH:1.1.1.1
	TURBINE_PEER:1.3
	TIGRIS_0_9_2_1:1.3
	TIGRIS_0_9_2:1.3.0.10
	TIGRIS_0_9_0:1.3.0.8
	TIGRIS_0_8_4:1.3.0.6
	TIGRIS_NOV_12_2000:1.3
	OLDHELM:1.3.0.4
	TIGRIS_NOV_11_2000:1.3
	TIGRIS_SEP_13_2000:1.3.0.2
	TIGRIS_BASELINE:1.3;
locks; strict;
comment	@# @;


1.3
date	2000.06.15.19.35.58;	author dlr;	state Exp;
branches;
next	1.2;

1.2
date	2000.04.02.04.07.18;	author jrobbins;	state Exp;
branches;
next	1.1;

1.1
date	2000.01.31.10.14.52;	author jrobbins;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	2001.02.21.00.37.02;	author dlr;	state Exp;
branches;
next	;


desc
@@


1.3
log
@Fixed broken mailto link thanks to a patch from Josh Lucas <josh@@stonecottage.com>.
@
text
@<P>
<TABLE BORDER="0" CELLPADDING="2" WIDTH="98%" BGCOLOR="white">

<TR>
<TD WIDTH="100%" BGCOLOR="#CCCC99"><STRONG><font color="#000033"
FACE="Arial, Helvetica, sans-serif">
Helm Participants
</font></STRONG></TD>
</TR>


<TR>
<TD WIDTH="100%" HEIGHT="100" BGCOLOR="#f0f0f0">
<P>


<p>This project is just getting off the ground.  We are looking for
developers who are interested in sharing their ideas and getting down
to coding in the near future.
</p>

<p>
To get involved, join the developer's mailing list by sending email to
<a href="mailto:dev-subscribe@@helm.tigris.org">dev-subscribe@@helm.tigris.org</a>. 
</p>

<P>
The first thing you should do when you join the list is to post an
introduction message that tells the group:
</P>

<ul>
<li>who you are, </li>
<li>your interest in bug tracking,</li>
<li>the role you would like to play in the project
(e.g., do you want to just discuss ideas, write code, do UI design, or
be an early users?), and</li>
<li>the rough level of effort you expect to put (e.g., mainly lurking,
a few postings a week, a few evenings, several hours a week, this is
part of my full-time job).</li>
</ul>

<P>
See the mailing list <a
href="http://helm.tigris.org/helm-dev/">archive</a> to see how
others have introduced themselves.
</P>

<br>
</td>
</tr>
</TABLE>
@


1.2
log
@made anti-spam email addresses more practical
@
text
@d24 1
a24 1
<a href="dev-subscribe@@helm.tigris.org">dev-subscribe@@helm.tigris.org</a>. 
@


1.1
log
@initial checkin
@
text
@d24 1
a24 2
<a href="dev-subscribe at helm.tigris.org">dev-subscribe at
helm.tigris.org</a>. 
a52 22
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>

<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>

@


1.1.1.1
log
@Replacing the HEAD with the HELM_PEER_PORT_BRANCH.
@
text
@d24 2
a25 1
<a href="mailto:dev-subscribe@@helm.tigris.org">dev-subscribe@@helm.tigris.org</a>. 
d54 22
@


