On Fri, 2010-03-19 at 09:58 -0400, Matt White wrote:

> I've often thought we should get a place on the wiki for feature
> bounties.  Its a very popular thing to do in the asterisk world if you
> feel a feature is important....pony up some money.

I'm not familiar with what asterisk does specifically, but it seems to
me that before _I'd_ want to invest my time (assuming that my time was
mine to invest, which in this case it is not), I'd want more assurance
that there was actually money than text that someone put on a wiki page.

> I understand that with the bulk of development being done by Avaya
> employee's a bounty is a bit like moonlighting.  

For those of us that work for Avaya it would be substantially worse than
moonlighting.

> However, some of the features like ACD are really about moving to a
> freeswitch backend, which could mean a larger development base.

And if someone out there wants to do the work, I'd be delighted to hear
about it and provide whatever information they need.

> I could right now offer at a least $1000 bounty for someone to get a
> decent freeswitch based ACD(or fix the current ACD but it sounds like
> thats a dead end), into the main tree.

That's a fine stake in the ground, and your offer is in the archive :-),
but you understand that what you're offering is perhaps a week or at
most two of programmer time at fair market rates?  That's not much of an
ACD.  

Understand... what the community is getting for no $ (not quite free, as
I've expressed elsewhere) is the result of many _millions_ of dollars of
developer time.  Yes, it's missing some things and has some warts, but
those things cost real money to build and fix.  If you can find someone
to do them for $1K... more power to you - we'll take the output if it's
good.


_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to