[asterisk-dev] AstriDevCon 2014:Agenda item Deprecate AMI/AGI(Ben Klang)

[Paul Albrecht]

On Oct 22, 2014, at 3:27 PM, Kevin Larsen <kevin.larsen at pioneerballoon.com> wrote:

> > From: Paul Albrecht <palbrecht at glccom.com> 
> > Here’s a link to the minutes:  https://wiki.asterisk.org/wiki/
> > display/AST/AstriDevCon+2014 
> > 
> > It has you saying: Leif: we're in a transition, moving from dialplan
> > model to external control model.  Probably need external application
> > to be built  for us to move completely away from AMI/AGI. 
> > 
> > So you’re saying Asterisk is moving away from the dial plan or were 
> > you misquoted? 
> 
> Paul, 
> 
> I think you are getting worked up way too early in this process. This is one comment with only a little bit of context surrounding it. Such a major change would take quite awhile to make and there would be plenty of warning before it happens, with plenty of opportunities to discuss. The dial plan isn't going away tomorrow and if it does ever go away, there will be plenty of time to work out a transition plan. 
> 

Seems like now is as good a time as any to raise these issues, in fact, sooner is better than later because once developers start down a path it’s very difficult to get them change their minds no matter how much sense it makes. The fact that developers are even considering taking away user functionality like the dial plan is in of itself a very serious problem because it demonstrates they don’t see Asterisk from the user perspective.

> Looking at the path development has taken, it seems pretty clear that they have been working towards enabling greater external control of what Asterisk does, making it the engine that can drive other media applications. Doesn't mean it can't and won't be used as a traditional pbx, but to grow what it does will require some changes. 
> 
> If being a mature part of Asterisk means that something shouldn't be changed, we should also protest the move from the current SIP stack to pjsip. There are any number of reasons to deprecate mature code. It may not be needed or something better may come along. 
> 

Don’t object to extending the Asterisk user interface or changing Asterisk internals. Do object to is taking away functionality that users expect, are familiar with, and has made the Asterisk project successful.

> All I can say is that having experience with a few versions of Asterisk, it seems to get better and more stable as new versions come along. Perhaps a bit of faith that they are not trying to kill off their product simply by having a discussion at a dev conference is in order. 
> 

Then your experience is atypical. Asterisk has been unstable for several years as developers have continually shoveled new features into the code base over several releases. That’s not necessary objectionable, it’s even to be expected; however, at some point developers need to turn their attention to less glamorous less exciting things like stability and performance.

> Kevin Larsen -- 
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20141023/56f31235/attachment-0001.html>