[Zope3-dev] Lesson's learned about Z3 Dev Practices & Schemas

[Stephan Richter]

Hello everyone,

sorry about my remarks last night, but I was slightly aggrevated. Here are =
the=20
things I observed:

1. Larger projects, such as Schemas, always need a proposal, even though th=
ey=20
are started at a sprint. Really, the problem was that people made decisions=
=20
at the sprint and did not write them down. I had read all the Schema Wiki=20
stuff again before coding this weekend. I had mentioned that to Jim already=
=20
after the EP sprint.

2. Before someone starts coding on a component, they should notify the mail=
ing=20
lists. IRC is not enough, since noone can be there all the time. If someone=
=20
claims a module and cannot finish it (I know we had this case often), they=
=20
either write another message to the Z3 dev list or we have some sort of=20
timeout.

3. IF it is obvious that someone is working on a module (like I did this=20
weekend), then an additional developer should check back. I had already man=
y=20
more lines of Forms implementation, which I had to rewrite because my=20
check-ins were overwritten.

4. If possible, developers should be at least logged into IRC while=20
developing. This way immediate feedback is possible.

5. We should vote about the naming of the fields. While the EP Schema team=
=20
decided to stay with shortcuts, I had at least five people responding to my=
=20
original mail preferring the long names (which also follows the style guide=
).=20
I will write a separate message for that.

That's it.

Regards,
Stephan
=2D-=20
Stephan Richter
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training