Towards becoming a pkg-voip developer

[Mark Purcell]

> On Wednesday 22 February 2006 17:54, Lee A. Azzarello wrote:
>> I have a feeling I'm not the only one working on this and I
>> would like to join the pkg-voip-maintainers group. What would I need to
>> do
>> to contribute changes? Do I have to get sponsored by an existing Debian
>> developer?

Sorry I have been a bit on the fringes for this discussion. [Only got
broadband back on Tuesday (2 months downtime) after a move]

1. To join the pkg-voip-maintainers all you need to do is contribute on
the mailing list, then you are part of the team :-)

2. Other things which can be done, include Bug triage, responding to users
 and the like via the mailing list (please remember to CC: the user as
they generally aren't on list), documentation, ...

3. Next level up is supplying changesto be incorporated into the svn archive;
i) as a patch via the BTS, which will be incorporated by someone with svn
access,
ii) or directly by uploading changes to svn. (alioth account required),
and ensuring that the svn archive remains buildable, stable.
iii) tagging the svn archive for release.

4. Next level up is reviewing the changes, signs the released debs and
uploads to Debian (Debian developer required)

Everyone on the planet is invited to do 1 & 2, if you have proved yourself
via 1&2 then entry into 3 is pretty straight forward (setup an alioth
account and send your keys), 4 is a more lengthy process stipulated by
Debian proper.

> I think I'm in similar situation, Lee. I've been working on SpanDSP
> packages
> and started packaging Unicall and MFC/R2 and would like to be the
> maintainers
> for them. I have an Alioth account already but don't know how to work
> properly with the team nor how to make changes available faster, not
> needing
> to wait a long time to get a 'no, thanks'.

svn access on alioth sounds like the best option.

> Couldn't you guys sponsor all VoIP packages? I think it would take an
> (useless) extra time to find a DD with free time to sponsor a few
> packages.

Well I think we are pretty much on track for that anyway.  We tend to act
as the critical mass for VoIP, so I certainly see it on track to sponsor
packages, or rather bring the packages into svn, and the (new) maintainer
uses svn and step 3 above.

Finally on the cdbs, there are a number of packages in voip-maintainers
which are cdbs (twinkle, kphone, ...) mainly done by myself.  I'm happy
with cdbs and am also using in in pkg-kde-extras, so am happy to sign,
sponsor cdbs packages as well.

Mark