[Serdev] SER architectural decisions - was: So who/what is SER for, anyway?

[Greger V. Teigre]

>> If none, that's good :-)
>> If there are, how do we organize SER so that good and balanced decisions
>> are made?
>> g-)
>>
>>     
>
> This might sound crazy, but if it is so hard and slow to gradually
> evolve SER, what do yo say if a new branch would start? One that would
> take a lot of code base from the current one, yet problematic parts
> being rewritten from scratch. New internal APIs, new module interface,
> new scripts, etc. There are a lot of things that are very good now, so
> it won't take forever to get it working. I would happily participate and
> also move the Open IMS Core to the new project to help testing.
>
> And was there enough watter under the bridge so that this next gen SER
> would see a reunification of the SER/OpenSER teams?
>
> -Dragos
>   
Well, I would say that if your goals in terms of where you want SER to 
go are so different that you cannot work within the SER community, you 
should do that. I would prefer to house people with differing goals 
within the community, as I don't believe in the "forking is good" 
mentality. IMHO, it just fragments scarce developer resources and 
creates niche-products that too often never get critical mass.
g-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.iptel.org/pipermail/serdev/attachments/20070129/fb587670/attachment.html