Hi, I think so, too. There we had the example: the new user comes, looks, compares and leaves. Imo, the average user doesn't care whether he can add new features or who the maintainer works for or how's the project managed, but rather when and what features he can use in his interest. A better documentation repository, also for *older* stable version would be a good ideea. If I want to use apache, I don't download the source and look through those files, maybe a developer was kind enough to write something in some readme; and in no case do I search for a makefile to compile my documentation! This is a nice feature for bookkeeping features and code documentation, but mostly irrelevant to the average *user*. Every mature foss project has a documentation concentrator (software enterprises have a department only for that!). And www.iptel.org for sure isn't that concentrator, but rather a relic, with its ancient old docs. We could come to the point of finding men to do this job, but if there aren't volunteers, maybe having the developer spend some extra time for that, instead of writing some more code would pay off. His code is pretty useless if I can not find anything about its functionality; and I can go on like that with some more common blahblah. But if openser managed to gather some volunteers, probably the trouble is somewhere else. Onsip and voipinfo and so, are nice, but not enough - I don't want to gather bits and pieces when I can have an alternative I can easily use (like the one provided by ser's sibling, which apparently manages somehow "in their intension to go forward with SER to the direction that it had headed to"...). Just my 2 eurocents, WL. Note: Concurrency is the key to innovation. On 7/26/06, Adrian Georgescu <ag(a)ag-projects.com> wrote: