Hi,<br><br>[long response time too]<br><br>A couple things: <br><br>1. I should probably clarify that I certainly can *handle* bugs filed against any of my packages, in the sense that I can respond to them, fix them, and create a new package with the new version, but I basically had no experience tagging or assigning or triaging or whatever other things you can do with the metadata.<br>
<br>2. While I'm totally down with teamwork, I've been subscribed to the pkg-multimedia-maintainer mailing list for a while now, and I have to say that the volume is almost too much for me to handle on a daily basis, and certainly will be in a couple months when I start school again (not to mention the -commits mailing list, which seems to be even *higher* volume).<br>
<br>So honestly, although you've convinced me that I'd be qualified to join the team, and I'll hang out with you guys and help out when I have time, I just don't think I could handle being subscribed to the mailing lists for any substantial amount of time.<br>
<br>Jeremy<br><br><div class="gmail_quote">On Mon, Jun 6, 2011 at 3:21 AM, Jonas Smedegaard <span dir="ltr"><<a href="mailto:dr@jones.dk" target="_blank">dr@jones.dk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Jeremy (and fellow Multimedia Maintainers),<br>
<br>
[sorry forthe lateresponse!]<br>
<div><br>
On 11-06-02 at 07:50am, Jeremy Salwen wrote:<br>
> I'm confused, because there seem to be two standards by which one<br>
> might join the Debian Multimedia Maintainers team. The first seems to<br>
> be an informal one, by which someone who has created a couple of<br>
> debian packages is invited to join (Alessio extended to me a similar<br>
> offer). If I thought this were the final word, I would be happy to<br>
> join. However, when I go to the website to look into joining, I find<br>
> a second set of standards, including the items:<br>
><br>
> - are familiar with managing bugs in debian.<br>
> - agree to review other's work (patches and packages).<br>
><br>
> Neither of which I am okay with. I am not familiar with managing bugs<br>
> in debian. I simply don't know how to do anything besides send an<br>
> email to the bug report.<br>
><br>
> As for the second point, I suppose I could technically review others'<br>
> work, but it probably wouldn't be much of a review. Much of this<br>
> stuff is over my head. If I were to look at the source of Ardour, for<br>
> instance, it would probably take me a week to make heads or tails of<br>
> it.<br>
<br>
</div>The requirement about managing bugs is mostly aimed at contributors<br>
*less* involved than you - in fact I am surprised by your comment: As<br>
maintainer for a package officially part of Debian, you *must* be able<br>
to handle bugs filed against it!<br>
<br>
<br>
That other requirement about reviewing works of others really is about<br>
interest in doing teamwork. Feel free to ask questions, but don't join<br>
if you do not intend to contribute yourself. That's more fun for us all.<br>
<br>
<br>
But both those requirements are about _interest_ in such work. We are<br>
not an sxclusive club and we do not require university degrees or DD<br>
membership for you to work with us.<br>
<br>
Have a look at our mailinglist, or join our IRC channel. I am confident<br>
that you will find us to be pretty nice people to hang out with :-D<br>
<div><div></div><div><br>
<br>
Kind regards,<br>
<br>
- Jonas<br>
<br>
--<br>
* Jonas Smedegaard - idealist & Internet-arkitekt<br>
* Tlf.: <a href="tel:%2B45%2040843136" value="+4540843136" target="_blank">+45 40843136</a> Website: <a href="http://dr.jones.dk/" target="_blank">http://dr.jones.dk/</a><br>
<br>
[x] quote me freely [ ] ask before reusing [ ] keep private<br>
</div></div></blockquote></div><br>