Lance Waterman wrote:
I am trying to understand expectations around how the ODE project
plans to
work. Based on past exchanges you made the following comment:
I think the versioning changes will require an understanding of how the
feature would be implemented -- a design reveiew. As for the scratch vs
patch, scratch is called for when multiple developers are going to be
involved in developing a feature.
and Alex made the following comment:
An idea: you could also create a temporary branch to make it easier to
share, collaborate and merge/synchronize the code if you think the
scope
warrants it.
Now I think I hear you saying that the interface is not stable and folks
should not be surprised if it should change ( i.e. adding versioning )
without notification/discussion and at some future point in time we may
decide to lock it down.
Lance,
Just to be clear, I did not request that you create a separate branch.
In that earlier thread, you were saying that you would develop something
outside of the repository and commit it when completed. I merely
suggested that you could work in a branch if you wanted to increase your
chances of collaboration/help/feedback before integration into the trunk.
At this point in time, I'm more in favor of a fluid (read: less formal)
development methodology. A lot of pieces are still in flux and we're
trying to get to something working in order to allow people to start
using and contributing to Ode. Apache projects typically favor working
code over grand ideas because this is how things actually get done.
This being said, nothing is set in stone so there's always an
opportunity to comment on what has been done and improve the code if it
doesn't suit your purposes. Your feedback is important and I'm sure we
can work things out if you think we can improve (PM API or anything
else). I actually like the fact that we get things quickly integrated
in the trunk since it allows for good measure and validation of the
various changes we're making.
Later on when things stabilize I agree changes to public interfaces
(incl. configuration and database schemas) should be discussed with the
community before they are effected. This will be an important
"contract" with the community of users and developers who will most
likely want a smooth evolution of their environments.
cheers,
alex
