<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Oct 22, 2014, at 3:39 PM, Matthew Jordan <<a href="mailto:mjordan@digium.com">mjordan@digium.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 22, 2014 at 1:55 PM, Paul Albrecht <span dir="ltr"><<a href="mailto:palbrecht@glccom.com" target="_blank">palbrecht@glccom.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><span class=""><div>On Oct 22, 2014, at 11:31 AM, Matthew Jordan <<a href="mailto:mjordan@digium.com" target="_blank">mjordan@digium.com</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 22, 2014 at 11:14 AM, Paul Albrecht <span dir="ltr"><<a href="mailto:palbrecht@glccom.com" target="_blank">palbrecht@glccom.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span><br>
On Oct 22, 2014, at 10:33 AM, Joshua Colp <<a href="mailto:jcolp@digium.com" target="_blank">jcolp@digium.com</a>> wrote:<br>
<br>
> Paul Albrecht wrote:<br>
>> Really? Shouldn’t something this major affecting the entire Asterisk<br>
>> community get discussed on the lists? Any idea what Leif is talking<br>
>> about when he says the community is in transition, moving from dial<br>
>> plan model to external control.<br>
><br>
> It was something Ben Klang brought up and wanted to talk about - it's<br>
> not something that has been decided 'nor does anyone know what the<br>
> future entails. Any further discussions will naturally occur on the<br>
> mailing list and in fact some things have explicit action items to bring<br>
> them up on here.<br>
><br>
<br>
</span>The suggestion that Asterisk should consider deprecating AMI/AGI is “crazy talk.” It doesn’t merit discussion and shouldn’t be on the agenda in the first place. It’s completely impractical and can never happen. Moreover, Leif seems to think we (the asterisk community) are in transition. What does that mean? Are we abandoning the dial plan? Seriously? That’s never gonna happen either. ARI isn’t easier to use than dial plan scripting. I guess one could hope that "what happens in Vegas stays in Vegas”, but I don’t think the Asterisk community has that kind of luck.<br>
<div><br></div></blockquote><div><br></div><div>Just because someone decided to bring up a radical idea does not mean we refuse to discuss it.<br><br></div></div></div></div></blockquote><div><br></div></span><div>So you agree that deprecating AMI/AGI is “crazy talk” but you’ll discuss it because of your open-mindedness?</div></div></div></blockquote><div><br></div><div>I didn't say that the idea of deprecating AMI/AGI is "crazy talk". I did say that radical ideas - and even ones that some folks think are crazy - are all fine to discuss at AstriDevCon.</div><div><br></div><div>The whole point of AstriDevCon is to have a large, free, and open conversation about Asterisk Development. I fundamentally disagree with the notion that that should be discouraged.</div><div><br></div></div></div></div></blockquote><div><br></div><div>The problem with AstriConDev is there is no user input so what you have is a developer echo chamber and what you get is groupthink.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><span class=""><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">This is an open source project. Communication is done in an open, transparent manner. People should feel like they can bring up interesting, radical, and yes - even crazy - ideas.<br><br></div></div></div></blockquote><div><br></div></span><div>By the same token, when you propose ideas, you must be prepared for honest criticism and accept it in graciously rather than simply resorting to argument ad hominem. </div></div></blockquote><div><br></div><div>You didn't have honest criticism. You labelled a discussion point as "crazy talk" and said we shouldn't have even discussed it.</div><div><br></div><div>There was no ad hominem attack. I never attacked you. I never even attacked your statements. I simply defended the free exchange of ideas in AstriDevCon. I have no problem doing that.</div><div><br></div><div>On the other hand, you did callously label an Asterisk Developer's admittedly ambitious idea as "crazy talk". In the future, you may want to choose your language more carefully if you wish for others to have a more open discussion with you.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><span class=""><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>If you don't like that, you don't have to participate in the discussion.<br></div><div><br></div></div></div></div></blockquote><div><br></div></span><div>You haven’t really responded to the substance of my post, that is, is asterisk abandoning the dial plan?</div></div></blockquote></div><div class="gmail_extra"><br></div><div class="gmail_extra">There are Asterisk users (who also happen to develop) who would like to minimize the dialplan necessary in their systems, to the point where they may no longer even need the dialplan. This is a fundamentally sound idea for some systems, particularly those that require scaling Asterisk out to many machines.</div><div class="gmail_extra"><br></div><div class="gmail_extra">There are also some Asterisk users who build complex applications on top of Asterisk, and who find having to use multiple interfaces cumbersome. They like ARI, and would like to see it able to do more than what it currently does today.</div><div class="gmail_extra"><br></div></div></div></blockquote><div><br></div><div>Don’t have a problem with extending the Asterisk user interface or changing Asterisk internals that are not visible to users. Do object to taking away taking away user functionality like the dial plan that users expect, are familiar with, and has made the Asterisk project successful.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_extra">Fully deprecating a feature in Asterisk is non-trivial. You must have:</div><div class="gmail_extra">(1) A logical and full replacement for the feature</div><div class="gmail_extra">(2) Buy-off from the developer community</div><div class="gmail_extra">(3) Several major versions of the project in which the deprecated feature must remain</div><div class="gmail_extra"><br></div><div class="gmail_extra">Even in the case of point #3, deprecated features have often lasted in *many* versions of Asterisk. We are enormously conservative in what we choose to remove from the project.</div><div class="gmail_extra"><br></div></div></div></blockquote><div><br></div><div>Not interested in what rules or process steps need to be followed to deprecate features. The fact of the matter is you’re not starting with a blank sheet of paper and you can’t simply abandon the existing user interface because what will really happen is your users will abandon you and your project. </div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_extra">I would imagine that things as important as traditional dialplan, AMI, or AGI would be very difficult to ever deprecate.</div><div class="gmail_extra"><br></div>Finally, as I've noted to you before [1] [2], please don't cross post across lists. As this discussion is about AstriDevCon, it should be on the asterisk-dev mailing list.</div><div class="gmail_extra"><br></div></div></blockquote><div><br></div><div>Everybody doesn’t read both lists so I think it’s important to post to both lists because those getting done unto deserve to see what they’re going to get.</div><div><br></div><div>Lastly, the veiled threat to boot me from the list thus stifling dissent really belies your repeated assertions of your open-mindedness to different ideas.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">[1] <a href="http://lists.digium.com/pipermail/asterisk-dev/2013-October/063075.html">http://lists.digium.com/pipermail/asterisk-dev/2013-October/063075.html</a></div><div class="gmail_extra">[2] <a href="http://lists.digium.com/pipermail/asterisk-app-dev/2013-October/000113.html">http://lists.digium.com/pipermail/asterisk-app-dev/2013-October/000113.html</a><br clear="all"><div><br></div>-- <br><div dir="ltr"><div>Matthew Jordan<br></div><div>Digium, Inc. | Engineering Manager</div><div>445 Jan Davis Drive NW - Huntsville, AL 35806 - USA</div><div>Check us out at: <a href="http://digium.com/" target="_blank">http://digium.com</a> & <a href="http://asterisk.org/" target="_blank">http://asterisk.org</a></div></div>
</div></div>
-- <br>_____________________________________________________________________<br>-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com">http://www.api-digital.com</a> --<br>New to Asterisk? Join us for a live introductory webinar every Thurs:<br> <a href="http://www.asterisk.org/hello">http://www.asterisk.org/hello</a><br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a></blockquote></div><br></body></html>