Re: Great work

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Great work
by Louai Al-Khanji on Monday 21/Apr/2008, @20:20

Well, I do try to help out as I can, so I am not "sitting on the outside" in that sense. I have an svn account and occasionally submit fixes here and there. The thing is, to do that effectively does require a functional desktop - in this case the plasma breakage came as a bit of a surprise as I missed the announcement on kcd. I elected to fall back to KDE3 kicker.

I do not assume that trunk always functions 100%, that's not reasonable. I do assume that the major parts compile, as per the svn guidelines, which for a (short) while wasn't true.

Please don't take this the wrong way, I'm just trying to give some constructive feedback.

Related Links

·   Articles on Developer
·   Also by Louai Al-Khanji
·   Contact author

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

Re: Great work
by Ménard Alexis on Tuesday 22/Apr/2008, @00:50

Trunk is for development by definition, so it's normal to have breakages. I'm sorry but when the merge was done kdebase was ok for compilation so it's correct with svn guidelines. Plasma sprint was announced some weeks ago, with a WoC planned. Applets in PLAYground and EXTRAgear was broken but it's additionnals applets. There is a lot of plasma applets all around the code base so it's normal that applets not compile.

[ Reply To This | View ]

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


		"I tried to play with some toy applications and enjoyed it." -- Werner Trobin
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.