Development/FAQs/General FAQ - Revision history

Maidis: Not sure about current situation of qt-copy: http://websvn.kde.org/trunk/qt-copy/ http://gitorious.org/+kde-developers/qt/kde-qt http://quickgit.kde.org/?p=qt%2Fqt5.git

2013-05-11T19:04:05Z

Not sure about current situation of qt-copy: http://websvn.kde.org/trunk/qt-copy/ http://gitorious.org/+kde-developers/qt/kde-qt http://quickgit.kde.org/?p=qt%2Fqt5.git

Maidis: kde -> KDE

2013-05-11T18:47:13Z

kde -> KDE

Maidis: "Building 2 Versions" doc no longer available. Don't sure but this videos tell similar thing? If not we can comment in this q&a until a new Building 2 Versions will written

2013-05-11T18:44:21Z

"Building 2 Versions" doc no longer available. Don't sure but this videos tell similar thing? If not we can comment in this q&a until a new Building 2 Versions will written

Maidis: some cosmetic changes

2013-05-11T18:29:16Z

some cosmetic changes

Maidis: uppercase y

2013-05-11T18:11:32Z

uppercase y

Maidis: line breake handling at quoted paragraphs: http://en.wikipedia.org/wiki/Wikipedia:Line-break_handling

2013-05-11T18:10:46Z

line breake handling at quoted paragraphs: http://en.wikipedia.org/wiki/Wikipedia:Line-break_handling

Maidis: remove "all in one line" expression

2013-05-11T17:52:07Z

remove "all in one line" expression

Maidis: some cosmetic changes

2013-05-11T17:49:27Z

some cosmetic changes

Maidis: show links prettier

2013-05-11T17:34:07Z

show links prettier

Maidis: add link to referred article

2013-05-11T17:29:02Z

add link to referred article

@@ Line 190: / Line 190: @@
 <tt>kde-config</tt> and all KDE programs accept <tt>--version</tt> as argument.
-==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?== <!--T:55-->
+==Qt-copy or Qt from qt.digia.com: if one were doing a clean build of trunk, which would be preferable?== <!--T:55-->
 <!--T:56-->

@@ Line 188: / Line 188: @@
 <!--T:54-->
-<tt>kde-config</tt> and all kde programs accept <tt>--version</tt> as argument.
+<tt>kde-config</tt> and all KDE programs accept <tt>--version</tt> as argument.
 ==Qt-copy or Qt from qt.nokia.com : if one were doing a clean build of trunk, which would be preferable?== <!--T:55-->

@@ Line 180: / Line 180: @@
 <!--T:52-->
-Yes, check the Building 2 Versions documentation.
+Yes, check Building KDE Software from git.kde.org video series:
 == How do I know which version of Qt/KDE I am using? == <!--T:53-->

@@ Line 135: / Line 135: @@
 <!--T:36-->
-See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].
+See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Get a KDE Contributor Account]].
 <!--T:37-->
-Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.
+Go to [http://identity.kde.org KDE Identity], fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.
 <!--T:38-->
-Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.
+Please also include the name of your [https://bugs.kde.org/ bugs.kde.org] account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.
 <!--T:39-->
@@ Line 152: / Line 152: @@
 <!--T:41-->
-Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)
+Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on [[Schedules]] page)
 <!--T:42-->

@@ Line 96: / Line 96: @@
 <!--T:26-->
 There are three requirements:
-* your app must compile with the latest version of KDE (git master or SVN trunk).
+* Your app must compile with the latest version of KDE (git master or SVN trunk).
-* your app must be stable.
+* Your app must be stable.
-* your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
+* Your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.
 See also the next question.

@@ Line 107: / Line 107: @@
 <blockquote>
 Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.
 <!--T:29-->
-:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.
+Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.
 <!--T:30-->
 On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.
 <!--T:31-->
 You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.
 <!--T:32-->
 In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.
 <!--T:33-->

@@ Line 62: / Line 62: @@
 <!--T:22-->
-You need to add the ignore list to the [miscellany] group in your ~/.subversion/config (all in one line):
+You need to add the ignore list to the [miscellany] group in your ~/.subversion/config:
 <syntaxhighlight lang="bash">
 [miscellany]

@@ Line 62: / Line 62: @@
 <!--T:22-->
-<syntaxhighlight lang="text">[miscellany]
+You need to add the ignore list to the [miscellany] group in your ~/.subversion/config (all in one line):
 global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
 config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
@@ Line 69: / Line 71: @@
 *_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
 Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
-*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
+*.o *.lo *.la #*# .*.rej *.rej *.pyc
-And to make svn diff ignore whitespace, and print function names:
+</syntaxhighlight>
-<syntaxhighlight lang="text">[helpers]
-diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>
+And to make svn diff ignore whitespace, and print function names:
 <!--T:23-->
 with the following in {{path|/usr/local/bin/_svndiff}}:
-<syntaxhighlight lang="text">#!/bin/sh
-exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>
+<syntaxhighlight lang="bash">
 <!--T:24-->

@@ Line 54: / Line 54: @@
 <!--T:20-->
-Yes
+Yes. There are many ways to do this:
-* Browse http://websvn.kde.org/ and https://projects.kde.org/
+* Browse [http://websvn.kde.org/ websvn.kde.org], [http://quickgit.kde.org/ quickgit.kde.org], and [https://projects.kde.org/ projects.kde.org]
-* Search the source code at http://lxr.kde.org/search
+* Search the source code at [http://lxr.kde.org/search lxr.kde.org/search]
-* Browse API docs generated from the source code at http://api.kde.org/
+* Browse API docs generated from the source code at [http://api.kde.org/ api.kde.org]
 == What should I put in my .subversion/config? == <!--T:21-->

@@ Line 49: / Line 49: @@
 <!--T:18-->
-See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.
+See the [[Special:myLanguage/Getting_Started#Building_and_Running_KDE_Software_From_Source|Building and Running KDE Software From Source]] section on the [[Special:myLanguage/Getting_Started|Getting Started]] page.
 == Can I access KDE source code online? == <!--T:19-->