Re: A HUGE job indeed.

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: A HUGE job indeed.
by Christian Loose on Friday 12/Aug/2005, @12:46

> You remember me of a teacher I once had, who thought he was always right just because he had studied psychology.

Then you misunderstood me.

I was replying to James point that professional software developers would advise the KDE developers to do the port differently. And I answered him that he is wrong because:

a) I'm a KDE developer
b) I'm a professional software developer
c) I would do the port exactly like it's done now.

I don't remember saying I was always right or that I studied anything.

> Btw. is there a plan for this transition, saying which job is done by (or under supervision of) who?

Don't think so.

Related Links

·   Articles on Developer
·   Also by Christian Loose
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: A HUGE job indeed.
by koos on Saturday 13/Aug/2005, @04:31

No that's what I meant to say. Since reasoning is a process of the mind, how can a psychologist be wrong?

> Don't think so
I find this a bit frustrating. I have time to work on KDE, but I really have no idea whom to contact or what areas to work on. Patches/questions sent to devel ml seems to either stay unanswered or interpreted as a personal insult of the author of that particular piece of code.
From the other side, I've seen someone porting code to Qt4 that I more or less maintain and completely breaking it. Never had any mail asking about this.
This is complete chaos IMHO, some list of the maintain->library should be available I think, no?

[ Reply To This | View ]

Re: A HUGE job indeed.
by Chris Howells on Saturday 13/Aug/2005, @04:52

"Patches/questions sent to devel ml seems to either stay unanswered"

Possible if the original authors/people familiar in the code aren't involved in KDE atm. And most developers don't read kde-devel due to the high traffic volume.

"or interpreted as a personal insult of the author of that particular piece of code."

Sorry, but you are completely wrong if you think that this is the opinion of authors on the whole. I don't remember ever experiencing it. Personally I am delighted that someone is using my program and then gone even further to try and fix something that they didn't like.

[ Reply To This | View ]

Re: A HUGE job indeed.
by Chris Howells on Saturday 13/Aug/2005, @04:54

"From the other side, I've seen someone porting code to Qt4 that I more or less maintain and completely breaking it"

Is this in KDE? Well, maybe that's because the initial aim of the porting was to get it compiling against Qt 4, not a completely fully working port to Qt 4 -- if we had that we could release KDE 4 now.

"Never had any mail asking about this."

So did you mail them to express your concerns?

"some list of the maintain->library should be available I think, no?"

There are a few lists of maintainers of various classes in kdelibs.

[ Reply To This | View ]

Re: A HUGE job indeed.
by SadEagle on Saturday 13/Aug/2005, @05:32

For maintainers, much of kdelibs has MAINTAINERS files, and if that fails, there is always (c) notices. And it's probably best to use kde-core-devel and not kde-devel for library patches

[ Reply To This | View ]

Re: A HUGE job indeed.
by James Richard Tyrer on Sunday 14/Aug/2005, @09:01

I have to report the same experience with patches.

I have posted them to bug reports, I have posted them to kde-core-devel, etc.

Occasionally, people take it as an insult, but mostly I am ignored.

So, now I am posting stuff to KDE Apps/Look: KDE Improvements. But, that wouldn't be appropriate for everone.

If there are any other frustrated would be contributors that think they could put up with the old engineer, please contact me by private mail and I will see if we can start a project.

tyrerj@acm.org

[ Reply To This | View ]

Re: A HUGE job indeed.
by Anonymous on Sunday 14/Aug/2005, @09:29

> I have to report the same experience with patches.

Please start to understand: it's about you. First making yourself unpopular with your comments and then expecting to be received cordially doesn't work.

[ Reply To This | View ]

Re: A HUGE job indeed.
by James Richard Tyrer on Sunday 14/Aug/2005, @10:58

Interesting theory:

Better the bug goes unfixed than have someone that you don't like fix it.

And I thought that this was supposed to be a meritocracy. :-)

[ Reply To This | View ]

Re: A HUGE job indeed.
by Anonymous on Sunday 14/Aug/2005, @11:43

You have a SVN account for one and half month now - and did you make one single commit since then? No! You just keep bitching...

[ Reply To This | View ]

Re: A HUGE job indeed.
by James Richard Tyrer on Sunday 14/Aug/2005, @12:21

I deliberately waited till the 3.5 branch was split.

Then I have had a lot of problems with SVN. I thought that I had it working OK and was going to do a build that would be up to date and I got mysterious error messages:

svn: Delta source ended unexpectedly

I posted this to kde-devel: 08/10/05 21:30. Nobody had any cure. A Goggle search turned it up as a bug. So, three modules were dead. Other problems continue. I keep getting the wrong "admin" module. Am I just unlucky -- I never had any trouble with CVS.

So, I have a build started again and I hope that it goes OK. If so, I will be able to do some work.

However, you should not presume that just because I have not committed anything that I haven't done anything. I have icons and patches ready to commit. Some of the CrystalSVG ones were posted to KDE-Look.

[ Reply To This | View ]

Re: A HUGE job indeed.
by Nicolas Goutte on Sunday 14/Aug/2005, @12:38

Try to clean your local working copy with:

svn cleanup

(I do not know if it will work or not but when you get problems under SVN, it is a good try.)

Have a nice day!

[ Reply To This | View ]

Re: A HUGE job indeed.
by Foobar on Tuesday 16/Aug/2005, @02:35

> Please start to understand: it's about you

I second that; its impossible to have a discussion since the good old engineer always has to be right and never gives in one inch. Thats not what a discussion is suppost to be about.
Its faster to fix the problem yourself then to get into a discussion with JRT, is what I always say.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"Never miss an opportunity to throw away code." -- Guillaume Laurent
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.