[Corelinux-public] If you want to join the team

[Frank V. C. <fr...@co...>]

This will be included in a CoreLinux++ FAQ I will start to put together, =
in the meantime:

To join the CoreLinux++ development team (in whatever capacity) please =
e-mail me direct fr...@us... with the following =
information:

1. Your Source Forge User Name
2. Your area of interest
3. Your Linux distribution
4. Your hardware setup
5. Optionally your strongest and weakest areas of experience

Once I receive this I can add you to the project team configuration. The =
only piece of info I really need for that is #1, the rest is so we have =
a handle on who can do what, on what platform, etc. A broad =
diversification will insure a robust deliverable.

Once you are added to the project you will have read/write access to CVS =
BUT Source Forge will only allow access through the SSH Shell. To review =
how this works go to the Source Forge home page at =
http://www.sourceforge.org and follow the Site Documentation link. Then =
read the CVS documentation. It will help to be familiar with CVS =
commands, etc.

If you are nervous about doing any changes with CVS early on, send me =
whatever you want to post with an explanation. We have yet to determine =
the tracking aspect of WHY changes are occurring but relating it to a =
Feature (use the message # from the Forum) or a Defect ( use the defect =
# from the Bug list ) will be very safe to begin with.

If you are making changes that are to the CoreLinux++ Home Pages, =
http://corelinux.sourceforge.net , you will need to do additional work:

1. First make the changes and get them committed into our CVS tree
2. Upload the *.html or whatever (graphics, php scripts, docs) to the =
CoreLinux web page files using SCP ( it is a SSH copy file program ).

TEST, TEST, TEST, and oh yes, TEST