§ General

§ How do I get the latest SIP Communicator source code?

You could either cvs checkout all of it from the SIP Communicator CVS repository (see Version Control for details) or use one of the nightly source snapshots (check the Download page).

§ How do I become an Observer of the project?

You can request the Observer project role here

§ I’ve discovered a bug, what can I do?

Please, report it to the developers!
Take a look at the Reporting bugs guidelines page describing the steps to report bugs effectively.

§ Where do I find the log files?

The log files are located in the log folder residing in:

• Windows: “%APPDATA%\SIP Communicator”. On Windows XP and earlier, this path translates to “C:\Documents and Settings\<Windows login/user name>\Application Data\SIP Communicator”. On Windows Vista and 7, it expands to “C:\Users\<Windows login/user name>\AppData\Roaming\SIP Communicator”. Note that these folders are hidden on Windows 2000 and later.
• Mac OS X: ~/Library/Application Support/SIP Communicator
• Linux: ~/.sip-communicator

§ How do you spell SIP Communicator?

The correct spelling of the application name is SIP Communicator. When referring to the general community or project one may also use the name of the site or in other words sip-communicator.org. Any other form including dashes or mixed case in the application name is kind of wrong :)

§ I’d like to see a new feature in SIP Communicator, can you do that for me?

Yes, developers take into account feature requests. First of all you’ll need to email directly the development list and describe in detail what new feature you want to see in SIP Communicator. After we examine its feasibility and decide whether it can be included in the SIP Communicator distributions you would like be asked to fill in a new entry in the java.net Issue Tracker. It is worth mentioning though, that handling feature requests is highly dependent of the developers’ availability and there is no guarantee that all requests will be satisfied.

§ How do I subscribe to mailing lists?

To subscribe to one of the lists, you can either subscribe directly from java.net project page once logged in or send an email to listname-subscribe@sip-communicator.dev.java.net. Please visit Mailing Lists page to learn more about SIP Communicator’s mailing lists.

§ How do I contact the project developers?

You can ask questions concerning usage of the SIP Communicator on the users mailing list. In case you’d like to discuss anything having to do with the development please refer to the dev mailing list (Note that the mailing lists are moderated, so there may be a delay before your post shows up). For all urgent queries you could use IRC at irc.freenode.net, channel #sip-communicator.

§ How do I send a patch?

Mail patches to the dev mailing list, with a subject line that contains the word “PATCH” in all uppercase, for example

 Subject: [PATCH] fix for SDP descriptor in INVITE message

A patch submission should contain one logical change; please don’t mix N unrelated changes in one submission, send N separate emails instead.

The patch itself should be generated from within the project root directory using unified diff format. The following example shows one way to generate it:

 sip-communicator$ svn diff > myPatchfile.txt

You should give your patch files meaningful names. For instance if you fix a socket bug in the foo class do not call your patch file “patchfile.txt” but instead call it “foo-socket.txt”.

If the patch implements a new feature, make sure to describe the feature completely in your mail; if the patch fixes a bug, describe the bug in detail and give a reproduction recipe. An exception to these guidelines is when the patch addresses a specific issue in the issues database — in that case, just make sure to refer to the issue number in your log message.

§ I would like to update this wiki - what can I do?

Currently, only project developers are permitted to update the wiki. Please send your suggested changes to the dev mailing list.

A wiki page can be updated by appending the string ?action=edit to the current url and refreshing the page. The page will then be displayed with an extra menu line that includes a ‘Page Edit’ item.

If you click on the ‘Page Edit’ item, you will be redirected to a logon page. Enter your developer username and password and you should be redirected back to the original page. Click on ‘Page Edit’ again to access the source content of the page (a quick reference to wiki markup syntax is also displayed).

§ Development topics

§ Is there a port of SIP Communicator for “Android” ?

The port effort has started but is not yet finished. You can find the current progress at https://sc-android.dev.java.net/

§ The cc-buildloop target of ant fails with the following error message: “Could not create task or type of type: junitreport”.

On some Linux distributions such as Debian, the ant package is actualy subdivided into multiple packages. So when you chose to install junit and ant with the distribution specific package system, don’t forget to install ant-optional too.

§ The cc-buildloop target of ant fails with the following error message: “No test with id=IcqProtocolProviderSlick”.

Have you created your own accounts.properties file in the lib directory? You’ll need to define two ICQ test accounts at least, and preferably some test accounts for the other supported protocols.