SipSupport

Version 26 (Adrian Georgescu, 03/31/2009 10:22 am)

1 5 Adrian Georgescu
= Support =
2 1 Adrian Georgescu
3 10 Adrian Georgescu
[[TOC(Sip*, depth=2)]]
4 10 Adrian Georgescu
5 23 Adrian Georgescu
Support for SIP SIMPLE client is provided on a best-effort basis. "best-effort" means that we try to solve the bugs you report or help fix your problems as soon as we can, subject to available resources. The project is developed and supported by [http://ag-projects.com AG Projects].  
6 1 Adrian Georgescu
7 2 Adrian Georgescu
 * To request support you must use the [http://lists.ag-projects.com/mailman/listinfo/sipclient mailing list]. 
8 13 Adrian Georgescu
 * Bug reports must be submitted by opening a [http://sipsimpleclient.com/newticket ticket]. To open ticket please Register first. 
9 23 Adrian Georgescu
10 2 Adrian Georgescu
11 5 Adrian Georgescu
== Contributing ==
12 5 Adrian Georgescu
13 18 Adrian Georgescu
If you want to help us fixing a bug that you found or if you want to contribute with a new feature you must be familiar with the darcs version control system from http://darcs.net. 
14 18 Adrian Georgescu
15 18 Adrian Georgescu
First make sure you are using the latest version by doing a 'darcs pull'. Then record your changes using 'darcs record'. Follow the following guidelines for recording your changes:
16 5 Adrian Georgescu
17 25 Adrian Georgescu
 * Keep a patch name under 74 characters, so that a darcs changes in a 80 char console is consistent and readable. If you need to write more than that, use --edit-long-comment or do not specify -m "patch name" and it will automatically ask for a patch name and a long comment.  Keep the long comment inside the 80 char frame.
18 5 Adrian Georgescu
 * When you add a long comment, you have the patch name on the first line.  After that, leave an empty line and then add the long comment starting from the 1st column. If you need to add bulleted entries in the long comment, use a dash (-) not an asterisk (*), to avoid confusion with the asterisk darcs places before every patch name. 
19 5 Adrian Georgescu
 * Record separate patches for each distinct changes you make. Do not mix different changes in a single record.
20 5 Adrian Georgescu
 * Use darcs replace to rename tokens if possible instead of using a  search and replace in your editor. It correctly handles cases where someone else still kept using the old name (it will automatically rename this uses of the old name when he pull the darcs replace patch, which a simple token rename done by the editor and recorded as a standard diff will never do, requiring further patches to rename the old tokens that the other developer added in his code while you were doing the renaming).
21 5 Adrian Georgescu
22 24 Adrian Georgescu
Finally, open a ticket at http://sipsimpleclient.com/newticket describing your patch and the problem solved and submit the patch using:
23 5 Adrian Georgescu
24 5 Adrian Georgescu
{{{
25 5 Adrian Georgescu
darcs send --to devel@ag-projects.com
26 5 Adrian Georgescu
}}}