|
You walk up to the Meeting Lounge and look through the windows from the
hallway. There are a whole bunch of CSH members in attendence, and Garrett
is by the whiteboards talking to everyone. The door is locked, but you
knock on it, and Conlon opens the door for you. You walk in and take a
seat on the floor amidst the attentive CSHers.
"... the appropriate project process," Garrett continues. "Now, when
you make a change to your code within the guidelines of the project, you
must go to the webpage and fill out a new 'Code Change Form', whereas if
the guidelines differ from those of the project in question, then you
must fill out a 'Change of Code Request', not to be confused with a
'Request for Code Change'; you fill out that form before fixing your
code, along with the 'Change Acknowledgement for Code' form. Be sure to
Cc: them to the project manager, the documention personnel, the ARG
mailing list, the project mailing list, Ken Thompson, and myself.
Anyone not writing in Java will be shot immediately. Now, onto the Change
of Guidelines submission form..."
Hmm... this is getting nowhere near your search for the yearbook. What
do you want to do now?
* Raise your hand, and when called upon, ask "How much code
does a code change change if a code change actually changes code?"
* Ask if anyone here has seen the yearbook CD.
* Start searching the room for the yearbook.
|