<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">This is easy. Just count the number of useful commits for the functionality used by your customers and go for that one. <div><br></div><div>Adrian</div><div><br></div><div><div><div>On Nov 6, 2008, at 4:35 PM, Brett Nemeroff wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Adrian,<div>We deal with it fine. But I don't have a good idea of which project to devote my attention to anymore. Neither do my clients. It's not a big deal, but some amount of confidence in the project has been lost.</div> <div><br><br><div class="gmail_quote">On Thu, Nov 6, 2008 at 9:32 AM, Adrian Georgescu <span dir="ltr"><<a href="mailto:ag@ag-projects.com">ag@ag-projects.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div style="word-wrap:break-word">Brett,<div><br></div><div>You should only worry only when you see that no new code is being committed or no end-users are supported or is silence on the mailing list. When that happens that definitely is a bad sign, the project either stagnated or there is no market demand anymore. </div> <div><br></div><div>Until that moment for all of us involved is business as usual as your have seen in the last 5 years or so. If you plot a graph you will see that every year this discussion happens and no end users are really suffering from it. </div> <div><br></div><div>So learn to live with it as we all do and tell your customers that is business as usual.</div><div><br></div><font color="#888888"><div>Adrian</div></font><div><div></div><div class="Wj3C7c"><div><br></div> <div><div><div>On Nov 6, 2008, at 4:22 PM, Brett Nemeroff wrote:</div><br><blockquote type="cite">All,<div>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.</div> <div><br></div><div>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. </div> <div><br></div><div>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. </div> <div><br></div><div>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. </div> <div><br></div><div>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. </div> <div>-Brett</div><div><br></div></blockquote></div></div></div></div></div></blockquote></div></div></blockquote></div><br></div></body></html>