Creating icons and other art

James Richard Tyrer | 1 Sep 2005 02:44

[kde-artists] The need for management

Yes, even though this is an Open Source Software project, we need 
management.  Especially with KDE (and any other similar projects) 
because it has become too large to be managed by constructive anarchy.

DA said:

> "Stepping on toes" is an inevitable consequence of doing work within KDE, in 
> my opinion.

WRONG, anyone that thinks that way needs to rethink their position.

Now, I don't mean that we won't have disagreement.  We should have 
disagreements.  Engineers argue (somewhat vehemently) about how do do 
things.  The problem I see with the WallPaper issue is that the argument 
is getting personal and that it is occurring after the action was taken.

True arguments should alway be about the issue.  I brought up an issue 
on another list a while ago and I thought I was the target of a tag-team 
rhetoric and insult gang.  This could be used as a textbook example of 
how NOT to argue.

So, arguments should stick to the issue.  Also, they should occur before 
an issue is decided.

But, getting back to management.  In business, people think that 
management means other people telling you what to do.  That isn't really 
the case.  Management determines the process of how decisions are made. 
  And, I note that in any organization, after decisions are made that 
everyone needs to abide by them.

(Continue reading)

headers

David Laban | 1 Sep 2005 04:09

Re: [kde-artists] The need for management

On Thursday 01 September 2005 01:44, James Richard Tyrer wrote:
> DA told me:
> > If every single thing that I did needed to be discussed by some slow
> > mailing list for days, and by disinterested persons, I wouldn't get
> > anything done. So, I use my judgement, discuss potentially controvertial
> > changes with others ard wait for your disagreement mail  :)

I think he has a point about mailing lists. They're not a very easy way to 
involve lots of people. If I want to view KDE mailinglists, I need to sign up 
to them and once I've signed up, I get more emails from each mailinglist than 
I do from my friends. It's also very hard to see what was posted before you 
signed up (which results in a lot of repetition (especially on kde-usability)

If we wanted to involve as many people in the decision making process as 
possible (and hence avoid stepping on peoples toes) we really need a 
browsable forum. In order for it to succeed, it would need

1) General information on KDE (and help/support, like the Gentoo forums, which 
are about the 3rd link on "gg:forums" ), to involve newcomers in the project 

2) A Decision Making forum for each area (areas relating to each of the KDE 
mailinglists, which is clearly marked as such and contains only relevant 
proposals

3) Documentation and resources for programmers (including style guides and the 
HIG) all in the same place with discussion pointed towards sister threads in 
"Decision Making" to keep it clean

4) Most important of all: The ability to receive the entire contents of a 
section of the forum (including new posts) by email in text only format and

(Continue reading)