Re: [Fwd: Re: [RFC] Software Process Improvement in Free Software, Closing the Quality Cycle, Inventing Non-Developer-Demotivating QA/QM/SPI]
Thomas Schorpp wrote:
> >Free software works by people simply doing things and contributing
> >them to the community. If other people are interested, it will be
> >picked up.
> Sorry, requirements for QM/SPI- projects is to assure that before start
> or error or failure risks would be too high.
I wonder if this means that QM/SPI simply does not fit in with Free Software?
I was once in a discussion with non-software people to discuss the
question "Can a Free Software project fail?". This is an interesting
question. Can it or can't it? If it can't, there would be no failure
risk, and even if it can, what is the failure risk?
To give you an example, writing a tool for foo which is not accepted
by the public but works sufficiently for your personal tasks would be
a total failure when viewed from the public but a large success for
the one person using it. Even abandoned (maybe some sort of failure
as well) software may still be useful for some people.
> >I suggest you do a QA process assessments of Debian and
> >write up your findings in a way Debian people will be able to
> >understand. Based on this document, we can discuss further steps.
> I agree with that, but I can do it only with participation of Your team,
> never alone.
Then please let us know how to help without bombarding the Debian
developers with buzzwords and acronyms most of them won't be able to
grok without a degree in software engeneering.
> So I should work out or point You to a basics introdution.
No. You sould explain in detail what you want, what you mean and what
you want from us. If we cannot understand each other, the cooperation
is bound to fail.
Open source is important from a technical angle. -- Linus Torvalds
Please always Cc to me when replying to me on the lists.