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

[Olle E Johansson]

25 jan 2007 kl. 13.07 skrev Dragos Vingarzan:

> Olle E Johansson wrote:
>> Well, the same can be said for Asterisk. It's a problem with Open
>> Source, that
>> it keeps growing, hacks are laid on top of other hacks and there's a
>> shortage of resources for a re-start. In some cases, it happens  
>> through a
>> fork, in some cases within the project - like Apache or JabberD.
>
> Yes, this happens a lot, but when there is a clear and independent
> leader, maybe he could push big changes, cut branches, create new  
> ones,
> etc. When there are many, some of them would certainly have other
> interests and would want to keep the current tree as it is. Why break
> something that works just fine for some, right? But my impression is
> that too many core developers are just happy with SER and its position
> now to accept something really new, like a direction change. Maybe  
> some
> developers are too afraid that the new version would not be  
> accepted and
> used by the community if at the beginning it won't be on the par with
> the old one... Am I wrong?
>

I don't know. But we also have to consider that both Asterisk and SER
is spearheaded by companies that create commercial versions.

I would assume that would mean that the companies generate
resources and start the project for creating a generation two of
the product, but I haven't seen that happen in any of the projects.

Seems like the community needs to push them forward :-)

/O