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

_______________________________________________
Openpbx-dev mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-dev

Reply via email to