|
 |
3c5068 |
<sect1 id="repo-convs-publishing">
|
|
|
3c5068 |
|
|
|
3c5068 |
<title>Repository Publishing</title>
|
|
|
3c5068 |
|
|
|
3c5068 |
<para>
|
|
|
3c5068 |
When you perform changes inside your working copy, those
|
|
|
3c5068 |
changes are local to your working copy only. In order for you
|
|
|
3c5068 |
to share your changes with others, you need to commit them up
|
|
|
3c5068 |
to the central repository the working copy you are using was
|
|
|
3c5068 |
initially downloaded from. To commit your changes up to the
|
|
|
3c5068 |
central repository you use the <command>commit</command>
|
|
|
34cc77 |
command from the Subversion's client you've installed in your
|
|
|
34cc77 |
workstation.
|
|
|
3c5068 |
</para>
|
|
|
3c5068 |
|
|
|
3c5068 |
<para>
|
|
|
3c5068 |
Initially, when you get registered inside &TCAR;, you won't be
|
|
|
3c5068 |
able to publish your changes to &TCAR; immediatly. It is
|
|
|
34cc77 |
necessary that you prove your interest in contributing first
|
|
|
34cc77 |
sending a mail to the
|
|
|
34cc77 |
url="http://lists.centos.org/mailman/listinfo/centos-devel">CentOS
|
|
|
34cc77 |
Developers mailing list</ulink> (
|
|
|
34cc77 |
url="mailto:centos-devel@centos.org">centos-devel@centos.org</ulink>),
|
|
|
3c5068 |
preferably in conjunction with a description of the changes
|
|
|
3c5068 |
you pretend to commit. This restriction is necessary in order
|
|
|
3c5068 |
to protect the source repository from spammers.
|
|
|
3c5068 |
</para>
|
|
|
3c5068 |
|
|
|
3c5068 |
<para>
|
|
|
3c5068 |
Once you've received access to publish your changes, they will
|
|
|
3c5068 |
remain valid to you and there is no need for you to request
|
|
|
3c5068 |
permission to publish new changes as long as you behave as a
|
|
|
3c5068 |
good cooperating citizen.
|
|
|
3c5068 |
</para>
|
|
|
3c5068 |
|
|
|
3c5068 |
<para>
|
|
|
3c5068 |
As a good cooperating citizen one understand of a person who
|
|
|
3c5068 |
respects the work already done by others and share ideas with
|
|
|
3c5068 |
authors before changing relevant parts of their work,
|
|
|
3c5068 |
specially in situations when the access required to realize
|
|
|
3c5068 |
the changes has been granted already. Of course, there is a
|
|
|
3c5068 |
time when conversation has taken place, the paths has been
|
|
|
3c5068 |
traced and changing the work is so obvious that there is no
|
|
|
3c5068 |
need for you to talk about it; that's because you already did,
|
|
|
3c5068 |
you already built the trust to keep going. As complement, the
|
|
|
3c5068 |
mailing list mentioned above is available for sharing ideas in
|
|
|
3c5068 |
a way that good relationship between community citizens could
|
|
|
3c5068 |
be constantly balanced.
|
|
|
3c5068 |
</para>
|
|
|
3c5068 |
|
|
|
3c5068 |
<para>
|
|
|
3c5068 |
The relationship between community citizens is monitored by
|
|
|
3c5068 |
repository administrators. Repository administrators are
|
|
|
3c5068 |
responsible of granting that everything goes the way it needs
|
|
|
34cc77 |
to go in order for &TCAR; to accomplish its mission (see
|
|
|
34cc77 |
linkend="repo-convs-mission" />).
|
|
|
3c5068 |
</para>
|
|
|
3c5068 |
|
|
|
3c5068 |
</sect1>
|