Added: Dec 2, 2008
From: h4ck3rm1k3
Duration: 7:13
http://packages.debian.org/sid/developers-reference - - to the person they sponsored. It is also allowed to post a query to [ debian-devel@lists.debian.org], asking if anyone is aware of the whereabouts of the missing maintainer. Please Cc: the person in question. Once you have gathered all of this, you can contact [ mia@qa.debian.org]. People on this alias will use the information you provide in order to decide how to proceed. For example, they might orphan one or all of the packages of the maintainer. If a package has been NMUed, they might prefer to contact the NMUer before orphaning the package *** perhaps the person who has done the NMU is interested in the package. One last word: please remember to be polite. We are all volunteers and cannot dedicate all of our time to Debian. Also,you are not aware of the circumstances of the person who is involved. Perhaps they might be seriously ill or might even have died *** you do not know who may be on the receiving side. Imagine how a relative will feel if they read the e-mail of the deceased and find a very impolite, angry and accusing message! On the other hand, although we are volunteers, we do have a responsibility. So you can stress the importance of the greater good *** if a maintainer does not have the time or interest anymore, they should let go and give the package to someone with more time. If you are interested in working in the MIA team, please have a look at the README file in /org/qa.debian.org/ mia on qa.debian.org where the technical details and the MIA procedures are documented and contact [mia@qa.debian.org]. 7.5.**Interacting with prospective Debian developers Debian's success depends on its ability to attract and retain new and talented volunteers. If you are an experienced developer, we recommend that you get involved with the process of bringing in new developers. This section describes how to help new prospective developers. 7.5.1.**Sponsoring packages Sponsoring a package means uploading a package for a maintainer who is not able to do it on their own, a new maintainer applicant. Sponsoring a package also means accepting responsibility for it. New maintainers usually have certain difficulties creating Debian packages *** this is quite understandable. That is why thesponsor is there, to check the package and verify that it is good enough for inclusion in Debian. (Note that if the sponsored package is new, the ftpmasters will also have to inspect it before letting it in.) Sponsoring merely by signing the upload or just recompiling is definitely not recommended. You need to build the source package just like you would build a package of your own. Remember that it doesn't matter that you left the prospective developer's name both in the changelog and the control file, the upload can still be traced to you. If you are an application manager for a prospective developer, you can also be their sponsor. That way you can also verify how the applicant is handling the 'Tasks and Skills' part of their application. 7.5.2.**Managing sponsored packages By uploading a sponsored package to Debian, you are certifying that the package meets minimum Debian standards. That implies that you must build and test the package on your own system before uploading. You cannot simply upload a binary .deb from the sponsoree. In theory, you should only ask for the diff file and the location of the original source tarball, and then you should download the source and apply the diff yourself. In practice, you may want to use the source package built by your sponsoree. In that case, you have to check that they haven't altered the upstream files in the .orig.tar.gz file that they're providing.Do not be afraid to write the sponsoree back and point out changes that need to be made. It often takes several rounds of back-and-forth email before the package is in acceptable shape. Being a sponsor means being a mentor. Once the package meets Debian standards, build and sign it with dpkg-buildpackage -kKEY-ID before uploading it to the incoming directory. Of course, you can also use any part of your KEY-ID, as long as it's unique in your secret keyring. The Maintainer field of the control file and the changelog should list the person who did the packaging, i.e., the sponsoree. The sponsoree will therefore get all the BTS mail about the package. If you prefer to leave a more evident trace of your sponsorship job, you can add a line stating it in the most recent changelog entry. You are encouraged to keep tabs on the package you sponsor using Section**4.10, ***The Package Tracking System* ** . 7.5.3.**Advocating new developers See the page about advocating a prospective developer at the Debian web site. 7.5.4.**Handling new maintainer applications Please see Checklist for Application Managers at the Debian web site. Chapter**8.**Internationalizing, translating, being
Channel: Education
Tags: debian developers reference
Rating: ( ratings) Views: 17 Comments: 0
