Development/FAQs/General FAQ/zh-cn

From KDE TechBase
< Development‎ | FAQs
Revision as of 10:25, 11 March 2016 by FuzzyBot (talk | contribs) (Updating to match new version of source page)
Other languages:

我想要开发新的应用程序。有什么建议？

我们都同意需要编写大量的 KDE 应用程序。但同时也有很多现有的 KDE 应用程序需要你的帮助。

如果你想了解一下目前需要帮忙的地方，请看本页面。

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.

我是开发人员，我要如何帮助 KDE 呢？

尽管 Calligra 和 KDevelop 受到高度赞赏，它们只有极少数开发者，所以你可以从这里开始。提供帮助并不仅仅体现在加入 KDE 工作空间或 KDE 平台库的开发。KDE 是高度模块化的，所以你不必了解整个系统就能每次改善某个独立的方面。

您也可以在 kde-devel 邮件列表问问是否有人需要协助。使用最新版 KDE 并且关注需要的东西。一个主题生成器？一个 konsole 计划编辑器？改善一个游戏？这些项目总是有小功能缺失。去实现它吧！

你是熟悉或关注于特定领域吗？查看是否有相关的应用程序，可以获得您的帮助。或者自己写一个。KDE 需要更多非 geek 导向的应用程序。

我不是开发者，我要怎样帮忙

有大量不需要开发技术的任务。撰写应用程序评论帮助 KDE 推广（请见 kde-promo 邮件列表），帮助文件团队（请见 i18n.kde.org/doc），协助翻译（请见 i18n.kde.org），帮助过滤新增的 bug（请见 bugs.kde.org）等。

在哪里可以找到 Konqi 龙的图像?

一些人需要的 Konqi 龙 SDK 在 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2
在这个网站还未停止更新前，它被上传到 artist.kde.org 。

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.

贡献 KDE 需要什么样的水平？我应该学习什么？阅读什么？

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.

如何从 KDE git 或 SVN 仓库获取 KDE 软件?

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

可以在线访问 KDE 源码吗?

Yes. There are many ways to do this:

我的 .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 "$@"

不要忘了将 /usr/local/bin/_svndiff 设置为可执行。

我想将应用程序加到 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.

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

但...您把程序代码以开源授权放在 KDE 仓库就相当于同意整个世界，特别是KDE，使用您的程序代码。KDE 将斟酌使用此权利，以保护 KDE 的利益，即使违背作者当下的意愿。

知道这个是重要的，但不要害怕。通常，事情进展得很好。在五年里，这仅仅发生了一次：一个开发者把他的作品保留在 KDE 中，尽管他想移除它。

如何获得 KDE 仓库的写权限?

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.

我的应用程序还不稳定，但我想让它加入 KDE

第一步，我们可以把它放在 playground（"kde-alpha"）。在那里开发它，完善后，申请将应用程序移动到适当的 KDE 包或 extragear 模块。

我不想失去我的 SVN 历史.

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 ?

它包含 Qt 的 Ruby、PHP 和 C# 绑定、KDE 的 Ruby、C# 和 python 绑定以及让非 KDE 的应用程序作为 KPart 嵌入的 XParts。请见 TechBase 的 绑定页面。

功能冻结是否适用于 playground？

不，playground 不会发布套件。kdereview 和 extragear 也是相同的：他们没有冻结和发布。但如果你希望你的应用程序转移到套件包，请在 beta 发布之前先询问。

可以同时有稳定和不稳定的 KDE 在同一台计算机上吗？

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

我怎么知道我使用的 Qt/KDE 版本？

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?

任何一个您都可以使用。它们是二进制兼容的（往前和往后）。但 qt-copy 修正几个 Qt 最新版中的 bug。特别是从 qt-copy 建构，要注意补丁脚本。

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.

如何取得其中一个 KDE 应用程序作为一个独立的压缩文件？

kdesdk/scripts/svn2dist 是一个从 KDE 原始码树中提取应用程序的脚本，并打包为一个独立的应用程序。

如何关闭我自己的 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.

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.

如何监控别人所做的更改？

kde-commits 邮件列表即附带 KDE SVN 仓库所有修改的自动通知。但 KDE-commits 邮件列表流量是非常高的。另一种方法是 CommitFilter，它可以只通知你感兴趣的领域。

Retrieved from "https://techbase.kde.org/index.php?title=Development/FAQs/General_FAQ/zh-cn&oldid=87473"