I have been rather silent member of the group. I handle business operations at Sidance solutions ( http://www.sidance.com), part of Adiance Group ( http://www.adiance.com). Asterisk modification and development forms large part of our business activiites. I can place few of my Asterisk experts on part time basis for the development of openpbx. I can myself take up some responsibility in terms of handling the project if there's any.
Let me know guys, how I can be helpful to the community.
Thanks
--
Hardik Sanghvi
Adiance
+91 98792 00499
+19782232254
MSN: [EMAIL PROTECTED]
Skype: hardiksa
Yahoo: hardik_sng
On 1/25/06, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
Send Openpbx-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openpbx.org/mailman/listinfo/openpbx-dev
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Openpbx-dev digest..."
Today's Topics:
1. Re: Continuation of OpenPBX? (Armin Schindler)
2. Re: Continuation of OpenPBX? (Daniel Swarbrick)
3. Re: Continuation of OpenPBX? (Marc Olivier Chouinard)
4. Re: Continuation of OpenPBX? (Rico -mc- Gloeckner)
5. Re: Continuation of OpenPBX? (Jonathan J Smith)
6. Re: Continuation of OpenPBX? (Daniel Swarbrick)
7. Re: Continuation of OpenPBX? (Shidan)
---------- Forwarded message ----------
From: Armin Schindler < [EMAIL PROTECTED]>
To: "OpenPBX.org Developers Mailing List" <[email protected]>
Date: Tue, 24 Jan 2006 12:56:28 +0100 (CET)
Subject: Re: [Openpbx-dev] Continuation of OpenPBX?
On Wed, 25 Jan 2006, Daniel Swarbrick wrote:
> Is anybody still enthusiastic about continuing OpenPBX development? Is
> it just me, or has development and wiki updates slowed to a crawl?
>
> I realise that Freeswitch is now in the pipeline, but probably a few
> months from being anything close to a drop-in replacement for
> OpenPBX/Asterisk. With that in mind though, is there actually much point
> in maintaining/enhancing the current OpenPBX code, if it's potentially
> going to be superseded by Freeswitch + mod_pbx?
>
> It's about 2.5 months since OpenPBX was cut from the Asterisk tree, and
> we are now woefully behind with patches. There are probably still bugs
> lurking in OpenPBX which may have even been fixed in Asterisk by now.
> While I've come to appreciate that OpenPBX is much cleaner code layout
> than Asterisk, I may be forced to go back to Asterisk as an interim
> solution while Freeswitch is still baking... I don't want to be one of
> only about three developers who look after the OpenPBX tree, since it
> will be a losing battle.
I feel exactly the same and actually I began yesterday to update the pbx in
our office to use new Asterisk.
I still want to work with OpenPBX and do enhancements/fixes, in the parts I
have knowledge of. But with just 3 or 4 people committing, it will
not work.
Armin
---------- Forwarded message ----------
From: Daniel Swarbrick < [EMAIL PROTECTED]>
To: "OpenPBX.org Developers Mailing List" <[email protected]>
Date: Wed, 25 Jan 2006 01:23:13 +1300
Subject: Re: [Openpbx-dev] Continuation of OpenPBX?
Armin Schindler wrote:
> I feel exactly the same and actually I began yesterday to update the pbx in
> our office to use new Asterisk.
> I still want to work with OpenPBX and do enhancements/fixes, in the parts I
> have knowledge of. But with just 3 or 4 people committing, it will
> not work.
I started trying to update OpenPBX trunk a bit today, working through
Asterisk's svn history, starting around the day that OpenPBX was forked.
I soon realised that it is a mammoth job! Even though the code is fairly
similar, and I don't have to hunt around too much to see what needs to
go where, the process can't really be automated, since we've replaced
ast/AST with opbx/OPBX prefixes. Ok, I could take the diffs from
Asterisk svn, then do a search and replace on the diff before applying
the patch - but there are a few areas where we are quite different to
Asterisk, such as the generator threads. I also found that some (not
many) patches had already been applied, so there was no clear, definite
point in time at which OpenPBX stopped tracking Asterisk updates.
I think the best thing about working on OpenPBX was being able to get
patches/enhancements accepted quickly (and having the privilege of svn
commit access myself). I think things are a little better than they used
to be over in the Asterisk camp these days (they are doing quite
substantial code cleanups, and writing more portable, less
Linux-specific code), but everything is still controlled by the Digium
administapo.
It's unfortunate that Asterisk can't really benefit from OpenPBX's
efforts due to license complications, and nor can OpenPBX's modules be
used with Freeswitch. If it is the end of the road for OpenPBX, I hope
everybody has learned some things and had some fun along the way. I sure
have, and look forward to writing some modules for Freeswitch.
I suppose in a way, some of OpenPBX's ideals have rubbed off on
Asterisk, such as writing more cross-platform code. That's not such a
bad result...
---------- Forwarded message ----------
From: Marc Olivier Chouinard <[EMAIL PROTECTED]>
To: "OpenPBX.org Developers Mailing List" < [email protected]>
Date: Tue, 24 Jan 2006 09:14:46 -0500
Subject: Re: [Openpbx-dev] Continuation of OpenPBX?
I did all the first Asterisk -> OpenPBX.org patch post and it is a long
process Especially that there is code that shouldn't be ported, and
some that has but wont commit without alot of changes.
Also now my time is extremely low, and I saw it would be mostly non
existent until end April minimum.
So the project would need someone to take on the management of 0.2
release since I know from my end It wont get anywhere soon. The project
is open to all, and should run by itself, but it seem it require daily
motivation that I cannot provide ;)
So if anyone is interested, speak up.
Thanks
Marc O. C.
Daniel Swarbrick wrote:
> Armin Schindler wrote:
>
>> I feel exactly the same and actually I began yesterday to update the pbx in
>> our office to use new Asterisk.
>> I still want to work with OpenPBX and do enhancements/fixes, in the parts I
>> have knowledge of. But with just 3 or 4 people committing, it will
>> not work.
>>
>
> I started trying to update OpenPBX trunk a bit today, working through
> Asterisk's svn history, starting around the day that OpenPBX was forked.
> I soon realised that it is a mammoth job! Even though the code is fairly
> similar, and I don't have to hunt around too much to see what needs to
> go where, the process can't really be automated, since we've replaced
> ast/AST with opbx/OPBX prefixes. Ok, I could take the diffs from
> Asterisk svn, then do a search and replace on the diff before applying
> the patch - but there are a few areas where we are quite different to
> Asterisk, such as the generator threads. I also found that some (not
> many) patches had already been applied, so there was no clear, definite
> point in time at which OpenPBX stopped tracking Asterisk updates.
>
> I think the best thing about working on OpenPBX was being able to get
> patches/enhancements accepted quickly (and having the privilege of svn
> commit access myself). I think things are a little better than they used
> to be over in the Asterisk camp these days (they are doing quite
> substantial code cleanups, and writing more portable, less
> Linux-specific code), but everything is still controlled by the Digium
> administapo.
>
> It's unfortunate that Asterisk can't really benefit from OpenPBX's
> efforts due to license complications, and nor can OpenPBX's modules be
> used with Freeswitch. If it is the end of the road for OpenPBX, I hope
> everybody has learned some things and had some fun along the way. I sure
> have, and look forward to writing some modules for Freeswitch.
>
> I suppose in a way, some of OpenPBX's ideals have rubbed off on
> Asterisk, such as writing more cross-platform code. That's not such a
> bad result...
>
> _______________________________________________
> Openpbx-dev mailing list
> [email protected]
> http://lists.openpbx.org/mailman/listinfo/openpbx-dev
>
---------- Forwarded message ----------
From: Rico -mc- Gloeckner <[EMAIL PROTECTED] >
To: "OpenPBX.org Developers Mailing List" <[email protected]>
Date: Tue, 24 Jan 2006 15:22:34 +0100
Subject: Re: [Openpbx-dev] Continuation of OpenPBX?
On Tue, Jan 24, 2006 at 09:14:46AM -0500, Marc Olivier Chouinard wrote:
> So the project would need someone to take on the management of 0.2
> release since I know from my end It wont get anywhere soon. The project
> is open to all, and should run by itself, but it seem it require daily
> motivation that I cannot provide ;)
Motivation is brought by Goals, aims, guidelines (not rules), etc.
"Being better than asterisk" is not what i mean, though. It requires
some "Where do we want to go" (for example architecture wise), it doesnt
make sense to develop just to get the code all thrown over a hill
because it doesnt fit any future architecture.
FWIW, asterisk made some improvements since the fork, but until now i
still find it a big mess.
Also, its nice that anthm(?) started freeswitch and obviously some
people are rather moving there, but i felt lost when i first heard of
freeswitch and iam having thoughts wether freeswitch will make some of
asterisk's mistakes again.
I guess it would be helpful if the commiters to openpbx-svn would say
something about where they want to go and what they want to do, so that
the rest of commiters knows where everyone is standing.
my 2c.
--
http://www.ukeer.de/about.html
/* no comment */
---------- Forwarded message ----------
From: "Jonathan J Smith" < [EMAIL PROTECTED]>
To: "'OpenPBX.org Developers Mailing List'" <[email protected]>
Date: Tue, 24 Jan 2006 09:44:02 -0500
Subject: Re: [Openpbx-dev] Continuation of OpenPBX?
I would like to talk to you about taking over this..
Thanks,
Jonathan
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Marc Olivier Chouinard
Sent: Tuesday, January 24, 2006 9:15 AM
To: OpenPBX.org Developers Mailing List
Subject: Re: [Openpbx-dev] Continuation of OpenPBX?
I did all the first Asterisk -> OpenPBX.org patch post and it is a long
process Especially that there is code that shouldn't be ported, and
some that has but wont commit without alot of changes.
Also now my time is extremely low, and I saw it would be mostly non
existent until end April minimum.
So the project would need someone to take on the management of 0.2
release since I know from my end It wont get anywhere soon. The project
is open to all, and should run by itself, but it seem it require daily
motivation that I cannot provide ;)
So if anyone is interested, speak up.
Thanks
Marc O. C.
Daniel Swarbrick wrote:
> Armin Schindler wrote:
>
>> I feel exactly the same and actually I began yesterday to update the pbx
in
>> our office to use new Asterisk.
>> I still want to work with OpenPBX and do enhancements/fixes, in the parts
I
>> have knowledge of. But with just 3 or 4 people committing, it will
>> not work.
>>
>
> I started trying to update OpenPBX trunk a bit today, working through
> Asterisk's svn history, starting around the day that OpenPBX was forked.
> I soon realised that it is a mammoth job! Even though the code is fairly
> similar, and I don't have to hunt around too much to see what needs to
> go where, the process can't really be automated, since we've replaced
> ast/AST with opbx/OPBX prefixes. Ok, I could take the diffs from
> Asterisk svn, then do a search and replace on the diff before applying
> the patch - but there are a few areas where we are quite different to
> Asterisk, such as the generator threads. I also found that some (not
> many) patches had already been applied, so there was no clear, definite
> point in time at which OpenPBX stopped tracking Asterisk updates.
>
> I think the best thing about working on OpenPBX was being able to get
> patches/enhancements accepted quickly (and having the privilege of svn
> commit access myself). I think things are a little better than they used
> to be over in the Asterisk camp these days (they are doing quite
> substantial code cleanups, and writing more portable, less
> Linux-specific code), but everything is still controlled by the Digium
> administapo.
>
> It's unfortunate that Asterisk can't really benefit from OpenPBX's
> efforts due to license complications, and nor can OpenPBX's modules be
> used with Freeswitch. If it is the end of the road for OpenPBX, I hope
> everybody has learned some things and had some fun along the way. I sure
> have, and look forward to writing some modules for Freeswitch.
>
> I suppose in a way, some of OpenPBX's ideals have rubbed off on
> Asterisk, such as writing more cross-platform code. That's not such a
> bad result...
>
> _______________________________________________
> Openpbx-dev mailing list
> [email protected]
> http://lists.openpbx.org/mailman/listinfo/openpbx-dev
>
_______________________________________________
Openpbx-dev mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-dev
---------- Forwarded message ----------
From: Daniel Swarbrick <[EMAIL PROTECTED]>
To: "OpenPBX.org Developers Mailing List" <[email protected]>
Date: Wed, 25 Jan 2006 10:52:26 +1300
Subject: Re: [Openpbx-dev] Continuation of OpenPBX?
Rico -mc- Gloeckner wrote:
> Motivation is brought by Goals, aims, guidelines (not rules), etc.
> "Being better than asterisk" is not what i mean, though. It requires
> some "Where do we want to go" (for example architecture wise), it doesnt
> make sense to develop just to get the code all thrown over a hill
> because it doesnt fit any future architecture.
Architecture-wise, I think we all agree that the Asterisk core is a pig.
Somehow, it manages to run some fairly big sites, but I'm sure we are
all familiar with (and tired of) random segfaults and other bizarre
crap. The Asterisk core is incredibly fragile - it's a wonder any of us
PBX admins get any sleep at night.
OpenPBX always had an alternative plan to replace the core, and I think
Freeswitch could be the solution to that. What would be great, is if the
current OpenPBX dev team stuck together long enough for Freeswitch to
offer a viable platform, around which we could develop Asterisk-like
features (excluding the crashing, thanks).
> FWIW, asterisk made some improvements since the fork, but until now i
> still find it a big mess.
This is true - I looked at Asterisk trunk yesterday, and thought to
myself how familiar some of their new stuff is. More cross-platform
coding, replacement of db1 with sqlite etc. Maybe OpenPBX was a bit of a
kick in the pants for Asterisk... ;-)
> Also, its nice that anthm(?) started freeswitch and obviously some
> people are rather moving there, but i felt lost when i first heard of
> freeswitch and iam having thoughts wether freeswitch will make some of
> asterisk's mistakes again.
I'm nowhere near the level of coder that Anthony is, but from looking at
his code and API documentation, I have to say I like it. It looks clean,
well-designed, and stable. Not like the inter-dependency hell that
Asterisk's core is.
> I guess it would be helpful if the commiters to openpbx-svn would say
> something about where they want to go and what they want to do, so that
> the rest of commiters knows where everyone is standing.
For me personally, I feel like OpenPBX (in its current state) may have
already come to the end of its usefulness. I am trying to fix a bug that
is affecting two production PBX's I run, where it randomly crashes at a
CAPI call hangup. This may already be fixed in Asterisk. Even if I find
the bug in OpenPBX and fix it, how many other bugs are lurking that are
going to stick their head up in a few weeks? The commercial reality is
that I need to run with code that is being actively maintained (by more
people than just myself). Ok, Asterisk is a big yucky mess of code, but
it has a lot of users, and hence a lot of momentum. I reported a bug in
Asterisk's Postgres CDR module yesterday (one that I had known about for
a long time) and was shocked (and pleasantly surprised) when OEJ patched
it within an hour or two of me reporting it.
My official job role in my company is not to maintain open source
projects - the give me a bit of leeway since we are developing solutions
around OpenPBX, but I'm really supposed to be doing other things. At the
end of the day, we need to know that the software around which our
solutions are based is stable, actively maintained, and not heading down
a dead-end. For that reason, I am considering moving back to Asterisk as
an interim solution, while Freeswitch comes up to speed.
OpenPBX is great - but I just think it was too little, too late. I'd
love to see an OpenPBX v2.0, based around Freeswitch - I'll definitely
lend my time to helping out with that.
---------- Forwarded message ----------
From: Shidan <[EMAIL PROTECTED] >
To: "OpenPBX.org Developers Mailing List" <[email protected]>
Date: Tue, 24 Jan 2006 17:17:42 -0500
Subject: Re: [Openpbx-dev] Continuation of OpenPBX?
Hi I would like to know why people don't consider Yate to be an
alternative platform to develop on. OpenPBX I can understand because
of political reasons, but why reinvent the wheel if there is an
application already out there which has a clean design, why not build
all the good features of Freeswitch into Yate and save the man years?
Shidan
On 1/24/06, Daniel Swarbrick <[EMAIL PROTECTED]> wrote:
> Rico -mc- Gloeckner wrote:
> > Motivation is brought by Goals, aims, guidelines (not rules), etc.
> > "Being better than asterisk" is not what i mean, though. It requires
> > some "Where do we want to go" (for example architecture wise), it doesnt
> > make sense to develop just to get the code all thrown over a hill
> > because it doesnt fit any future architecture.
>
> Architecture-wise, I think we all agree that the Asterisk core is a pig.
> Somehow, it manages to run some fairly big sites, but I'm sure we are
> all familiar with (and tired of) random segfaults and other bizarre
> crap. The Asterisk core is incredibly fragile - it's a wonder any of us
> PBX admins get any sleep at night.
>
> OpenPBX always had an alternative plan to replace the core, and I think
> Freeswitch could be the solution to that. What would be great, is if the
> current OpenPBX dev team stuck together long enough for Freeswitch to
> offer a viable platform, around which we could develop Asterisk-like
> features (excluding the crashing, thanks).
>
> > FWIW, asterisk made some improvements since the fork, but until now i
> > still find it a big mess.
>
> This is true - I looked at Asterisk trunk yesterday, and thought to
> myself how familiar some of their new stuff is. More cross-platform
> coding, replacement of db1 with sqlite etc. Maybe OpenPBX was a bit of a
> kick in the pants for Asterisk... ;-)
>
> > Also, its nice that anthm(?) started freeswitch and obviously some
> > people are rather moving there, but i felt lost when i first heard of
> > freeswitch and iam having thoughts wether freeswitch will make some of
> > asterisk's mistakes again.
>
> I'm nowhere near the level of coder that Anthony is, but from looking at
> his code and API documentation, I have to say I like it. It looks clean,
> well-designed, and stable. Not like the inter-dependency hell that
> Asterisk's core is.
>
> > I guess it would be helpful if the commiters to openpbx-svn would say
> > something about where they want to go and what they want to do, so that
> > the rest of commiters knows where everyone is standing.
>
> For me personally, I feel like OpenPBX (in its current state) may have
> already come to the end of its usefulness. I am trying to fix a bug that
> is affecting two production PBX's I run, where it randomly crashes at a
> CAPI call hangup. This may already be fixed in Asterisk. Even if I find
> the bug in OpenPBX and fix it, how many other bugs are lurking that are
> going to stick their head up in a few weeks? The commercial reality is
> that I need to run with code that is being actively maintained (by more
> people than just myself). Ok, Asterisk is a big yucky mess of code, but
> it has a lot of users, and hence a lot of momentum. I reported a bug in
> Asterisk's Postgres CDR module yesterday (one that I had known about for
> a long time) and was shocked (and pleasantly surprised) when OEJ patched
> it within an hour or two of me reporting it.
>
> My official job role in my company is not to maintain open source
> projects - the give me a bit of leeway since we are developing solutions
> around OpenPBX, but I'm really supposed to be doing other things. At the
> end of the day, we need to know that the software around which our
> solutions are based is stable, actively maintained, and not heading down
> a dead-end. For that reason, I am considering moving back to Asterisk as
> an interim solution, while Freeswitch comes up to speed.
>
> OpenPBX is great - but I just think it was too little, too late. I'd
> love to see an OpenPBX v2.0, based around Freeswitch - I'll definitely
> lend my time to helping out with that.
> _______________________________________________
> Openpbx-dev mailing list
> [email protected]
> http://lists.openpbx.org/mailman/listinfo/openpbx-dev
>
_______________________________________________
Openpbx-dev mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-dev
_______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
