[sip-comm-dev] Website update proposal


#1

Hello,

Last week, I send a mail to know if someone was working on the IRC protocol.

While downloading the app "Cairo-dock", I surf a little on their
website and they have a page where they list which point their working
on and the progress.
We should create a same page where we should list which point is under
development and who is working on it.

For example :

[bold]Profile Manager[/bold]
ROTH Damien: main system

[bold]Translation[/bold]
Yana Stamcheva: English
Vincent Lucas: French

What do you think of this idea ?

Bye

Damien

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

I love that idea. If it included the "last milestone" and "next
milestone" reached in their project, they wouldn't have to answer those
questions by email as much. And I'd love it even more.

  It's like the traditional .project file available to the "finger"
protocol.

···

On Wed, 2008-07-30 at 13:18 +0200, Damien Roth wrote:

Hello,

Last week, I send a mail to know if someone was working on the IRC protocol.

While downloading the app "Cairo-dock", I surf a little on their
website and they have a page where they list which point their working
on and the progress.
We should create a same page where we should list which point is under
development and who is working on it.

For example :

[bold]Profile Manager[/bold]
ROTH Damien: main system

[bold]Translation[/bold]
Yana Stamcheva: English
Vincent Lucas: French

What do you think of this idea ?

Bye

Damien

--

(C) Matthew Rubenstein

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi Damien,

We should create a same page where we should list which point is under
development and who is working on it.

I think it's a good idea, but this will require frequent update to avoid outdated information.
I think we could even extend this page with all the plugins that exists, ongoing and finished, and who is the developer/maintener of the plugin, and if it exists, a link to the documentation for the plugin. AFAICT such information is not on the website, so many people are not aware of the various extensions that exist for SC.

Cheers,

···

On 2008/07/30, at 13:18, Damien Roth wrote:
--
Romain KUNTZ
kuntz@lsiit.u-strasbg.fr
LSIIT - Networks and Protocols Team
http://clarinet.u-strasbg.fr/~kuntz/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Hello,

I think it's a good idea, but this will require frequent update to avoid
outdated information.

The update can be easily done by the team developers while comiting a patch.
To add new informations, a contributor can simply send a mail to the
dev list and a developer will update the website.
Since our community is growing well, there is enough developers to add
the informations rapidly.

I think we could even extend this page with all the plugins that exists,
ongoing and finished, and who is the developer/maintener of the plugin, and
if it exists, a link to the documentation for the plugin. AFAICT such
information is not on the website, so many people are not aware of the
various extensions that exist for SC.

It's a good idea to have a detailed list of the bundles on a page :
name, developer/maintainer, description, status (Complete, On-hold,
...).
I think this list should be on a page and the points that are under
development on another

I will prepare a little model of the page.

Bye

Damien

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Hey folks,

Guess what! We already have such a page! :slight_smile:

https://sip-communicator.dev.java.net/issues/buglist.cgi?component=sip-communicator&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED

Even though it is severely out of date our issue tracker is supposed
to play exactly that role. The problem is of course keeping it synced
with project state. Romain already mentioned that maintaining task
state implies a considerable maintenance overhead. The more detailed
such a page is the more likely it is to go out of sync with reality.
In other words people would still need to query the mailing list if
they need the exact status of an issue.

Don't get me wrong though, I am not against keeping the tracker up to
date and we should definitely try it again.

I also like Matthew's suggestion about grouping the different tasks by
milestones. It's been a while since we've last updated it (i.e. the
alpha2 release) so we'd need to do some cleaning up in there, and
since we are at it we should probably also do something which is even
more important:

Update our roadmap! There has been a lot to do on SIP Communicator
during the last three years but we are now very close to a state that
is worth the beta and then the 1.0 label.

I am on holiday this week but I'll sync the roadmap with our current
state first thing next week and we can then start a thread in which we
should determine exactly what it is that we'd like to see in 1.0 and
who is going to do it. We can then define several, preferably
short-term milestones that would get us there.

... I can hardly wait actually ... :slight_smile:

Cheers
Emil

···

On Wed, Jul 30, 2008 at 10:51 PM, Damien Roth <damien.roth@gmail.com> wrote:

Hello,

I think it's a good idea, but this will require frequent update to avoid
outdated information.

The update can be easily done by the team developers while comiting a patch.
To add new informations, a contributor can simply send a mail to the
dev list and a developer will update the website.
Since our community is growing well, there is enough developers to add
the informations rapidly.

I think we could even extend this page with all the plugins that exists,
ongoing and finished, and who is the developer/maintener of the plugin, and
if it exists, a link to the documentation for the plugin. AFAICT such
information is not on the website, so many people are not aware of the
various extensions that exist for SC.

It's a good idea to have a detailed list of the bundles on a page :
name, developer/maintainer, description, status (Complete, On-hold,
...).
I think this list should be on a page and the points that are under
development on another

I will prepare a little model of the page.

Bye

Damien

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#6

Hi Emil,

Guess what! We already have such a page! :slight_smile:

https://sip-communicator.dev.java.net/issues/buglist.cgi?component=sip-communicator&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED

Yes exactly, and I follow what you said about updating the roadmap.
But this only refers to ongoing development, so I think we would also need a page that gathers the already-existing plugin, no?

... I can hardly wait actually ... :slight_smile:

same here :slight_smile:

Cheers,
romain

···

On 2008/07/31, at 12:06, Emil Ivov wrote:

On Wed, Jul 30, 2008 at 10:51 PM, Damien Roth > <damien.roth@gmail.com> wrote:

Hello,

I think it's a good idea, but this will require frequent update to avoid
outdated information.

The update can be easily done by the team developers while comiting a patch.
To add new informations, a contributor can simply send a mail to the
dev list and a developer will update the website.
Since our community is growing well, there is enough developers to add
the informations rapidly.

I think we could even extend this page with all the plugins that exists,
ongoing and finished, and who is the developer/maintener of the plugin, and
if it exists, a link to the documentation for the plugin. AFAICT such
information is not on the website, so many people are not aware of the
various extensions that exist for SC.

It's a good idea to have a detailed list of the bundles on a page :
name, developer/maintainer, description, status (Complete, On-hold,
...).
I think this list should be on a page and the points that are under
development on another

I will prepare a little model of the page.

Bye

Damien

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Romain KUNTZ
kuntz@lsiit.u-strasbg.fr
LSIIT - Networks and Protocols Team
http://clarinet.u-strasbg.fr/~kuntz/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#7

Hey Romain,

But this only refers to ongoing development, so I think we would also need a
page that gathers the already-existing plugin, no?

Yes indeed, the two are not connected so we could definitely setup a
page for plugins somewhere. We could also use it to explain how people
could create subprojects for sip-communicator on java.net so that they
could have version control, issue tracking, and mailing lists for
their plugin projects.

Such a page would be especially useful once we have our plugin
management interface ready (wink at Mathieu :wink: ) because that would
allow us to get rid of many bundles that are pure plugins and that
should be downloaded only by users who need them. This way the page
could actually contain a human readable version of the content of our
plugin repository.

Anyways, we can already start to set it up, so please go ahead if you
are interested in doing it.

Cheers
Emil

···

... I can hardly wait actually ... :slight_smile:

same here :slight_smile:

Cheers,
romain

On Wed, Jul 30, 2008 at 10:51 PM, Damien Roth <damien.roth@gmail.com> >> wrote:

Hello,

I think it's a good idea, but this will require frequent update to avoid
outdated information.

The update can be easily done by the team developers while comiting a
patch.
To add new informations, a contributor can simply send a mail to the
dev list and a developer will update the website.
Since our community is growing well, there is enough developers to add
the informations rapidly.

I think we could even extend this page with all the plugins that exists,
ongoing and finished, and who is the developer/maintener of the plugin,
and
if it exists, a link to the documentation for the plugin. AFAICT such
information is not on the website, so many people are not aware of the
various extensions that exist for SC.

It's a good idea to have a detailed list of the bundles on a page :
name, developer/maintainer, description, status (Complete, On-hold,
...).
I think this list should be on a page and the points that are under
development on another

I will prepare a little model of the page.

Bye

Damien

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Romain KUNTZ
kuntz@lsiit.u-strasbg.fr
LSIIT - Networks and Protocols Team
http://clarinet.u-strasbg.fr/~kuntz/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#8

Hey,

···

2008/7/31 Emil Ivov <emcho@sip-communicator.org>:

Anyways, we can already start to set it up, so please go ahead if you
are interested in doing it.

I'm going to start to build this page.

Bye

Damien

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#9

Hi devs!

I created an update/patch for the german translation. I have corrected some typing errors and changed some formulations, but I noticed that not all of my changes and many of the old translations don't lead to a "GUI translation". Is there any reason for that? Nevertheless I attached the patch, because some of the changes are working.

Cheers Rupert.

PS: Thomas if you don't like some of my changes, feel free to start a nice flame war with me. I would really love that, because now I know what hard work it is to translate the sip com. :wink:

German_translation_patch.txt (23.5 KB)


#10

Hi Damien,

···

On 2008/07/31, at 21:14, Damien Roth wrote:

Anyways, we can already start to set it up, so please go ahead if you
are interested in doing it.

I'm going to start to build this page.

Great, thank you for your initiating this! Let me know when and where I can edit it, I can at least take care of the plugin I developed, plus some others.

Cheers,
--
Romain KUNTZ
kuntz@lsiit.u-strasbg.fr
LSIIT - Networks and Protocols Team
http://clarinet.u-strasbg.fr/~kuntz/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#11

Hi there!

I found an annoying behavior:
I've configured a sip-proxy to listen on a ip-adress. E.g. 10.10.10.10
But nowadays my sip-proxy is give an domain name, e.g.
mysipserver.domain.com. however, the sip-proxy is not bound to this address
(no local domain for that).

So the problem is, that in sipregistrarconnection uri is made the following
way:

        registrarURI = sipProvider.getAddressFactory().createSipURI(
                null, registrarAddress.getHostName());

where registrarAddress is an instanceof InetAddress. The problem is, that
getHostName performs an reverse lookup. However, I think, that the following
would be the necessary use:

if the user enters a domainname in his accout (e.g. 123@domain.com) the
sip-uri is 123@domain.com, if the user enters 123@10.10.10.10 the sip-uri is
123@10.10.10.10 and not 123@domain.com (reverse lookuped)

WDYT?

Cheers,thomas

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#12

Hello,

I've list all the bundles I've found by exploring the folders and
through the plugin.

You can found this list at this adress :
http://thrawn.wedge.free.fr/sc-bundles.html
It's on my personal web server until I got an acces on the SC website
or the list is complete.

I've cut the list in 3 parts : Services and Implementations, Protocols, Wizards.
There is 71 bundles.

Here are some problems that I noticed while listing the bundles :
- There is only 6 system bundles : more bundles should be registered
as system. For example :File Access Servce
- Bad names : one of the "Contact Info" should be renamed as "Account Info"
- The version plugin is in double (one in the impl the other in the
services directory)
- A plugin doesn't have a name

To complete this list, I need to know who develop / maintain each
plugin. So if you can send me by mail informations to complete the
list ?

If you have some comments or if I miss a bundle, let me know.

Bye

Damien

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#13

Hi Damien and all,

First congratulations for becoming a main developer :slight_smile:

I think your list is quite exhaustive and well organized. Can you move it on sip-communicator.org? This way every contributor will be able to place and move his/her name (and only his/her name). This way you will not have to refresh your site everytime.

Cheers,
Vincent

PS: With one or two weeks late (two weeks without an internet connection is too long):
[V] +1 Accept Lubomir as a committer. (Congratulations too)
[V] +1 Accept Damien as a committer.

Damien Roth wrote:

···

Hello,

I've list all the bundles I've found by exploring the folders and
through the plugin.

You can found this list at this adress :
http://thrawn.wedge.free.fr/sc-bundles.html
It's on my personal web server until I got an acces on the SC website
or the list is complete.

I've cut the list in 3 parts : Services and Implementations, Protocols, Wizards.
There is 71 bundles.

Here are some problems that I noticed while listing the bundles :
- There is only 6 system bundles : more bundles should be registered
as system. For example :File Access Servce
- Bad names : one of the "Contact Info" should be renamed as "Account Info"
- The version plugin is in double (one in the impl the other in the
services directory)
- A plugin doesn't have a name

To complete this list, I need to know who develop / maintain each
plugin. So if you can send me by mail informations to complete the
list ?

If you have some comments or if I miss a bundle, let me know.

Bye

Damien

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#14

Hello Damien,

I've list all the bundles I've found by exploring the folders and
through the plugin.

That was certainly quite a tedious work, thanks for that. See my comments inline.

I've cut the list in 3 parts : Services and Implementations, Protocols, Wizards.
There is 71 bundles.

What you have done was a necessary starting point, but I had in mind a different view of what we should display on the website:
- Services should IMHO appear in the developer documentation,
- Implementations, Protocols and Wizard should be sorted in 2 categories, namely:
-- one that gathers all the basic features of SC, i.e. that are part of the core SC and that will be maintained in time,
-- one that gathers plugins that are not part of the SC sources but that are available through another page.

The idea behind the second category would be first to move some of the plugins (I think about the ones that nobody maintains at the moment) from the current SC repository to external repositories; and second to have a page where we can reference any future contributions.

To complete this list, I need to know who develop / maintain each
plugin. So if you can send me by mail informations to complete the
list ?

I'm not sure this is a good idea to put a name on specific plugins. For plugins that will be in the second category (i.e. maintained by contributors that are not in the dev team and that are available on another URL), we can provide the URL where the plugin is available; for the features that are maintained by the dev team, it would be better to not stick a name on a specific feature, but rather display it as a team work. If people have a question on a specific feature, the mailing list is the right place to find information about it.

What do you (and other people) think?

Cheers,

···

On 2008/08/01, at 18:26, Damien Roth wrote:
--
Romain KUNTZ
kuntz@lsiit.u-strasbg.fr
LSIIT - Networks and Protocols Team
http://clarinet.u-strasbg.fr/~kuntz/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#15

Hey Thomas,

(please excuse the delay)

I agree that we could handle such DNS discrepancies more gracefully. Do
you have a patch in mind? Ideally we should be creating the inet address
with the following method:

public static InetAddress getByAddress(String host, byte[] addr)

(passing the value to both host and addr)

According to the javadocs the method "Creates an InetAddress based on
the provided host name and IP address No name service is checked for the
validity of the address. "

However we can only do this after making sure that host is indeed an IP
address and I am a bit worried that between v6, v4, and the various
forms that addresses can be written in we may miss a case and get a bug
instead of a work around for a user DNS problem. We should be careful. I
am tempted to reuse the parsing in InetAddress.getByName() but wanted to
check whether anyone else is aware of a better alternative.

Cheers
Emil

Thomas Hofer написа:

···

Hi there!

I found an annoying behavior:
I've configured a sip-proxy to listen on a ip-adress. E.g. 10.10.10.10
But nowadays my sip-proxy is give an domain name, e.g.
mysipserver.domain.com. however, the sip-proxy is not bound to this address
(no local domain for that).

So the problem is, that in sipregistrarconnection uri is made the following
way:

        registrarURI = sipProvider.getAddressFactory().createSipURI(
                null, registrarAddress.getHostName());

where registrarAddress is an instanceof InetAddress. The problem is, that
getHostName performs an reverse lookup. However, I think, that the following
would be the necessary use:

if the user enters a domainname in his accout (e.g. 123@domain.com) the
sip-uri is 123@domain.com, if the user enters 123@10.10.10.10 the sip-uri is
123@10.10.10.10 and not 123@domain.com (reverse lookuped)

WDYT?

Cheers,thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#16

Hello,

I found some time to put the initial list on the website. You can
found it here :
http://www.sip-communicator.org/index.php/Documentation/Plugins

What you have done was a necessary starting point, but I had in mind a
different view of what we should display on the website:
- Services should IMHO appear in the developer documentation,
- Implementations, Protocols and Wizard should be sorted in 2 categories,
namely:
-- one that gathers all the basic features of SC, i.e. that are part of the
core SC and that will be maintained in time,
-- one that gathers plugins that are not part of the SC sources but that are
available through another page.
The idea behind the second category would be first to move some of the
plugins (I think about the ones that nobody maintains at the moment) from
the current SC repository to external repositories; and second to have a
page where we can reference any future contributions.

I agree with this idea. But why not spliting the first category in two :
- core bundles : absolutly needed to run SC (ConfigurationPlugin, ...)
- bundles : most of the plugins (protocols, accounts wizards, ...)

Bye Damien

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#17

Hi,

I am working with netbeans and vista and I can't use the debugger because ide-targets.xml was messed up sometime ago with a bad commit. I was wondering if someone has one available to post here or to update the SC. I believe it is on a "todo" list somewhere :slight_smile: but I sure could use one now to dig out some of the peskier bugs.

thanks, Kim

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#18

Kim Michael Fairchild wrote:

I am working with netbeans and vista and I can't use the debugger because ide-targets.xml was messed up sometime ago with a bad commit. I was wondering if someone has one available to post here or to update the SC. I believe it is on a "todo" list somewhere :slight_smile: but I sure could use one now to dig out some of the peskier bugs.

It has been on my todo list for at least 6 weeks, but due to pressure of paid work I just haven't had the time to spend on it yet. It is now about two items from the top and I really intend to do something this weekend (unpaid!)

You can help me by saying what you need to do most - are you trying to debug the running application, or are you trying to debug a junit test suite. Both tasks are broken, but differently. I'll begin with the task that would be most useful to you.

Brian

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#19

I forgot to mention that I have not yet done the work on debugging the unit tests or compiling a single file. I hope to do this work soon.

Brian

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#20

I have been running the ant test target and noticed there is something wrong with the logging configuration.

The repository contains a ./log/ directory, which is properly defined in the project-level svn:ignore property so that any files within it will not be accidentally committed.

However, when I run "ant test", the ant target creates a new directory tree called ./null/null/log/ and stores the sip-communicator0.log file in it. The Netbeans File view shows that ./null/, ./null/null/, ./null/null/log/ and ./null/null/log/sip-communicator0.log are all locally modified and could easily be committed by simply clicking "commit" on the project object (netbeans does an implicitly add if required as part of a commit).

I haven't worked on logging for several years, so can anyone sort this problem out quickly? If not, I'll put it on my ToDo list (which doesn't get cleared very quickly!)

Regards,

Brian

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net