[asterisk-gui] Project status & submitting patches

[Ryan Brindley]

Hey Nathan,
Awk here (the old maintainer of the project that was active during that ticket time). I know it seems confusing, but there are two details that might help you understand what Digium did. First off, the issue was 'suspended'. During that time, Digiums' resources (aka, me, as I was the only active employee working on the GUI), was tied up in another project (of which I cannot speak). Instead of just not responded to the community, we decided to 'suspend' all current issues so they were at least informed of the lack of resources. The message about joining the IRC channels wasn't about that particular issue or to report issues there, but more generally about project involvement ("if you are interested in moving this project forward", we were looking for committers interested in helping maintain the project :) ).

The RC releases that you see are related to GUI branches/fixes from our ABE and AA50 edition of the GUI. To keep the open source versions in line with those version, we committed patches back to the open source branch and made releases in conjunction. 

Anyway, hope this helps explain things a bit more. I'd love to see someone pick this back up and I might even throw some code around with you if time permits. 

-- 
Ryan Brindley


On Sunday, May 13, 2012 at 1:14 PM, Nathan Anderson wrote:

> On Sunday, May 13, 2012 10:08 AM, Erin Spiceland <> wrote:
> 
> > Digium is not actively developing Asterisk GUI, but we are occasionally
> > committing some bug fixes. We do look at patches that come in through
> > JIRA. The patch you've linked to is 4 years old.
> > 
> 
> 
> 3.5 years, yeah...true. But from comparing his changes to what exists in the last branch, his fix was never committed. Not only that, but discussion on it was resurrected a little over 2 years ago, the original reporter/patch author engaged in the response, and then the following day! the ticket was unceremoniously closed by a Digium staff member citing lack of available resources and asking the reporter to go bother the IRC channel instead (? instead of bothering with a bug report through official channels?). Then, seemingly out of nowhere, an RC release branch is tagged over a year later. So you will forgive me if it feels like Digium is sending out mixed signals on this. :-)
> 
> > Please feel free to submit your patches to us via JIRA. They may not be
> > committed immediately, but they will be evaluated. Bug fix patches are
> > much more likely to be committed than feature patches. Thanks!
> > 
> 
> 
> Sounds good. Thanks for your response!
> 
> -- 
> Nathan Anderson
> First Step Internet, LLC
> nathana at fsr.com (mailto:nathana at fsr.com)
> 
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-gui mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-gui
> 
> 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-gui/attachments/20120514/ec385081/attachment.htm>