Author: francisco
Date: Wed Aug 22 08:41:08 2007
New Revision: 1068
Log:
Capítulo 8. Sección "territoriality". Párrafo 3.
Modified:
trunk/es/ch08.xml
Modified: trunk/es/ch08.xml
==============================================================================
--- trunk/es/ch08.xml (original)
+++ trunk/es/ch08.xml Wed Aug 22 08:41:08 2007
@@ -362,45 +362,25 @@
diferente; la gente tiene áreas donde es más o menos influyente, y los
inexpertos
habitualmente dejan que los expertos tomen las riendas en ciertos dominios
del proyecto. Pero la clave es que todo esto es algo voluntario; la autoridad
-se gana medianta la competencia y un juicio probado,
-
-<para>Watch out for participants who try to stake out exclusive
-ownership of certain areas of the project, and who seem to want to do
-all the work in those areas, to the extent of aggressively taking over
-work that others start. Such behavior may even seem healthy at first.
-After all, on the surface it looks like the person is taking on more
-responsibility, and showing increased activity within a given area.
-But in the long run, it is destructive. When people sense a "no
-trespassing" sign, they stay away. This results in reduced review in
-that area, and greater fragility, because the lone developer becomes a
-single point of failure. Worse, it fractures the cooperative,
-egalitarian spirit of the project. The theory should always be that
-any developer is welcome to help out on any task at any time. Of
-course, in practice things work a bit differently: people do have
-areas where they are more and less influential, and non-experts
-frequently defer to experts in certain domains of the project. But
-the key is that this is all voluntary: informal authority is granted
-based on competence and proven judgement, but it should never be
-actively
-<emphasis>taken</emphasis>. Even if the person desiring the authority
-really is competent, it is still crucial that she hold that authority
-informally, through the consensus of the group, and that the authority
-never cause her to exclude others from working in that area.</para>
-
-<para>Rejecting or editing someone's work for technical reasons is an
-entirely different matter, of course. There, the decisive factor
-is the content of the work, not who happened to act as gatekeeper. It
-may be that the same person happens to do most of the reviewing for a
-given area, but as long as he never tries to prevent someone else from
-doing that work too, things are probably okay.</para>
-
-<para>In order to combat incipient territorialism, or even the
-appearance of it, many projects have taken the step of banning the
-inclusion of author names or designated maintainer names in source
-files. I wholeheartedly agree with this practice: we follow it in the
-Subversion project, and it is more or less official policy at the
-Apache Software Foundation. ASF member Sander Striker puts it this
-way:</para>
+se gana mediante la competencia y conocimiento probado, y nunca debe ser
+<emphasis>conquistada</emphasis> activamente. Incluso si la persona deseando la
+autoridad es realmente competente, aún así es crucial que maneje esa
+autoridad de manera informal, a través del consenso del grupo, y sin apartar
+a nadie de colaborar en su area de influencia.</para>
+
+<para>Por supuesto, rechazar o editar el trabajo de otro por motivos técnicos
es
+un asusto totalmente distinto. En este caso, el factor decisivo es el contenido
+del trabajo, no quien actúa como portero. Podría suceder que la misma persona
+realize la mayor parte de revisiones para un área particular, pero mientras no
+evite que otros hagan su trabajo, las cosas deberían ir bien.</para>
+
+<para>Para combatir cualquier territorialismo incipiente, o incluso la mera
+apariencia del mismo, muchos proyectos han tomado medidas como la de prohibir
+la inclusión del nombre del autor, o de los encargados elegidos, en el
+código fuente. Yo estoy de acuerdo de todo corazón con esta práctica; la
+utilizamos en el proyecto Subversion y es, más o menos, la política oficial
+en la Apache Software Foundation. Los miembros del ASF Sander Striker lo
+explica de esta forma:</para>
<blockquote>
<para><emphasis>At the Apache Software foundation we discourage the
_______________________________________________
Producingoss-translators mailing list
[email protected]
http://www.red-bean.com/mailman/listinfo/producingoss-translators
