On Friday 15 October 2010 13:08:10 Luca Bertoletti wrote: > Hello I'm italian linux users.I worked for erickson and I studied I.T at > Università di Milano Bicocca. > I know shell scripting and this programmation languages: pyton, perl, java, > c, c++ and for the dbms sql languages. > I want to know if I want to became an Debian developer how can I do? > thanks for your attention Becoming a DD is not (directly) based on your curriculum vitae, but rather on the quality and amount of volunteer work done for Debian, particularly around packaging. I believe the "New Maintainer's Guide" is the current official reference for the process, but I don't have a link available. Anything further is based on my experience watching from the outside (IANADD) and my or may not be official (TINASOODP). Becoming a DD is about producing work that helps Debian grow, usually by increasing the number of available packages or (preferred) increasing the quality of existing packages. For some time, another DD will look over your work and perform the final upload to Debian, but you will share in the credit (or failure) of the work. Once you've produced enough, you'll be able to join the Debian network of trust and the project will start accepting work directly from you, which makes you a DD. As a volunteer project, there's always plenty of work to do, but you'll rarely get work "assigned" to you by someone else. Instead, you'll have to be self- directing and find place(s) you want to contribute. This list, as well as the mailing lists for each maintenance team, are good places to get your work reviewed and find a DD to perform in final upload, but not a place were you can get "assignments". Assuming you use Debian, I recommend starting with the "wnpp-alert" and "rc- alert" tools. These tools will inspect a running Debian system to find installed packages with open bugs. You can then view these bugs via the web interface or receive more details on them via email. You can also manipulate the bugs via email. Eventually, you'll find a bug that you can address with your skills. If the package currently has a maintainer, work with them to address the bug. Oftimes, this will entail generating a patch and attaching it to the bug. If the maintainer is non-responsive, attaching a patch to the bug usually a good idea and might be a way to start the MIA process. If the package does not have a maintainer, prepare a new source package and use this list and/or a team list to get that package uploaded to Debian and continue to address bugs in that package. There are a number of tools that are helpful in preparing new (patches to) source packages, but they are fairly well documented, both on the Debian web site and in the mailing list archives. If you have specific questions, this list can generally answer them. Examples include: *-buildpackage, debhelper, lintian, piuparts, and pbuilder (and variants like cowbuilder). -- Boyd Stephen Smith Jr. ,= ,-_-. =. email@example.com ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Description: This is a digitally signed message part.