GnomeMeeting 1.00 has been released yesterday together with a brand new website. We have not received complaints despite the big amount of downloads of the software, which is good news. Many things are on the roadmap to 2.00. Mainly SIP support, support for audio and video codecs plugins, better address book integrated with Evolution Data Server, Bonobo or DBUS integration, ...
We actually have 2 big directions for the 2.00 release: better integration with the desktop, and support for the other major VoIP/IP Telephony protocol, namely SIP. SIP support is a bit worrying because it will add more complexity to the software. Calling normal users won't be more difficult than it is now and will still be based on URLs, however, people will have to understand that when they are using a Gatekeeper, it only works for giving and receiving H.323 calls. Similarly, an incoming H.323 call can only be forwarded to a H.323 host, an incoming SIP call can only be forwarded to a SIP host. Does that mean that we should have 2 different possible settings for the forward host, or only one which would lead to an error when the host you are forwarding to only supports one protocol? If we have 2 different settings, what will we do for the current "FORWARD ALL CALLS" setting, should it be usable only when you have specified your 2 forward hosts? That will be a hard task, but our main motivation will be to "keep things simple"
IRC release party
We did an IRC release party yesterday, it was fun. Nearly nobody was talking on IRC as we were all connected to a big MCU provided by Stefan. Video and audio chatting is much more convenient than simple IRC, and you can see how the party is happening in the rooms of the different people involved in GnomeMeeting. All of us want to do it again for 1.2.