[OpenSIPS-Users] [Fwd: [Serdev] the sip router project]

Johansson Olle E oej at edvina.net
Thu Nov 6 16:41:47 CET 2008

6 nov 2008 kl. 16.22 skrev Brett Nemeroff:

> All,
> I'm probably well out of line commenting on any of this. However, I  
> thought it might be worthwhile for you to have some opinions of  
> users, like me, who are not involved in the politics but are  
> genuinely interested in using the product.
> I've been using some flavor of SER for the last 5 or 6 years now. I  
> love the product. It's always been great. It's well documented and  
> it "just plain works". I started with SER when that was all there  
> was. Then the needed to use the LCR module caused me to jump the  
> OpenSER (as it seemed OpenSER was a bit more progressive). The  
> latest fork caused me, and my clients to wonder "What the heck is  
> going on?", and "Which project do we use now?". It certainly took a  
> huge hit in confidence.
> As a user, I can't answer the question of which product to use. I  
> don't really know the difference between the two (especially since  
> it's so easy to switch between one and the other). The latest  
> addition of the drouting module makes me want to stick with  
> opensips. Besides that, I don't have any good reason to be with one  
> or the other. I hope that doesn't offend anyone.
> Seriously tho. We as users are confused. Sure, I'm trying to read  
> and keep up with all of these emails. What do I think? Does it  
> matter? I think you guys are all brilliant and I tend to think if  
> you put your heads together, you'll most definitely come up with  
> something better than individual projects. As is the nature of any  
> project consisting of more than one intelligent being, there will  
> ALWAYS be dissension amongst peers. Especially since you are all so  
> bright. I think a fork is necessary if the products are going to  
> eventually become two separate products. However, if it's the same  
> product, and there is a disagreement between methodologies, then I'd  
> recommend that you form a technical advisory board consisting of  
> Users AND Developers which will provide an impartial vote on the  
> direction. This is a very common method of formulating technical  
> direction in many start up organizations. The loyalties to  
> individual developers is ridiculous and will hurt the product. The  
> loyalty should be to the end product and the the clients using the  
> product.
> Now that being said, I'd like to disclaim it by saying "I don't know  
> what the heck I'm talking about". And that I respect all of you and  
> that I love what you've come up with. Please, for our sakes, find a  
> way to work together.
> -Brett


Thank you for a very clear message to all of us involved in the  
project in one role or another.

Well worth reading, because for all Open Source developers, the love  
of our products by the users are very important. This applies to all  
developers in all projects. In some cases, there's just a huge  
difference in how we feel we can deliver the best products ever to the  

(not a developer in these projects, but involved as an active user)

More information about the Users mailing list