Friday, October 28, 2011

Setting up User Environment for Openmeetings

The manual covers requirements for connecting a participant's computer to Internet, recommended hardware list and a number of steps to install the software on the computer. It is assumed that software installation is done by IT profesional with administrative privileges.

Saturday, October 22, 2011

Review: Real Time Specification API of WHATWG

The Web Hypertext Application Technology Working Group (WHATWG) is working on a specification for the future of HTML in Realtime Collaboration:  

On the first sight it covers a lot of the topic developers are waiting for a long time: 
Beeing able to access the microphone and camera natively by using the pure JavaScript.
It seems like the nature of the communication is based on a Peer-2-Peer communication, which obviously must sound like christmas in some ears :).

First: The WHATWG is not reallye "the" specification group of HTML, the real specs will be done by the W3C. There are also specs in process at the w3c http://www.w3.org/2011/04/webrtc-charter.html.

If looking more closely at the specs you have to admit that there are some open questions on both sides, the w3c and even more at the WHATWG.

Some very basic question is if the Codec that will be used for encoding the audio and video will be an open one or not. I do understand that manufactors have little interest in publishing a codec that is suitable for everybody. On the other hand it could be quite difficult if different browsers support different codecs. Or even worse if big companies like Google, Microsoft and Apple agree on certain Codec, license each other but lock-out browser vendors that don't have 20.000 patents to claim each other.
Having an open standard for realtime communication does not necessarily mean that everybody can implement those specs. If there is no open codec available that all browser platforms do support that could even lock-out small software vendors.
A very basic technical question is also how they plan to fix the Firewall problem: Peer2Peer is nice, but even Skype has a fallback method to proxy data through a central server.

But looking at the milestones planned in the specification (End in 02/2013), there might be also major changes in those specs.

OpenMeetings 1.8.5 released

Changes in OpenMeetings 1.8.5 
  • Update of installer and new option to exclude the default rooms in the installation (this can be handy if you import a backup directly after installation) 
  • Fix backup import tool issue with wrong organization_id after import (Users could get assigned to a previous existing organization if there are multiple) 
Download:
http://openmeetings.googlecode.com/files/openmeetings_1_8_5_r4452.zip

Monday, October 10, 2011

3 steps to install OpenMeetings in Version 1.8.4

In Version 1.8.4 installation of OpenMeetings is a 30 second task:


To update from past versions or migrate see UpdateOpenMeetings, for payed services see Service and Hosting.

You can download latest version from:
GoogleCode Website

Friday, October 7, 2011

New Moodle Module for OpenMeetings 1.8.3

With the new integration and OpenMeetings version 1.8.3 you can now create separated users in OpenMeetings with the access-level "SOAP-Only".
The "SOAP-Only" user can do exactly what is needed to run the integration but nothing more. This does result in no need for any OpenMeetings Admin-User in the Moodle Module config! So you can better protect your OpenMeetings server from non-authorized access via the SOAP Gateway and
no need to share confidential account data."SOAP-Only" users can not login to OpenMeetings administration or manipulate user accounts via SOAP.

It is recommended to update to the latest version of OpenMeetings (1.8.3). Moodle Mod 0.9 for Moodle 1.9.x is still compatible with OpenMeetings 1.8.3 and you can also use the new secure user with access level "SOAP-Only" with the old Moodle Mod 0.9.

Sample Video showing the installation of Moodle Mod and integration with new access level:

New features of Moodle Plugin:
- Secure "SOAP-Only" user access level (see documentation on top)
- 3 Moderation Types for Conference Rooms (Moodle admins, teachers and course creators are automatically a moderator):
Moderation Type A) Participants need to wait till the teacher enters the room
Moderation Type B) Participants can already start (first User in room becomes moderator)
Moderation Type C) Every participant is automatically moderator when he/she enters the room
- New Flag "Allow Recording": You can set in the room configuration now a flag that controls if the recording button is available or not
- Fix Icon in Moodle Course overview and edit page
- Fix Issue when deleting a conference room from a course (all conference rooms where deleted from all courses)
- Add/Fix Moodle Mod languages: German, French, Spanish (OpenMeetings itself has around 30 languages)
- Clear and restructure conference creation form for Moodle moderators
You can try and test the Moodle integration at:
http://moodle.openmeetings.de
Download is available from our project side: http://code.google.com/p/openmeetings/
Support is available at: http://www.openmeetings.de