On Tue, 2006-08-29 at 09:47 -0400, David Yip wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Denis Leroy wrote:
What is the status of the inkboard feature ? Is it considered stable ?
The version in Inkscape trunk is not yet stable. The .44 Inkboard had a number of stability fixes applied to it, but it is still disabled by default (partly because of security concerns).
More importantly, is it considered safe (from a security standpoint) ?
Inkboard's security status is probably best labeled as unknown. Although there haven't been any major security flaws shown to exist in Inkboard (.44 or trunk), neither Inkboard codebase has been audited for security, and a rewrite certainly doesn't help us insofar as security is concerned.
I think we should enable this feature by default (in configure and in the menu) to get more people to help out. I've been compiling in the with-perl and with-python and have contributed some superficial fixes that I wouldn't have seen without enabling those features.
If we enabled now, we could help stabilize this code. This seems to be important because we should show proudly our summer of code work upon next release. Do you all agree?
I've implemented several jabber infrastructures and should lend a hand as well...
We had requests in Fedora to have the feature enabled and so am doing some testing on my side. It was originally turned off because it was pretty unstable and would often crash in the loudmouth library, but that was a while ago...
A number of crash bugs (and some rather silly mistakes) were fixed in the .44 release; you might want to give that a try. If you encounter problems, please let us know.
As Dale pointed out, some Inkboard features -- such as multi-user conferences -- don't work across all Jabber servers, due to deviations from behaviors specified in the JEPs.
Do we have an ejabberd server test setup? If not, we should as its the most compliant and stable. I've contributed to this project in the past and have experience with it...
Jon
<snip />