Re: A HUGE job indeed.

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

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

Related Links

·   Articles on Developer
·   Also by SadEagle
·   Contact author

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

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 )


		"KDE is much too well-structured for this world..." -- Rob Buis
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.