KDE TechBase - User contributions [en]

Development/FAQs/General FAQ/tr

2012-02-07T15:14:54Z

Doğan: Created page with "[https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] adresi üzerinden başka bir uygulama için yardıma ihtiyaç olup olmadığını sorabilirsiniz. Geliştirme yapark..."

<languages />
{{Template:I18n/Language Navigation Bar/tr|Development/FAQs/General FAQ}}

==Yeni bir uygulama geliştirmeye başlamak istiyorum. Bu konudaki önerileriniz nelerdir?==

Yazılması gereken daha birçok KDE uygulaması olduğu konusunda sizinle hemfikiriz. Ne var ki, hali hazırda yazılmış olan ve katkılarınızı bekleyen birçok KDE uygulaması da mevcuttur.

Katkılarınızı bekleyen konuları görmek için [http://www.kde.org/jobs/ bu sayfayı] ziyaret ediniz.

Yeni bir uygulama geliştirmeye başlamadan önce, [http://www.kde-apps.org/ KDE-Apps.org] adresinden var olan uygulamaları kontrol etmek ve [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] posta listesinde başka bir geliştiricinin benzer bir proje üzerinde çalışıp çalışmadığını sormak her daim iyi bir fikirdir.

==Geliştiriciyim, K Masaüstü Ortamının (KDE) geliştirilmesine nasıl katkıda bulunabilirim?==

Topladıkları övgülere rağmen, KOffice ve KDevelop bölümlerinde çok az geliştirici bulunmaktadır. Dilerseniz bu bölümleri kontrol edebilirsiniz. Bunun yanında, KDE gelişimine katkıda bulunmak için bir KDE çekirdek geliştiricisi olmanıza gerek yoktur. KDE oldukça modüler bir yapıya sahiptir ve bu nedenle tüm sistemin nasıl çalıştığını bilmenize gerek kalmadan geliştirme alanlarından herhangi birinde de mükemmel işler çıkarabilirsiniz.

[https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] adresi üzerinden başka bir uygulama için yardıma ihtiyaç olup olmadığını sorabilirsiniz.

Geliştirme yaparken K Masaüstü Ortamının son sürümünü kullanın ve neye ihtiyaç varsa ona yönelin. Bu bir tema oluşturucusu, konsol şema düzenleyicisi ya da bir oyunun geliştirilmesi olabilir. Her zaman küçük de olsa bir özellik eksiktir. Bunları tamamlamak da size düşüyor.

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 needs 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 [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]).

==Where can I find images of Konqi the dragon?==

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 />
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==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.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.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.

==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 [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[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</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/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:
<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.

: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.
</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.

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

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.

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}})

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 developer.kde.org)

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

==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 [[Special:myLanguage/Development/Languages|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 the Building 2 Versions documentation.

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

<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?==

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:
<code>svn co -N /playground/utils; svn up reaktivate</code>
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:

<Code>BUG: XXXXX</code> 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
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.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,
{{Input|1= 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 [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]]

Translations:Development/FAQs/General FAQ/8/tr

2012-02-07T15:14:53Z

[https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] adresi üzerinden başka bir uygulama için yardıma ihtiyaç olup olmadığını sorabilirsiniz.

Geliştirme yaparken K Masaüstü Ortamının son sürümünü kullanın ve neye ihtiyaç varsa ona yönelin. Bu bir tema oluşturucusu, konsol şema düzenleyicisi ya da bir oyunun geliştirilmesi olabilir. Her zaman küçük de olsa bir özellik eksiktir. Bunları tamamlamak da size düşüyor.

Development/FAQs/General FAQ/tr

2012-02-07T14:43:57Z

Doğan: Created page with "Topladıkları övgülere rağmen, KOffice ve KDevelop bölümlerinde çok az geliştirici bulunmaktadır. Dilerseniz bu bölümleri kontrol edebilirsiniz. Bunun yanında, KDE ge..."

<languages />
{{Template:I18n/Language Navigation Bar/tr|Development/FAQs/General FAQ}}

==Yeni bir uygulama geliştirmeye başlamak istiyorum. Bu konudaki önerileriniz nelerdir?==

Yazılması gereken daha birçok KDE uygulaması olduğu konusunda sizinle hemfikiriz. Ne var ki, hali hazırda yazılmış olan ve katkılarınızı bekleyen birçok KDE uygulaması da mevcuttur.

Katkılarınızı bekleyen konuları görmek için [http://www.kde.org/jobs/ bu sayfayı] ziyaret ediniz.

Yeni bir uygulama geliştirmeye başlamadan önce, [http://www.kde-apps.org/ KDE-Apps.org] adresinden var olan uygulamaları kontrol etmek ve [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] posta listesinde başka bir geliştiricinin benzer bir proje üzerinde çalışıp çalışmadığını sormak her daim iyi bir fikirdir.

==Geliştiriciyim, K Masaüstü Ortamının (KDE) geliştirilmesine nasıl katkıda bulunabilirim?==

Topladıkları övgülere rağmen, KOffice ve KDevelop bölümlerinde çok az geliştirici bulunmaktadır. Dilerseniz bu bölümleri kontrol edebilirsiniz. Bunun yanında, KDE gelişimine katkıda bulunmak için bir KDE çekirdek geliştiricisi olmanıza gerek yoktur. KDE oldukça modüler bir yapıya sahiptir ve bu nedenle tüm sistemin nasıl çalıştığını bilmenize gerek kalmadan geliştirme alanlarından herhangi birinde de mükemmel işler çıkarabilirsiniz.

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 KDE 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 needs 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 [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]).

==Where can I find images of Konqi the dragon?==

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 />
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==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.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.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.

==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 [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[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</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/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:
<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.

: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.
</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.

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

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.

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}})

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 developer.kde.org)

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

==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 [[Special:myLanguage/Development/Languages|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 the Building 2 Versions documentation.

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

<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?==

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:
<code>svn co -N /playground/utils; svn up reaktivate</code>
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:

<Code>BUG: XXXXX</code> 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
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.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,
{{Input|1= 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 [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]]

Translations:Development/FAQs/General FAQ/7/tr

2012-02-07T14:43:57Z

Topladıkları övgülere rağmen, KOffice ve KDevelop bölümlerinde çok az geliştirici bulunmaktadır. Dilerseniz bu bölümleri kontrol edebilirsiniz. Bunun yanında, KDE gelişimine katkıda bulunmak için bir KDE çekirdek geliştiricisi olmanıza gerek yoktur. KDE oldukça modüler bir yapıya sahiptir ve bu nedenle tüm sistemin nasıl çalıştığını bilmenize gerek kalmadan geliştirme alanlarından herhangi birinde de mükemmel işler çıkarabilirsiniz.

Development/FAQs/General FAQ/tr

2012-02-07T14:36:35Z

Doğan: Created page with "==Geliştiriciyim, K Masaüstü Ortamının (KDE) geliştirilmesine nasıl katkıda bulunabilirim?=="

<languages />
{{Template:I18n/Language Navigation Bar/tr|Development/FAQs/General FAQ}}

==Yeni bir uygulama geliştirmeye başlamak istiyorum. Bu konudaki önerileriniz nelerdir?==

Yazılması gereken daha birçok KDE uygulaması olduğu konusunda sizinle hemfikiriz. Ne var ki, hali hazırda yazılmış olan ve katkılarınızı bekleyen birçok KDE uygulaması da mevcuttur.

Katkılarınızı bekleyen konuları görmek için [http://www.kde.org/jobs/ bu sayfayı] ziyaret ediniz.

Yeni bir uygulama geliştirmeye başlamadan önce, [http://www.kde-apps.org/ KDE-Apps.org] adresinden var olan uygulamaları kontrol etmek ve [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] posta listesinde başka bir geliştiricinin benzer bir proje üzerinde çalışıp çalışmadığını sormak her daim iyi bir fikirdir.

==Geliştiriciyim, K Masaüstü Ortamının (KDE) geliştirilmesine nasıl katkıda bulunabilirim?==

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

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 KDE 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 needs 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 [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]).

==Where can I find images of Konqi the dragon?==

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 />
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==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.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.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.

==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 [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[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</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/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:
<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.

: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.
</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.

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

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.

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}})

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 developer.kde.org)

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

==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 [[Special:myLanguage/Development/Languages|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 the Building 2 Versions documentation.

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

<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?==

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:
<code>svn co -N /playground/utils; svn up reaktivate</code>
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:

<Code>BUG: XXXXX</code> 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
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.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,
{{Input|1= 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 [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]]

Translations:Development/FAQs/General FAQ/6/tr

2012-02-07T14:36:35Z

Doğan: Created page with "==Geliştiriciyim, K Masaüstü Ortamının (KDE) geliştirilmesine nasıl katkıda bulunabilirim?=="

==Geliştiriciyim, K Masaüstü Ortamının (KDE) geliştirilmesine nasıl katkıda bulunabilirim?==

Development/FAQs/General FAQ/tr

2012-02-07T14:35:00Z

Doğan:

<languages />
{{Template:I18n/Language Navigation Bar/tr|Development/FAQs/General FAQ}}

==Yeni bir uygulama geliştirmeye başlamak istiyorum. Bu konudaki önerileriniz nelerdir?==

Yazılması gereken daha birçok KDE uygulaması olduğu konusunda sizinle hemfikiriz. Ne var ki, hali hazırda yazılmış olan ve katkılarınızı bekleyen birçok KDE uygulaması da mevcuttur.

Katkılarınızı bekleyen konuları görmek için [http://www.kde.org/jobs/ bu sayfayı] ziyaret ediniz.

Yeni bir uygulama geliştirmeye başlamadan önce, [http://www.kde-apps.org/ KDE-Apps.org] adresinden var olan uygulamaları kontrol etmek ve [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] posta listesinde başka bir geliştiricinin benzer bir proje üzerinde çalışıp çalışmadığını sormak her daim iyi bir fikirdir.

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

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

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 KDE 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 needs 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 [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]).

==Where can I find images of Konqi the dragon?==

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 />
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==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.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.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.

==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 [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[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</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/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:
<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.

: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.
</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.

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

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.

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}})

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 developer.kde.org)

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

==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 [[Special:myLanguage/Development/Languages|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 the Building 2 Versions documentation.

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

<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?==

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:
<code>svn co -N /playground/utils; svn up reaktivate</code>
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:

<Code>BUG: XXXXX</code> 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
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.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,
{{Input|1= 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 [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]]

Translations:Development/FAQs/General FAQ/4/tr

2012-02-07T14:35:00Z

Doğan:

Katkılarınızı bekleyen konuları görmek için [http://www.kde.org/jobs/ bu sayfayı] ziyaret ediniz.

Translations:Development/FAQs/General FAQ/2/tr

2012-02-07T14:34:02Z

Doğan:

==Yeni bir uygulama geliştirmeye başlamak istiyorum. Bu konudaki önerileriniz nelerdir?==

Development/FAQs/General FAQ/tr

2012-02-07T14:34:02Z

Doğan:

<languages />
{{Template:I18n/Language Navigation Bar/tr|Development/FAQs/General FAQ}}

==Yeni bir uygulama geliştirmeye başlamak istiyorum. Bu konudaki önerileriniz nelerdir?==

Yazılması gereken daha birçok KDE uygulaması olduğu konusunda sizinle hemfikiriz. Ne var ki, hali hazırda yazılmış olan ve katkılarınızı bekleyen birçok KDE uygulaması da mevcuttur.

Katkılarınızı bekleyen konuları görmek için [http://www.kde.org/jobs/ this page] adresini ziyaret ediniz.

Yeni bir uygulama geliştirmeye başlamadan önce, [http://www.kde-apps.org/ KDE-Apps.org] adresinden var olan uygulamaları kontrol etmek ve [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] posta listesinde başka bir geliştiricinin benzer bir proje üzerinde çalışıp çalışmadığını sormak her daim iyi bir fikirdir.

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

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

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 KDE 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 needs 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 [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]).

==Where can I find images of Konqi the dragon?==

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 />
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==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.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.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.

==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 [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[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</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/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:
<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.

: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.
</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.

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

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.

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}})

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 developer.kde.org)

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

==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 [[Special:myLanguage/Development/Languages|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 the Building 2 Versions documentation.

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

<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?==

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:
<code>svn co -N /playground/utils; svn up reaktivate</code>
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:

<Code>BUG: XXXXX</code> 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
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.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,
{{Input|1= 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 [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]]

Development/FAQs/General FAQ/tr

2012-02-07T14:33:16Z

Doğan: Created page with "Yeni bir uygulama geliştirmeye başlamadan önce, [http://www.kde-apps.org/ KDE-Apps.org] adresinden var olan uygulamaları kontrol etmek ve [https://mail.kde.org/mailman/listin..."

<languages />
{{Template:I18n/Language Navigation Bar/tr|Development/FAQs/General FAQ}}

==Yeni bir uygulamaya geliştirmeye başlamak istiyorum. Bu konudaki önerileriniz nelerdir?==

Yazılması gereken daha birçok KDE uygulaması olduğu konusunda sizinle hemfikiriz. Ne var ki, hali hazırda yazılmış olan ve katkılarınızı bekleyen birçok KDE uygulaması da mevcuttur.

Katkılarınızı bekleyen konuları görmek için [http://www.kde.org/jobs/ this page] adresini ziyaret ediniz.

Yeni bir uygulama geliştirmeye başlamadan önce, [http://www.kde-apps.org/ KDE-Apps.org] adresinden var olan uygulamaları kontrol etmek ve [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] posta listesinde başka bir geliştiricinin benzer bir proje üzerinde çalışıp çalışmadığını sormak her daim iyi bir fikirdir.

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

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

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 KDE 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 needs 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 [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]).

==Where can I find images of Konqi the dragon?==

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 />
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==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.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.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.

==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 [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[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</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/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:
<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.

: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.
</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.

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

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.

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}})

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 developer.kde.org)

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

==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 [[Special:myLanguage/Development/Languages|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 the Building 2 Versions documentation.

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

<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?==

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:
<code>svn co -N /playground/utils; svn up reaktivate</code>
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:

<Code>BUG: XXXXX</code> 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
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.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,
{{Input|1= 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 [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]]

Translations:Development/FAQs/General FAQ/5/tr

2012-02-07T14:33:16Z

Yeni bir uygulama geliştirmeye başlamadan önce, [http://www.kde-apps.org/ KDE-Apps.org] adresinden var olan uygulamaları kontrol etmek ve [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] posta listesinde başka bir geliştiricinin benzer bir proje üzerinde çalışıp çalışmadığını sormak her daim iyi bir fikirdir.

Development/FAQs/General FAQ/tr

2012-02-07T14:28:48Z

Doğan: Created page with "Katkılarınızı bekleyen konuları görmek için [http://www.kde.org/jobs/ this page] adresini ziyaret ediniz."

<languages />
{{Template:I18n/Language Navigation Bar/tr|Development/FAQs/General FAQ}}

==Yeni bir uygulamaya geliştirmeye başlamak istiyorum. Bu konudaki önerileriniz nelerdir?==

Yazılması gereken daha birçok KDE uygulaması olduğu konusunda sizinle hemfikiriz. Ne var ki, hali hazırda yazılmış olan ve katkılarınızı bekleyen birçok KDE uygulaması da mevcuttur.

Katkılarınızı bekleyen konuları görmek için [http://www.kde.org/jobs/ this page] adresini ziyaret ediniz.

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] 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.

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

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

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 KDE 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 needs 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 [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]).

==Where can I find images of Konqi the dragon?==

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 />
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==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.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.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.

==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 [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[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</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/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:
<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.

: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.
</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.

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

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.

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}})

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 developer.kde.org)

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

==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 [[Special:myLanguage/Development/Languages|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 the Building 2 Versions documentation.

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

<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?==

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:
<code>svn co -N /playground/utils; svn up reaktivate</code>
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:

<Code>BUG: XXXXX</code> 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
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.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,
{{Input|1= 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 [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]]

Translations:Development/FAQs/General FAQ/4/tr

2012-02-07T14:28:48Z

Doğan: Created page with "Katkılarınızı bekleyen konuları görmek için [http://www.kde.org/jobs/ this page] adresini ziyaret ediniz."

Katkılarınızı bekleyen konuları görmek için [http://www.kde.org/jobs/ this page] adresini ziyaret ediniz.

Development/FAQs/General FAQ/tr

2012-02-07T14:27:17Z

Doğan: Created page with "Yazılması gereken daha birçok KDE uygulaması olduğu konusunda sizinle hemfikiriz. Ne var ki, hali hazırda yazılmış olan ve katkılarınızı bekleyen birçok KDE uygulam..."

<languages />
{{Template:I18n/Language Navigation Bar/tr|Development/FAQs/General FAQ}}

==Yeni bir uygulamaya geliştirmeye başlamak istiyorum. Bu konudaki önerileriniz nelerdir?==

Yazılması gereken daha birçok KDE uygulaması olduğu konusunda sizinle hemfikiriz. Ne var ki, hali hazırda yazılmış olan ve katkılarınızı bekleyen birçok KDE uygulaması da mevcuttur.

To see the areas where help is needed, check [http://www.kde.org/jobs/ this page].

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] 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.

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

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

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 KDE 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 needs 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 [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]).

==Where can I find images of Konqi the dragon?==

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 />
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==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.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.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.

==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 [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[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</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/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:
<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.

: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.
</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.

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

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.

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}})

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 developer.kde.org)

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

==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 [[Special:myLanguage/Development/Languages|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 the Building 2 Versions documentation.

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

<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?==

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:
<code>svn co -N /playground/utils; svn up reaktivate</code>
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:

<Code>BUG: XXXXX</code> 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
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.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,
{{Input|1= 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 [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]]

Translations:Development/FAQs/General FAQ/3/tr

2012-02-07T14:27:17Z

Yazılması gereken daha birçok KDE uygulaması olduğu konusunda sizinle hemfikiriz. Ne var ki, hali hazırda yazılmış olan ve katkılarınızı bekleyen birçok KDE uygulaması da mevcuttur.

Development/FAQs/General FAQ/tr

2012-02-07T14:20:37Z

Doğan: Created page with "==Yeni bir uygulamaya geliştirmeye başlamak istiyorum. Bu konudaki önerileriniz nelerdir?=="

<languages />
{{Template:I18n/Language Navigation Bar/tr|Development/FAQs/General FAQ}}

==Yeni bir uygulamaya geliştirmeye başlamak istiyorum. Bu konudaki önerileriniz nelerdir?==

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 [http://www.kde.org/jobs/ this page].

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] 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.

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

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

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 KDE 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 needs 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 [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]).

==Where can I find images of Konqi the dragon?==

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 />
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==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.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.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.

==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 [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[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</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/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:
<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.

: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.
</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.

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

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.

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}})

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 developer.kde.org)

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

==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 [[Special:myLanguage/Development/Languages|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 the Building 2 Versions documentation.

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

<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?==

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:
<code>svn co -N /playground/utils; svn up reaktivate</code>
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:

<Code>BUG: XXXXX</code> 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
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.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,
{{Input|1= 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 [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]]

Translations:Development/FAQs/General FAQ/2/tr

2012-02-07T14:20:36Z

Doğan: Created page with "==Yeni bir uygulamaya geliştirmeye başlamak istiyorum. Bu konudaki önerileriniz nelerdir?=="

==Yeni bir uygulamaya geliştirmeye başlamak istiyorum. Bu konudaki önerileriniz nelerdir?==

Development/FAQs/General FAQ/tr

2012-02-07T14:19:23Z

Doğan: Created page with "{{Template:I18n/Language Navigation Bar/tr|Development/FAQs/General FAQ}}"

<languages />
{{Template:I18n/Language Navigation Bar/tr|Development/FAQs/General FAQ}}

==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 [http://www.kde.org/jobs/ this page].

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] 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.

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

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

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 KDE 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 needs 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 [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]).

==Where can I find images of Konqi the dragon?==

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 />
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==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.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.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.

==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 [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[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</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/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:
<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.

: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.
</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.

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

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.

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}})

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 developer.kde.org)

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

==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 [[Special:myLanguage/Development/Languages|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 the Building 2 Versions documentation.

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

<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?==

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:
<code>svn co -N /playground/utils; svn up reaktivate</code>
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:

<Code>BUG: XXXXX</code> 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
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.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,
{{Input|1= 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 [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]]

Translations:Development/FAQs/General FAQ/1/tr

2012-02-07T14:19:23Z

Doğan: Created page with "{{Template:I18n/Language Navigation Bar/tr|Development/FAQs/General FAQ}}"

{{Template:I18n/Language Navigation Bar/tr|Development/FAQs/General FAQ}}

Translations:Development/FAQs/General FAQ/Page display title/tr

2012-02-07T14:19:10Z

Doğan: Created page with "Geliştirme/SSS/Sıkça Sorulanlar"

Geliştirme/SSS/Sıkça Sorulanlar

Development/FAQs/General FAQ/tr

2012-02-07T14:19:10Z

Doğan: Created page with "Geliştirme/SSS/Sıkça Sorulanlar"

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs/General FAQ}}

==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 [http://www.kde.org/jobs/ this page].

Before starting a new application, it's always a good idea to check [http://www.kde-apps.org/ KDE-Apps.org] 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.

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

KOffice and KDevelop, despite being very praised, have very few developers, so you might check there. There is no need to be a KDE core-developer to help. KDE is very modular so you can perfectely improve one area without knowing how the whole system works.

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 KDE 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 needs 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 [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]).

==Where can I find images of Konqi the dragon?==

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 />
It was posted to artist.kde.org before that site ceased to be updated.

Further images are on [http://kde.org/stuff/clipart.php KDE merchandise].

==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.
[http://techbase.kde.org KDE TechBase] and [http://doc.qt.nokia.com/ doc.qt.nokia.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.

==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 [[Special:myLanguage/Getting_Started|Getting_Started]] page.

==Can I access KDE source code online?==

Yes
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Search the source code at http://lxr.kde.org/search
* Browse API docs generated from the source code at http://api.kde.org/

==What should I put in my .subversion/config?==

<syntaxhighlight lang="text">[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</syntaxhighlight>
And to make svn diff ignore whitespace, and print function names:
<syntaxhighlight lang="text">[helpers]
diff-cmd = /usr/local/bin/_svndiff</syntaxhighlight>

with the following in {{path|/usr/local/bin/_svndiff}}:
<syntaxhighlight lang="text">#!/bin/sh
exec /usr/bin/diff -b -u -p "$@"</syntaxhighlight>

Don't forget to make {{path|/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:
<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.

: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.
</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.

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

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.

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}})

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 developer.kde.org)

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

==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 [[Special:myLanguage/Development/Languages|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 the Building 2 Versions documentation.

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

<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?==

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:
<code>svn co -N /playground/utils; svn up reaktivate</code>
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:

<Code>BUG: XXXXX</code> 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
<code>ssh-keygen -t dsa</code>
This will create a private key as {{path|~/.ssh/id_dsa}} and a public key as {{path|~/.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,
{{Input|1= 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 [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]]

Development/FAQs/Debugging FAQ/tr

2012-02-07T14:16:30Z

Doğan: Created page with "==Genel=="

<languages />
==Genel==

===How do I avoid Dr Konqi?===

You must set the environment variable KDE_DEBUG (to 1 or whatever you want in fact).

To get Dr Konqi back, unset the KDE_DEBUG environment variable.

Example:<br />
*To avoid Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*To see Dr Konqi:
::<code>unset KDE_DEBUG</code>

===How do I switch Dr Konqi to developer mode?===

Edit file $KDEHOME/share/config/drkonqirc and add the following:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===What is a core file? How do I get a core file?===

A core file is an image of the memory when your application crashed. Using the core file, you can know which variables were set and where your application crashed.

Some distributions disable the generation of core files. To re-enable them, use <code>ulimit -c unlimited</code>.

Once you have a core file for a crash, you can examine it with gdb appname core . This will open gdb on the core file for the given application. Once at the gdb prompt, the most useful command is <code>bt</code> which generates a backtrace of the crash.
For more information about how to use gdb, see [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|this page]]

===What tools are available to debug my application?===

*kDebug() (kdDebug() in KDE3) calls are a simple but efficient way to debug an application.
*gdb, the GNU debugger, is the quickest way to execute step-by-step and investigate variables (recommended versions are gdb >= 6.x)
*Valgrind
*kdbg is a nice graphical frontend to gdb with a KDE GUI. It has support for many Qt types (including QString).
*Memory leak tracer : See kdesdk/kmtrace. The README explains it all.
*qdbus and dbus-viewer from Qt allow to browse DBus interfaces and to easily make DBus calls.

Check [[Special:myLanguage/Development/Tools|this page]] and kdesdk, there are a bunch of useful scripts there.

===How do I print a QString in gdb?===

Check out kdesdk, and add this line to your ~/.gdbinit :
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
Then in gdb you can do <code>printqstring myqstring</code> to see its contents.
For instance, <code>QString myqstring = QString::fromLatin1("contents");</code> can be examined using

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

See the <tt>kde-devel-gdb</tt> file for the other macros it defines.

===I have no symbol when I debug an app that uses kpart, what should I do?===

You must stop just after the main to load the debugging symbols of the shared library. After that, you can debug normally.
One can go as far as creating a gdb macro, to stop right after the part was loaded. For kword, by example, I use:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===How do I debug an ioslave?===

See [[Development/Tutorials/Debugging/Debugging IOSlaves|debugging ioslaves]]

=== Why isn't my signal and slot connection working? ===

Here are some steps that you can use to troubleshoot why your signal/slot connection is not working (your slot does not get called for some reason).

1) Verify that the connect() doesn't print a warning to the console at runtime.

If it does, check that you wrote Q_OBJECT, that the parameter names are not in the connect, that the parameter types are compatible, and that the slot is defined, and that the moc was compiled.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false

==KDE 4 specific==

===Is there a preferred way to print debug output on stderr?===

Yes, you must use kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

It is possible to omit the debug area number when calling kDebug by adding the following code to your top-level CMakeLists.txt:

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

For more information, about this, see [http://www.kdedevelopers.org/node/3171 Allen Winter's blog post].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

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

Translations:Development/FAQs/Debugging FAQ/1/tr

2012-02-07T14:16:30Z

Doğan: Created page with "==Genel=="

==Genel==

Development/FAQs/Debugging FAQ/tr

2012-02-07T14:16:19Z

Doğan: Created page with "Geliştirme/Sıkça Sorulan Sorular/Hata Ayıklama ile ilgili Sıkça Sorulan Sorular"

<languages />
==General==

===How do I avoid Dr Konqi?===

You must set the environment variable KDE_DEBUG (to 1 or whatever you want in fact).

To get Dr Konqi back, unset the KDE_DEBUG environment variable.

Example:<br />
*To avoid Dr Konqi:
::<code>export KDE_DEBUG=1</code>
*To see Dr Konqi:
::<code>unset KDE_DEBUG</code>

===How do I switch Dr Konqi to developer mode?===

Edit file $KDEHOME/share/config/drkonqirc and add the following:
<syntaxhighlight lang="ini">
[drkonqi]
ConfigName=developer
</syntaxhighlight>

===What is a core file? How do I get a core file?===

A core file is an image of the memory when your application crashed. Using the core file, you can know which variables were set and where your application crashed.

Some distributions disable the generation of core files. To re-enable them, use <code>ulimit -c unlimited</code>.

Once you have a core file for a crash, you can examine it with gdb appname core . This will open gdb on the core file for the given application. Once at the gdb prompt, the most useful command is <code>bt</code> which generates a backtrace of the crash.
For more information about how to use gdb, see [[Special:myLanguage/Development/Tutorials/Debugging/Debugging_with_GDB|this page]]

===What tools are available to debug my application?===

*kDebug() (kdDebug() in KDE3) calls are a simple but efficient way to debug an application.
*gdb, the GNU debugger, is the quickest way to execute step-by-step and investigate variables (recommended versions are gdb >= 6.x)
*Valgrind
*kdbg is a nice graphical frontend to gdb with a KDE GUI. It has support for many Qt types (including QString).
*Memory leak tracer : See kdesdk/kmtrace. The README explains it all.
*qdbus and dbus-viewer from Qt allow to browse DBus interfaces and to easily make DBus calls.

Check [[Special:myLanguage/Development/Tools|this page]] and kdesdk, there are a bunch of useful scripts there.

===How do I print a QString in gdb?===

Check out kdesdk, and add this line to your ~/.gdbinit :
{{Input|1=source /path/to/kde/sources/kdesdk/scripts/kde-devel-gdb}}
Then in gdb you can do <code>printqstring myqstring</code> to see its contents.
For instance, <code>QString myqstring = QString::fromLatin1("contents");</code> can be examined using

{{Input|1=
(gdb) printqstring myqstring
$1 = "content"}}

See the <tt>kde-devel-gdb</tt> file for the other macros it defines.

===I have no symbol when I debug an app that uses kpart, what should I do?===

You must stop just after the main to load the debugging symbols of the shared library. After that, you can debug normally.
One can go as far as creating a gdb macro, to stop right after the part was loaded. For kword, by example, I use:
{{Input|1=
define startkword
break main
run
break 'KoDocument::KoDocument(int, QWidget *, char const *,
QObject *, char const *, bool)' cont}}

===How do I debug an ioslave?===

See [[Development/Tutorials/Debugging/Debugging IOSlaves|debugging ioslaves]]

=== Why isn't my signal and slot connection working? ===

Here are some steps that you can use to troubleshoot why your signal/slot connection is not working (your slot does not get called for some reason).

1) Verify that the connect() doesn't print a warning to the console at runtime.

If it does, check that you wrote Q_OBJECT, that the parameter names are not in the connect, that the parameter types are compatible, and that the slot is defined, and that the moc was compiled.

1b) Or you can just check to see what connect() returns as a bool. Although this won't give you the error message.
2) Verify that the signal is indeed emitted
3) Verify that the receiver isn't already deleted at that time
4) Verify that emitter->signalsBlocked() returns false

==KDE 4 specific==

===Is there a preferred way to print debug output on stderr?===

Yes, you must use kDebug():

<syntaxhighlight lang="cpp-qt">
#include <kdebug.h>
kDebug() << "KMyApp just started";
</syntaxhighlight>

The syntax is much like cout, you can use many native types between the "<<". This will print out a debugging message, which will automatically be turned off at release time (by <tt>--disable-debug</tt>). In case you want the message to still be there during releases, because it's a warning or an error, use <tt>kWarning()</tt> or <tt>kError()</tt>.

Components and libraries are advised to use a debug area number, as in kDebug(1234). For this, the number must be registered in kdelibs/kdecore/kdebug.areas. Debug areas make it possible to turn off or on the debug output for specific area numbers, using the {{program|kdebugdialog}} program, which is part of kdebase. <tt>kdebugdialog --fullmode</tt> also permits to control where to log debug output. It is usually not necessary to register area numbers for standalone applications, unless it's so complex that you want to divide the output into several areas.

It is possible to omit the debug area number when calling kDebug by adding the following code to your top-level CMakeLists.txt:

<code>
add_definitions(-DKDE_DEFAULT_DEBUG_AREA=XXXX)
</code>

For more information, about this, see [http://www.kdedevelopers.org/node/3171 Allen Winter's blog post].

To make it clear: do NOT use <tt>qDebug()</tt>, this one does not get disabled at releases. Also avoid using <tt>assert()</tt> or <tt>kFatal()</tt> which lead to a crash when something goes wrong and that is not a nice experience for the user. Better detect the error, output a <tt>kWarning()</tt> or <tt>kError()</tt>, and recover if possible.

To get timestamps with your debug output, which are useful for debugging multi-threaded, networked and asynchronous operations, <tt>export KDE_DEBUG_TIMESTAMP=1</tt> before running your app. Since KDE SC 4.5.

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

Translations:Development/FAQs/Debugging FAQ/Page display title/tr

2012-02-07T14:16:18Z

Doğan: Created page with "Geliştirme/Sıkça Sorulan Sorular/Hata Ayıklama ile ilgili Sıkça Sorulan Sorular"

Geliştirme/Sıkça Sorulan Sorular/Hata Ayıklama ile ilgili Sıkça Sorulan Sorular

Translations:Development/FAQs/5/tr

2012-02-07T14:15:04Z

Doğan: Created page with "Category:FAQs"

[[Category:FAQs]]

Development/FAQs/tr

2012-02-07T14:11:18Z

Doğan:

<languages />
{{Template:I18n/Language Navigation Bar/tr|Development/FAQs}}

:K Masaüstü Ortamının (KDE) Geliştirilmesinde yer almak isteyenler için
;[[Special:myLanguage/Development/FAQs/General FAQ|Sıkça Sorulanlar]]
:K Masaüstü Ortamı (KDE) Geliştiricileri için
;[[Special:myLanguage/Development/FAQs/Technical FAQ|Teknik konular ile ilgili sorular]]
:Uygulamalarında hata ayıklaması yapmak isteyenler için
;[[Special:myLanguage/Development/FAQs/Debugging FAQ|Hata ayıklama ile ilgili sorular]]

SSS Bölümünde yanıtı bulunmayan sorularınız varsa, bu soruları eklemeniz yeterlidir. Sorularınız muhtemelen diğer katılımcılar tarafından yanıtlanacaktır.

Soru ve cevap listeleri özgün halleriyle, sırasıyla, Philippe Fremy ve David Daure tarafından hazırlanmıştır.

Katkıda bulunanlar: Marco Krohn, Malte Starostik, Andreas Pour, Waldo Bastian, Lars Knoll, Triskelios, Eric Sigra, Rolf Dubitzky, Martijn Klingens, Karl-Heinz Zimmer, George Staikos.

[[Category:FAQs]]

Translations:Development/FAQs/1/tr

2012-02-07T14:11:18Z

Doğan:

Development/FAQs/tr

2012-02-07T14:10:20Z

Doğan:

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs}}

:K Masaüstü Ortamının (KDE) Geliştirilmesinde yer almak isteyenler için
;[[Special:myLanguage/Development/FAQs/General FAQ|Sıkça Sorulanlar]]
:K Masaüstü Ortamı (KDE) Geliştiricileri için
;[[Special:myLanguage/Development/FAQs/Technical FAQ|Teknik konular ile ilgili sorular]]
:Uygulamalarında hata ayıklaması yapmak isteyenler için
;[[Special:myLanguage/Development/FAQs/Debugging FAQ|Hata ayıklama ile ilgili sorular]]

SSS Bölümünde yanıtı bulunmayan sorularınız varsa, bu soruları eklemeniz yeterlidir. Sorularınız muhtemelen diğer katılımcılar tarafından yanıtlanacaktır.

Soru ve cevap listeleri özgün halleriyle, sırasıyla, Philippe Fremy ve David Daure tarafından hazırlanmıştır.

Katkıda bulunanlar: Marco Krohn, Malte Starostik, Andreas Pour, Waldo Bastian, Lars Knoll, Triskelios, Eric Sigra, Rolf Dubitzky, Martijn Klingens, Karl-Heinz Zimmer, George Staikos.

[[Category:FAQs]]

Translations:Development/FAQs/1/tr

2012-02-07T14:10:20Z

Doğan:

Development/FAQs/tr

2012-02-07T14:08:46Z

Doğan: Created page with "{{Template:I18n/Language Navigation Bar/tr|Development/FAQs}}"

Translations:Development/FAQs/1/tr

2012-02-07T14:08:46Z

Doğan: Created page with "{{Template:I18n/Language Navigation Bar/tr|Development/FAQs}}"

Development/FAQs/tr

2012-02-07T14:05:00Z

Doğan: Created page with "Katkıda bulunanlar: Marco Krohn, Malte Starostik, Andreas Pour, Waldo Bastian, Lars Knoll, Triskelios, Eric Sigra, Rolf Dubitzky, Martijn Klingens, Karl-Heinz Zimmer, George Sta..."

Translations:Development/FAQs/4/tr

2012-02-07T14:05:00Z

Katkıda bulunanlar: Marco Krohn, Malte Starostik, Andreas Pour, Waldo Bastian, Lars Knoll, Triskelios, Eric Sigra, Rolf Dubitzky, Martijn Klingens, Karl-Heinz Zimmer, George Staikos.

Development/FAQs/tr

2012-02-07T14:04:16Z

Doğan:

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs}}

:K Masaüstü Ortamının (KDE) Geliştirilmesinde yer almak isteyenler için
;[[Special:myLanguage/Development/FAQs/General FAQ|Sıkça Sorulanlar]]
:K Masaüstü Ortamı (KDE) Geliştiricileri için
;[[Special:myLanguage/Development/FAQs/Technical FAQ|Teknik konular ile ilgili sorular]]
:Uygulamalarında hata ayıklaması yapmak isteyenler için
;[[Special:myLanguage/Development/FAQs/Debugging FAQ|Hata ayıklama ile ilgili sorular]]

SSS Bölümünde yanıtı bulunmayan sorularınız varsa, bu soruları eklemeniz yeterlidir. Sorularınız muhtemelen diğer katılımcılar tarafından yanıtlanacaktır.

Soru ve cevap listeleri özgün halleriyle, sırasıyla, Philippe Fremy ve David Daure tarafından hazırlanmıştır.

Contributions from: Marco Krohn, Malte Starostik, Andreas Pour, Waldo Bastian, Lars Knoll, Triskelios, Eric Sigra, Rolf Dubitzky, Martijn Klingens, Karl-Heinz Zimmer, George Staikos.

[[Category:FAQs]]

Translations:Development/FAQs/3/tr

2012-02-07T14:04:16Z

Doğan:

SSS Bölümünde yanıtı bulunmayan sorularınız varsa, bu soruları eklemeniz yeterlidir. Sorularınız muhtemelen diğer katılımcılar tarafından yanıtlanacaktır.

Soru ve cevap listeleri özgün halleriyle, sırasıyla, Philippe Fremy ve David Daure tarafından hazırlanmıştır.

Development/FAQs/tr

2012-02-07T13:55:02Z

Doğan: Created page with "SSS Bölümünde yanıtı bulunmayan sorularınız varsa, bu soruları eklemeniz yeterlidir. Sorularınız muhtemelen diğer katılımcılar tarafından yanıtlanacaktır."

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs}}

:K Masaüstü Ortamının (KDE) Geliştirilmesinde yer almak isteyenler için
;[[Special:myLanguage/Development/FAQs/General FAQ|Sıkça Sorulanlar]]
:K Masaüstü Ortamı (KDE) Geliştiricileri için
;[[Special:myLanguage/Development/FAQs/Technical FAQ|Teknik konular ile ilgili sorular]]
:Uygulamalarında hata ayıklaması yapmak isteyenler için
;[[Special:myLanguage/Development/FAQs/Debugging FAQ|Hata ayıklama ile ilgili sorular]]

SSS Bölümünde yanıtı bulunmayan sorularınız varsa, bu soruları eklemeniz yeterlidir. Sorularınız muhtemelen diğer katılımcılar tarafından yanıtlanacaktır.

Contributions from: Marco Krohn, Malte Starostik, Andreas Pour, Waldo Bastian, Lars Knoll, Triskelios, Eric Sigra, Rolf Dubitzky, Martijn Klingens, Karl-Heinz Zimmer, George Staikos.

[[Category:FAQs]]

Translations:Development/FAQs/3/tr

2012-02-07T13:55:02Z

Doğan: Created page with "SSS Bölümünde yanıtı bulunmayan sorularınız varsa, bu soruları eklemeniz yeterlidir. Sorularınız muhtemelen diğer katılımcılar tarafından yanıtlanacaktır."

SSS Bölümünde yanıtı bulunmayan sorularınız varsa, bu soruları eklemeniz yeterlidir. Sorularınız muhtemelen diğer katılımcılar tarafından yanıtlanacaktır.

Development/FAQs/tr

2012-02-07T13:51:01Z

Doğan: Created page with ":K Masaüstü Ortamının (KDE) Geliştirilmesinde yer almak isteyenler için ;Sıkça Sorulanlar :K Masaüstü Ortamı (KDE) ..."

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs}}

:K Masaüstü Ortamının (KDE) Geliştirilmesinde yer almak isteyenler için
;[[Special:myLanguage/Development/FAQs/General FAQ|Sıkça Sorulanlar]]
:K Masaüstü Ortamı (KDE) Geliştiricileri için
;[[Special:myLanguage/Development/FAQs/Technical FAQ|Teknik konular ile ilgili sorular]]
:Uygulamalarında hata ayıklaması yapmak isteyenler için
;[[Special:myLanguage/Development/FAQs/Debugging FAQ|Hata ayıklama ile ilgili sorular]]

If you have questions which are not answered in the FAQs simply add them. Other contributors will probably answer.

Original question list by Philippe Fremy, answers by David Faure.

Contributions from: Marco Krohn, Malte Starostik, Andreas Pour, Waldo Bastian, Lars Knoll, Triskelios, Eric Sigra, Rolf Dubitzky, Martijn Klingens, Karl-Heinz Zimmer, George Staikos.

[[Category:FAQs]]

Translations:Development/FAQs/2/tr

2012-02-07T13:51:01Z

Doğan: Created page with ":K Masaüstü Ortamının (KDE) Geliştirilmesinde yer almak isteyenler için ;Sıkça Sorulanlar :K Masaüstü Ortamı (KDE) ..."

:K Masaüstü Ortamının (KDE) Geliştirilmesinde yer almak isteyenler için
;[[Special:myLanguage/Development/FAQs/General FAQ|Sıkça Sorulanlar]]
:K Masaüstü Ortamı (KDE) Geliştiricileri için
;[[Special:myLanguage/Development/FAQs/Technical FAQ|Teknik konular ile ilgili sorular]]
:Uygulamalarında hata ayıklaması yapmak isteyenler için
;[[Special:myLanguage/Development/FAQs/Debugging FAQ|Hata ayıklama ile ilgili sorular]]

Translations:Development/FAQs/Page display title/tr

2012-02-07T13:30:34Z

Doğan: Created page with "KDE Ortamında Geliştirme/Sıkça Sorulan Sorular"

KDE Ortamında Geliştirme/Sıkça Sorulan Sorular

Development/FAQs/tr

2012-02-07T13:30:34Z

Doğan: Created page with "KDE Ortamında Geliştirme/Sıkça Sorulan Sorular"

<languages />
{{Template:I18n/Language Navigation Bar|Development/FAQs}}

;[[Special:myLanguage/Development/FAQs/General FAQ|General questions]]
:How to get involved in KDE development
;[[Special:myLanguage/Development/FAQs/Technical FAQ|Technical questions]]
:Technical questions for KDE developers
;[[Special:myLanguage/Development/FAQs/Debugging FAQ|Debugging questions]]
:How to debug your application

If you have questions which are not answered in the FAQs simply add them. Other contributors will probably answer.

Original question list by Philippe Fremy, answers by David Faure.

Contributions from: Marco Krohn, Malte Starostik, Andreas Pour, Waldo Bastian, Lars Knoll, Triskelios, Eric Sigra, Rolf Dubitzky, Martijn Klingens, Karl-Heinz Zimmer, George Staikos.

[[Category:FAQs]]

Welcome to KDE TechBase/tr

2012-02-07T13:28:58Z

Doğan:

{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}

<languages />

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|colspan=2|[[Image:Discover.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_launch.svg|noframe|left|40px]] ||
;;[[:Getting_Started/tr|KDE Geliştirme Ortamının Düzenlenmesi]]
:KDE Geliştirme Ortamını
::'''&rsaquo;''' nasıl '''''edinebileceğinizi''''',
::'''&rsaquo;''' nasıl '''''yapılandırabileceğinizi''''' ve
::'''&rsaquo;''' nasıl '''''çalıştırabileceğinizi''''' öğrenin.
|-
| style="padding-left: 50px;"|[[Image:Action_configure.svg|noframe|left|40px]] ||
;;[[:Development/tr|KDE Ortamında Geliştirme]]
::[[:Development/Tutorials/tr|Dersler]] | [http://api.kde.org API Belgelendirmesi] | [[:Development/FAQs/tr|Sıkça Sorulan Sorular]] ve daha fazlası.
::''Benzer İçerikler'':
:*[[:Takvimler|Sürüm Takvimleri ve Eklenmesi Planlanan Özellikler]]
:*[[:İlkeler|Kod Paylaşımı ve Geliştirici Kılavuzu]]
|-
| style="padding-left: 50px;"|[[Image:Devices_system.svg|noframe|left|40px]] ||
;;[[:KDE Sistem Yönetimi|KDE Sistem Yönetimi]]
:KDE dağıtımlarını yöneten sistem yöneticileri için gerekli bilgiler.
|-
|colspan=2|[[Image:Interact.png|noframe]]
|-
| style="padding-left: 50px;"|[[Image:Action_favorites.svg|noframe|left|40px]] ||
;;[[:Katkıda Bulunun|KDE Takımına Katılım ve Katkıda Bulunun]]
:Topluluğumuza katılın, topluluktan bilgi alın, yamalara katkıda bulunun.
:''Benzer İçerikler:''
:*[[:İlkeler|KDE Projesi İlkeleri]]
:*[http://www.kde.org/support/support.php Bağışta Bulunun]

;[[:BYD|BYD ile ilgili bilgiler]]
:Geliştiriciler için Bağımsız Yazılım Dağıtıcılarına ilişkin bilgiler.
|-
|colspan=2|[[Image:Develop.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_wizard.svg|noframe|left|40px]] ||
;;[[:Projeler|KDE Projeleri]]
:Çeşitli KDE Projeleri için geliştirici wiki'leri, görev listeleri vb. gibi bağlantılar.

|}

Translations:Welcome to KDE TechBase/3/tr

2012-02-07T13:28:58Z

Doğan:

:[[:Development/Tutorials/tr|Dersler]] | [http://api.kde.org API Belgelendirmesi] | [[:Development/FAQs/tr|Sıkça Sorulan Sorular]] ve daha fazlası.

Welcome to KDE TechBase/tr

2012-02-07T13:28:13Z

Doğan:

{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}

<languages />

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|colspan=2|[[Image:Discover.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_launch.svg|noframe|left|40px]] ||
;;[[:Getting_Started/tr|KDE Geliştirme Ortamının Düzenlenmesi]]
:KDE Geliştirme Ortamını
::'''&rsaquo;''' nasıl '''''edinebileceğinizi''''',
::'''&rsaquo;''' nasıl '''''yapılandırabileceğinizi''''' ve
::'''&rsaquo;''' nasıl '''''çalıştırabileceğinizi''''' öğrenin.
|-
| style="padding-left: 50px;"|[[Image:Action_configure.svg|noframe|left|40px]] ||
;;[[:Development/tr|KDE Ortamında Geliştirme]]
:[[Special:myLanguage/Development/Tutorials|
Tutorials]] | [http://api.kde.org API Documentation] | [[Special:myLanguage/Development/FAQs|
FAQs]]
and more.
::''Benzer İçerikler'':
:*[[:Takvimler|Sürüm Takvimleri ve Eklenmesi Planlanan Özellikler]]
:*[[:İlkeler|Kod Paylaşımı ve Geliştirici Kılavuzu]]
|-
| style="padding-left: 50px;"|[[Image:Devices_system.svg|noframe|left|40px]] ||
;;[[:KDE Sistem Yönetimi|KDE Sistem Yönetimi]]
:KDE dağıtımlarını yöneten sistem yöneticileri için gerekli bilgiler.
|-
|colspan=2|[[Image:Interact.png|noframe]]
|-
| style="padding-left: 50px;"|[[Image:Action_favorites.svg|noframe|left|40px]] ||
;;[[:Katkıda Bulunun|KDE Takımına Katılım ve Katkıda Bulunun]]
:Topluluğumuza katılın, topluluktan bilgi alın, yamalara katkıda bulunun.
:''Benzer İçerikler:''
:*[[:İlkeler|KDE Projesi İlkeleri]]
:*[http://www.kde.org/support/support.php Bağışta Bulunun]

;[[:BYD|BYD ile ilgili bilgiler]]
:Geliştiriciler için Bağımsız Yazılım Dağıtıcılarına ilişkin bilgiler.
|-
|colspan=2|[[Image:Develop.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_wizard.svg|noframe|left|40px]] ||
;;[[:Projeler|KDE Projeleri]]
:Çeşitli KDE Projeleri için geliştirici wiki'leri, görev listeleri vb. gibi bağlantılar.

|}

Translations:Welcome to KDE TechBase/2/tr

2012-02-07T13:28:13Z

Doğan:

;[[:Development/tr|KDE Ortamında Geliştirme]]

Welcome to KDE TechBase/tr

2012-02-07T13:27:14Z

Doğan:

{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}

<languages />

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|colspan=2|[[Image:Discover.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_launch.svg|noframe|left|40px]] ||
;;[[:Getting_Started/tr|KDE Geliştirme Ortamının Düzenlenmesi]]
:KDE Geliştirme Ortamını
::'''&rsaquo;''' nasıl '''''edinebileceğinizi''''',
::'''&rsaquo;''' nasıl '''''yapılandırabileceğinizi''''' ve
::'''&rsaquo;''' nasıl '''''çalıştırabileceğinizi''''' öğrenin.
|-
| style="padding-left: 50px;"|[[Image:Action_configure.svg|noframe|left|40px]] ||
;[[Special:myLanguage/Development|
Developing with KDE]]
:[[Special:myLanguage/Development/Tutorials|
Tutorials]] | [http://api.kde.org API Documentation] | [[Special:myLanguage/Development/FAQs|
FAQs]]
and more.
::''Benzer İçerikler'':
:*[[:Takvimler|Sürüm Takvimleri ve Eklenmesi Planlanan Özellikler]]
:*[[:İlkeler|Kod Paylaşımı ve Geliştirici Kılavuzu]]
|-
| style="padding-left: 50px;"|[[Image:Devices_system.svg|noframe|left|40px]] ||
;;[[:KDE Sistem Yönetimi|KDE Sistem Yönetimi]]
:KDE dağıtımlarını yöneten sistem yöneticileri için gerekli bilgiler.
|-
|colspan=2|[[Image:Interact.png|noframe]]
|-
| style="padding-left: 50px;"|[[Image:Action_favorites.svg|noframe|left|40px]] ||
;;[[:Katkıda Bulunun|KDE Takımına Katılım ve Katkıda Bulunun]]
:Topluluğumuza katılın, topluluktan bilgi alın, yamalara katkıda bulunun.
:''Benzer İçerikler:''
:*[[:İlkeler|KDE Projesi İlkeleri]]
:*[http://www.kde.org/support/support.php Bağışta Bulunun]

;[[:BYD|BYD ile ilgili bilgiler]]
:Geliştiriciler için Bağımsız Yazılım Dağıtıcılarına ilişkin bilgiler.
|-
|colspan=2|[[Image:Develop.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_wizard.svg|noframe|left|40px]] ||
;;[[:Projeler|KDE Projeleri]]
:Çeşitli KDE Projeleri için geliştirici wiki'leri, görev listeleri vb. gibi bağlantılar.

|}

Translations:Welcome to KDE TechBase/2/tr

2012-02-07T13:27:14Z

Doğan:

[[Special:myLanguage/Development|
Developing with KDE]]

Welcome to KDE TechBase/tr

2012-02-07T13:26:44Z

Doğan:

{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}

<languages />

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|colspan=2|[[Image:Discover.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_launch.svg|noframe|left|40px]] ||
;;[[:Getting_Started/tr|KDE Geliştirme Ortamının Düzenlenmesi]]
:KDE Geliştirme Ortamını
::'''&rsaquo;''' nasıl '''''edinebileceğinizi''''',
::'''&rsaquo;''' nasıl '''''yapılandırabileceğinizi''''' ve
::'''&rsaquo;''' nasıl '''''çalıştırabileceğinizi''''' öğrenin.
|-
| style="padding-left: 50px;"|[[Image:Action_configure.svg|noframe|left|40px]] ||
;;[[:Development/tr|KDE Ortamında Geliştirme]]
:[[Special:myLanguage/Development/Tutorials|
Tutorials]] | [http://api.kde.org API Documentation] | [[Special:myLanguage/Development/FAQs|
FAQs]]
and more.
::''Benzer İçerikler'':
:*[[:Takvimler|Sürüm Takvimleri ve Eklenmesi Planlanan Özellikler]]
:*[[:İlkeler|Kod Paylaşımı ve Geliştirici Kılavuzu]]
|-
| style="padding-left: 50px;"|[[Image:Devices_system.svg|noframe|left|40px]] ||
;;[[:KDE Sistem Yönetimi|KDE Sistem Yönetimi]]
:KDE dağıtımlarını yöneten sistem yöneticileri için gerekli bilgiler.
|-
|colspan=2|[[Image:Interact.png|noframe]]
|-
| style="padding-left: 50px;"|[[Image:Action_favorites.svg|noframe|left|40px]] ||
;;[[:Katkıda Bulunun|KDE Takımına Katılım ve Katkıda Bulunun]]
:Topluluğumuza katılın, topluluktan bilgi alın, yamalara katkıda bulunun.
:''Benzer İçerikler:''
:*[[:İlkeler|KDE Projesi İlkeleri]]
:*[http://www.kde.org/support/support.php Bağışta Bulunun]

;[[:BYD|BYD ile ilgili bilgiler]]
:Geliştiriciler için Bağımsız Yazılım Dağıtıcılarına ilişkin bilgiler.
|-
|colspan=2|[[Image:Develop.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_wizard.svg|noframe|left|40px]] ||
;;[[:Projeler|KDE Projeleri]]
:Çeşitli KDE Projeleri için geliştirici wiki'leri, görev listeleri vb. gibi bağlantılar.

|}

Translations:Welcome to KDE TechBase/3/tr

2012-02-07T13:26:44Z

Doğan:

[[Special:myLanguage/Development/Tutorials|
Tutorials]] | [http://api.kde.org API Documentation] | [[Special:myLanguage/Development/FAQs|
FAQs]]
and more.

Welcome to KDE TechBase/tr

2012-02-07T13:26:28Z

Doğan:

{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}

<languages />

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|colspan=2|[[Image:Discover.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_launch.svg|noframe|left|40px]] ||
;;[[:Getting_Started/tr|KDE Geliştirme Ortamının Düzenlenmesi]]
:KDE Geliştirme Ortamını
::'''&rsaquo;''' nasıl '''''edinebileceğinizi''''',
::'''&rsaquo;''' nasıl '''''yapılandırabileceğinizi''''' ve
::'''&rsaquo;''' nasıl '''''çalıştırabileceğinizi''''' öğrenin.
|-
| style="padding-left: 50px;"|[[Image:Action_configure.svg|noframe|left|40px]] ||
;;[[:Development/tr|KDE Ortamında Geliştirme]]
:<span class="mw-translate-fuzzy">
Special:myLanguage/Development/Tutorials|
Tutorials]] | [http://api.kde.org API Documentation] | [[Special:myLanguage/Development/FAQs|
FAQs]]
and more.
</span>
::''Benzer İçerikler'':
:*[[:Takvimler|Sürüm Takvimleri ve Eklenmesi Planlanan Özellikler]]
:*[[:İlkeler|Kod Paylaşımı ve Geliştirici Kılavuzu]]
|-
| style="padding-left: 50px;"|[[Image:Devices_system.svg|noframe|left|40px]] ||
;;[[:KDE Sistem Yönetimi|KDE Sistem Yönetimi]]
:KDE dağıtımlarını yöneten sistem yöneticileri için gerekli bilgiler.
|-
|colspan=2|[[Image:Interact.png|noframe]]
|-
| style="padding-left: 50px;"|[[Image:Action_favorites.svg|noframe|left|40px]] ||
;;[[:Katkıda Bulunun|KDE Takımına Katılım ve Katkıda Bulunun]]
:Topluluğumuza katılın, topluluktan bilgi alın, yamalara katkıda bulunun.
:''Benzer İçerikler:''
:*[[:İlkeler|KDE Projesi İlkeleri]]
:*[http://www.kde.org/support/support.php Bağışta Bulunun]

;[[:BYD|BYD ile ilgili bilgiler]]
:Geliştiriciler için Bağımsız Yazılım Dağıtıcılarına ilişkin bilgiler.
|-
|colspan=2|[[Image:Develop.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_wizard.svg|noframe|left|40px]] ||
;;[[:Projeler|KDE Projeleri]]
:Çeşitli KDE Projeleri için geliştirici wiki'leri, görev listeleri vb. gibi bağlantılar.

|}

Translations:Welcome to KDE TechBase/3/tr

2012-02-07T13:26:28Z

Doğan:

Special:myLanguage/Development/Tutorials|
Tutorials]] | [http://api.kde.org API Documentation] | [[Special:myLanguage/Development/FAQs|
FAQs]]
and more.

Thread:User talk:Doğan/Başlangıç İçin/reply (11)

2012-02-07T13:16:29Z

Doğan: Reply to Başlangıç_İçin

Pain is good :) At least it teaches something. I hope, i haven't caused much trouble for you :(

Welcome to KDE TechBase/tr

2012-02-07T12:26:31Z

Doğan:

{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}

<languages />

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|colspan=2|[[Image:Discover.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_launch.svg|noframe|left|40px]] ||
;;[[:Getting_Started/tr|KDE Geliştirme Ortamının Düzenlenmesi]]
:KDE Geliştirme Ortamını
::'''&rsaquo;''' nasıl '''''edinebileceğinizi''''',
::'''&rsaquo;''' nasıl '''''yapılandırabileceğinizi''''' ve
::'''&rsaquo;''' nasıl '''''çalıştırabileceğinizi''''' öğrenin.
|-
| style="padding-left: 50px;"|[[Image:Action_configure.svg|noframe|left|40px]] ||
;;[[:Development/tr|KDE Ortamında Geliştirme]]
::[[:Geliştirme/Dersler|Dersler]] | [http://api.kde.org API Belgelendirmesi] | [[:Geliştirme/SSS|Sıkça Sorulan Sorular]] ve daha fazlası.
::''Benzer İçerikler'':
:*[[:Takvimler|Sürüm Takvimleri ve Eklenmesi Planlanan Özellikler]]
:*[[:İlkeler|Kod Paylaşımı ve Geliştirici Kılavuzu]]
|-
| style="padding-left: 50px;"|[[Image:Devices_system.svg|noframe|left|40px]] ||
;;[[:KDE Sistem Yönetimi|KDE Sistem Yönetimi]]
:KDE dağıtımlarını yöneten sistem yöneticileri için gerekli bilgiler.
|-
|colspan=2|[[Image:Interact.png|noframe]]
|-
| style="padding-left: 50px;"|[[Image:Action_favorites.svg|noframe|left|40px]] ||
;;[[:Katkıda Bulunun|KDE Takımına Katılım ve Katkıda Bulunun]]
:Topluluğumuza katılın, topluluktan bilgi alın, yamalara katkıda bulunun.
:''Benzer İçerikler:''
:*[[:İlkeler|KDE Projesi İlkeleri]]
:*[http://www.kde.org/support/support.php Bağışta Bulunun]

;[[:BYD|BYD ile ilgili bilgiler]]
:Geliştiriciler için Bağımsız Yazılım Dağıtıcılarına ilişkin bilgiler.
|-
|colspan=2|[[Image:Develop.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_wizard.svg|noframe|left|40px]] ||
;;[[:Projeler|KDE Projeleri]]
:Çeşitli KDE Projeleri için geliştirici wiki'leri, görev listeleri vb. gibi bağlantılar.

|}

Translations:Welcome to KDE TechBase/2/tr

2012-02-07T12:26:31Z

Doğan:

;[[:Development/tr|KDE Ortamında Geliştirme]]

Thread:User talk:Doğan/Başlangıç İçin/reply (9)

2012-02-07T12:24:06Z

Doğan: Reply to Başlangıç_İçin

I did what you asked for. Created Note/tr and Warning/tr and applied them in translations. Any other issues to be corrected?

Template:Note/tr

2012-02-07T12:18:30Z

Doğan: Created page with "{{Box|Not|2=40px{{{1}}} <div class="clear"></div> }} <noinclude> {{Template:I18n/Language Navigation Bar|Template:Note}} [[Category:Temp..."

{{Box|Not|2=[[Image:Note-box-icon.png|noframe|left|40px]]{{{1}}} <div class="clear"></div> }}
<noinclude>
{{Template:I18n/Language Navigation Bar|Template:Note}}

[[Category:Template]]
</noinclude>

Template:Warning/tr

2012-02-07T12:17:38Z

Doğan:

{{Box|1={{{3|Uyarı}}}|2=[[Image:Warning.png|noframe|left|40px]]{{{1}}} <div class="clear"></div> }}
<noinclude>

{{Template:I18n/Language Navigation Bar|Template:Warning}}

[[Category:Template]]
</noinclude>

Translations:Welcome to KDE TechBase/1/tr

2012-02-07T12:15:53Z

Doğan:

;[[:Getting_Started/tr|KDE Geliştirme Ortamının Düzenlenmesi]]
:KDE Geliştirme Ortamını
::'''&rsaquo;''' nasıl '''''edinebileceğinizi''''',
::'''&rsaquo;''' nasıl '''''yapılandırabileceğinizi''''' ve
::'''&rsaquo;''' nasıl '''''çalıştırabileceğinizi''''' öğrenin.

Welcome to KDE TechBase/tr

2012-02-07T12:15:53Z

Doğan:

{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}

<languages />

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|colspan=2|[[Image:Discover.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_launch.svg|noframe|left|40px]] ||
;;[[:Getting_Started/tr|KDE Geliştirme Ortamının Düzenlenmesi]]
:KDE Geliştirme Ortamını
::'''&rsaquo;''' nasıl '''''edinebileceğinizi''''',
::'''&rsaquo;''' nasıl '''''yapılandırabileceğinizi''''' ve
::'''&rsaquo;''' nasıl '''''çalıştırabileceğinizi''''' öğrenin.
|-
| style="padding-left: 50px;"|[[Image:Action_configure.svg|noframe|left|40px]] ||
;;[[:Geliştirme|KDE Ortamında Geliştirme]]
::[[:Geliştirme/Dersler|Dersler]] | [http://api.kde.org API Belgelendirmesi] | [[:Geliştirme/SSS|Sıkça Sorulan Sorular]] ve daha fazlası.
::''Benzer İçerikler'':
:*[[:Takvimler|Sürüm Takvimleri ve Eklenmesi Planlanan Özellikler]]
:*[[:İlkeler|Kod Paylaşımı ve Geliştirici Kılavuzu]]
|-
| style="padding-left: 50px;"|[[Image:Devices_system.svg|noframe|left|40px]] ||
;;[[:KDE Sistem Yönetimi|KDE Sistem Yönetimi]]
:KDE dağıtımlarını yöneten sistem yöneticileri için gerekli bilgiler.
|-
|colspan=2|[[Image:Interact.png|noframe]]
|-
| style="padding-left: 50px;"|[[Image:Action_favorites.svg|noframe|left|40px]] ||
;;[[:Katkıda Bulunun|KDE Takımına Katılım ve Katkıda Bulunun]]
:Topluluğumuza katılın, topluluktan bilgi alın, yamalara katkıda bulunun.
:''Benzer İçerikler:''
:*[[:İlkeler|KDE Projesi İlkeleri]]
:*[http://www.kde.org/support/support.php Bağışta Bulunun]

;[[:BYD|BYD ile ilgili bilgiler]]
:Geliştiriciler için Bağımsız Yazılım Dağıtıcılarına ilişkin bilgiler.
|-
|colspan=2|[[Image:Develop.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_wizard.svg|noframe|left|40px]] ||
;;[[:Projeler|KDE Projeleri]]
:Çeşitli KDE Projeleri için geliştirici wiki'leri, görev listeleri vb. gibi bağlantılar.

|}

Getting Started/tr

2012-02-07T12:15:09Z

Doğan:

<languages />

{{Warning/tr|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

{{Template:I18n/Language Navigation Bar|Başlarken}}

== Giriş ==

KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır.

<span class="mw-translate-fuzzy">
Aşağıdaki bağlantılarda KDE Topluluğuna katılmakla ilgili daha genel bilgilere ulaşabilirsiniz:
* [http://kde.org/community/getinvolved/ KDE Topluluğuna Katılın]
* [[:Katkıda Bulunun|KDE'ye Katkıda Bulunun]]
</span>

KDE TechBase Geliştirici Üssü'nün bu alt bölümü, KDE Topluluğunun geliştirmeyle ilgili kesimine katılmanıza yardımcı olmak amacıyla tasarlanmıştır. Bu alt bölümde KDE yazılımının yapısı ve nasıl yapılandırıldığı ve bu yapılandırmada nasıl yer alabileceğiniz anlatılmaktadır.

<span class="mw-translate-fuzzy">
{{Note/tr|'''Hızlı bir başlangıç için:''' Ne yaptığınızı bilmeksizin başlamak için sabırsızlanıyorsanız, doğrudan "Bir [[:Başlangıç İçin/Yapılandırma#Betikli_Yapılandırmalar|Yapılandırma Betiği]]'nin Kullanılması" bölümüne geçebilirsiniz, fakat öncesinde bu belgelendirmeyi okumanız şiddetle tavsiye olunur.}}
</span>

== KDE Yazılımının Kullanılması ==

Eğer sadece bilgisayarınızdaki günlük kullanım gereksinimleriniz için kararlı bir KDE yazılımı kullanmak istiyorsanız, KDE yazılımını kendiniz yapılandırmak zorunda değilsiniz. Bunun yerine kullandığınız Linux dağıtımının paket yöneticisi tarafından sunulan KDE paketini kurabilirsiniz.

<span class="mw-translate-fuzzy">
Bunu nasıl yapacağınızı öğrenmek için en iyi yer kullandığınız dağıtımın bilindik destek kanallarıdır; tabi aşağıdaki bağlantılarda yer alan bilgiler de sizin için yararlı olabilir:
* [http://www.kde.org/download/distributions.php KDE Desteği Veren Linux Dağıtımları]
* [[:Başlangıç İçin/Yapılandırma/Dağıtımlar|KDE Yazılımının Linux ve BSD Dağıtımlarına Kurulması]]
* [[:Prjeler/Windows ve KDE/Kurulum|Windows'a KDE Kurulumu]]
* KDE Yazılımının Mac OS X için henüz mevcut bir kur dosyası yoktur ancak [http://mac.kde.org/?id=build MacPorts or Fink] bağlantısını kullanarak yapılandırma işleminizi kolaylaştırabilirsiniz.
</span>

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Special:myLanguage/Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Browsing the code ==
The KDE project is all free and open source. You can view its source code and make changes.

http://projects.kde.org hosts the source for many KDE-related initiatives, including [https://projects.kde.org/projects/kde KDE itself]. Choose a piece of KDE such as KDE Libraries, then click Repository to browse its source. [[Getting_Started/Sources]] explains the organization of KDE source code.

There are other utilities to browse the source code:

* http://lxr.kde.org/search lets you search the code ''(may be out of date?)''
* http://api.kde.org lets you browse API documentation generated from the code. You can search for class names, but not filenames.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Special:myLanguage/Getting_Started/Build/Methods|Build Methods page]].



The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[Special:myLanguage/Getting_Started/Sources|How the KDE Source Code is structured]]
* [[Special:myLanguage/Getting_Started/Build|How to Build and Install the software]]
* [[Special:myLanguage/Getting_Started/Run/Nested_Session|How to Run a nested session of KDE]]
* [[Special:myLanguage/Getting_Started/Run/Full_Session|How to Run a full session of KDE]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Special:myLanguage/Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Special:myLanguage/Development/Software_Engineering_Framework|The KDE Software Engineering Framework]]
* [[Special:myLanguage/Policies|KDE Development Policies and Procedures to follow]]
* [[Special:myLanguage/Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Special:myLanguage/Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [[Special:myLanguage/Development/Tutorials/Using_Qt_Creator|Qt Creator]]
* [http://www.kdevelop.org/ KDevelop 4]
* [[Special:myLanguage/Development/Tools/Eclipse|Eclipse]]
* [[Special:myLanguage/Getting_Started/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Special:myLanguage/Contribute|Contribute]]
* [[Special:myLanguage/Contribute/Send_Patches|Send Patches]]
* [[Special:myLanguage/Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Translations:Getting Started/Page display title/tr

2012-02-07T12:14:49Z

Doğan:

Başlarken

Getting Started/tr

2012-02-07T12:14:49Z

Doğan:

<languages />

{{Warning/tr|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

{{Template:I18n/Language Navigation Bar|Başlangıç İçin}}

== Giriş ==

KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır.

<span class="mw-translate-fuzzy">
Aşağıdaki bağlantılarda KDE Topluluğuna katılmakla ilgili daha genel bilgilere ulaşabilirsiniz:
* [http://kde.org/community/getinvolved/ KDE Topluluğuna Katılın]
* [[:Katkıda Bulunun|KDE'ye Katkıda Bulunun]]
</span>

KDE TechBase Geliştirici Üssü'nün bu alt bölümü, KDE Topluluğunun geliştirmeyle ilgili kesimine katılmanıza yardımcı olmak amacıyla tasarlanmıştır. Bu alt bölümde KDE yazılımının yapısı ve nasıl yapılandırıldığı ve bu yapılandırmada nasıl yer alabileceğiniz anlatılmaktadır.

<span class="mw-translate-fuzzy">
{{Note/tr|'''Hızlı bir başlangıç için:''' Ne yaptığınızı bilmeksizin başlamak için sabırsızlanıyorsanız, doğrudan "Bir [[:Başlangıç İçin/Yapılandırma#Betikli_Yapılandırmalar|Yapılandırma Betiği]]'nin Kullanılması" bölümüne geçebilirsiniz, fakat öncesinde bu belgelendirmeyi okumanız şiddetle tavsiye olunur.}}
</span>

== KDE Yazılımının Kullanılması ==

Eğer sadece bilgisayarınızdaki günlük kullanım gereksinimleriniz için kararlı bir KDE yazılımı kullanmak istiyorsanız, KDE yazılımını kendiniz yapılandırmak zorunda değilsiniz. Bunun yerine kullandığınız Linux dağıtımının paket yöneticisi tarafından sunulan KDE paketini kurabilirsiniz.

<span class="mw-translate-fuzzy">
Bunu nasıl yapacağınızı öğrenmek için en iyi yer kullandığınız dağıtımın bilindik destek kanallarıdır; tabi aşağıdaki bağlantılarda yer alan bilgiler de sizin için yararlı olabilir:
* [http://www.kde.org/download/distributions.php KDE Desteği Veren Linux Dağıtımları]
* [[:Başlangıç İçin/Yapılandırma/Dağıtımlar|KDE Yazılımının Linux ve BSD Dağıtımlarına Kurulması]]
* [[:Prjeler/Windows ve KDE/Kurulum|Windows'a KDE Kurulumu]]
* KDE Yazılımının Mac OS X için henüz mevcut bir kur dosyası yoktur ancak [http://mac.kde.org/?id=build MacPorts or Fink] bağlantısını kullanarak yapılandırma işleminizi kolaylaştırabilirsiniz.
</span>

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Special:myLanguage/Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Browsing the code ==
The KDE project is all free and open source. You can view its source code and make changes.

http://projects.kde.org hosts the source for many KDE-related initiatives, including [https://projects.kde.org/projects/kde KDE itself]. Choose a piece of KDE such as KDE Libraries, then click Repository to browse its source. [[Getting_Started/Sources]] explains the organization of KDE source code.

There are other utilities to browse the source code:

* http://lxr.kde.org/search lets you search the code ''(may be out of date?)''
* http://api.kde.org lets you browse API documentation generated from the code. You can search for class names, but not filenames.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Special:myLanguage/Getting_Started/Build/Methods|Build Methods page]].



The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[Special:myLanguage/Getting_Started/Sources|How the KDE Source Code is structured]]
* [[Special:myLanguage/Getting_Started/Build|How to Build and Install the software]]
* [[Special:myLanguage/Getting_Started/Run/Nested_Session|How to Run a nested session of KDE]]
* [[Special:myLanguage/Getting_Started/Run/Full_Session|How to Run a full session of KDE]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Special:myLanguage/Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Special:myLanguage/Development/Software_Engineering_Framework|The KDE Software Engineering Framework]]
* [[Special:myLanguage/Policies|KDE Development Policies and Procedures to follow]]
* [[Special:myLanguage/Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Special:myLanguage/Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [[Special:myLanguage/Development/Tutorials/Using_Qt_Creator|Qt Creator]]
* [http://www.kdevelop.org/ KDevelop 4]
* [[Special:myLanguage/Development/Tools/Eclipse|Eclipse]]
* [[Special:myLanguage/Getting_Started/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Special:myLanguage/Contribute|Contribute]]
* [[Special:myLanguage/Contribute/Send_Patches|Send Patches]]
* [[Special:myLanguage/Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Translations:Getting Started/7/tr

2012-02-07T12:09:23Z

Doğan:

!!FUZZY!!{{Note/tr|'''Hızlı bir başlangıç için:''' Ne yaptığınızı bilmeksizin başlamak için sabırsızlanıyorsanız, doğrudan "Bir [[:Başlangıç İçin/Yapılandırma#Betikli_Yapılandırmalar|Yapılandırma Betiği]]'nin Kullanılması" bölümüne geçebilirsiniz, fakat öncesinde bu belgelendirmeyi okumanız şiddetle tavsiye olunur.}}

Template:Warning/tr

2012-02-07T12:06:47Z

Doğan: Created page with "{{Box|Not|2=40px{{{1}}} <div class="clear"></div> }} <noinclude> {{Template:I18n/Language Navigation Bar|Template:Note}} [[Category:Temp..."

{{Box|Not|2=[[Image:Note-box-icon.png|noframe|left|40px]]{{{1}}} <div class="clear"></div> }}
<noinclude>
{{Template:I18n/Language Navigation Bar|Template:Note}}

[[Category:Template]]
</noinclude>

Thread:User talk:Doğan/Başlangıç İçin/reply (7)

2012-02-06T09:24:17Z

Doğan: Reply to Başlangıç_İçin

Yes those links you mentioned are the ones to be removed. However I couldn't get the last thing you asked. Am I supposed to create a new template just like in:

http://techbase.kde.org/Getting_Started/tr

under the language bar it says "Template:Warning/tr".

Is that what you asked?

(Very very sorry for the trouble. I'm not so good at working on wiki. I may have caused more trouble than the amount I contributed)

Getting Started/tr

2012-02-06T09:17:08Z

Doğan:

<languages />

{{Warning/tr|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

{{Template:I18n/Language Navigation Bar|Başlangıç İçin}}

== Giriş ==

KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır.

<span class="mw-translate-fuzzy">
Aşağıdaki bağlantılarda KDE Topluluğuna katılmakla ilgili daha genel bilgilere ulaşabilirsiniz:
* [http://kde.org/community/getinvolved/ KDE Topluluğuna Katılın]
* [[:Katkıda Bulunun|KDE'ye Katkıda Bulunun]]
</span>

KDE TechBase Geliştirici Üssü'nün bu alt bölümü, KDE Topluluğunun geliştirmeyle ilgili kesimine katılmanıza yardımcı olmak amacıyla tasarlanmıştır. Bu alt bölümde KDE yazılımının yapısı ve nasıl yapılandırıldığı ve bu yapılandırmada nasıl yer alabileceğiniz anlatılmaktadır.

<span class="mw-translate-fuzzy">
{{Note_(tr)|'''Hızlı bir başlangıç için:''' Ne yaptığınızı bilmeksizin başlamak için sabırsızlanıyorsanız, doğrudan "Bir [[:Başlangıç İçin/Yapılandırma#Betikli_Yapılandırmalar|Yapılandırma Betiği]]'nin Kullanılması" bölümüne geçebilirsiniz, fakat öncesinde bu belgelendirmeyi okumanız şiddetle tavsiye olunur.}}
</span>

== KDE Yazılımının Kullanılması ==

Eğer sadece bilgisayarınızdaki günlük kullanım gereksinimleriniz için kararlı bir KDE yazılımı kullanmak istiyorsanız, KDE yazılımını kendiniz yapılandırmak zorunda değilsiniz. Bunun yerine kullandığınız Linux dağıtımının paket yöneticisi tarafından sunulan KDE paketini kurabilirsiniz.

<span class="mw-translate-fuzzy">
Bunu nasıl yapacağınızı öğrenmek için en iyi yer kullandığınız dağıtımın bilindik destek kanallarıdır; tabi aşağıdaki bağlantılarda yer alan bilgiler de sizin için yararlı olabilir:
* [http://www.kde.org/download/distributions.php KDE Desteği Veren Linux Dağıtımları]
* [[:Başlangıç İçin/Yapılandırma/Dağıtımlar|KDE Yazılımının Linux ve BSD Dağıtımlarına Kurulması]]
* [[:Prjeler/Windows ve KDE/Kurulum|Windows'a KDE Kurulumu]]
* KDE Yazılımının Mac OS X için henüz mevcut bir kur dosyası yoktur ancak [http://mac.kde.org/?id=build MacPorts or Fink] bağlantısını kullanarak yapılandırma işleminizi kolaylaştırabilirsiniz.
</span>

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Special:myLanguage/Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Browsing the code ==
The KDE project is all free and open source. You can view its source code and make changes.

http://projects.kde.org hosts the source for many KDE-related initiatives, including [https://projects.kde.org/projects/kde KDE itself]. Choose a piece of KDE such as KDE Libraries, then click Repository to browse its source. [[Getting_Started/Sources]] explains the organization of KDE source code.

There are other utilities to browse the source code:

* http://lxr.kde.org/search lets you search the code ''(may be out of date?)''
* http://api.kde.org lets you browse API documentation generated from the code. You can search for class names, but not filenames.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Special:myLanguage/Getting_Started/Build/Methods|Build Methods page]].



The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[Special:myLanguage/Getting_Started/Sources|How the KDE Source Code is structured]]
* [[Special:myLanguage/Getting_Started/Build|How to Build and Install the software]]
* [[Special:myLanguage/Getting_Started/Run/Nested_Session|How to Run a nested session of KDE]]
* [[Special:myLanguage/Getting_Started/Run/Full_Session|How to Run a full session of KDE]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Special:myLanguage/Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Special:myLanguage/Development/Software_Engineering_Framework|The KDE Software Engineering Framework]]
* [[Special:myLanguage/Policies|KDE Development Policies and Procedures to follow]]
* [[Special:myLanguage/Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Special:myLanguage/Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [[Special:myLanguage/Development/Tutorials/Using_Qt_Creator|Qt Creator]]
* [http://www.kdevelop.org/ KDevelop 4]
* [[Special:myLanguage/Development/Tools/Eclipse|Eclipse]]
* [[Special:myLanguage/Getting_Started/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Special:myLanguage/Contribute|Contribute]]
* [[Special:myLanguage/Contribute/Send_Patches|Send Patches]]
* [[Special:myLanguage/Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Translations:Getting Started/1/tr

2012-02-06T09:17:08Z

Doğan:

{{Warning/tr|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

Getting Started/tr

2012-02-06T09:15:50Z

Doğan:

<languages />

<span class="mw-translate-fuzzy">
{{Warning/tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}
</span>

{{Template:I18n/Language Navigation Bar|Başlangıç İçin}}

== Giriş ==

KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır.

<span class="mw-translate-fuzzy">
Aşağıdaki bağlantılarda KDE Topluluğuna katılmakla ilgili daha genel bilgilere ulaşabilirsiniz:
* [http://kde.org/community/getinvolved/ KDE Topluluğuna Katılın]
* [[:Katkıda Bulunun|KDE'ye Katkıda Bulunun]]
</span>

KDE TechBase Geliştirici Üssü'nün bu alt bölümü, KDE Topluluğunun geliştirmeyle ilgili kesimine katılmanıza yardımcı olmak amacıyla tasarlanmıştır. Bu alt bölümde KDE yazılımının yapısı ve nasıl yapılandırıldığı ve bu yapılandırmada nasıl yer alabileceğiniz anlatılmaktadır.

<span class="mw-translate-fuzzy">
{{Note_(tr)|'''Hızlı bir başlangıç için:''' Ne yaptığınızı bilmeksizin başlamak için sabırsızlanıyorsanız, doğrudan "Bir [[:Başlangıç İçin/Yapılandırma#Betikli_Yapılandırmalar|Yapılandırma Betiği]]'nin Kullanılması" bölümüne geçebilirsiniz, fakat öncesinde bu belgelendirmeyi okumanız şiddetle tavsiye olunur.}}
</span>

== KDE Yazılımının Kullanılması ==

Eğer sadece bilgisayarınızdaki günlük kullanım gereksinimleriniz için kararlı bir KDE yazılımı kullanmak istiyorsanız, KDE yazılımını kendiniz yapılandırmak zorunda değilsiniz. Bunun yerine kullandığınız Linux dağıtımının paket yöneticisi tarafından sunulan KDE paketini kurabilirsiniz.

<span class="mw-translate-fuzzy">
Bunu nasıl yapacağınızı öğrenmek için en iyi yer kullandığınız dağıtımın bilindik destek kanallarıdır; tabi aşağıdaki bağlantılarda yer alan bilgiler de sizin için yararlı olabilir:
* [http://www.kde.org/download/distributions.php KDE Desteği Veren Linux Dağıtımları]
* [[:Başlangıç İçin/Yapılandırma/Dağıtımlar|KDE Yazılımının Linux ve BSD Dağıtımlarına Kurulması]]
* [[:Prjeler/Windows ve KDE/Kurulum|Windows'a KDE Kurulumu]]
* KDE Yazılımının Mac OS X için henüz mevcut bir kur dosyası yoktur ancak [http://mac.kde.org/?id=build MacPorts or Fink] bağlantısını kullanarak yapılandırma işleminizi kolaylaştırabilirsiniz.
</span>

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Special:myLanguage/Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Browsing the code ==
The KDE project is all free and open source. You can view its source code and make changes.

http://projects.kde.org hosts the source for many KDE-related initiatives, including [https://projects.kde.org/projects/kde KDE itself]. Choose a piece of KDE such as KDE Libraries, then click Repository to browse its source. [[Getting_Started/Sources]] explains the organization of KDE source code.

There are other utilities to browse the source code:

* http://lxr.kde.org/search lets you search the code ''(may be out of date?)''
* http://api.kde.org lets you browse API documentation generated from the code. You can search for class names, but not filenames.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Special:myLanguage/Getting_Started/Build/Methods|Build Methods page]].



The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[Special:myLanguage/Getting_Started/Sources|How the KDE Source Code is structured]]
* [[Special:myLanguage/Getting_Started/Build|How to Build and Install the software]]
* [[Special:myLanguage/Getting_Started/Run/Nested_Session|How to Run a nested session of KDE]]
* [[Special:myLanguage/Getting_Started/Run/Full_Session|How to Run a full session of KDE]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Special:myLanguage/Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Special:myLanguage/Development/Software_Engineering_Framework|The KDE Software Engineering Framework]]
* [[Special:myLanguage/Policies|KDE Development Policies and Procedures to follow]]
* [[Special:myLanguage/Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Special:myLanguage/Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [[Special:myLanguage/Development/Tutorials/Using_Qt_Creator|Qt Creator]]
* [http://www.kdevelop.org/ KDevelop 4]
* [[Special:myLanguage/Development/Tools/Eclipse|Eclipse]]
* [[Special:myLanguage/Getting_Started/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Special:myLanguage/Contribute|Contribute]]
* [[Special:myLanguage/Contribute/Send_Patches|Send Patches]]
* [[Special:myLanguage/Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Translations:Getting Started/1/tr

2012-02-06T09:15:50Z

Doğan:

{{Warning/tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

Thread:User talk:Doğan/Başlangıç İçin/reply (4)

2012-02-04T16:06:22Z

Doğan: Reply to Başlangıç_İçin

Yes! I'll re-translate them not to confuse the readers of Turkish langauge :) Even I'm confused when I returned to go on translating.

If I'm not mistaken, I created a redirection page also, in order that the page titles such as "Welcome to KDETechbase", "Getting started", etc. could be in Turkish too. I'll be glad if you remove those.

And before you carry out the removal, I shall also get a confirmation. This removal process will not have effect on my translation account, will it? I mean can i continue translating, using the translation tool?

Thread:User talk:Doğan/Başlangıç İçin/reply (2)

2012-02-04T04:52:43Z

Doğan: Reply to Başlangıç_İçin

Hi! I, in advance apologize if I disturb you. However, I need to request some kind of help for a problem similar to the one you mentioned in your previous private message. If it does not make any trouble, would you mind to reset ALL Turkish pages I arbitraily created or edited/translated on-page without using the translation tool?

I would appreciate if you help me do the translation as required by the procedures.

Thread:User talk:Doğan/Başlangıç İçin/reply

2011-12-09T21:09:59Z

Doğan: Reply to Başlangıç_İçin

I'm sorry for that inconvenience and thanks for the notification. Since I was away for a while I forgot that I should use the translation tool. Again, thanks for the notification.

Translations:Welcome to KDE TechBase/Page display title/tr

2011-10-13T04:54:37Z

Doğan: Created page with "KDE TechBase Geliştirici Üssüne Hoşgeldiniz"

KDE TechBase Geliştirici Üssüne Hoşgeldiniz

Getting Started/tr

2011-10-09T21:38:24Z

Doğan: Created page with "Bunu nasıl yapacağınızı öğrenmek için en iyi yer kullandığınız dağıtımın bilindik destek kanallarıdır; tabi aşağıdaki bağlantılarda yer alan bilgiler de si..."

<languages />

{{Warning_(tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

{{Template:I18n/Language Navigation Bar|Başlangıç İçin}}

== Giriş ==

KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır.

Aşağıdaki bağlantılarda KDE Topluluğuna katılmakla ilgili daha genel bilgilere ulaşabilirsiniz:
* [http://kde.org/community/getinvolved/ KDE Topluluğuna Katılın]
* [[:Katkıda Bulunun|KDE'ye Katkıda Bulunun]]

KDE TechBase Geliştirici Üssü'nün bu alt bölümü, KDE Topluluğunun geliştirmeyle ilgili kesimine katılmanıza yardımcı olmak amacıyla tasarlanmıştır. Bu alt bölümde KDE yazılımının yapısı ve nasıl yapılandırıldığı ve bu yapılandırmada nasıl yer alabileceğiniz anlatılmaktadır.

{{Note_(tr)|'''Hızlı bir başlangıç için:''' Ne yaptığınızı bilmeksizin başlamak için sabırsızlanıyorsanız, doğrudan "Bir [[:Başlangıç İçin/Yapılandırma#Betikli_Yapılandırmalar|Yapılandırma Betiği]]'nin Kullanılması" bölümüne geçebilirsiniz, fakat öncesinde bu belgelendirmeyi okumanız şiddetle tavsiye olunur.}}

== KDE Yazılımının Kullanılması ==

Eğer sadece bilgisayarınızdaki günlük kullanım gereksinimleriniz için kararlı bir KDE yazılımı kullanmak istiyorsanız, KDE yazılımını kendiniz yapılandırmak zorunda değilsiniz. Bunun yerine kullandığınız Linux dağıtımının paket yöneticisi tarafından sunulan KDE paketini kurabilirsiniz.

Bunu nasıl yapacağınızı öğrenmek için en iyi yer kullandığınız dağıtımın bilindik destek kanallarıdır; tabi aşağıdaki bağlantılarda yer alan bilgiler de sizin için yararlı olabilir:
* [http://www.kde.org/download/distributions.php KDE Desteği Veren Linux Dağıtımları]
* [[:Başlangıç İçin/Yapılandırma/Dağıtımlar|KDE Yazılımının Linux ve BSD Dağıtımlarına Kurulması]]
* [[:Prjeler/Windows ve KDE/Kurulum|Windows'a KDE Kurulumu]]
* KDE Yazılımının Mac OS X için henüz mevcut bir kur dosyası yoktur ancak [http://mac.kde.org/?id=build MacPorts or Fink] bağlantısını kullanarak yapılandırma işleminizi kolaylaştırabilirsiniz.

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Getting_Started/Build/Methods|Build Methods page]].

The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[/Sources|How the KDE Source Code is structured]]
* [[/Build|How to Build and Install the software]]
* [[/Run|How to Run the software]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Development/Software_Engineering_Framework|The KDE Software Engineering Framwork]]
* [[Policies|KDE Development Policies and Procedures to follow]]
* [[Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [http://www.kdevelop.org/ KDevelop 4]
* [[Development/Tools/Eclipse|Eclipse]]
* [[/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Contribute|Contribute]]
* [[Contribute/Send_Patches|Send Patches]]
* [[Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Translations:Getting Started/10/tr

2011-10-09T21:38:24Z

Bunu nasıl yapacağınızı öğrenmek için en iyi yer kullandığınız dağıtımın bilindik destek kanallarıdır; tabi aşağıdaki bağlantılarda yer alan bilgiler de sizin için yararlı olabilir:
* [http://www.kde.org/download/distributions.php KDE Desteği Veren Linux Dağıtımları]
* [[:Başlangıç İçin/Yapılandırma/Dağıtımlar|KDE Yazılımının Linux ve BSD Dağıtımlarına Kurulması]]
* [[:Prjeler/Windows ve KDE/Kurulum|Windows'a KDE Kurulumu]]
* KDE Yazılımının Mac OS X için henüz mevcut bir kur dosyası yoktur ancak [http://mac.kde.org/?id=build MacPorts or Fink] bağlantısını kullanarak yapılandırma işleminizi kolaylaştırabilirsiniz.

Getting Started/tr

2011-10-09T21:36:55Z

Doğan: Created page with "Eğer sadece bilgisayarınızdaki günlük kullanım gereksinimleriniz için kararlı bir KDE yazılımı kullanmak istiyorsanız, KDE yazılımını kendiniz yapılandırmak zor..."

<languages />

{{Warning_(tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

{{Template:I18n/Language Navigation Bar|Başlangıç İçin}}

== Giriş ==

KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır.

Aşağıdaki bağlantılarda KDE Topluluğuna katılmakla ilgili daha genel bilgilere ulaşabilirsiniz:
* [http://kde.org/community/getinvolved/ KDE Topluluğuna Katılın]
* [[:Katkıda Bulunun|KDE'ye Katkıda Bulunun]]

KDE TechBase Geliştirici Üssü'nün bu alt bölümü, KDE Topluluğunun geliştirmeyle ilgili kesimine katılmanıza yardımcı olmak amacıyla tasarlanmıştır. Bu alt bölümde KDE yazılımının yapısı ve nasıl yapılandırıldığı ve bu yapılandırmada nasıl yer alabileceğiniz anlatılmaktadır.

{{Note_(tr)|'''Hızlı bir başlangıç için:''' Ne yaptığınızı bilmeksizin başlamak için sabırsızlanıyorsanız, doğrudan "Bir [[:Başlangıç İçin/Yapılandırma#Betikli_Yapılandırmalar|Yapılandırma Betiği]]'nin Kullanılması" bölümüne geçebilirsiniz, fakat öncesinde bu belgelendirmeyi okumanız şiddetle tavsiye olunur.}}

== KDE Yazılımının Kullanılması ==

Eğer sadece bilgisayarınızdaki günlük kullanım gereksinimleriniz için kararlı bir KDE yazılımı kullanmak istiyorsanız, KDE yazılımını kendiniz yapılandırmak zorunda değilsiniz. Bunun yerine kullandığınız Linux dağıtımının paket yöneticisi tarafından sunulan KDE paketini kurabilirsiniz.

The best place to learn how to do this is through your distributions normal support channels, although you may find some useful information on the following pages:
* [http://www.kde.org/download/distributions.php Distributions shipping KDE]
* [[/Build/Distributions|Install KDE Software on Linux and BSD Distributions]]
* [[Projects/KDE_on_Windows/Installation|Install KDE Software on Windows]]
* Mac OS X does not currently have an installer available for KDE Software, but you can simplify building it by using [http://mac.kde.org/?id=build MacPorts or Fink]

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Getting_Started/Build/Methods|Build Methods page]].

The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[/Sources|How the KDE Source Code is structured]]
* [[/Build|How to Build and Install the software]]
* [[/Run|How to Run the software]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Development/Software_Engineering_Framework|The KDE Software Engineering Framwork]]
* [[Policies|KDE Development Policies and Procedures to follow]]
* [[Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [http://www.kdevelop.org/ KDevelop 4]
* [[Development/Tools/Eclipse|Eclipse]]
* [[/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Contribute|Contribute]]
* [[Contribute/Send_Patches|Send Patches]]
* [[Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Translations:Getting Started/9/tr

2011-10-09T21:36:55Z

Eğer sadece bilgisayarınızdaki günlük kullanım gereksinimleriniz için kararlı bir KDE yazılımı kullanmak istiyorsanız, KDE yazılımını kendiniz yapılandırmak zorunda değilsiniz. Bunun yerine kullandığınız Linux dağıtımının paket yöneticisi tarafından sunulan KDE paketini kurabilirsiniz.

Getting Started/tr

2011-10-09T21:36:35Z

Doğan: Created page with "== KDE Yazılımının Kullanılması =="

<languages />

{{Warning_(tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

{{Template:I18n/Language Navigation Bar|Başlangıç İçin}}

== Giriş ==

KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır.

Aşağıdaki bağlantılarda KDE Topluluğuna katılmakla ilgili daha genel bilgilere ulaşabilirsiniz:
* [http://kde.org/community/getinvolved/ KDE Topluluğuna Katılın]
* [[:Katkıda Bulunun|KDE'ye Katkıda Bulunun]]

KDE TechBase Geliştirici Üssü'nün bu alt bölümü, KDE Topluluğunun geliştirmeyle ilgili kesimine katılmanıza yardımcı olmak amacıyla tasarlanmıştır. Bu alt bölümde KDE yazılımının yapısı ve nasıl yapılandırıldığı ve bu yapılandırmada nasıl yer alabileceğiniz anlatılmaktadır.

{{Note_(tr)|'''Hızlı bir başlangıç için:''' Ne yaptığınızı bilmeksizin başlamak için sabırsızlanıyorsanız, doğrudan "Bir [[:Başlangıç İçin/Yapılandırma#Betikli_Yapılandırmalar|Yapılandırma Betiği]]'nin Kullanılması" bölümüne geçebilirsiniz, fakat öncesinde bu belgelendirmeyi okumanız şiddetle tavsiye olunur.}}

== KDE Yazılımının Kullanılması ==

If you just want to use stable KDE software for your everyday computing needs, then you do not need to build KDE Software for yourself. You should instead use the software installer provided by your Linux distribution to install KDE package.

The best place to learn how to do this is through your distributions normal support channels, although you may find some useful information on the following pages:
* [http://www.kde.org/download/distributions.php Distributions shipping KDE]
* [[/Build/Distributions|Install KDE Software on Linux and BSD Distributions]]
* [[Projects/KDE_on_Windows/Installation|Install KDE Software on Windows]]
* Mac OS X does not currently have an installer available for KDE Software, but you can simplify building it by using [http://mac.kde.org/?id=build MacPorts or Fink]

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Getting_Started/Build/Methods|Build Methods page]].

The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[/Sources|How the KDE Source Code is structured]]
* [[/Build|How to Build and Install the software]]
* [[/Run|How to Run the software]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Development/Software_Engineering_Framework|The KDE Software Engineering Framwork]]
* [[Policies|KDE Development Policies and Procedures to follow]]
* [[Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [http://www.kdevelop.org/ KDevelop 4]
* [[Development/Tools/Eclipse|Eclipse]]
* [[/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Contribute|Contribute]]
* [[Contribute/Send_Patches|Send Patches]]
* [[Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Translations:Getting Started/8/tr

2011-10-09T21:36:35Z

Doğan: Created page with "== KDE Yazılımının Kullanılması =="

== KDE Yazılımının Kullanılması ==

Getting Started/tr

2011-10-09T21:36:00Z

Doğan: Created page with "{{Note_(tr)|'''Hızlı bir başlangıç için:''' Ne yaptığınızı bilmeksizin başlamak için sabırsızlanıyorsanız, doğrudan "Bir [[:Başlangıç İçin/Yapılandırma#B..."

<languages />

{{Warning_(tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

{{Template:I18n/Language Navigation Bar|Başlangıç İçin}}

== Giriş ==

KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır.

Aşağıdaki bağlantılarda KDE Topluluğuna katılmakla ilgili daha genel bilgilere ulaşabilirsiniz:
* [http://kde.org/community/getinvolved/ KDE Topluluğuna Katılın]
* [[:Katkıda Bulunun|KDE'ye Katkıda Bulunun]]

KDE TechBase Geliştirici Üssü'nün bu alt bölümü, KDE Topluluğunun geliştirmeyle ilgili kesimine katılmanıza yardımcı olmak amacıyla tasarlanmıştır. Bu alt bölümde KDE yazılımının yapısı ve nasıl yapılandırıldığı ve bu yapılandırmada nasıl yer alabileceğiniz anlatılmaktadır.

{{Note_(tr)|'''Hızlı bir başlangıç için:''' Ne yaptığınızı bilmeksizin başlamak için sabırsızlanıyorsanız, doğrudan "Bir [[:Başlangıç İçin/Yapılandırma#Betikli_Yapılandırmalar|Yapılandırma Betiği]]'nin Kullanılması" bölümüne geçebilirsiniz, fakat öncesinde bu belgelendirmeyi okumanız şiddetle tavsiye olunur.}}

== Using KDE Software ==

If you just want to use stable KDE software for your everyday computing needs, then you do not need to build KDE Software for yourself. You should instead use the software installer provided by your Linux distribution to install KDE package.

The best place to learn how to do this is through your distributions normal support channels, although you may find some useful information on the following pages:
* [http://www.kde.org/download/distributions.php Distributions shipping KDE]
* [[/Build/Distributions|Install KDE Software on Linux and BSD Distributions]]
* [[Projects/KDE_on_Windows/Installation|Install KDE Software on Windows]]
* Mac OS X does not currently have an installer available for KDE Software, but you can simplify building it by using [http://mac.kde.org/?id=build MacPorts or Fink]

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Getting_Started/Build/Methods|Build Methods page]].

The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[/Sources|How the KDE Source Code is structured]]
* [[/Build|How to Build and Install the software]]
* [[/Run|How to Run the software]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Development/Software_Engineering_Framework|The KDE Software Engineering Framwork]]
* [[Policies|KDE Development Policies and Procedures to follow]]
* [[Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [http://www.kdevelop.org/ KDevelop 4]
* [[Development/Tools/Eclipse|Eclipse]]
* [[/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Contribute|Contribute]]
* [[Contribute/Send_Patches|Send Patches]]
* [[Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Translations:Getting Started/7/tr

2011-10-09T21:36:00Z

{{Note_(tr)|'''Hızlı bir başlangıç için:''' Ne yaptığınızı bilmeksizin başlamak için sabırsızlanıyorsanız, doğrudan "Bir [[:Başlangıç İçin/Yapılandırma#Betikli_Yapılandırmalar|Yapılandırma Betiği]]'nin Kullanılması" bölümüne geçebilirsiniz, fakat öncesinde bu belgelendirmeyi okumanız şiddetle tavsiye olunur.}}

Getting Started/tr

2011-10-09T21:34:04Z

Doğan: Created page with "KDE TechBase Geliştirici Üssü'nün bu alt bölümü, KDE Topluluğunun geliştirmeyle ilgili kesimine katılmanıza yardımcı olmak amacıyla tasarlanmıştır. Bu alt bölü..."

<languages />

{{Warning_(tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

{{Template:I18n/Language Navigation Bar|Başlangıç İçin}}

== Giriş ==

KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır.

Aşağıdaki bağlantılarda KDE Topluluğuna katılmakla ilgili daha genel bilgilere ulaşabilirsiniz:
* [http://kde.org/community/getinvolved/ KDE Topluluğuna Katılın]
* [[:Katkıda Bulunun|KDE'ye Katkıda Bulunun]]

KDE TechBase Geliştirici Üssü'nün bu alt bölümü, KDE Topluluğunun geliştirmeyle ilgili kesimine katılmanıza yardımcı olmak amacıyla tasarlanmıştır. Bu alt bölümde KDE yazılımının yapısı ve nasıl yapılandırıldığı ve bu yapılandırmada nasıl yer alabileceğiniz anlatılmaktadır.

{{Note|'''Quickstart:''' If you are impatient to get started without understanding what you are doing then you can skip straight to using a [[/Build#Scripted_Builds|Build Script]], but it is strongly recommended you read this documentation first.}}

== Using KDE Software ==

If you just want to use stable KDE software for your everyday computing needs, then you do not need to build KDE Software for yourself. You should instead use the software installer provided by your Linux distribution to install KDE package.

The best place to learn how to do this is through your distributions normal support channels, although you may find some useful information on the following pages:
* [http://www.kde.org/download/distributions.php Distributions shipping KDE]
* [[/Build/Distributions|Install KDE Software on Linux and BSD Distributions]]
* [[Projects/KDE_on_Windows/Installation|Install KDE Software on Windows]]
* Mac OS X does not currently have an installer available for KDE Software, but you can simplify building it by using [http://mac.kde.org/?id=build MacPorts or Fink]

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Getting_Started/Build/Methods|Build Methods page]].

The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[/Sources|How the KDE Source Code is structured]]
* [[/Build|How to Build and Install the software]]
* [[/Run|How to Run the software]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Development/Software_Engineering_Framework|The KDE Software Engineering Framwork]]
* [[Policies|KDE Development Policies and Procedures to follow]]
* [[Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [http://www.kdevelop.org/ KDevelop 4]
* [[Development/Tools/Eclipse|Eclipse]]
* [[/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Contribute|Contribute]]
* [[Contribute/Send_Patches|Send Patches]]
* [[Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Translations:Getting Started/6/tr

2011-10-09T21:34:04Z

KDE TechBase Geliştirici Üssü'nün bu alt bölümü, KDE Topluluğunun geliştirmeyle ilgili kesimine katılmanıza yardımcı olmak amacıyla tasarlanmıştır. Bu alt bölümde KDE yazılımının yapısı ve nasıl yapılandırıldığı ve bu yapılandırmada nasıl yer alabileceğiniz anlatılmaktadır.

Getting Started/tr

2011-10-09T21:33:43Z

Doğan: Created page with "Aşağıdaki bağlantılarda KDE Topluluğuna katılmakla ilgili daha genel bilgilere ulaşabilirsiniz: * [http://kde.org/community/getinvolved/ KDE Topluluğuna Katılın] * [[:..."

<languages />

{{Warning_(tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

{{Template:I18n/Language Navigation Bar|Başlangıç İçin}}

== Giriş ==

KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır.

Aşağıdaki bağlantılarda KDE Topluluğuna katılmakla ilgili daha genel bilgilere ulaşabilirsiniz:
* [http://kde.org/community/getinvolved/ KDE Topluluğuna Katılın]
* [[:Katkıda Bulunun|KDE'ye Katkıda Bulunun]]

This section of KDE TechBase is designed to help get you started in participating in the technical side of the KDE community. It will explain to you how KDE Software is structured and built, and how you can participate by building KDE for yourself.

{{Note|'''Quickstart:''' If you are impatient to get started without understanding what you are doing then you can skip straight to using a [[/Build#Scripted_Builds|Build Script]], but it is strongly recommended you read this documentation first.}}

== Using KDE Software ==

If you just want to use stable KDE software for your everyday computing needs, then you do not need to build KDE Software for yourself. You should instead use the software installer provided by your Linux distribution to install KDE package.

The best place to learn how to do this is through your distributions normal support channels, although you may find some useful information on the following pages:
* [http://www.kde.org/download/distributions.php Distributions shipping KDE]
* [[/Build/Distributions|Install KDE Software on Linux and BSD Distributions]]
* [[Projects/KDE_on_Windows/Installation|Install KDE Software on Windows]]
* Mac OS X does not currently have an installer available for KDE Software, but you can simplify building it by using [http://mac.kde.org/?id=build MacPorts or Fink]

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Getting_Started/Build/Methods|Build Methods page]].

The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[/Sources|How the KDE Source Code is structured]]
* [[/Build|How to Build and Install the software]]
* [[/Run|How to Run the software]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Development/Software_Engineering_Framework|The KDE Software Engineering Framwork]]
* [[Policies|KDE Development Policies and Procedures to follow]]
* [[Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [http://www.kdevelop.org/ KDevelop 4]
* [[Development/Tools/Eclipse|Eclipse]]
* [[/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Contribute|Contribute]]
* [[Contribute/Send_Patches|Send Patches]]
* [[Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Translations:Getting Started/5/tr

2011-10-09T21:33:43Z

Aşağıdaki bağlantılarda KDE Topluluğuna katılmakla ilgili daha genel bilgilere ulaşabilirsiniz:
* [http://kde.org/community/getinvolved/ KDE Topluluğuna Katılın]
* [[:Katkıda Bulunun|KDE'ye Katkıda Bulunun]]

Getting Started/tr

2011-10-09T21:33:00Z

Doğan: Created page with "KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır."

<languages />

{{Warning_(tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

{{Template:I18n/Language Navigation Bar|Başlangıç İçin}}

== Giriş ==

KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır.

You can find more general information on getting involved in KDE at the following links:
* [http://kde.org/community/getinvolved/ Getting Involved in KDE]
* [[Contribute|Contribute to KDE]]

This section of KDE TechBase is designed to help get you started in participating in the technical side of the KDE community. It will explain to you how KDE Software is structured and built, and how you can participate by building KDE for yourself.

{{Note|'''Quickstart:''' If you are impatient to get started without understanding what you are doing then you can skip straight to using a [[/Build#Scripted_Builds|Build Script]], but it is strongly recommended you read this documentation first.}}

== Using KDE Software ==

If you just want to use stable KDE software for your everyday computing needs, then you do not need to build KDE Software for yourself. You should instead use the software installer provided by your Linux distribution to install KDE package.

The best place to learn how to do this is through your distributions normal support channels, although you may find some useful information on the following pages:
* [http://www.kde.org/download/distributions.php Distributions shipping KDE]
* [[/Build/Distributions|Install KDE Software on Linux and BSD Distributions]]
* [[Projects/KDE_on_Windows/Installation|Install KDE Software on Windows]]
* Mac OS X does not currently have an installer available for KDE Software, but you can simplify building it by using [http://mac.kde.org/?id=build MacPorts or Fink]

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Getting_Started/Build/Methods|Build Methods page]].

The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[/Sources|How the KDE Source Code is structured]]
* [[/Build|How to Build and Install the software]]
* [[/Run|How to Run the software]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Development/Software_Engineering_Framework|The KDE Software Engineering Framwork]]
* [[Policies|KDE Development Policies and Procedures to follow]]
* [[Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [http://www.kdevelop.org/ KDevelop 4]
* [[Development/Tools/Eclipse|Eclipse]]
* [[/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Contribute|Contribute]]
* [[Contribute/Send_Patches|Send Patches]]
* [[Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Translations:Getting Started/4/tr

2011-10-09T21:32:59Z

Doğan: Created page with "KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır."

KDE Topluluğunda yer almanın, en basitinden yazılımızı kullanmaktan, çekirdek platformu geliştiricisi olmaya kadar birçok yolu vardır.

Getting Started/tr

2011-10-09T17:29:58Z

Doğan: Created page with "== Giriş =="

<languages />

{{Warning_(tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

{{Template:I18n/Language Navigation Bar|Başlangıç İçin}}

== Giriş ==

There are many different ways to become involved in the KDE Community, ranging all the way from a simply using our software through to being a core platform developer.

You can find more general information on getting involved in KDE at the following links:
* [http://kde.org/community/getinvolved/ Getting Involved in KDE]
* [[Contribute|Contribute to KDE]]

This section of KDE TechBase is designed to help get you started in participating in the technical side of the KDE community. It will explain to you how KDE Software is structured and built, and how you can participate by building KDE for yourself.

{{Note|'''Quickstart:''' If you are impatient to get started without understanding what you are doing then you can skip straight to using a [[/Build#Scripted_Builds|Build Script]], but it is strongly recommended you read this documentation first.}}

== Using KDE Software ==

If you just want to use stable KDE software for your everyday computing needs, then you do not need to build KDE Software for yourself. You should instead use the software installer provided by your Linux distribution to install KDE package.

The best place to learn how to do this is through your distributions normal support channels, although you may find some useful information on the following pages:
* [http://www.kde.org/download/distributions.php Distributions shipping KDE]
* [[/Build/Distributions|Install KDE Software on Linux and BSD Distributions]]
* [[Projects/KDE_on_Windows/Installation|Install KDE Software on Windows]]
* Mac OS X does not currently have an installer available for KDE Software, but you can simplify building it by using [http://mac.kde.org/?id=build MacPorts or Fink]

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Getting_Started/Build/Methods|Build Methods page]].

The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[/Sources|How the KDE Source Code is structured]]
* [[/Build|How to Build and Install the software]]
* [[/Run|How to Run the software]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Development/Software_Engineering_Framework|The KDE Software Engineering Framwork]]
* [[Policies|KDE Development Policies and Procedures to follow]]
* [[Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [http://www.kdevelop.org/ KDevelop 4]
* [[Development/Tools/Eclipse|Eclipse]]
* [[/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Contribute|Contribute]]
* [[Contribute/Send_Patches|Send Patches]]
* [[Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Translations:Getting Started/3/tr

2011-10-09T17:29:57Z

Doğan: Created page with "== Giriş =="

== Giriş ==

Getting Started/tr

2011-10-09T17:29:42Z

Doğan: Created page with "{{Template:I18n/Language Navigation Bar|Başlangıç İçin}}"

<languages />

{{Warning_(tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

{{Template:I18n/Language Navigation Bar|Başlangıç İçin}}

== Introduction ==

There are many different ways to become involved in the KDE Community, ranging all the way from a simply using our software through to being a core platform developer.

You can find more general information on getting involved in KDE at the following links:
* [http://kde.org/community/getinvolved/ Getting Involved in KDE]
* [[Contribute|Contribute to KDE]]

This section of KDE TechBase is designed to help get you started in participating in the technical side of the KDE community. It will explain to you how KDE Software is structured and built, and how you can participate by building KDE for yourself.

{{Note|'''Quickstart:''' If you are impatient to get started without understanding what you are doing then you can skip straight to using a [[/Build#Scripted_Builds|Build Script]], but it is strongly recommended you read this documentation first.}}

== Using KDE Software ==

If you just want to use stable KDE software for your everyday computing needs, then you do not need to build KDE Software for yourself. You should instead use the software installer provided by your Linux distribution to install KDE package.

The best place to learn how to do this is through your distributions normal support channels, although you may find some useful information on the following pages:
* [http://www.kde.org/download/distributions.php Distributions shipping KDE]
* [[/Build/Distributions|Install KDE Software on Linux and BSD Distributions]]
* [[Projects/KDE_on_Windows/Installation|Install KDE Software on Windows]]
* Mac OS X does not currently have an installer available for KDE Software, but you can simplify building it by using [http://mac.kde.org/?id=build MacPorts or Fink]

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Getting_Started/Build/Methods|Build Methods page]].

The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[/Sources|How the KDE Source Code is structured]]
* [[/Build|How to Build and Install the software]]
* [[/Run|How to Run the software]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Development/Software_Engineering_Framework|The KDE Software Engineering Framwork]]
* [[Policies|KDE Development Policies and Procedures to follow]]
* [[Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [http://www.kdevelop.org/ KDevelop 4]
* [[Development/Tools/Eclipse|Eclipse]]
* [[/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Contribute|Contribute]]
* [[Contribute/Send_Patches|Send Patches]]
* [[Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Getting Started/tr

2011-10-09T17:29:03Z

Doğan: Created page with "{{Warning_(tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayf..."

<languages />

{{Warning_(tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

{{Template:I18n/Language Navigation Bar|Getting_Started}}

== Introduction ==

There are many different ways to become involved in the KDE Community, ranging all the way from a simply using our software through to being a core platform developer.

You can find more general information on getting involved in KDE at the following links:
* [http://kde.org/community/getinvolved/ Getting Involved in KDE]
* [[Contribute|Contribute to KDE]]

This section of KDE TechBase is designed to help get you started in participating in the technical side of the KDE community. It will explain to you how KDE Software is structured and built, and how you can participate by building KDE for yourself.

{{Note|'''Quickstart:''' If you are impatient to get started without understanding what you are doing then you can skip straight to using a [[/Build#Scripted_Builds|Build Script]], but it is strongly recommended you read this documentation first.}}

== Using KDE Software ==

If you just want to use stable KDE software for your everyday computing needs, then you do not need to build KDE Software for yourself. You should instead use the software installer provided by your Linux distribution to install KDE package.

The best place to learn how to do this is through your distributions normal support channels, although you may find some useful information on the following pages:
* [http://www.kde.org/download/distributions.php Distributions shipping KDE]
* [[/Build/Distributions|Install KDE Software on Linux and BSD Distributions]]
* [[Projects/KDE_on_Windows/Installation|Install KDE Software on Windows]]
* Mac OS X does not currently have an installer available for KDE Software, but you can simplify building it by using [http://mac.kde.org/?id=build MacPorts or Fink]

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Getting_Started/Build/Methods|Build Methods page]].

The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[/Sources|How the KDE Source Code is structured]]
* [[/Build|How to Build and Install the software]]
* [[/Run|How to Run the software]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Development/Software_Engineering_Framework|The KDE Software Engineering Framwork]]
* [[Policies|KDE Development Policies and Procedures to follow]]
* [[Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [http://www.kdevelop.org/ KDevelop 4]
* [[Development/Tools/Eclipse|Eclipse]]
* [[/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Contribute|Contribute]]
* [[Contribute/Send_Patches|Send Patches]]
* [[Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Translations:Getting Started/1/tr

2011-10-09T17:29:03Z

{{Warning_(tr)|Bu sayfalar KDE'nin yeni altyapısını yansıtabilmek adına yakın zamanda tam anlamıyla yeniden yazılmaya başlanmıştır ve tutarlı olmayabilir. Bazı sayfalardaki bilgi ve komutlar artık geçerli olmayabileyeceği gibi bunların dikkatli kullanılması gerekmektedir.}}

Translations:Getting Started/Page display title/tr

2011-10-09T17:26:49Z

Doğan: Created page with "Başlangıç İçin"

Başlangıç İçin

Getting Started/tr

2011-10-09T17:26:49Z

Doğan: Created page with "Başlangıç İçin"

<languages />

{{Warning|These pages are currently being completely re-written to reflect the new KDE infrastructure and may not be in a consistent state. Information and commands on some page may no longer be valid and should be used with care.}}

{{Template:I18n/Language Navigation Bar|Getting_Started}}

== Introduction ==

There are many different ways to become involved in the KDE Community, ranging all the way from a simply using our software through to being a core platform developer.

You can find more general information on getting involved in KDE at the following links:
* [http://kde.org/community/getinvolved/ Getting Involved in KDE]
* [[Contribute|Contribute to KDE]]

This section of KDE TechBase is designed to help get you started in participating in the technical side of the KDE community. It will explain to you how KDE Software is structured and built, and how you can participate by building KDE for yourself.

{{Note|'''Quickstart:''' If you are impatient to get started without understanding what you are doing then you can skip straight to using a [[/Build#Scripted_Builds|Build Script]], but it is strongly recommended you read this documentation first.}}

== Using KDE Software ==

If you just want to use stable KDE software for your everyday computing needs, then you do not need to build KDE Software for yourself. You should instead use the software installer provided by your Linux distribution to install KDE package.

The best place to learn how to do this is through your distributions normal support channels, although you may find some useful information on the following pages:
* [http://www.kde.org/download/distributions.php Distributions shipping KDE]
* [[/Build/Distributions|Install KDE Software on Linux and BSD Distributions]]
* [[Projects/KDE_on_Windows/Installation|Install KDE Software on Windows]]
* Mac OS X does not currently have an installer available for KDE Software, but you can simplify building it by using [http://mac.kde.org/?id=build MacPorts or Fink]

== Getting Help ==

If you are looking for help in using the KDE Workspace or KDE Applications then please visit the [http://userbase.kde.org/ KDE UserBase].

If you have any questions or problems with building or developing KDE Software please feel free to [[Development/Getting_Help|ask for help]]. However, be patient while waiting for a response, and try to work through the problem yourself, we aren't going to do it ''all'' for you. Working your way through and understanding why something doesn't work is a good way to learn how to do things the right way.

== Building and Running KDE Software From Source ==

There are several possible ways to build and install KDE software and the method you choose depends on what you want to do with the software. In particular if you are only wanting to build and develop a single application you may not need to build the entire KDE Development Platform to do so. You can read more about this on the [[Getting_Started/Build/Methods|Build Methods page]].

The following sections explain the steps you need to understand and give the instructions you need to follow to successfully build KDE Software from source:

* [[/Sources|How the KDE Source Code is structured]]
* [[/Build|How to Build and Install the software]]
* [[/Run|How to Run the software]]

== Development Model ==

TODO: General introduction to the dev model, release cycles, etc.

* [[Schedules/Release_Schedules_Guide|The KDE Release Schedule]]
* [[Development/Software_Engineering_Framework|The KDE Software Engineering Framwork]]
* [[Policies|KDE Development Policies and Procedures to follow]]
* [[Policies/Application_Lifecycle|The development lifecycle for a new application]]

== Development Tools ==

There are a number of [[Development/Tools|Development Tools]] that are either required or helpful when building KDE Software. For these you will usually want to use the stable packages provided by your distribution.

You may want to use a graphical IDE for your development work:
* [http://www.kdevelop.org/ KDevelop 4]
* [[Development/Tools/Eclipse|Eclipse]]
* [[/Using_an_IDE_with_KDE4|Using an IDE with KDE4]]

== Contributing To KDE ==

Once you have a copy of KDE built you can then start contributing back to KDE. The pages below will help you find out how you can help make KDE even better.

[[Image:Action_tool.svg|right|32px]]
* [[Contribute|Contribute]]
* [[Contribute/Send_Patches|Send Patches]]
* [[Contribute/Bugsquad|Bugsquad]]

[[Category:Build_KDE]]

Welcome to KDE TechBase/tr

2011-10-09T17:23:37Z

Doğan:

{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}

<languages />

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|colspan=2|[[Image:Discover.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_launch.svg|noframe|left|40px]] ||
;;[[:Başlangıç İçin|KDE Geliştirme Ortamının Düzenlenmesi]]
:KDE Geliştirme Ortamını
::'''&rsaquo;''' nasıl '''''edinebileceğinizi''''',
::'''&rsaquo;''' nasıl '''''yapılandırabileceğinizi''''' ve
::'''&rsaquo;''' nasıl '''''çalıştırabileceğinizi''''' öğrenin.
|-
| style="padding-left: 50px;"|[[Image:Action_configure.svg|noframe|left|40px]] ||
;;[[:Geliştirme|KDE Ortamında Geliştirme]]
::[[:Geliştirme/Dersler|Dersler]] | [http://api.kde.org API Belgelendirmesi] | [[:Geliştirme/SSS|Sıkça Sorulan Sorular]] ve daha fazlası.
::''Benzer İçerikler'':
:*[[:Takvimler|Sürüm Takvimleri ve Eklenmesi Planlanan Özellikler]]
:*[[:İlkeler|Kod Paylaşımı ve Geliştirici Kılavuzu]]
|-
| style="padding-left: 50px;"|[[Image:Devices_system.svg|noframe|left|40px]] ||
;;[[:KDE Sistem Yönetimi|KDE Sistem Yönetimi]]
:KDE dağıtımlarını yöneten sistem yöneticileri için gerekli bilgiler.
|-
|colspan=2|[[Image:Interact.png|noframe]]
|-
| style="padding-left: 50px;"|[[Image:Action_favorites.svg|noframe|left|40px]] ||
;;[[:Katkıda Bulunun|KDE Takımına Katılım ve Katkıda Bulunun]]
:Topluluğumuza katılın, topluluktan bilgi alın, yamalara katkıda bulunun.
:''Benzer İçerikler:''
:*[[:İlkeler|KDE Projesi İlkeleri]]
:*[http://www.kde.org/support/support.php Bağışta Bulunun]

;[[:BYD|BYD ile ilgili bilgiler]]
:Geliştiriciler için Bağımsız Yazılım Dağıtıcılarına ilişkin bilgiler.
|-
|colspan=2|[[Image:Develop.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_wizard.svg|noframe|left|40px]] ||
;;[[:Projeler|KDE Projeleri]]
:Çeşitli KDE Projeleri için geliştirici wiki'leri, görev listeleri vb. gibi bağlantılar.

|}

Translations:Welcome to KDE TechBase/13/tr

2011-10-09T17:23:36Z

Doğan:

-->
:Geliştiriciler için Bağımsız Yazılım Dağıtıcılarına ilişkin bilgiler.

Translations:Welcome to KDE TechBase/12/tr

2011-10-09T17:23:16Z

Doğan:

-->
;[[:BYD|BYD ile ilgili bilgiler]]<!--

Welcome to KDE TechBase/tr

2011-10-09T17:23:16Z

Doğan:

{{Template:I18n/Language Navigation Bar|Welcome to KDE TechBase}}

<languages />

{| style="margin: 1em 2.5% 0 2.5%; padding: 0 5px;" cellpadding="5"
|-
|colspan=2|[[Image:Discover.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_launch.svg|noframe|left|40px]] ||
;;[[:Başlangıç İçin|KDE Geliştirme Ortamının Düzenlenmesi]]
:KDE Geliştirme Ortamını
::'''&rsaquo;''' nasıl '''''edinebileceğinizi''''',
::'''&rsaquo;''' nasıl '''''yapılandırabileceğinizi''''' ve
::'''&rsaquo;''' nasıl '''''çalıştırabileceğinizi''''' öğrenin.
|-
| style="padding-left: 50px;"|[[Image:Action_configure.svg|noframe|left|40px]] ||
;;[[:Geliştirme|KDE Ortamında Geliştirme]]
::[[:Geliştirme/Dersler|Dersler]] | [http://api.kde.org API Belgelendirmesi] | [[:Geliştirme/SSS|Sıkça Sorulan Sorular]] ve daha fazlası.
::''Benzer İçerikler'':
:*[[:Takvimler|Sürüm Takvimleri ve Eklenmesi Planlanan Özellikler]]
:*[[:İlkeler|Kod Paylaşımı ve Geliştirici Kılavuzu]]
|-
| style="padding-left: 50px;"|[[Image:Devices_system.svg|noframe|left|40px]] ||
;;[[:KDE Sistem Yönetimi|KDE Sistem Yönetimi]]
:KDE dağıtımlarını yöneten sistem yöneticileri için gerekli bilgiler.
|-
|colspan=2|[[Image:Interact.png|noframe]]
|-
| style="padding-left: 50px;"|[[Image:Action_favorites.svg|noframe|left|40px]] ||
;;[[:Katkıda Bulunun|KDE Takımına Katılım ve Katkıda Bulunun]]
:Topluluğumuza katılın, topluluktan bilgi alın, yamalara katkıda bulunun.
:''Benzer İçerikler:''
:*[[:İlkeler|KDE Projesi İlkeleri]]
:*[http://www.kde.org/support/support.php Bağışta Bulunun]

;[[:BYD|BYD ile ilgili bilgiler]]<!--]]:Geliştiriciler için Bağımsız Yazılım Dağıtıcılarına ilişkin bilgiler.
|-
|colspan=2|[[Image:Develop.png|noframe]]
|-
| style="padding-left: 50px;" |[[Image:Action_wizard.svg|noframe|left|40px]] ||
;;[[:Projeler|KDE Projeleri]]
:Çeşitli KDE Projeleri için geliştirici wiki'leri, görev listeleri vb. gibi bağlantılar.

|}

Translations:Welcome to KDE TechBase/12/tr

2011-10-09T17:21:34Z

Doğan:

-->
;[[:BYD|BYD ile ilgili bilgiler]]