[asterisk-dev] Development of asterisk 1.4.23 Can we please get some development?

[Matthew Jordan]

On Thu, Jul 14, 2016 at 5:25 PM, Loren Tedford <lorentedford at gmail.com>
wrote:

> I have only been using the project since 2013 I had no idea at the time
> what version of asterisk was being used to install the modules needed..
>
> Forgotten or not this is where we stand with it now..
>
> Even if a developer donated 20 minutes on it a week that adds up to
> roughly 17 hrs of possible improvement from what we got..
>
> I have experimented with trying to cobble things together on older
> versions of asterisk what i generally find is it literally barfs all over
> the place.. It really seems like they have changed some thing in the way
> asterisk handles the transmit and receive sides of everything.. To my
> knowledge I do not see any developers with  in the app_rpt actually posting
> any work or upgrades to the project.. I figured since asterisk was asterisk
> at one point in time developers might at least be interested in helping out
> or donating some time..
>
> Their is alot of cool things that could be done with it if it was
> integrated with asterisk phone system today even in the commercial world..
>
> I wonder what exact core changes occurred to create the problem we have
> today and is it reversible or do we need to completely redesign asterisk..
>
>
The modules you are referring to were removed quite awhile ago due to not
having an active maintainer contributing to the project [1]. Since no one
active in the project used the modules, or could verify their
functionality, and those who were using them had forked Asterisk
completely, we opted to remove them rather than ship broken or vulnerable
code.

I do not think that anyone in Digium is interested in maintaining these
modules, nor is anyone here interested in doing the port of the old 1.4
modules to the existing code base. I think all of us would be happy to
answer questions, but someone else in the greater Asterisk community would
have to do the work and commit to being the maintainer of those modules.

Asterisk is an open source project. As an open source project, anyone -
absolutely *anyone* - can step up, modify the existing
app_rpt/chan_usbradio/core of Asterisk, and submit the patches back to the
project. We have a lot of resources to help with that:

(1) Coding guidelines so that your submission fits within the standards of
the rest of the project [2]
(2) A well defined process for submitting patches to the project [3],
participating in code review [4], and understanding the kinds of things
reviewers will look for in submissions [5]
(3) An automated test suite for verifying functionality [6], with a Jenkins
based open source infrastructure definition [7] that trigger on patch
submission
(4) This mailing list, for when you have questions about the code and get
stuck
(5) The #asterisk-dev IRC channel, for when you want your questions
answered in real-time

If you're interested, you may want to review the resources mentioned above
and linked below, and familiarize yourself with the major changes in
Asterisk from 1.4 to now. The most influential of those would be:

(1) The API changes made in DAHDI, which - if I understand correctly - were
never adopted by the modules and were the first breaking change
(2) The adoption of reference counted semantics for ast_channel done in
Asterisk 1.8
(3) The opaquification of the ast_channel structure done in Asterisk 11
(4) If any native bridging is used anywhere, the bridging framework
introduced in Asterisk 12
(5) The stasis message bus as a mechanism to raise information to reporting
systems (CDR, CEL, AMI), introduced in Asterisk 12

Matt


[1] https://reviewboard.asterisk.org/r/1764/
[2] https://wiki.asterisk.org/wiki/display/AST/Coding+Guidelines
[3] https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process
[4] https://wiki.asterisk.org/wiki/display/AST/Code+Review
[5] https://wiki.asterisk.org/wiki/display/AST/Code+Review+Checklist
[6]
https://wiki.asterisk.org/wiki/display/AST/Asterisk+Test+Suite+Documentation
[7] http://git.asterisk.org/gitweb/?p=asterisk/infrastructure.git;a=summary

-- 
Matthew Jordan
Digium, Inc. | CTO
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20160715/2d1ae336/attachment.html>