TRAC

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

TRAC
by mag on Wednesday 21/Mar/2007, @17:32

I think that setting up a system like TRAC with milestones and small things that needs geting done will speed up development and releaseing betas

Many people would like to contribute, but they usualy do not have time to white 1000 line piece of code. They can add small improvements or fixes if they know what needs to be fixed

Related Links

·   Articles on Developer
·   Also by mag
·   Contact author

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

Re: TRAC -> tips on what to do and how
by annma on Thursday 22/Mar/2007, @00:20

We already have several tools for people who would like to help with KDE 4. Those tools tell you exactly what needs to be fixed. It can be code fixes or doc fixes for non-developers. Not to mention doc writing ... We have the EBN
http://www.englishbreakfastnetwork.org/krazy/?component=kde-4.0
and the dashboard
http://ktown.kde.org/~dirk/dashboard/4.0/
Pick up an application and fixe all warnings found by those tools. Then please send the patch to the kde-devel mailing list. That's as simple as that!

[ Reply To This | View ]

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


		"I'm adding spaces everywhere so that Charles doesn't edit the files." -- Stephan Kulow
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.