head	1.3;
access;
symbols
	dlr:1.1.1
	TIGRIS_0_9_2_4:1.1.6.1
	TIGRIS_0_9_2_3:1.1.6.1
	HELM_PEER_PORT_BRANCH:1.1.1.1
	TURBINE_PEER:1.1
	TIGRIS_0_9_2_1:1.1
	TIGRIS_0_9_2:1.1.0.6
	TIGRIS_0_8_4:1.1.0.4
	TIGRIS_0_9_0:1.1.0.2;
locks; strict;
comment	@# @;


1.3
date	2001.02.26.23.36.41;	author lori;	state dead;
branches;
next	1.2;

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

1.1
date	2000.12.30.23.22.00;	author jrobbins;	state Exp;
branches
	1.1.1.1
	1.1.4.1
	1.1.6.1
	1.1.8.1;
next	;

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

1.1.4.1
date	2001.01.16.00.17.44;	author susank;	state Exp;
branches;
next	;

1.1.6.1
date	2001.01.29.22.05.03;	author susank;	state Exp;
branches;
next	;

1.1.8.1
date	2001.02.17.18.39.15;	author edk;	state Exp;
branches;
next	;


desc
@@


1.3
log
@removed file; obsoleted by 1.0 help
@
text
@<HTML>
<HEAD>

<TITLE>Web-based Administration</TITLE>

</HEAD>
<BODY>
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <TD class="Header" nowrap>Web-based administration</TD>  
  </TR>
</TABLE>

<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
  <TR>
    <TD class="PlainText" VALIGN="top">

<P>Users with adminstrative accounts may use the "admin" item in the
project menu to access administrative web pages. There are four basic
concepts involved in the e-speak administrative web pages: users,
projects, modules, and mailing lists.</P>

      <UL>

        <LI>Users have login id's, names, and passwords. They also
        play a given role on the site with certain permissions.</LI>

        <LI>Projects are collections of modules, members, and mailing
        lists. Each project has its own subdomain, e.g.,
        http://platform.e-speak, and may have its own domain, e.g.,
        http://www.myproject.org. Each project has a set of issues in
        the issue tracking database associated with it.</LI>

        <LI>Modules are parts of a project. Each project has a "www"
        module that contains the web pages for the project web
        site. Projects also have one or more source code or
        documentation modules.</LI>

        <LI>Mailing lists provide a way for developers to communicate
        with one another and to receive notifications of project
        events. By default, each project has an announcements list,
        developers' discussion list, a users' list, a bug notification
        list, and a CVS commit notification list.</LI>

      </UL>
    </TD>
  </TR>  
</table>
</BODY>
</HTML>
@


1.2
log
@added <title> tags to all files
@
text
@@


1.1
log
@moved core documentation into helm, fewer overrides need to be in instances now
@
text
@d1 7
d49 2
@


1.1.1.1
log
@Replacing the HEAD with the HELM_PEER_PORT_BRANCH.
@
text
@a0 7
<HTML>
<HEAD>

<TITLE>Web-based Administration</TITLE>

</HEAD>
<BODY>
a41 2
</BODY>
</HTML>
@


1.1.8.1
log
@porting changes from the head to the branch
@
text
@a0 7
<HTML>
<HEAD>

<TITLE>Web-based Administration</TITLE>

</HEAD>
<BODY>
a41 2
</BODY>
</HTML>
@


1.1.6.1
log
@removed mention of e-speak
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d13 1
a13 1
concepts involved in the administrative web pages: users,
d23 2
a24 2
        http://project1.DOMAIN, and may have its own domain, e.g.,
        http://www.myproject1.org. Each project has a set of issues in
@


1.1.4.1
log
@adding the generic, default docs into this branch, bc they are in the head and nec for instantiations using stable branches
@
text
@@

