crossley 02/05/13 01:50:49 Modified: src/documentation/content/xdocs contrib.xml Log: Changed all to
for document-v11 DTD. Revision Changes Path 1.3 +12 -12 xml-forrest/src/documentation/content/xdocs/contrib.xml Index: contrib.xml =================================================================== RCS file: /home/cvs/xml-forrest/src/documentation/content/xdocs/contrib.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- contrib.xml 21 Apr 2002 02:43:37 -0000 1.2 +++ contrib.xml 13 May 2002 08:50:49 -0000 1.3 @@ -13,7 +13,7 @@ - +

The Forrest Project is an Open Source @@ -47,9 +47,9 @@ we have work for you!

- +
- +

The rest of this document is mainly about contributing new or improved code and/or documentation, but we would also be glad to have @@ -80,10 +80,10 @@ - +

- +

An overview of how to use CVS to participate in Forrest development. Do not be afraid - you cannot accidently destroy the actual code repository, because you are working with a local copy as an anonymous user. Therefore, @@ -104,9 +104,9 @@ repository, how to keep it up-to-date, and how to generate the differences to create a patch. (The commands are for Linux.)

- +
- +

After a developer has consistently provided contributions (code, documentation and discussion), then the rest of the dev community may vote to grant this developer commit access to CVS. @@ -124,10 +124,10 @@ - See the bottom of the page for links to tips for UNIX and Windows. Even if you are on UNIX, the Windows page will also help. - +

- +

There are two methods for discussing development and submitting patches. So that everyone can be productive, it is important to know which method @@ -177,10 +177,10 @@ posting - perhaps it was not clear enough and the readers' eyes glazed over.

- +
- +

This is a collection of tips for contributing to the project in a manner that is productive for all parties. @@ -269,7 +269,7 @@ see the way other people do things. Follow the leading examples. - +