HTML Team Meeting Agenda

Please submit proposed agenda items to Lisa Beal (lbeal@fortnet.org) by no later than Friday, April 7, 1995.

Attendees

(to be developed)

Old Business

1. Status of Current HTML Assignments [Buning]
   • (to be developed)
2. Quality Assurance resources on FortNet's WWW Server [Clarke, Beal]
3. Status of WWW services and documents [Grapek, Beal]
4. (more to be developed)

New Business

1. About New HTML Assignments [Buning]
   • (to be developed)
2. Shack Demolition [Buning]
3. New Meeting Place [Buning, Luse]
4. Version Control [Clarke, Beal]
   • "Should we require all documents owned by FortNet (my view of this is mainly those under ~www/htdocs/FortNet) to be under version control and if so, which version control system. I would suggest that we do require it for FortNet documents and strongly suggest it for others. The reasons for this are: better protection from two people editting the same file and only the last saver's changes taking place, ease of rolling back to a previous version if something goes wrong with the current version. The two main contenders that I see for systems are RCS and CVS." - clarke@fortnet.org
5. (more to be developed)

Presentation Committee Announcements [J. Westover]

Presentation

Version Control and FortNet's HTML Development [Beal] (Clarke may assist)

OUTLINE
1. What is Version Control?
2. Why Use Version Control?
3. How Version Control can help the FortNet HTML group
4. Overview of several version control systems:
   • Source Code Control System (SCCS)
   • Revision Control System (RCS)
   • Concurrent Versioning System (CVS)
5. Commonly used CVS commands - what we will use for HTML maintenance

Next HTML Meeting Scheduled:

(new location to be announced)
Fort Collins, CO
xx/xx/xx, 7 pm