[prev in list] [next in list] [prev in thread] [next in thread]
List: asterisk-dev
Subject: Re: [asterisk-dev] Time to rename chan_gulp?
From: Steve Totaro <stotaro () asteriskhelpdesk ! com>
Date: 2013-04-30 14:54:59
Message-ID: CAGA-L+VT=wW_DWw22yDiGefbS03nbGn-8OoHRK8=bRPy+hoC_g () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Tue, Apr 30, 2013 at 9:46 AM, Tilghman Lesher <tilghman@meg.abyt.es>wrote:
> On Mon, Apr 29, 2013 at 11:33 AM, Russell Bryant
> <russell@russellbryant.net> wrote:
> > On Mon, Apr 29, 2013 at 11:56 AM, Matthew Jordan <mjordan@digium.com>
> wrote:
> >> I'm fine with whatever we call this. How about a vote being taken on the
> >> channel driver name and we go with whatever the majority of people
> >> decide is best?
> >
> > chan_gulp seems fine to me.
> >
> > I'm personally more interested in the function and structural integrity
> of
> > the bike shed than its color.
>
> +1
>
>
>
Somewhat agree but I have always held naming convention in very high
regards.
Chan_bluetooth to chan_mobile may have been easy but it's bad practice to
even introduce this stuff into dev. Errors like, "This shouldn't happen
here!" or whatever are the result of fun and games, which has it's place
but ends up in production and FUBARs things.
Give it a bit and a logical naming convention will come out. SIP, GULP,
yeah funny and cute. One is a real acronym that means something, what is
the DCAP question going to say, what does SIP stand for? What does GULP
stand for? Just get it as close to right from the start.
I will see if I can come up with something better too.....
Thanks,
Steve T
[Attachment #5 (text/html)]
<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, \
Apr 30, 2013 at 9:46 AM, Tilghman Lesher <span dir="ltr"><<a \
href="mailto:tilghman@meg.abyt.es" \
target="_blank">tilghman@meg.abyt.es</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div class="im">On Mon, Apr 29, 2013 at 11:33 AM, Russell \
Bryant<br> <<a href="mailto:russell@russellbryant.net">russell@russellbryant.net</a>> \
wrote:<br> > On Mon, Apr 29, 2013 at 11:56 AM, Matthew Jordan <<a \
href="mailto:mjordan@digium.com">mjordan@digium.com</a>> wrote:<br> </div><div \
class="im">>> I'm fine with whatever we call this. How about a vote being \
taken on the<br> >> channel driver name and we go with whatever the majority of \
people<br> >> decide is best?<br>
><br>
</div><div class="im">> chan_gulp seems fine to me.<br>
><br>
> I'm personally more interested in the function and structural integrity \
of<br> > the bike shed than its color.<br>
<br>
</div>+1<br>
<div class="HOEnZb"><div \
class="h5"><br><br></div></div></blockquote><div><br></div><div style>Somewhat agree \
but I have always held naming convention in very high regards. </div><div \
style><br></div><div style>Chan_bluetooth to chan_mobile may have been easy but \
it's bad practice to even introduce this stuff into dev. Errors like, "This \
shouldn't happen here!" or whatever are the result of fun and games, which \
has it's place but ends up in production and FUBARs things.</div> <div \
style><br></div><div style>Give it a bit and a logical naming convention will come \
out. SIP, GULP, yeah funny and cute. One is a real acronym that means something, \
what is the DCAP question going to say, what does SIP stand for? What does GULP \
stand for? Just get it as close to right from the start.</div> <div \
style><br></div><div style>I will see if I can come up with something better \
too.....</div><div style><br></div><div style>Thanks,</div><div style>Steve T \
</div></div><br></div></div>
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic