RE: [reSIProcate] I have a suggestion on the Docs, and even can guide the efforts.
John,
I think you are expecting too much out of an open-source
community. I am certainly not going to assume what your
particular motivations are, but I have seen many people
come looking to open source projects to find "free" software,
only to be disappointed when they do not find the support,
documentation, etc that can be found in commercial products.
This seems to be the case with you. You have written what
comes across to many resip developers and users alike as
demanding and highly critical postings that seem to imply
that you are owed something.
Open source is not free. In many ways it can cost more than
commercial due to the additional effort required to use it.
I would never suggest to anyone that resip is as easy to use
as other closed packages. There is much hard work involved
and most of that *must* be on your own. That is the nature
of open source. This project is, like most others, run by
a handful of dedicated people who have other real jobs. They
never will document the project or support novices
adequately (nor should they be expected to). Using an open
source project (like democracy) requires that you accept
your own responsibilities for it to work.
My suggestions at this point are this:
- If you are building a commercial product with resip, then
I think you would be much better off going out and buying
a commercial stack. They will give you the support you are
seeking (and not getting).
- If you are experimenting or working on a product that
is not driven by the unrelenting demands of capitalism,
then maybe you could use resip with some serious learning
about SIP (other posts, especially this one, gave good
sources). But slow computer or not, if you take this path
you really need to post less and experiment more.
- As others have suggested, please spend more time with
the advanced C++ learning that is required to understand
much of the underlying code in resip (and be thankful you
are not trying to study boost :).
- Lastly, go out and spend some time on other open source
mailing lists. You will see that there is an etiquette to
follow and that most postings are very short, explicit
questions or proposed fixes.
> -----Original Message-----
> From: Mariano Stokle [mailto:mstokle@xxxxxxxxx]
> Sent: Friday, October 28, 2005 6:04 PM
> To: John Draper
> Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxx; Alan Hawrylyshen
> Subject: Re: [reSIProcate] I have a suggestion on the
> Docs,and even can guide the efforts.
>
>
> John,
> No ofense, but after reading your posts it is clear
> you still did not understand the SIP terminology and
> principles. You continuosly misinterpret SIP terminology
> (like UAServer, UAClient, Answer, etc.) with the "daily use"
> of those words. I understand you want to build a SIP phone
> but this is a community effort, and you must respect other
> people's motivation. You cannot "demand" what you think is
> needed when reSIProcate is a common effort and people is free
> to dedicate to improve it in the areas they want to dedicate
> their effort. If you think is important to document things to
> facilitate SIP phone development using reSIProcate: do it by
> yourself! lead that initiative! But first you need to
> understand the basics. I recommend you to start from the
> begin again and a good place to start is Henry Sinreich and
> Alan Johnston book "Internet Communications using SIP" or one
> of the several tutorials you can google it. Also it is worth
> to read "Architecture and Design Principles of the Session
> Initiation Protocol" by J. Rosenberg and H. Schulzrinne
> (http://www.softarmor.com/wgdb/docs/draft-rosenberg-sipping-si
> p-arch-01.txt).
>
> PS: I want to make clear this are my personal feelings and opinions.
>
> Regards,
>
...snip...