[RFC] Software Process Improvement in Free Software

[fzr]

hi all,

as i see you try to maintain quality in debian efficently.

ive been thinking for months now about inventing and adopting
the SPI-standards cmm(x), spice, iso12207, and iso 9001,
etc, in free sw's lifecycles
and would like to ask you about comments and discussion.

discussion/research points:

1. closing and improving the spi/qm/qa- cycle with the developers by
analyzing their dev-processes, tools, configuration/analysis mngmnt and
give non-demotivating feedback with

-what i call now- "CMP" ( Capability Maturity Points), scale 10-100 (log).

the classic industry way has shown up to be demotivating, developers
would avoid the system or even trick it off.

2. escape the megawave of developer->feature->bug->developer bad cycles
by targeting q-lacks at the beginning of a lifecyle leaving no stage
uncovered, just building a dam against the bug-hazard at the end
and maintaining old waterfall structures has shown up no more
sufficent -UNDEPENDENTLY- of the size and amount of sw-project(s).

3. research, collect and provide "best practices", not just scales.

4. invent software metrics for oss like function/class points.

. . .

y
tom

[feltel]

I´ve moved your Topic to the Smalltalk-Forum since our Grundsatzfragen-Forum is mainly for Questions regarding basic Linux-Operations and Commands.

[fzr]

ist in Ordnung, dankeschön, gehört auch eigentlich in meinem thread über aufbau einer qualitätsmanagementabteilung

leider haben einige leute dort dann über spezielle bugs diskutiert anstatt über wissenschaftliche Ansätze, deshalb wollte ich nen neuen thread machen.

gruss,
tom