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

[Olle E Johansson]

25 jan 2007 kl. 09.35 skrev Greger V. Teigre:

> Greger's comment: The next discussion item I identified in Dragos'  
> post was the topic of architectural decisions and who make them and  
> when. I call the thread "SER architectural decisions"
> ----------------------------------------------
>
> To me, the whole thing looks like a pile of hacks. When was the last
> time that there was a overall design discussion? I think that modules
> and extensions just grew around, but nobody wanted or had the power to
> cut some dead branches, enforce some policies and specify some clear
> internal interfaces. If one person would take care of it end-to- 
> end, OK,
> but it's not the case.

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.

Whether or not Apache or Jabberd succeeded with 2.0 architecture
is an interesting issue. I just realized that Jabberd 2.0 and Jabberd  
1.x
have forked and continue as separate projects...

/O