[Kde-i18n-pt_br] Fwd: Account created for KDE SVN

[Joao Emanuel]

Certo Fernando o Stephan já criou a conta. Bem vou pegar o pacote
extragear-graphics, ok? Como já é de interesse da lista estou enviando
para lista também, ok?

TIA

---------- Forwarded message ----------
From: Stephan Kulow <coolo em kde.org>
Date: 29/04/2006 10:51
Subject: Account created for KDE SVN
To: Joao Emanuel <joaoemanuel1981 em gmail.com>
Cc: sysadmin em kde.org


Your account has been created.
Your login is "joaoemanuel". Please find instructions attached.




--
Joao Emanuel
Mensageiros
MSN: joaoemanuel1981 em gmail.com.br
Jabber: joaoemanuel1981 em jabber.org
(se quiser me em envie o seu endereço
do seu mensageiro para incluir)
-------------- Próxima Parte ----------
Note: Your username, name and email, have been added to kde-common/accounts
(in SVN). If your e-mail changes, please update that file.

1. SVN QuickStart
=================
First, read the online tutorial about the KDE SVN repository:
http://developer.kde.org/documentation/tutorials/subversion/index.html

Do NOT commit any documentation or translation into your source subdirectory.
Translations go to l10n, and documentation goes to <module>/doc/<appname>.

2. Monitoring Development
=========================
For every commit to the KDE SVN repository a notification messages is send to
the kde-commits em kde.org mailinglist. This mailinglist is VERY high traffic!
See https://mail.kde.org/mailman/listinfo/kde-commits

If you only want to get notifications about specific areas of KDE, such as
the application(s) you are working on, you can use CVSfilter.
See http://commitfilter.kde.org/

3. KDE Development
==================
For more details about the way KDE development works:
read the KDE Developer FAQ at http://developer.kde.org/documentation/other/developer-faq.html,
the KDE Developer's Checklist at http://developer.kde.org/documentation/other/checklist.html
and the KDE Commit Policy at http://developer.kde.org/policies/commitpolicy.html.

There are several applications and tools available which can assist with SVN and
KDE Development in general, including example code. Refer to kdesdk/README for
more information.

4. KDE SVN keywords
===================
When you commit changes to SVN you will be asked for a description
of your commit. There are several special keywords defined that you can
use in this description. These keywords are always uppercase and followed
by a colon. Each keyword should be placed on a line of its own.
The following keywords can be used:

BUG: <bugnumber>
        Marks the bug as closed by CC'ing the commit message to
<bugnumber>-done em bugs.kde.org This keyword will also be used to
automatically extract entries for the release changelog.

CCBUG: <bugnumber>
        CC's to the bugreport by sending mail to <bugnumber>@bugs.kde.org

CCMAIL: <email-address>
        CC's to the given e-mail address.

CVS_SILENT or SVN_SILENT:
        Marks the commit message "silent" by adding "(silent)" to the
        subject of the mail to allow filtering out trivial commits.
        Use this tag carefully and only for really uninteresting,
        uncontroversial commits.

FEATURE: [<bugnumber>]
        Marks the feature as implemented by CC'ing the commit message to
<bugnumber>-done em bugs.kde.org. This keyword will also be used to
automatically extract entries for the release changelog, so it makes sense to
use it for new features even if you don't have a bugnumber for the feature.

GUI:
        Indicates a change in the user interface. This is used to make
the documentation team aware of such changes.



Hope this helps, have fun !

The KDE SVN admins, sysadmin em kde.org