Version 2.0 of Apache OpenMeetings Incubating released!

This is our first release as Apache project and there have been major changes almost everywhere in the application.

Restyled UI The UI has been refactored to have a common look and feel. Additionally most of the icons are now loaded at runtime. That means you can change colors and icons at runtime without changing the source code. More info: http://incubator.apache.org/openmeetings/themes-and-branding.html

New Calendar The calendar was completely refactored and got a new UI that was built from scratch that also adds some new functions. For example it is possible now to password protect invitations sent via the calendar. Further the timezone handling has been refactored and there is now also a SOAP/REST API to handle calendar Events ( http://incubator.apache.org/openmeetings/SoapRestAPI.html )

Integration with Asterisk The application contains now modules to directly integrate OpenMeetings with Asterisk for SIP/VoIP integration. It enables you to dial in as well as dial out of conference room to SIP or ordinary phones. More info: http://incubator.apache.org/openmeetings/voip-sip-integration.html

Install/Backup/Import via command line Additionally to the Web-Interface you can now do all basic operations via console. Just cd to your OpenMeetings installation directory and type “admin” (or ./admin.sh) and you will see all the options available (OpenMeetings service should be shut down while doing those operations)

Using SWF10 for Video Components All audio/video related components now use SWF10 for broadcasting and receiving audio and video signals. That makes it possible to use for example the echo cancellation feature build in the SWF10 Flash Player.

There are a lot more improvements for example to recording, screen sharing and new layout options. To see the full list please review our Release Notes for Version 2.0:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312720&version=12319197

There are also new Integration Plugins in the pipe!

Integration into Atlassian Jira There is a plugin in our SVN that will be released soon for integration with Atlassian Jira, you can watch a demo here: https://blogs.apache.org/openmeetings/entry/jira_integration_apache_openmeetings_demo

Integration into Atlassian Confluence Same for Atlassian Confluence Wiki, you can watch a demo here: https://blogs.apache.org/openmeetings/entry/demo_video_about_upcoming_atlassian

Important Changes OpenOffice service does not need to be running as permanent service. But you have to set the path to OpenOffice (or LibreOffice) and JODConverter tools in OpenMeetings configuration. OpenMeetings (and JODConverter) will start and stop the OpenOffice service when they need it.

Upgrading from Version 1.9 or prior To update from an old version of OpenMeetings to 2.x you should use the integrated Backup and Import tool that exists since around Version 1.3. You should follow our documentation, see: http://incubator.apache.org/openmeetings/Upgrade.html

Downloads of sources and binaries are available from the mirrors linked here:
http://incubator.apache.org/openmeetings/downloads.html

All downloads can be verified using the Apache OpenMeetings code signing KEYS .

Commercial Openmeetings Support FAQ

That's our attempt to keep support knowledge structured and save your time asking questions.

OpenMeetings Hosting Services

Currently there are two hosting offerings: non-extensive usage offering called Integrated Room Service with a standard price, and a special offering called Advanced Hosting Plan for high load or customized cases.

What you choose depends on the mode in which you are going to use OpenMeetings, i.e. how often you plan to make your conferences, how many users you are going to have, etc.

Most customers start from the Integrated Room Hosting package and transfer to a special offering if their businesses grow.

Integrated Room Service includes creating rooms and users for your organization on our server and integration with your web site.

You have possibility to create OpenMeetings rooms from your CMS, place OpenMeetings room and recording links on your site and single sign-on feature for the OpenMeetings room entering.

This service has “reasonable load usage” limitation: we make some monitoring of the hosting services, and if we see that workload of some organization users is too big, we recommend client to move to another service.

Great benefit of this is that it’s cheap and you can pay quarterly. Monthly fee for the service is 50 euro and initial service setup fee is 100 euro + the cost of your CMS plugin installing. Plugin installing service depends on your site details, you can find the prices for most supported systems in our FAQ.

Upgrade OpenMeetings and CMS plugins to the recent releases and urgent security updates are included into the price.

If it becomes not enough for your goals, or you have customized OpenMeetings version, or you need some non-standard integration features, you would need to switch to Advanced Hosting Plan.

We do not have our own data center, so you can rent a server from some provider yourselves, or we can do it for you. We have successful experience of work with Amazon which would be convenient for USA clients, Scalaxy and Hetzner. Advantage of these providers is that they promise guaranteed bandwidth at any moment of time and allow manage network bandwidth dynamically. So for the clients who want to have big OpenMeetings conferences at some scheduled times we suggest increase bandwidth for the conference time and then decrease it back when the conference is finished. This helps save the money for the hosting, despite that these providers look more expensive in compare with other ones. Other providers are also possible on your behalf.

For the Advances Hosting Plan, all the cases should be discussed individually and the price depends on the exact details of your project.

Another Apache Planet Welcome

This is actually another test. For interesting openmeetings news you can read my latest post at blogs.apache.org.

Welcome, Planet Apache

We are on the Planet Apache blog list now. This is a test post and a warm welcome.

Community member Daniel Asher has created a survey to find out how people are using OpenMeetings.

You can fill it out online:
https://docs.google.com/spreadsheet/viewform?fromEmail=true&formkey=dG1DTXQyVHg2T09RMU1tNTBleExKeWc6MQ

The results of the survey will be reported back to the community.

Please fill out :)

OpenMeeting Team Meeting Minutes 26-June-2012

Attendees

• Alexei Fedotov
• Denis Kandrov
• German Grekhov
• Irina Arkhipets
• Maxim Solodovnik
• Yulia Algaer

Issues

• Release shipping: Voting for the first release is still not finished. All agreed that OpenMeetings should be released as soon as possible. Alexei told that one of his clients successfully uses trunk version last 1,5 months.
• German has finished with the Jitsi plugin installer
• Maxim is developing a cluster for the commercial cluster. Two issues in trunk found during the cluster implementation testing have been finished (lamguage import and calendar events problem). Now main functionality works OK.
• Irina has repaired Joomla plugin and now is preparing a demo video for Joomla plugin installation and integration. Should be finished in a couple of days.
• Yulia has made Russian localization for trunk.
• Denis is preparing a script which collects e-mail statistics for the commercial support email address. Hope to have some useful results till the next week.
• Irina will invite openmeetings-dev mailing list to the next monthly update meeting.

Presentation at the Java User Group Karlsruhe/Germany

Anybody interested in a presentation about Apache OpenMeetings can join us at in Karlsruhe/Germany at July, 18th 2012. The Java User Group of Karlsruhe organizes regular presentations and they organized a presentation about Apache OpenMeetings.

More Info:

http://jug-karlsruhe.mixxt.de/networks/events/show_event.62240

You can also sign up at Xing:

https://www.xing.com/events/apache-openmeetings-1101661

OpenMeeting Team Meeting Minutes 29-May-2012

Attendees

• Sebastian Wagner
• Alexei Fedotov
• Denis Kandrov
• German Grekhov
• Irina Arkhipets
• Maxim Solodovnik
• Yulia Algaier

Issues

1. Release 2.0 shipping. There is one blocking bug which should be fixed before the release of 2.0. This is a bug in Red5 (issue #295 in Jira and #224 in red5). RTMPT does not work because of this.

2. Maxim is currently working on the manual cluster implementation:

• Each room uses a separate server.
• The server IP added to each room description, users are directed to the specific server when they enter room.
• All servers use the same database - this makes all virtually on the same server.

Maxim will write an e-mail with the brief description of the possible cluster architectures into dev list.

3. German almost finished works with teambox plugin. Currently it’s possible to have OpenMeetings room for each project. Pablo also asked to do the same on the organizations level.

4. We need to store info about each commercial support e-mail and have some statistic about the commercial client requests. Irina will arrange another meeting with Sebastian and Alexei to discuss this.

5. Yulia Algaer has joined the project recently

OpenMeeting Team Meeting Minutes 22-May-2012

Attendees

• Alexei Fedotov
• Denis Kandrov
• German Grekhov
• Irina Arkhipets
• Maxim Solodovnik

Issues

1. OpenMeetings clustering

• Investigating of the possible clustering implementations is a first priority task for Maxim
• Existing Red5 instruction does not work on the recent version
• OpenMeetings objects are not serialized well
• Maxim will write a document with the description of 3 possible architectures and sent it to OpenMeetings and Red5 dev mailing lists

2. Teambox plugin

• Denis will configure https access on demo.dataved.ru
• Alexei will write an article about the teambox on habrahabr
• Maxim will write an e-mail to Pablo about the strating integration

3. Network checking script

• It should be checked into svn. Denis will create a bug in Jira and attach a patch

4. Release shipping

• German starts to work on the open source bugs
• Irina will take care about the localization for Russian