[kepler-dev] RFC new directory structure

Bertram Ludaescher ludaesch at sdsc.edu
Wed Mar 17 21:23:16 PST 2004


btw: Some of this looks overly "formal" or complicated. On the other
hand one needs some mechanism to make sure new members of the team had 
a chance to read the guidelines, familiarize themselves with the code, 
the organisation (chaotic as it may seem;-) etc.

Otherwise, it is very easy to

1. make assumptions about how things work
2. make changes that affect others
3. discover that things broke unintentionally 

That's all. Obviously, new developers to a project (say SPA) need to
have a means to contribute their code, and without delay.

At the same time, if this involves changing existing structures or
code, those changes should be discussed with all involved parties. A
self-managed collaboration such as Kepler offers many benefits (some
of which only become clear once one has actually been an active member 
for a while a "met the family"). But it also has some (IMHO small)
coordination cost.



More information about the Kepler-dev mailing list