Posted by TimP on Tue Sep 15 13:13:03 1998
| Distribution: | paneris |
|---|
As Paneris expands its membership we need to formalise the
the tacic understandings that have been assumed todate.1. Paneris is a cooperative, be cooperative.
2. Working as a group is difficult, so think of it as a game.
the particular game to think of depends on the
type of the group.
The types I have encountered todate are:
Group Members Game Example One person, no impact on others Tetris DOS.html Two people, no customer Network Doom PMS One or more people, plus customer I went to the shops and I bought a Curly Wurly... Gemnet
Paneris Pass the ball New Box
3. To be a coding member, (and I expect to be a Graphic Contributor )
you should aim to contribute some of your code to the paneris corpus.
Ideally this should happen before working for a customer.
Even better than contributing some code is modifyig existing code and promulgating the modifications.
See guidelines.4. Paneris the organisation is about gaining the synergy
of a group whilst maintaining the freedom of the individual.
A term I would like to introduce is egoless programming,
a term that was used in the only successful coding team I have been a member of.
The essense of it is that 'owned code' is bad code.
Just as the compiler is your friend so is the reviewer.5. Each activity has an implicit quorum, which should be made
explicit ASAP.
Every member of the quorum has a veto.
To ignore someones veto is to expel them from the quorum.6. When you have finished something give it to someone else to have a go.
Love
Tim