[asterisk-dev] SIP Stack - Update

[Matthew Jordan]

On 12/19/2012 02:24 PM, Paul Belanger wrote:
> On 12-12-19 09:56 AM, Matthew Jordan wrote:
>> On 12/17/2012 01:59 PM, Paul Belanger wrote:
>>> On 12-12-10 08:56 PM, Matthew Jordan wrote:
>> I'm not sure what you mean by "provide incentives (sp)" for help. As far
>> as approaching upstream package maintainers, its fairly clear that a
>> number of package maintainers have already been involved in this thread.
>> Its a little premature to ask someone to make packages before a product
>> has a build system that allows for this; once that's in place we can
>> certainly ask if someone would be interested in producing said packages.
>>
> Right, drop Debian then. The point I'm trying to make is if you do
> contribute and maintain pjproject to Fedora (EPEL[1] actually) the
> benefit to the RPM community will be huge.  Like you say, there is at
> least 3 Fedora packages active on this list, I cannot speak for them,
> but I'm sure everybody would be happy to work from a common packaging
> source.
> 

If someone would like to create a common packaging source that services
all three distros, that'd be great. At this time, Digium is not going to
spend engineering resources on that effort. We have an interest in
making packages for CentOS, as AsteriskNOW uses that distro. If someone
else wants to take on the effort of unifying those packages I'd be more
than willing to communicate and work with them on that, but we do not
have the resources to do that at this time.

>>> Right now, we don't even do a good job even providing the latest
>>> versions of asterisk packages any more. And we already have a list of
>>> people complaining about the lack up updates.  I don't believe this is
>>> intentional, but a lack of resources.
>>
>> For what distros? We provide packages for CentOS - and while the last
>> updates took a bit to get out, they are updated.
>>
> Right, but why take the unnecessary burden and solo responsibility to
> get the latest version of pjproject out. IMO, distro's usually do a fine
> job at packaging the latest.

If a distro (or someone) picks up packaging pjproject for CentOS, I
think we'd be happy handing that off to them. The same goes obviously
for any other distro.

> As for versions, it looks like we are still only doing CentOS 5
> packages, what about CentOS 6?

We've been making packages for CentOS 5 because that's what AsteriskNOW
uses. When AsteriskNOW migrates to CentOS 6, I expect that to change.

Again (and this is a common refrain), if someone else would like to pick
up any portion of the pjproject packaging work, that'd be hugely
appreciated.

> Unless nighthawk has changed, it was setup on the internal network.  So,
> anybody who wants to submit packaging to the build server would need VPN
> access.  This might have changed recently with your network rework a few
> months ago.

As I understand it, Nighthawk is not critical to making the packages -
it simply was configured to do the packaging. The instructions on the
wiki that you created would allow someone to set up a similar system and
perform the packaging.

>>> Or, please have the local resource apply and become a package maintainer
>>> for Fedora or Debian and use their existing infrastructure.  If Digium
>>> wishes to maintain a local repo, back-porting from upstream is straight
>>> forward.
>>>
>>
>> I don't see that happening. We do have sufficient resources to maintain
>> CentOS packages ourselves, but beyond that, we do not have the resources
>> to make packages for other distros.
>>
> Again, maintain them yourself does nothing for the RPM community.  You
> should be working together, contributing patches. I fear if you take
> sole responsibility for your own version of pjproject package, it just
> adds yet another thing on your plate to handle and reported issue just
> linger.

How are we taking this burden on again? We're saying that yes, we'd like
to make CentOS packages - because we need them for AsteriskNOW. If
someone else would like to make them independent of that - fantastic!
I'd love to see that happen. I'd love to see someone make packages for
every distro.

> Look at ANOW-149[2] for example, ~18months old, zero activity and even
> has people volunteering to help.

There's a single volunteer on that issue (+1 doesn't cut it). That
person volunteered 9 days ago, so I wouldn't say there's been an
outpouring of people looking to assist with that effort.

As it is, I'd expect to see some progress made on that front in the next
few weeks.

> Hell, if I have to learn how to create RPM spec files and mock, I'll be
> the first to step up and offer my time to help get this going.

That'd be great. If unified RPMs are created for pjproject, I'd
certainly be more than happy to not be in the critical path for the
pjproject packages.


-- 
Matthew Jordan
Digium, Inc. | Engineering Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org