[oi-dev] Testing Updating packages and hipster-testing repo.

[Thomas Wagner]

Maybe the problems dicussed here are only a symptom
and *not* the root cause.

If you put non-coordinated, non-discussed, non-approved
changes in a consolidation repository to test how things
fit together, then you need not wonder how much and 
how bad stuff can break.

The Problem is the missing control of what _is_ to be
changed and _when_ and _how_. There is not even a
mechanism to _hold_ a change if it is wrong or dangerous
or breaks with a rule which OI has set for themselves.

Is this true?


Who else then _YOU_ developers can make up a commitee
which is in control of the general diretion, set rules,
monitor changes and issue corrective actions.

Thomas


PS: There are plenty of examples out there how to manage
    an open source project. Just OI team ignores best
    prectise.


PS2: don't discuss with me, _YOU_ developers need to
    sit at one table and discuss and come to agreements