Contribute (pt BR)

Revision as of 23:28, 19 November 2009 by Dherik (Talk | contribs)

Jump to: navigation, search


Contents

Contribute

Esta página pretende dar uma visão geral dos diferentes aspectos do desenvolvimento do KDE, em particular a assuntos relacionados com programação. O projeto KDE dá as boas vindas a todos dispostos a ajudar.

{{{3}}}
 
noframe
Existem várias maneiras de participar do desenvolvimento do KDE, as quais podem ser divididas em diversas categorias:
Documentação, Tradução, Desenvolvimento, Usabilidade, Acessibilidade, Artwork, Promoção

Não é um programador? Veja as páginas do KDE em como participar para conferir outras maneiras que você pode ajudar. Veja também: Bugsquad!

Nota


Notícias e Fontes de E-mail

A direção geral do projeto KDE é determinada por aqueles que fazem o trabalho - não existe nenhum tipo de plano único o qual determine como o KDE irá ser no futuro.

Se você quer saber o que está atualmente acontecendo, então existem um número de fontes de informação as quais você deve considerar:

Listas de e-mail
Provavelmente a melhor maneira de encontrar o que está acontecendo no desenvolvimento do KDE. Os arquivos estão disponíveis aqui.
CommitFilter
Notificação de recebimento de mudanças do SVN em áreas de seu interesse.
KDE Commit-Digest
Um resumo semanal das mudanças ocorridas no SVN.
The Dot
A página de notícias do KDE.

Getting Started with Coding

Getting started at coding for KDE is a matter of finding something to fix, and fixing it. You may want to consult the module overview to help find what you are looking for; once you have fixed something, you will want to send in a patch. If you do that a few times, you may want to apply for an SVN account so you can fix things directly.

C++

KDE is mostly written in C++. If you are not familiar with C++, you should do at least some work on it. There are a number of good books on C++ - an excellent source is Bruce Eckel's "Thinking in C++", which is available both as a free download and as a printed document. It isn't essential to understand everything before you start in KDE, but you do need to understand basic syntax and operations.

Qt

To become proficient with KDE coding, you should understand the Qt toolkit. If you are not familiar with Qt, you should work through the tutorials included with Qt (Qt4 version, Qt3 version).

If you are more into multimedia and videos for a start you might want to spend two amazing minutes on watching Building a Simple Help Documentation Browser with Qt4 Designer. If that got your attention you might also want to watch the video introduction Hello Qt by Mark Summerfield which is part of the Trolltech Developer Days 2006 presentations.

If you need a gentler introduction to Qt, or would just like an alternative view, then you may wish to look at the The Independent Qt Tutorial (Currently offline due to book contract).

If you prefer to learn Qt by reading a traditional book, take a look at Trolltechs book page. More suggestions on becoming familiar with Qt4 are available here as well.

KDE

A range of information on KDE techniques is available in the tutorial section. Note that some of these tutorials still target KDE3, though they should be at least partly applicable.

You will also find useful information on KDE coding in the FAQs section. This information may also be somewhat dated for KDE4, however much of it is broadly applicable, even outside KDE.

You can also read KDE coding books.

Last, but by no means least, KDE comes with extensive class (Application Programmer Interface) documentation. This is available in the KDE API Reference Manuals section, which also contains a number of useful links on how to write or update the class documentation. You can also generate these on your own machine, or refer to a more up-to-date online version at The English Breakfast Network.

A more detailed description of the steps above is available in our Programming Guide.

Getting Involved in Bug Hunting and Application Quality

There is a large number of applications within KDE, and not all of them have a maintainer dedicated to managing bugs and generally helping out with all the issues associated with turning some working code into a polished application.

If you are interested in helping out with KDE, but don't know where to start, visit Contribute Website for more information. Note that you do not need any programming skills to become involved. In particular develpers regurarly publish so-called Junior Jobs to encourage new contributions.

Of course, you can become involved in bug hunting without being part of the KDE Quality Team - just create yourself an account on the KDE bug tracking system, and start searching / sorting through the bugs. Again, you don't have to have programming skills - it helps the programmers enormously just to have a procedure that allows a bug to be consistently reproduced.

The Bugsquad tries to keep track of bugs in KDE software and make sure that valid bugs are noticed by developers. You do not need any programming knowledge to be in the Bugsquad; in fact it is a great way to return something to the KDE community if you cannot program.

Conseguir respostas para suas perguntas

If your question concerns KDE development, your options are pretty much the same general user ones, with some modifications:

  • Read the Developer FAQ. Many common developer questions have been answered in the KDE Developer FAQ
  • Search/browse KDE websites. A lot of questions can also be answered from the KDE websites, and the documentation included on it. You can search all the KDE websites on the homepage. In addition, you can browse the KDE developer website.
  • Search mailing lists. A lot of questions have already been answered on the KDE mailing lists, particular the lists kde-devel, kde2-porting, kde-core-devel, kde-games-devel, kfm-devel and koffice-devel. You can search these lists either at lists.kde.org. You should always search for your answer before asking questions on the mailing lists. When you ask a question on a mailing list you are emailing thousands of people -- please do this only if the answer is not available through a simple search.
  • Search engines. Do not forget about your favorite search engine. One of the best search engines is Google. With Google you can also search the great bulk of Usenet news sites, which is also particularly helpful, especially for general programming and gcc-related questions.
  • Ask on KDE mailing lists. If you still do not have an answer, try asking your question on one of the KDE mailing lists listed above.

A full list of KDE mailing lists is available here and here.

Historical Sources

KDE Traffic
Summary of the development mailing lists. KDE Traffic ran for 76 issues, from 10 March 2001 until 16 April 2004. The KDE Commit-Digest (described above) is its logical successor.



KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal