Re: skills of developers
On Sat, 16 Jul 2005 16:38:20 +0200, Torsten Landschoff <email@example.com> said:
> Hi *, What kind of discussion is this?
This is a discussion about project quality.
> We can't effort more bureaucrazy (typo intended) in the project. Let
> the people doing the work do the work instead of first measuring
> their ability.
This is quite possibly the silliest thing I have ever heard.
Please, people, before taking on a task that users depend on you to
perform well, _do_ assess whether you are up to the task. There is
no shame in acknowledging that you do not have to skills to maintain
something (you'll not find a python package in my stable, nor
haskel, not a slew of other languages I have no skill with).
If you do not have the skillset to perform a task, or the
time, ***DO NOT VOLUNTEER TO TAKE IT ON***. By doing so, someone
better able to perform that task would not do so
Find something else to maintain. There are 10,000 or so source
packages out there, I am sure you can find something you feel capable
of doing. Doing a bad job (and, as a maintainer, you can't do
anything _but_ a bad job if you can't help debuag/develop a package)
is not really better than doing something else.
> And critical packages are assigned anyway so why bother that much?
It is not just critical packages that deserve quality of
implementation. We have problems enough with ill maintained packages
to start encouraging people to do so.
In the next world, you're on your own.
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C