[RFR] wml://devel/join/nm-amhowto.wml
un saludo.
#use wml::debian::template title="Mini-CÓMO para gestores de solicitud de nuevos desarrolladores de Debian"
#use wml::debian::translation-check translation="1.30" maintainer="Fernando
Cerezal"
<UL>
<LI>Copyright Julian Gilbey <jdg@debian.org>, Septiembre de 2000</LI>
<LI>Este documento está cedido al dominio público.</LI>
</UL>
<P>
La fuente de todo conocimiento son las páginas del Nuevo Desarrollador.
Empiece en
<A HREF="newmaint">http://www.debian.org/devel/join/newmaint</A>
y eche un vistazo hasta que se familiarice con los conceptos. Ahí se
describen sus responsabilidades como GS (Gestor de Solicitud).</P>
<P>
Como GS, debería estar suscrito a la lista de correo de Nuevos
Desarrolladores: debian-newmaint@lists.debian.org. Siéntase libre de pedir
ayuda allí; ¡somos una lista amigable e intentamos ayudar a los voluntarios
a entrar en el proyecto! Tenga en cuenta que ésta es una lista archivada de
forma pública, de manera que las preguntas de naturaleza estrictamente
personal deberían ser dirigidas al Recepcionista (<I>Front Desk</I>)
de forma privada. Además, evite por favor enviar cosas como
identificaciones fotográficas a esta lista.</P>
<P>
Las otras páginas web cruciales son la base de datos:
<A HREF="http://nm.debian.org/";>http://nm.debian.org/</A>.
Recibirá una cuenta de acceso ahí (y no está cifrada, de manera que no use
una clave delicada); mire el final de la página. Esta base de datos se usa
para registrar el progreso de sus candidatos. Además podrá especificar
la cantidad de candidatos que desea controlar al mismo tiempo (vaya al
enlace "Your Profile"
que hay al lado para hacerlo). Si alguna vez le falta tiempo para tomar
a su cargo más candidatos, basta con cambiar este número a cero.</P>
<P>
El resto de las páginas de la base de datos son bastante autoexplicativas.
Si alguna vez tiene un candidato que tarda mucho en responder o que
necesita esperar un par de meses (vacaciones o lo que sea), siempre puede
dejarlo "pendiente" de manera que pueda pasar a otro candidato. Hay un
campo de texto "AM Comments"
para anotar las razones para esta acción, o para indicar cualquier
información significativa de interés para el recepcionista
y el DAM (Gestor de cuentas de desarrolladores).</P>
<P>Las tres direcciones de correo de interés son:</P>
<DL>
<DT>Lista de NM: debian-newmaint@lists.debian.org</DT>
<DD>Esta lista de correo cubre todos los aspectos del proceso de
Nuevos Desarrolladores, y la utiliza el grupo de NM (recepcionista,
Gestores de Solicitud, Gestor de Cuentas de Desarrolladores,
etc.) y otros para discutir asuntos de administración,
solicitantes y el proceso de Nuevos Desarrolladores. Esta lista de
correo es pública y se archiva, así que, por favor, no envíe
información muy personal a ella.</DD>
<DT>Recepcionista: new-maintainer@debian.org</DT>
<DD>Es donde se envían las solicitudes al principio, y donde se
envían los informes finales. Se debe dirigir aquí cualquier pregunta
personal sobre solicitudes individuales que sea inapropiada para un
foro público.</DD>
<DT>Gestores de Cuentas de Debian (DAMs): da-manager@debian.org</DT>
<DD>Lugar donde se envía también el informe final. Los DAM son
responsables de crear las cuentas en las máquinas de Debian y de
añadir las claves GPG al llavero (<I>keyring</I>). También toman las
decisiones finales sobre cada solicitud, como delegados oficiales
del Líder del Proyecto Debian para el proceso
de Nuevos Desarrolladores. ¡No moleste innecesariamente a los DAM, ya
que suelen estar muy ocupados!</DD>
</DL>
<P>
Por último, para facilitarle la vida, encontré útil crear algunas cartas
modelo, que adjunto más adelante como sigue:</P>
<P>
Tenga en cuenta que esto se mantiene sólo por su valor histórico.
Realmente debería usar los nuevos <A HREF =
"http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/templates/?cvsroot=nm-templates";>nm-templates</A>.
Sepa también de algunos comentarios útiles sobre producir buenos informes para AM (lea el <a href =
"http://lists.debian.org/debian-newmaint/2003/debian-newmaint-200303/msg00018.html";>primer</a>
y <a href =
"http://lists.debian.org/debian-newmaint/2004/debian-newmaint-200402/msg00010.html";>segundo</a>
correo con comentarios).</P>
<UL>
<LI><A HREF="#ap1">Apéndice 1: Ejemplo de mensaje inicial</A></LI>
<LI><A HREF="#ap2">Apéndice 2: Ejemplo de mensaje sobre tareas,
procedimientos y una introducción a la filosofía</A></LI>
<LI><A HREF="#ap3">Apéndice 3: Ejemplos de preguntas sobre filosofía</A></LI>
<LI><A HREF="#ap4">Apéndice 4: Ejemplo de informe para la lista de GS
(posiblemente firmada con GPG y enviada también a
debian-newmaint-admin@lists.debian.org); debería ser adjunta
en el informe final al
Recepcionista/DAM</A></LI>
<LI><A HREF="#ap5">Apéndice 5: Ejemplo de informe para el
Recepcionista y el DAM (firmada con GPG y enviada a
new-maintainer@debian.org y da-manager@debian.org)</A></LI>
</UL>
<strong>Nota del traductor</strong>: Se han mantenido los apéndices en el
inglés original, ya que será el idioma en que sean enviados.
<HR>
<H3><A NAME="ap1">APENDICE 1: EJEMPLO DE MENSAJE INICIAL</A></H3>
<PRE>
Hello *****!
I have just been appointed Application Manager for your Debian
maintainership application.
As a first step, have you checked out the New Maintainer corner of the
website? Have a look at http://www.debian.org/devel/join/newmaint,
and especially at the checklist referred to from there. That's what
we'll have to work through together.
So, if you can start by letting me have the following, we should be
able to progress fairly quickly:
- GPG key (preferably signed by a current developer or certification
authority)
- If your GPG is not signed by a current developer, you will need to
also provide a piece of GPG-signed digitally photo ID (let me know
if this is a problem; there are other ways to handle this step, but
this is the easiest)
- your preferred account name for the Debian machines
- the email address you would like to be subscribed to debian-private
Finally, please tell me about yourself and what you intend to do
for Debian (and how this fits in with The Social Contract). Also, how
you came to Linux and free software, and why you want to volunteer your
time. It would be nice if I could post some biographical information about
you to a public mailing list, so other developers can get to know you.
Please indicate which parts I may publish, and which not.
If you have packaged an application for Debian already, please give
me a URL where I can get the sources (the .diff and .orig) and the
package itself (the .deb).
Looking forward to helping you through the process. The next step is
"Philosophy and Procedures" -- I will ask you a few questions by e-mail
which you have to answer.
</PRE>
<HR>
<H3><A NAME="ap2">APÉNDICE 2: EJEMPLO DE MENSAJE SOBRE HABILIDADES,
TAREAS E INTRODUCCIÓN A LA FILOSOFÍA</A></H3>
<PRE>
"Skills" and "Philosophy".
The next thing we have to figure is whether you yet know enough to
maintain a Debian package, and if not, let me help you! You've said
what you intend to package; have you attempted to do so yet? It's
often easiest if you take over an existing package at first: then you
get to see how someone else has done it. You should also read how the
Bug Tracking System (BTS) works: see /usr/share/doc/debian/bug* or
http://bugs.debian.org/.
A word on mailing lists: there are quite a lot of Debian mailing lists
now and packaging-related packages, and I'd just like to check with
you whether you know about the key ones. I think all of the packages
are listed as dependencies of task-debian-devel, but you may not be
aware of what you have got.
Packages:
dpkg-dev All of the primary tools needed to put a Debian package
together: dpkg-buildpackage, dpkg-source, etc.
debhelper A very useful set of scripts designed to make
debian/rules files more readable and uniform.
debian-policy
Describe the policy relating to packages and details of
the packaging mechanism. Cover everything from
required gcc options to the way the maintainer scripts
(postinst etc.) work, package sections and priorities,
etc. An absolute must-read. Also useful is the file
/usr/share/doc/debian-policy/upgrading-checklist.txt,
which lists changes between versions of policy.
doc-debian Lots of useful Debian-specific documentation: the
constitution and DFSG, explanation of the Bug Tracking
System (BTS), etc.
maint-guide
The New Maintainer's Guide to making Debian packages.
devscripts Lots of useful (and not-so-useful) scripts to help build
packages.
developers-reference
Lots of information on procedures and the like.
dupload Automatically upload packages to the archive once they
or dput are built.
fakeroot Build packages without having to be root.
It's not half as bad as it seems at first, but the long-term
advantages to the maintainer and user of having such detailed
descriptions of package building should be clear ;-)
And as for mailing lists, you do not really need to read lots, but the
most significant ones are probably:
debian-announce: Major public announcements
debian-devel-announce: Major announcements to the developer community
These two lists are must-subscribes. Everything else is optional. I
abbreviate 'debian-' to '-' from now on!
-security-announce:
security updates to stable
-private: you'll be subscribed automatically when your new-maintainer
application is accepted; sensitive discussions, flamewars
etc. You can unsubscribe if you wish.
-devel: general mailing list for developer issues
-policy: where possible changes to debian-policy are discussed
There are many others; check the mailing list page on the web site
for details.
The other thing we have to discuss is "philosophy".
Have you read the Debian Social Contract
(/usr/share/doc/debian/social-contract.txt)? Do you agree to follow
it in your Debian-related work? We'll ask some more detailed
questions next time around.
</PRE>
<HR>
<H3><A NAME="ap3">APENDICE 3: EJEMPLO DE PREGUNTAS SOBRE FILOSOFIA</A></H3>
<PRE>
Philosophy
----------
We have to check that you understand the Social Contract and the Debian
Free Software Guidelines (DFSG). Have you read them? If not, please
do so. You can find them in /usr/share/doc/debian or on
http://www.debian.org
First, please explain the key points of the Social Contract and the
DFSG _in your own words_ (15-20 lines).
Secondly, a few questions, based on them:
- Donald Knuth, author of TeX, insists that no-one has the right to
modify the source code of TeX, and that any changes must be made using
"change files" (a sort of patch file). Is this allowed for a program
for the main section of Debian?
- What is Debian's (current) approach to non-free software? Why? Is
non-free part of the Debian System?
- Debian was offered a Debian-specific license to package a certain
piece of software (I forget which). Would we put it in main?
- Do you know (and can you explain) the difference between free speech
and free beer? Is Debian mainly about free speech or free beer?
- The e-mail client pine is in non-free. Can you tell me the
difference between main, contrib and non-free? Do you know what's
wrong with Pine's current license in regard to the DFSG? (If you
don't know this, never mind).
- At http://people.debian.org/~wolfie/mpg123_copyright you can
find the license of mpg123. Can you tell me why this program
is non-free according to the DFSG?
Do you agree to uphold the Social Contract and the DFSG?
If you are accepted as a Debian developer, you will get accounts
on the Debian machines. Have you read the Debian Machine Usage
Policies (DMUP) at http://www.debian.org/devel/dmup ? Do you
accept them?
I'm sure you have read the Debian Developers' Reference at
http://www.debian.org/doc/packaging-manuals/developers-reference/
- What are Non-Maintainer Uploads (NMUs) and when would you do an NMU?
- Tell me 3 different methods to close a bug in the BTS.
- What would you do if a bug was reported against your package and
you are not able to fix it yourself?
- You've just heard about this great program and you would like to package
it. What would you do?
- Do you know what 'lintian' is? Why is it useful?
- What does version 3.4-2.1 mean? What Debian control file would you
put this in? (Hint: NMU)
- You have a package in contrib, why would it have to go there? What could
you do (in theory at least) to get it into main?
- If you had a file in your package which usually gets changed by a system
administrator for local settings, how would you make sure your next
version of the package doesn't overwrite it?
- What would you do if you wanted to retire from the project and let
other developers maintain your packages?
</PRE>
<HR>
<H3><A NAME="ap4">APENDICE 4: EJEMPLO DE INFORME PARA LA LISTA AM</A></H3>
<PRE>
Report for new developer applicant:
Summary: Accept/Don't accept
1. Background
-------------
2. Identification
-----------------
3. Philosophy and Procedures
-----------------------------
4. Tasks and Skills
-------------------
</PRE>
<HR>
<H3><A NAME="ap5">APENDICE 5: EJEMPLO DE INFORME PARA EL RECEPCIONISTA Y DAM</A></H3>
<PRE>
Front Desk/DAM Report for new developer applicant:
Summary: Accept/Don't accept
1. The applicant's photo ID which is digitized and signed by the
applicant (if necessary)
* Attached/Not necessary
2. The applicants GPG (or PGP if needed) public key for Identification
* Attached
3. Logs of the discussions with the applicant to satisfy steps 2-4 in
the checklist.
* Attached [do not edit out any important contents; however, feel
free to remove unimportant mail headers (but do retain From, Date,
etc) and please remove big attachments such as .orig and .diff files
sent during the T&S stage.]
* Also attached: summary as sent to AM list
4. The applicants GPG public key (RSA/IDEA keys created by PGP are not
accepted now) to sign his (or her) Debian packages. This will be
incorporated into the Keyring of Debian
* Attached/As in 2
5. The request from the applicant for their account name on Debian
(used as <account>@debian.org)
* ???
6. The request from the applicant for the email address which will be
used to forward the emails at <account>@debian.org.
* ???
</PRE>
<HR>
<A HREF="./nm-amchecklist">De vuelta a "Nota para Gestores de solicitud"</A>
Reply to: