next up previous contents
Next: Annual Events Up: Documentation Previous: SIPB-Written Documents

How to Make More Documentation

If you want to write a new SIPB document, simply tell people (so as to avoid duplicating work, and possibly get suggestions) and start doing it. Once you've got a draft, /afs/sipb/project/doc is a good place to put it (usually in its own subdirectory.) Be sure to put draft copies around the office so that people ``bleed'' on them, ie. scribble on them with comments one what they think is wrong, poor, or badly typeset. (Don't get discouraged by it - would you rather have thousands of users notice instead?)

Once a document is useful enough to be handed out to people, we need to make sure copies exist. Survey of in-stock documents is done during the ``Documentation Report'' section of the weekly meeting: the document racks at the front of the office are checked first, and if there's none (or little) there, the documentation drawer in one of the filing cabinets at the back of the office is checked for extras. If anything is critically low, make a motion of the form ``Move to allocate up to x dollars for y copies of foo,'' and volunteer to deal. To deal, just fill out a requisition for what you want (be sure to specify number of copies, and that it should be delivered to the office), get an officer to sign it, and send the requisition and a newly printed double-sided copy of the document to CopyTech (11-004).

We also stock some Athena documentation such as cluster cards, Athena reference cards, and Emacs reference cards. To restock these, just send mail to sendpubs requesting what you want, and cc: sipb-office so that people know the documentation is on the way.


next up previous contents
Next: Annual Events Up: Documentation Previous: SIPB-Written Documents
sepherke
1998-09-04