Development/FAQs/General FAQ/zh-cn: Difference between revisions

From KDE TechBase
No edit summary
(Updating to match new version of source page)
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Proposed_deletion|Content is now at https://community.kde.org/KDE/FAQs/General_FAQ and this page may no longer be up-to-date. Translations are still available for this page, however.}}
<languages />
<languages />


== 我想要开发新的应用程序。有什么建议? ==
== I want to start this new application. What do you advise? ==


我们都同意需要编写大量的 KDE 应用程序。但同时也有很多现有的 KDE 应用程序需要你的帮助。
We all agree that there are plenty of KDE applications that need to be written. But there are also a lot of existing kde applications that need your help.


如果你想了解一下目前需要帮忙的地方,请看[http://www.kde.org/jobs/ 本页面]
To see the areas where help is needed, check [http://www.kde.org/jobs/ this page].


在开始新的应用程序前,检查 [http://www.kde-apps.org/ KDE-Apps.org] 上现有的应用程序,并在 [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] 邮件列表中进行咨询,看看是否有人已经开始类似的项目。
Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] and other open source software hosting services like [https://github.com/ GitHub], [https://code.google.com Google Code], and [http://sourceforge.net/ SourceForge] for existing applications and to ask on the  [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] mailing-list whether someone is already working on a similar project.


== 我是开发人员,我要如何帮助 KDE 呢?==
== I am a developer, how can I contribute to KDE software? ==


尽管 Calligra KDevelop 受到高度赞赏,它们只有极少数开发者,所以你可以从这里开始。提供帮助并不仅仅体现在加入 KDE 工作空间或 KDE 平台库的开发。KDE 是高度模块化的,所以你不必了解整个系统就能每次改善某个独立的方面。
Calligra and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a developer of the KDE workspaces or KDE platform libraries to help. The whole range of KDE software is very modular so you can perfectly improve one area without knowing how others work.


您也可以在 [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] 邮件列表问问是否有人需要协助。使用最新版 KDE 并且关注需要的东西。一个主题生成器?一个 konsole 计划编辑器?改善一个游戏?这些项目总是有小功能缺失。去实现它吧!
You can also ask on  [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] if someone needs help on an application.
Use the latest version of your favourite KDE software and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!


你是熟悉或关注于特定领域吗?查看是否有相关的应用程序,可以获得您的帮助。或者自己写一个。KDE 需要更多非 geek 导向的应用程序。
Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE especially welcomes more non-geek oriented applications.


== 我不是开发者,我要怎样帮忙 ==
== I am not a developer, how can I help? ==


有大量不需要开发技术的任务。撰写应用程序评论帮助 KDE 推广(请见 [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] 邮件列表),帮助文件团队(请见 [http://l10n.kde.org/docs/ i18n.kde.org/doc]),协助翻译(请见 [http://l10n.kde.org/ i18n.kde.org]),帮助过滤新增的 bug(请见 [https://bugs.kde.org/ bugs.kde.org])等。
There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo] mailing-list), help the documentation team (see [http://l10n.kde.org/docs/ i18n.kde.org/doc]), help the translations (see [http://l10n.kde.org/ i18n.kde.org]), help to filter the incoming bugs (see [https://bugs.kde.org/ bugs.kde.org]).


== 在哪里可以找到 Konqi 龙的图像? ==
== Where can I find images of Konqi the dragon? ==


一些人需要的 Konqi SDK [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2]<br />
The Konqi for some people SDK is at [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2]<br />
在这个网站还未停止更新前,它被上传到 [https://artist.kde.org artist.kde.org ]。
It was posted to artist.kde.org before that site ceased to be updated.


将来的图像在 [http://kde.org/stuff/clipart.php KDE merchandise].
Further images are on [http://kde.org/stuff/clipart.php KDE merchandise]. Also you can find some  unofficial Konqi images and models from [http://forum.kde.org/viewforum.php?f=254 Create Konqi with Krita Contest] and [http://sourceforge.net/projects/supertuxkart/ SuperTuxKart] game.


== 贡献 KDE 需要什么样的水平?我应该学习什么?阅读什么?==
== What is the level required to contribute to KDE? What should I learn? What should I read? ==


您需要了解 C++。阅读 Qt 的教学和浏览 Qt 的文件来熟悉 Qt。然后阅读 KDE 的教学和浏览架构和文件。您还可以阅读 KDE 的书籍。但你不用熟悉整个 KDE 的架构以成为 KDE 开发者。使用 KDE 的技术是很容易的,所以集中在你真正需要的,你可以以后再学习其他部分。[http://techbase.kde.org KDE 用户基地(本站)] [http://doc.qt.nokia.com/ doc.qt.nokia.com] (也在您的 {{path|$QTDIR/doc/html}}) 是宝贵的资源,要善用它们。然后浏览原始码,寻找范例目录,看看其他应用程序的写法。读写程序代码是最好的学习方法。
You need to know C++. Read the [http://qt-project.org/doc/qt-4.8/tutorials.html Qt tutorials] and browse the Qt docs to get familiar with what's available with Qt. Then read the [http://techbase.kde.org/Development/Tutorials KDE tutorials] and browse architecture and documentation. You can also read the [http://flossmanuals.net/kde-guide/ KDE Book], it can not harm. But you don't have to be familiar with the whole KDE architecture to become a KDE developer. Using KDE's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.digia.com/ doc.qt.digia.com] (also in your {{path|$QTDIR/doc/html}}) are invaluable resources, take advantage of them.
Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.


== 如何从 KDE git SVN 仓库获取 KDE 软件? ==
== How do I get KDE software from the KDE git or SVN repositories? ==


参阅[[Special:myLanguage/Getting_Started|开始]]页面的"从源代码编译和运行KDE软件"。
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.


== 可以在线访问 KDE 源码吗? ==
== Can I access KDE source code online? ==


可以
Yes. There are many ways to do this:
* 浏览代码: http://websvn.kde.org/
* Browse [http://websvn.kde.org/ websvn.kde.org], and [http://quickgit.kde.org/ quickgit.kde.org].
* 搜索代码: http://lxr.kde.org/search
* Search the source code at [http://lxr.kde.org/search lxr.kde.org/search]
* 浏览源代码生成的 API 文件: http://www.englishbreakfastnetwork.org/
* Browse API docs generated from the source code at [http://api.kde.org/ api.kde.org]
* Browse the source code on http://code.woboq.org/kde as in KDevelop


== 我的 .subversion/config 应该怎样配置? ==
== What should I put in my .subversion/config? ==


<syntaxhighlight lang="text">[miscellany]
You need to add the ignore list to the [miscellany] group in your ~/.subversion/config:
<syntaxhighlight lang="bash">
[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
Line 52: Line 60:
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc</syntaxhighlight>
*.o *.lo *.la #*# .*.rej *.rej *.pyc
svn diff 忽略空白并打印函数名:  
</syntaxhighlight>
<syntaxhighlight lang="text">[helpers]
 
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
 
<syntaxhighlight lang="bash">
[helpers]
diff-cmd = /usr/local/bin/_svndiff
</syntaxhighlight>
 
with the following in {{path|/usr/local/bin/_svndiff}}:


在 {{path|/usr/local/bin/_svndiff}} 中加入:
<syntaxhighlight lang="bash">
<syntaxhighlight lang="text">#!/bin/sh
#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>
exec /usr/bin/diff -b -u -p "$@"
</syntaxhighlight>


不要忘了将 {{path|/usr/local/bin/_svndiff}} 设置为可执行。
Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.


== 我想将应用程序加到 KDE ==
== I want to put my app in KDE ==


有三个要求:
There are three requirements:
* 您的应用程序必须使用最新版本的 KDE 编译(SVN trunk)。
* Your app must compile with the latest version of KDE (git master or SVN trunk).
* 您的应用程序必须是稳定的。
* Your app must be stable.
* 您的应用程序必须得到维护。你可能会得到大量的 bug 报告和愿望。人们期待你修复 bug 和实现有意义的愿望。
* 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.


== KDE 内部还是外部进行开发比较好? ==
== Is it better to develop inside or outside KDE? ==


核心开发者 Waldo Bastian 在邮件中解释:
As core developer Waldo Bastian explains in a copyrighted mail:
<blockquote>
<blockquote>
成为 KDE 的一份子,意味着你必须与他人一起工作。合作带来了好处,但同时也带来了责任。
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.
<br /><br />


:其中一些的优点是:你的程序代码会出现在所有发行版、人们可能会解决您的 bug、你可以得到免费的翻译和文件、你会得到大量的 bug 报告。
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.
<br /><br />


另一方面是缺点和责任:你将不得不为你的工作,与其他开发者沟通、其他人可能更改您的程序代码、你必须尊重发行冻结、你会得到极多的 bug 报告,人们期望你解决这些问题以及(what are they smoking?)维护你的程序代码。
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.
<br /><br />


你不能只选择优点,而忽略了随之而来的责任,它们是完整一体的,两者都要或都没有。
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.
<br /><br />


:一般来说,应该是软件的作者,选择把他的应用程序放进KDE的软件仓库。我们通常只有在作者发出请求时才把软件放在 KDE 仓库。反过来说,如果作者希望在外部开发他的应用程序,是他的权利。除非是应用程序的工作团队分裂,否则因为开发方式改变而 fork 应用程序是没有任何意义的。
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.
<br /><br />


'''''...您把程序代码以开源授权放在 KDE 仓库就相当于同意整个世界,特别是KDE,使用您的程序代码。KDE 将斟酌使用此权利,以保护KDE的利益,即使违背作者当下的意愿。</blockquote>
'''BUT'''... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.
</blockquote>


It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.
It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.


== 如何获得 KDE 仓库的写权限? ==
== How do I get write access to KDE repositories? ==


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]].


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.


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.


Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})
Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. {{path|~/.ssh/id_dsa.pub}})
Line 102: Line 125:
If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...
If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...


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)


A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE  Commit Policy]].
A detailed list of rules you should follow when committing to KDE repositories are listed in the [[Special:myLanguage/Policies/SVN_Commit_Policy|KDE  Commit Policy]].


== 我的应用程序还不稳定,但我想让它加入 KDE ==
== My app is not stable but I would like to have it in KDE ==


第一步,我们可以把它放在 playground("kde-alpha")。在那里开发它,完善后,申请将应用程序移动到适当的 KDE 包或 extragear 模块。
As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.


== 我不想失去我的 SVN 历史. ==
== I don't want to lose my SVN history. ==


This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.
This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.


== 什么是kdebindings? ==
== What is kdebindings? ==


它包含 Qt 的 Ruby、PHP 和 C# 绑定、KDE 的 Ruby、C# python 绑定以及让非 KDE 的应用程序作为 KPart 嵌入的 XParts。请见 TechBase 的 [[Special:myLanguage/Development/Languages|绑定页面]]
It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for  Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the [[Special:myLanguage/Development/Languages|binding page]] of TechBase.


== 功能冻结是否适用于 playground? ==
== Does the feature freeze apply to playground? ==


不,playground 不会发布套件。kdereview 和 extragear 也是相同的:他们没有冻结和发布。但如果你希望你的应用程序转移到套件包,请在 beta 发布之前先询问。
No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.


==可以同时有稳定和不稳定的 KDE 在同一台计算机上吗?==
==Can I have a stable and an unstable KDE on the same computer?==


Yes, check the Building 2 Versions documentation.  
Yes, check Building KDE Software from git.kde.org video series:
* [http://www.youtube.com/watch?v=cqnNVmJocR4 Building KDE Software from git.kde.org Part 1]
* [http://www.youtube.com/watch?v=OBJjk5q__Cc Building KDE Software from git.kde.org Part 2]
* [http://www.youtube.com/watch?v=SgwEnLeqsg8 Building KDE Software from git.kde.org Part 3]


== 我怎么知道我使用的 Qt/KDE 版本?==
== How do I know which version of Qt/KDE I am using? ==


<tt>kde-config</tt> 或在所有 KDE 程序都提供了 <tt>--version</tt> 参数选项。
<tt>kde-config</tt> and all KDE programs accept <tt>--version</tt> as argument.


==Qt-copy qt.nokia.com 的 Qt:应该用哪个做 trunk 建构?==
==Qt-copy or Qt from qt.digia.com: if one were doing a clean build of trunk, which would be preferable?==


任何一个您都可以使用。它们是二进制兼容的(往前和往后)。但 qt-copy 修正几个 Qt 最新版中的 bug。特别是从 qt-copy 建构,要注意补丁脚本。
You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.


== How can I checkout a single directory from a SVN module? ==
== How can I checkout a single directory from a SVN module? ==
Line 146: Line 172:
If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.
If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.


== 如何取得其中一个 KDE 应用程序作为一个独立的压缩文件? ==
== How can I get one of the KDE application as a standalone tarball? ==


kdesdk/scripts/svn2dist 是一个从 KDE 原始码树中提取应用程序的脚本,并打包为一个独立的应用程序。
kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.


== 如何关闭我自己的 bug 报告? ==
== How do I close my own bug reports? ==


If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.
If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.
Line 178: Line 204:
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.
In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.


== 如何监控别人所做的更改?==
== How can I monitor changes made by others? ==


[https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] 邮件列表即附带 KDE SVN 仓库所有修改的自动通知。但 KDE-commits 邮件列表流量是非常高的。另一种方法是 [http://commitfilter.kde.org/ CommitFilter],它可以只通知你感兴趣的领域。
The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.


[[Category:FAQs]]
[[Category:FAQs]]

Latest revision as of 10:10, 17 May 2019

 
Proposed for Deletion
This page has been proposed for deletion for the following reason:

Content is now at https://community.kde.org/KDE/FAQs/General_FAQ and this page may no longer be up-to-date. Translations are still available for this page, however.

Other languages:

I want to start this new application. What do you advise?

We all agree that there are plenty of KDE applications that need to be written. But there are also a lot of existing kde applications that need your help.

To see the areas where help is needed, check this page.

Before starting a new application, it's always a good idea to check KDE-Apps.org and other open source software hosting services like GitHub, Google Code, and SourceForge for existing applications and to ask on the kde-devel mailing-list whether someone is already working on a similar project.

I am a developer, how can I contribute to KDE software?

Calligra and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a developer of the KDE workspaces or KDE platform libraries to help. The whole range of KDE software is very modular so you can perfectly improve one area without knowing how others work.

You can also ask on kde-devel if someone needs help on an application. Use the latest version of your favourite KDE software and spot things that are needed. A theme generator? A konsole schema editor? Improve a game? There is always a small feature missing. Go and implement it!

Are you familiar or attracted with a specific field? See if there is a related application that could use your help. Or write one. KDE especially welcomes more non-geek oriented applications.

I am not a developer, how can I help?

There are plenty of tasks that don't require development skills. Write reviews of applications for the promoting of KDE (see the kde-promo mailing-list), help the documentation team (see i18n.kde.org/doc), help the translations (see i18n.kde.org), help to filter the incoming bugs (see bugs.kde.org).

Where can I find images of Konqi the dragon?

The Konqi for some people SDK is at ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on KDE merchandise. Also you can find some unofficial Konqi images and models from Create Konqi with Krita Contest and SuperTuxKart game.

What is the level required to contribute to KDE? What should I learn? What should I read?

You need to know C++. Read the Qt tutorials and browse the Qt docs to get familiar with what's available with Qt. Then read the KDE tutorials and browse architecture and documentation. You can also read the KDE Book, it can not harm. But you don't have to be familiar with the whole KDE architecture to become a KDE developer. Using KDE's technologies is quite easy, so concentrate on what you really need, you can learn the other bits later on. KDE TechBase and doc.qt.digia.com (also in your $QTDIR/doc/html) are invaluable resources, take advantage of them. Then, browse the source, look for the examples directories, see how the other did code their applications. Reading and writing code is the best way to learn.

How do I get KDE software from the KDE git or SVN repositories?

See the Building and Running KDE Software From Source section on the Getting Started page.

Can I access KDE source code online?

Yes. There are many ways to do this:

What should I put in my .subversion/config?

You need to add the ignore list to the [miscellany] group in your ~/.subversion/config:

[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_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

And to make svn diff ignore whitespace, and print function names:

[helpers]
diff-cmd = /usr/local/bin/_svndiff

with the following in /usr/local/bin/_svndiff:

#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"

Don't forget to make /usr/local/bin/_svndiff executable.

I want to put my app in KDE

There are three requirements:

  • Your app must compile with the latest version of KDE (git master or SVN trunk).
  • 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.

See also the next question.

Is it better to develop inside or outside KDE?

As core developer Waldo Bastian explains in a copyrighted mail:

Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.

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.

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.

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.

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.

BUT... by putting your code under and open source license and putting it in a KDE repository you give the world at large, as well as KDE in particular, the irrevocable right to use your code. And KDE will use that right at its discretion to protect the interests of KDE, even if that goes against the wishes of the author at that point in time.

It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.

How do I get write access to KDE repositories?

See full article at Get a KDE Contributor Account.

Go to KDE Identity, fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.

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.

Git requires use of an ssh key, and new accounts for SVN must also choose the svn+ssh protocol. Send a public ssh key (e.g. ~/.ssh/id_dsa.pub)

See also #How do I create a SSH key?

If you are contributing to an application that is not yours, it is a good idea to first submitting your coding as patches to the author and let him apply them. If the author is not maintaining his application, you might become the new maintainer...

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)

A detailed list of rules you should follow when committing to KDE repositories are listed in the KDE Commit Policy.

My app is not stable but I would like to have it in KDE

As a first step, we can put it in playground, which is essentially "kde-alpha". Develop it there and when it is ready, request that your app to be moved to the appropriate KDE package or the extragear module.

I don't want to lose my SVN history.

This is no longer possible with Subversion. Maybe in the future, if the server is upgraded and allows that. Note that for git this is not an issue.

What is kdebindings?

It contains Qt bindings for Ruby, PHP, C# to use Qt classes with those langages, KDE bindings for Ruby, C#, python to use KDE classes with those langages, and XParts to embed non-KDE apps as a KPart. Check the binding page of TechBase.

Does the feature freeze apply to playground?

No, playground are not a released packages. The same is true for kdereview and extragear: they are not frozen and released. But if you want your app to move to a package, ask for it before the beta-release.

Can I have a stable and an unstable KDE on the same computer?

Yes, check Building KDE Software from git.kde.org video series:

How do I know which version of Qt/KDE I am using?

kde-config and all KDE programs accept --version as argument.

Qt-copy or Qt from qt.digia.com: if one were doing a clean build of trunk, which would be preferable?

You can use either. They are binary compatible (forward and backward). There can be, however, a few bugfixes in qt-copy over the most recent Qt release. Especially if building from qt-copy, pay attention to the apply-patches script.

How can I checkout a single directory from a SVN module?

Checkout the top-level dir with 'svn co -N /modulename', 'cd modulename', 'svn up admin' to get the admin/ dir and then finally checkout the dir you want with 'svn up subdir'

For instance, to get only reaktivate from playground/utils: svn co -N /playground/utils; svn up reaktivate Then compile as usual.

The same answer applies to the question "How do I get a single language out of kde-i18n?".

If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.

How can I get one of the KDE application as a standalone tarball?

kdesdk/scripts/svn2dist is a script to extract an application from the KDE source tree and package it as a standalone application.

How do I close my own bug reports?

If you reported a bug that is fixed in a new release of KDE but is still reported as open, you can close it. It might happen because your bug is the same as another one, or simply because the developer fixed something without noticing that it would correct your bug.

You can do that from your Subversion commit. To do so, append to your commit message a line like this:

BUG: XXXXX where XXXXX is the bug report you want to close. If the report you're closing is adding a new feature, you can use FEATURE instead of BUG.

Managing a bug list is a huge task for the developers and they usually have a lot of bugs listed, some being fixed already without their knowledge, some being unreproducible, some without enough information to be corrected, etc. If you can help by managing and updating the list of outstanding bugs, you will be gladly welcome. And you will receive an even happier welcome if you provide a patch.

How do I create a SSH key?

SSH makes use of two keys: a private key and a public key. You should keep the private key secret at all times and only place it on machines over which you have direct control. Public, shared, and community machines are not suitable environments to store SSH private keys. Take action to help prevent theft of your SSH private key data. Setting a password on your SSH private key will help reduce the risks involved with private key theft.

Generate a key pair for each major location you work from. This helps to reduce the impact when your key gets stolen. When someone obtains access to your private key, your key can be abused in attempts to compromise KDE servers. Well known open source projects have been compromised this way in the past, YOU must help us to make sure that this doesn't happen with KDE servers as well. For that reason it is important to notify sysadmin (at) kde (dot) org immediately when you notice that someone may have had access to your private key for example when a computer on which it was stored has been hacked or infected with a virus, worm or trojan.

If you choose to make a backup of your SSH private key data, please ensure that any such backup is stored in a secure manner as well.

For the practical part, the following command can be used to generate a SSH private/public key pair with ssh-keygen -t dsa This will create a private key as ~/.ssh/id_dsa and a public key as ~/.ssh/id_dsa.pub.

There are times when you may want to use a key of a different name to the default, perhaps to use separate keys for different projects. To let SSH know which key you want to use for KDE.org, you can keep a list of servers and their corresponding keys in ~/.ssh/config. For example,

Host svn.kde.org 
IdentityFile ~/.ssh/id_dsa_kde

In order to use SSH to access KDE servers you need to send your public key to sysadmin (at) kde (dot) org.

How can I monitor changes made by others?

The kde-commits mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is CommitFilter which allows you to get notification for only those areas that interest you.