Development/FAQs/General FAQ/pt-br: Difference between revisions

From KDE TechBase
(Created page with "Você é familiar ou sente-se atraído por alguma área específica? Verifique se alguma aplicação relacionada pode ser melhorada. Ou escreva uma nova. O KDE precis de mais apl...")
(Created page with "== Posso acessar o código fonte do KDE online? ==")
 
(121 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Proposed_deletion|Content is now at https://community.kde.org/KDE/FAQs/General_FAQ and this page may no longer be up-to-date. Translations are still available for this page, however.}}
<languages />
<languages />
{{Template:I18n/Language Navigation Bar|Desenvolvimento/FAQs/FAQ geral}}


==Eu quero começar uma nova aplicação. O que você recomenda?==
== Eu quero iniciar este novo aplicativo. O que você aconselha? ==
 
Todos concordamos que existem muitos aplicativos do KDE que precisam ser escritos. Mas também existem muitos aplicativos kde que precisam da sua ajuda.
 
Para ver as áreas em que a ajuda é necessária, consulte [http://www.kde.org/jobs/ this page].


Todos concordamos que existem muitas aplicações para o KDE que precisam ser escritas. Mas também há muitas aplicações existentes no KDE que necessitam sua ajuda.
Antes de iniciar um novo aplicativo, é sempre uma boa ideia verificar o [http://www.kde-apps.org/ KDE-Apps.org] e outros serviços de hospedagem de software de código aberto como [https://github.com/ GitHub ], [https://code.google.com Google Code] e [http://sourceforge.net/ SourceForge] para aplicativos existentes e para solicitar as [https://mail.kde.org/mailman/listinfo / kde-devel kde-devel] lista de discussão se alguém já está trabalhando em um projeto semelhante.


Para ver as áreas que precisam ajuda, veja [http://www.kde.org/jobs/ esta página].
== Sou desenvolvedor, como posso contribuir com o software KDE? ==


Antes de começar uma nova aplicação, é uma boa idéia verificar o [http://www.kde-apps.org/ KDE-Apps.org] em busca de projetos existentes e também perguntar na lista de emails [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] se alguém já está trabalhando em algo similar.
O Calligra e o KDevelop, apesar de serem muito elogiados, têm muito poucos desenvolvedores, então você pode conferir lá. Não há necessidade de ser desenvolvedor das áreas de trabalho do KDE ou das bibliotecas da plataforma KDE para ajudar. Toda a gama de softwares do KDE é muito modular, para que você possa melhorar perfeitamente uma área sem saber como os outros funcionam.


==Sou um desenvolvedor, como posso contribuir com o KDE?==
Você também pode perguntar em [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] se alguém precisa de ajuda em um aplicativo. Use a versão mais recente do seu software KDE favorito e localize as coisas necessárias. Um gerador de temas? Um editor de esquema do konsole? Melhorar um jogo? Sempre há um pequeno recurso ausente. Vá e implemente!


KOffice e KDevelop, apesar de muito aclamados, possuem muito poucos desenvolvedores, então você pode verificar lá. Não é necessário ser um dos principais desevolvedores do KDE para ajudar.
Você está familiarizado ou atraído por um campo específico? Veja se existe um aplicativo relacionado que possa usar sua ajuda. Ou escreva um. O KDE congratula-se especialmente com mais aplicativos não orientados a geeks.
O KDE é muito modular, sendo possível melhorar uma área sem conhecer como o sistema completo funciona.


Você também pode perguntar na lista [https://mail.kde.org/mailman/listinfo/kde-devel kde-devel] por alguém precisando ajuda com algum aplicativo.
== Eu não sou um desenvolvedor, como posso ajudar? ==
Utilize a última versão do KDE e repare nas coisas necessárias. Um gerador de temas? Um editor de schema para o Konsole? Melhorar um jogo? Sempre há um pequeno recurso faltando. Vá e implemente-o!


Você é familiar ou sente-se atraído por alguma área específica? Verifique se alguma aplicação relacionada pode ser melhorada. Ou escreva uma nova. O KDE precis de mais aplicações orientadas a não-geeks.
Existem muitas tarefas que não exigem habilidades de desenvolvimento. Escreva revisões dos aplicativos para a promoção do KDE (consulte a lista de discussão [https://mail.kde.org/mailman/listinfo/kde-promo kde-promo]), ajude a equipe de documentação (consulte [http: // l10n.kde.org/docs/ i18n.kde.org/doc]), ajude as traduções (consulte [http://l10n.kde.org/ i18n.kde.org]), ajude a filtrar os bugs recebidos (consulte [https://bugs.kde.org/ bugs.kde.org]).  


==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?==
== Onde eu posso encontrar as imagens de Konqi, o dragão? ==


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 />
O SDK do Konqi para algumas pessoas está em [ftp://ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2 ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2]<br /> Foi postado no artist.kde.org antes que o site deixasse de ser atualizado.
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].
Mais imagens estão em [http://kde.org/stuff/clipart.php KDE merchandise]. Além disso, você pode encontrar algumas imagens e modelos não oficiais do Konqi em [http://forum.kde.org/viewforum.php?f=254 Create Konqi with Krita Contest] e [http://sourceforge.net/projects/supertuxkart/ SuperTuxKart ] jogos.


==What is the level required to contribute to KDE? What should I learn? What should I read?==
== Qual é o nível necessário para contribuir com o KDE? O que devo aprender? O que devo ler? ==


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.  
Você precisa conhecer C ++. Leia os [http://qt-project.org/doc/qt-4.8/tutorials.html Qt tutorials] e navegue nos documentos do Qt para se familiarizar-se com o que está disponível do Qt. Depois, leia os [http://techbase.kde.org/Development/Tutorials KDE tutorials] e navegue na arquitetura e documentação. Você também pode ler o [http://flossmanuals.net/kde-guide/ KDE Book], que não pode prejudicar. Mas você não precisa estar familiarizado com toda a arquitetura do KDE para se tornar um desenvolvedor do KDE. Usar as tecnologias do KDE é bastante fácil, então concentre-se no que você realmente precisa, para aprender os outros bits mais tarde.
[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.
[http://techbase.kde.org KDE TechBase] e [http://doc.qt.digia.com/ doc.qt.digia.com] (também em seu {{path | $ QTDIR / doc / html} }) são recursos inestimáveis, tire proveito deles.
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.
Em seguida, procure a fonte, procure os diretórios de exemplos, veja como o outro codificou seus aplicativos. Ler e escrever código é a melhor maneira para aprender.


==How do I get KDE software from the KDE git or SVN repositories?==
== Como obtenho o software KDE nos repositórios git ou SVN do KDE? ==


See the "Building and Running KDE Software From Source" section on the [[Special:myLanguage/Getting_Started|Getting_Started]] page.
Veja a seção [[Special:myLanguage/Getting_Started#Building_and_Running_KDE_Software_From_Source|Building and Running KDE Software From Source]] na seção [[Special: myLanguage / Getting_Started | Getting Started]].


==Can I access KDE source code online?==
== Posso acessar o código fonte do KDE online? ==


Yes
Yes. There are many ways to do this:
* Browse http://websvn.kde.org/ and https://projects.kde.org/
* Browse [http://websvn.kde.org/ websvn.kde.org], and [http://quickgit.kde.org/ quickgit.kde.org].
* Search the source code at http://lxr.kde.org/search
* Search the source code at [http://lxr.kde.org/search lxr.kde.org/search]
* Browse API docs generated from the source code at http://api.kde.org/
* Browse API docs generated from the source code at [http://api.kde.org/ api.kde.org]
* Browse the source code on http://code.woboq.org/kde as in KDevelop


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


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


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


Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.
Don't forget to make {{path|/usr/local/bin/_svndiff}} executable.


==I want to put my app in KDE==
== I want to put my app in KDE ==


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


==Is it better to develop inside or outside KDE?==
== Is it better to develop inside or outside KDE? ==


As core developer Waldo Bastian explains in a copyrighted mail:  
As core developer Waldo Bastian explains in a copyrighted mail:  
<blockquote>
<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.
Being part of KDE means that you have to work together with others. Such cooperation brings along advantages but it also brings along responsibilities.
<br /><br />


:Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.
Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.
<br /><br />


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.
On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.
<br /><br />


You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.
You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.
<br /><br />


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.
In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.
<br /><br />


'''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.
'''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.
Line 95: Line 111:
It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.
It is important to know that but don't be afraid. Usually, things work very well. In 5 years, it has only happened once that a developer had his work put kept in KDE while he wanted to remove it.


==How do I get write access to KDE repositories?==
== How do I get write access to KDE repositories? ==


See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Contribute > Get a KDE Contributor Account]].
See full article at [[Special:myLanguage/Contribute/Get_a_Contributor_Account|Get a KDE Contributor Account]].


Go to [[http://identity.kde.org KDE Identity]] , fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.
Go to [http://identity.kde.org KDE Identity], fill out the form and describe why you need write access. Make sure to specify your full name and e-mail address.


Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.
Please also include the name of your [https://bugs.kde.org/ bugs.kde.org] account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.


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


Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on developer.kde.org)
Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on [[Schedules]] page)


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


==My app is not stable but I would like to have it in KDE==
== 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.
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.==
== I don't want to lose my SVN history. ==


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


==What is kdebindings?==
== 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.  
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?==
== 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.
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.
Line 131: Line 147:
==Can I have a stable and an unstable KDE on the same computer?==
==Can I have a stable and an unstable KDE on the same computer?==


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


==How do I know which version of Qt/KDE I am using?==
== 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.
<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?==
==Qt-copy or Qt from qt.digia.com: if one were doing a clean build of trunk, which would be preferable?==


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


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


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'
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'
Line 153: Line 172:
If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.
If you don't know the name of the directory you want to check out, you can browse websvn.kde.org to find it.


==How can I get one of the KDE application as a standalone tarball?==
== 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.  
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?==
== How do I close my own bug reports? ==


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


==How can I monitor changes made by others?==
== 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.
The [https://mail.kde.org/mailman/listinfo/kde-commits kde-commits] mailinglist carries automatic notifications for all changes made in the KDE repositories. The KDE-Commits mailinglist is very high traffic. An alternative is [http://commitfilter.kde.org/ CommitFilter] which allows you to get notification for only those areas that interest you.


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

Latest revision as of 17:21, 3 November 2019

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

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

Eu quero iniciar este novo aplicativo. O que você aconselha?

Todos concordamos que existem muitos aplicativos do KDE que precisam ser escritos. Mas também existem muitos aplicativos kde que precisam da sua ajuda.

Para ver as áreas em que a ajuda é necessária, consulte this page.

Antes de iniciar um novo aplicativo, é sempre uma boa ideia verificar o KDE-Apps.org e outros serviços de hospedagem de software de código aberto como GitHub , Google Code e SourceForge para aplicativos existentes e para solicitar as / kde-devel kde-devel lista de discussão se alguém já está trabalhando em um projeto semelhante.

Sou desenvolvedor, como posso contribuir com o software KDE?

O Calligra e o KDevelop, apesar de serem muito elogiados, têm muito poucos desenvolvedores, então você pode conferir lá. Não há necessidade de ser desenvolvedor das áreas de trabalho do KDE ou das bibliotecas da plataforma KDE para ajudar. Toda a gama de softwares do KDE é muito modular, para que você possa melhorar perfeitamente uma área sem saber como os outros funcionam.

Você também pode perguntar em kde-devel se alguém precisa de ajuda em um aplicativo. Use a versão mais recente do seu software KDE favorito e localize as coisas necessárias. Um gerador de temas? Um editor de esquema do konsole? Melhorar um jogo? Sempre há um pequeno recurso ausente. Vá e implemente!

Você está familiarizado ou atraído por um campo específico? Veja se existe um aplicativo relacionado que possa usar sua ajuda. Ou escreva um. O KDE congratula-se especialmente com mais aplicativos não orientados a geeks.

Eu não sou um desenvolvedor, como posso ajudar?

Existem muitas tarefas que não exigem habilidades de desenvolvimento. Escreva revisões dos aplicativos para a promoção do KDE (consulte a lista de discussão kde-promo), ajude a equipe de documentação (consulte [http: // l10n.kde.org/docs/ i18n.kde.org/doc]), ajude as traduções (consulte i18n.kde.org), ajude a filtrar os bugs recebidos (consulte bugs.kde.org).


Onde eu posso encontrar as imagens de Konqi, o dragão?

O SDK do Konqi para algumas pessoas está em ftp.kde.org/pub/kde/devel/konqi_sdk.tar.bz2
Foi postado no artist.kde.org antes que o site deixasse de ser atualizado.

Mais imagens estão em KDE merchandise. Além disso, você pode encontrar algumas imagens e modelos não oficiais do Konqi em Create Konqi with Krita Contest e SuperTuxKart jogos.

Qual é o nível necessário para contribuir com o KDE? O que devo aprender? O que devo ler?

Você precisa conhecer C ++. Leia os Qt tutorials e navegue nos documentos do Qt para se familiarizar-se com o que está disponível do Qt. Depois, leia os KDE tutorials e navegue na arquitetura e documentação. Você também pode ler o KDE Book, que não pode prejudicar. Mas você não precisa estar familiarizado com toda a arquitetura do KDE para se tornar um desenvolvedor do KDE. Usar as tecnologias do KDE é bastante fácil, então concentre-se no que você realmente precisa, para aprender os outros bits mais tarde. KDE TechBase e doc.qt.digia.com (também em seu {{path | $ QTDIR / doc / html} }) são recursos inestimáveis, tire proveito deles. Em seguida, procure a fonte, procure os diretórios de exemplos, veja como o outro codificou seus aplicativos. Ler e escrever código é a melhor maneira para aprender.

Como obtenho o software KDE nos repositórios git ou SVN do KDE?

Veja a seção Building and Running KDE Software From Source na seção Getting Started.

Posso acessar o código fonte do KDE online?

Yes. There are many ways to do this:

What should I put in my .subversion/config?

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

[miscellany]
global-ignores = *.moc *.moc.cc *.moc.cpp config.log config.status \
config.cache *.gmo .deps .libs SunWS_cache *.lo *.la *.rpo *.la.closure \
*_la_closure.cpp *_la_closure.cc *_la_closure.cxx *.all_cc.cc *.all_cpp.cpp \
*.all_C.C *.all_cxx.cxx *_meta_unload.cc *_meta_unload.h *_meta_unload.cpp \
*_meta_unload.C *_meta_unload.cxx index.cache.bz2 .memdump Makefile.rules.in \
Makefile.calls.in Makefile.rules Makefile.calls autom4te.cache *.kidl \
*.o *.lo *.la #*# .*.rej *.rej *.pyc

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

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

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

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

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

I want to put my app in KDE

There are three requirements:

  • Your app must compile with the latest version of KDE (git master or SVN trunk).
  • Your app must be stable.
  • Your app must be maintained. You will probably get a good deal of bug reports and wishes. People expect you to fix the bugs and implement the wishes that make sense.

See also the next question.

Is it better to develop inside or outside KDE?

As core developer Waldo Bastian explains in a copyrighted mail:

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

Some of those advantages are: your code ends up on all distro's, people might fix your bugs, you get free translations and documentation, you get tons of bugreports.

On the other side there are disadvantages and responsibilities: you will have to communicate with other developers about your work, other people might make changes to your code, you will have to respect release freezes, you get tons of bugreports and people actually expect that you fix them as well (what are they smoking?), people expect you to maintain your code.

You can't chose for the advantages and ignore the responsibilities that come with it, it's a complete package, it's both or nothing.

In general it should be the author of a piece of software that chooses to put his application in KDE's repositories. We usually don't put software in KDE's repositories unless the author wishes to do so. The other way around, if the author prefers to work on his application elsewhere then that's his right as well. Unless there is a split in the actual group of people working on the application it makes no sense to fork the development of an application because of that.

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

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

How do I get write access to KDE repositories?

See full article at Get a KDE Contributor Account.

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

Please also include the name of your bugs.kde.org account, if non-existent please create one so that it can be given usual developer rights. Closing bugs.kde.org reports with keywords in commit comments only works if the email address of your KDE Identity and bugs.kde.org accounts match. You can change your bugs.kde.org address in the Bugzilla user settings.

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

See also #How do I create a SSH key?

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

Although there are few restrictions on repository commit rights, we expect you not to disrupt other developers' code without their consent. You must also respect the feature freezes of the release schedule (published on Schedules page)

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

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

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

I don't want to lose my SVN history.

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

What is kdebindings?

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

Does the feature freeze apply to playground?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

How do I close my own bug reports?

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

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

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

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

How do I create a SSH key?

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

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

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

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

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

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

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

How can I monitor changes made by others?

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