How can a non-DD join/help the debian-perl group?
I was watching the Debconf videos and noticed that there was a great
interest in getting people involved in Debian development. I've
always been resistant to join simply because it feels like there is a
big barrier to entry. After watching the videos, I felt less
concerned about this. Someone on the video said that there are always
plenty of tasks available in the perl group.
I'm not a DD. What does it take to begin helping out with random
tasks in the Debian Perl group?
I've been writing in Perl since sometime around 1996. I've created
several modules on the CPAN . This includes the Linux::APT module
 (I'd think there is already a nice module for this, but I don't
know about it and it doesn't seem to exist on the CPAN). I also
maintain the Win32::WindowsUpdate module , which is used (alongside
Linux::APT) extensively in our in-development perl-based distributed
computer management system.
I have been using Debian almost exclusively since Sarge (but started
learning and experimenting since Woody). I've been creating my own
packages for internal distribution for the last few years in our
company-wide repository. I don't promise that those packages are 100%
correct on policy, but they seem to pass lintian checks just fine,
except for a few intentional failures (copyright, changelog, some
overly-restricted file permissions). I used to maintain an unofficial
LogMeIn Hamachi package (for a couple of years, even though we stopped
using it ourselves quite awhile back, but discontinued last month due
to lack of interested users).
I don't have a specific interest other than to help out with the Perl
group. I'm willing to take on some tasks to become familiar with the
process and would be happy to move into a more responsible role when I
am sure I know what's going on and how to go about doing things with
the group. I would like to get to the point where I can (in addition
to general helping-out) maintain packages related to my CPAN-released
modules as well as parts (or all) of my company's computer management
system (much is GPL; might GPL the whole thing, hopefully).