[asterisk-biz] General development funding: discussion and survey

[Steve Totaro]

Apologies for bringing up an old thread but I had hoped it would have
continued on it's own and I take issue with Xorcom's code getting included
and causing issue after issue.

Kevin said "I believe that redfone did submit their driver for inclusion
into
Zaptel, and that it was rejected for the reasons you mentioned (coding
guidelines and code quality). We do not accept code that does not
conform to at least reasonable standards of quality, because doing so
would allow the code base to deteriorate and increase everyone else's
support burden."

Joeseph has a different story.  I would like to know what the "REAL" reason
is for not including his code.

I would also like to know why xpp (Xorcom) stuff has it's own Zaptel release
bug fixes (and I assume DAHDI as well) because it is released buggy and
won't build without hacking source code.  By default, I do make menuselect
and remove xpp now because I don't feel like fixing buggy Xorcom code.

I only mention this because of Kevin's statements about not meeting coding
guidlines.  I would assume part of coding guidelines is the ability to build
from source provided dependencies are met,  without crapping out.

Kevin Flemming "We do not accept code that does not
conform to at least reasonable standards of quality, because doing so
would allow the code base to deteriorate and increase everyone else's
support burden."

-- 
Thanks,
Steve Totaro
+18887771888 (Toll Free)
+12409381212 (Cell)
+12024369784 (Skype)

On Fri, Oct 31, 2008 at 6:46 PM, Joseph Benden <joe at thrallingpenguin.com>wrote:

> Hello all,
>
> I am the author and maintainer of TDMoE-Multiframe.
>
> [please do not read the following as an attack, but rather simple
> comments.]
>
> The code did not have any major coding or quality issues, but rather
> had licensing issues because I had an old license on file and Digium
> switching to a newer license (which I was unaware of the change), I
> submitted the new license (which was approved) and now the code sits
> and rots in the tracker, along with the new DAHDI implementation of
> the driver.
>
> This is not unusual around this part of the open source world. I've
> had other patches and contributions that have experienced the same fate.
>
> I do deal (program, patch, etc.) with other open source software and
> do not have this much trouble in having the maintainers accept the
> code. I assume their projects are just as widespread (proftpd, clamav,
> freebsd), so using the number of outstanding patches as a reason for
> not accepting them is not convincing to me.
>
> Because of the difficulties in having Asterisk accept the Solaris
> community (read as: accept high availability patches and Solaris/
> OpenSolaris specific patches), I had to fork the project which then
> became SolarisVoip.com
>
> I am trying to work towards updating SolarisVoip.com to 1.6 (including
> the DAHDI drivers), but am very hesitant. Would Digium finally agree
> to working with me in possibly having my yet-to-be patches for
> Solaris? How about a branch/module for the Solaris specific DAHDI
> drivers? I tried in the past at working with Digium, but was always
> pushed to the side and forgotten (even though some within Digium
> seemed happy to work with me.)
>
> Comments, suggestions, or ideas welcomed!
>
> Best Regards,
> Joseph Benden
>
>              .--.
>             |o_o |
>             |:_/ |
>            //   \ \
>           (|     | )
>           /'\_   _/`\
>           \___)=(___/
> http://www.ThrallingPenguin.com/
> --------------------------------
>  We design, develop, and extend
>  software technologies for the
>     most demanding business
>    applications, as well as
>      offer VoIP Consulting
>            services.
>
>
>
> On Oct 31, 2008, at 6:21 PM, Kevin P. Fleming wrote:
>
> > Kevin P. Fleming wrote:
> >> Bill Michaelson wrote:
> >>
> >>> ztd-ethmf.c
> >>
> >> As I said, that driver has been part of Zaptel, so could not have
> >> been
> >> removed.
> >
> > Correction: it was in Zaptel SVN for a very short time, it had been
> > committed without proper code review. It was removed quickly
> > thereafter,
> > and was never part of an Zaptel release.
> >
> > --
> > Kevin P. Fleming
> > Director of Software Technologies
> > Digium, Inc. - "The Genuine Asterisk Experience" (TM)
> >
> > _______________________________________________
> > --Bandwidth and Colocation Provided by http://www.api-digital.com--
> >
> > asterisk-biz mailing list
> > To UNSUBSCRIBE or update options visit:
> >   http://lists.digium.com/mailman/listinfo/asterisk-biz
> >
>
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-biz mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-biz
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-biz/attachments/20081109/33e93ca0/attachment.htm