[Openfirst-cvscommit] www/htdocs/doc/tut/howto information.php,1.2,1.3 roles.php,1.2,1.3

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Update of /cvsroot/openfirst/www/htdocs/doc/tut/howto
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv28434

Modified Files:
	information.php roles.php 
Log Message:
Write a bit more about the roles, correct mailing list instructions.

Index: roles.php
===================================================================
RCS file: /cvsroot/openfirst/www/htdocs/doc/tut/howto/roles.php,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** roles.php	29 Dec 2004 17:01:37 -0000	1.2
--- roles.php	5 Jan 2005 19:13:59 -0000	1.3
***************
*** 34,38 ****
   <p>Please read the Administrator section of the Brief Outline above before reading this section.</p>

!  <p>...</p>

   <h2><a name="developer">Developer (open to students only)</a></h2>
--- 34,40 ----
   <p>Please read the Administrator section of the Brief Outline above before reading this section.</p>

! Administrators require not only technical skills, but also communication and team work skills. It is important that you, as an administrator, are capable of acting as a sort of mentor for the other members of the project team. Always be kind and courteous. Clearly justify your position on issues, and your reasons for making decisions if questioned. It's not enough that you know the reasons; you must be able to convey them to others, doing so aids in the learning that others will receive from the project. Kepp in mind that people questioning your decisions is a good thing, it means they care about what's best for the project; not that they wish to insult you. Perhaps most importantly always be open to and accepting of new ideas, and alternative approaches to doing things. Never dismiss any idea without carefully considering it regardless of how much or how little experience the person suggesting it has.
! 
! Please also read the parts of the <a href="technology.php">Technology Section</a> relevant to the Administrator role.

   <h2><a name="developer">Developer (open to students only)</a></h2>
***************
*** 42,50 ****
   <p>...</p>

   <h2><a name="documentationwriter">Documentation Writer</a></h2>
   <h3>Applies to: Documentation Writer</h3>
   <p>Please read the Documentation Writer section of the Brief Outline above before reading this section.</p>

!  <p>...</p>

   <h2><a name="patchwriter">Patch Writer (open to students only)</a></h2>
--- 44,58 ----
   <p>...</p>

+   <p>Please also read the parts of the <a href="technology.php">Technology Section</a> relevant to the Developer role.</p>
+  
   <h2><a name="documentationwriter">Documentation Writer</a></h2>
   <h3>Applies to: Documentation Writer</h3>
   <p>Please read the Documentation Writer section of the Brief Outline above before reading this section.</p>

! Write documentation clearly and sensibly in the English language. Canadian English, British English, and yes, even American English, etc. are all fine, but work to avoid analogies/metaphors/similies that are dependent on cultural experiences which are only common to North America, but not necessarily elsewhere. The rationale for this is that while FIRST may now be primarily a North American affair, it, like the Lego League is expanding internationally. If you are able to write documentation in a language other than English, contact an Administrator to discuss the possibility of translation of the project/documentation into that language.
! 
! If you're not sure what to write documentation about, check Bugzilla (<a href="http://bugzilla.openfirst.org/">http://bugzilla.openfirst.org/</a>) for an open bug requesting documentation or ask an Administrator.
! 
! Please also read the parts of the <a href="technology.php">Technology Section</a> relevant to the Documentation Writer role.

   <h2><a name="patchwriter">Patch Writer (open to students only)</a></h2>
***************
*** 54,57 ****
--- 62,67 ----
   <p>...</p>

+   <p>Please also read the parts of the <a href="technology.php">Technology Section</a> relevant to the Patch Writer role.</p>
+  
   <h2><a name="publicity">Publicity</a></h2>
   <h3>Applies to: Publicity</h3>
***************
*** 60,63 ****
--- 70,75 ----
   <p>...</p>

+   <p>You may also wish to read the parts of the <a href="technology.php">Technology Section</a> relevant to the Publicity role.  You may or may not have to actually use any of these technologies depending on the method you choose to pursue for publicising the openFIRST project; but, it having a working knowledge of them may be useful.  Alternatively, you may wish to use the technology section only as a reference.</p>
+  
   <h2><a name="releasetechnician">Release Technician</a></h2>
   <h3>Applies to: Release Technician</h3>
***************
*** 65,69 ****

   <p>...</p>
!  
   <h2><a name="webmaster">Webmaster</a></h2>
   <h3>Applies to: Webmaster</h3>
--- 77,83 ----

   <p>...</p>
! 
!   <p>Please also read the parts of the <a href="technology.php">Technology Section</a> relevant to the Release Technician role.</p>
!   
   <h2><a name="webmaster">Webmaster</a></h2>
   <h3>Applies to: Webmaster</h3>
***************
*** 72,74 ****
--- 86,90 ----
   <p>...</p>

+  <p>Please also read the parts of the <a href="technology.php">Technology Section</a> relevant to the Webmaster role.</p>
+  
  <p><center><a href="atmosphere.php">Previous</a> | <a href="index.php">Table of Contents</a> | <a href="technology.php">Next</a></center></p>
\ No newline at end of file

Index: information.php
===================================================================
RCS file: /cvsroot/openfirst/www/htdocs/doc/tut/howto/information.php,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** information.php	29 Dec 2004 17:01:37 -0000	1.2
--- information.php	5 Jan 2005 19:13:59 -0000	1.3
***************
*** 26,30 ****
   <h3>Applies to: All</h3>

! The openFIRST Project makes use of a few mailing lists. All lists may be subscribed to by sending a blank e-mail to lis...@li.... They, including who they're relevant to, include:

   <ul>
--- 26,30 ----
   <h3>Applies to: All</h3>

! The openFIRST Project makes use of a few mailing lists. All lists may be subscribed to by sending a blank e-mail with subject "subscribe" to lis...@li.... They, including who they're relevant to, include:

   <ul>