Hello

[matt]

On Monday 29 May 2006 13:36, you wrote:
> Keep in mind, Matt, that there are various ways of giving. In particular,
> giving orders is often not appreciated; giving patches *is*. Far more
> valuable than a list of 100 things that can be improved is a list of 10
> things that can be improved along with the actual improvements. The reason
> for this is that the people doing the work have more than enough to do
> already; but if you become on of the people doing the work you are not
> increasing the workload, but *decreasing* it. And that's a good thing.
> Flooding lists or bugs.k.o with hundreds of reports just produces
> discouraging numbers (e.g. if there are 10 bugs, that's an amount you can
> deal with; 14000 bugs is insurmountable).

Don't worry, I know. I definitely would not like someone who didn't know what 
they were talking about giving orders to me if I were a lead developer. I'll 
try to just go through the existing codebase and see if I can fix some 
problems that exist by patches.

>
> Let's phrase this in a slightly more positive fashion:
>
> When you give advice or orders, they may be silently ignored; they may be
> vocally or rudely ignored. In either case, the community operates on a
> vaguely meritocratic basis and when you're new there is nothing that gives
> your advice or orders weight with the existing developers (or
> contributors). Make sure your advice is believable by showing that you can
> act on it first or by backing it up in a well-structured and documented way
> (for instance, the OpenUsability folks don't code, but they show how and
> why their advice is useful and by now they have the 'street cred' they
> deserve).

I know, don't worry.

Trust me, I'm not the kind of guy to give orders. I'm going to see what *I* 
can to do improve KDE, rather than tell people what they can do to improve 
it.
-- 
Valê,
Matt
matt at cfxnetworks.com