Dan, Sergey, Stephen, (and to myself),
Do you have an environment where you can test the stability/reliability of OpenMeetings. For example where several or more people can use OpenMeetings and report on any issues, and the try to repeat the same issue on another day. A clear, methodical approach to observing, and then identifying how to repeat issues really help developers. It is even better if you can match the issue with entries in the log files. While my OpenMeetings installation has been very good most of the time, there are instances where some of my "test" users in conference rooms have become unstable, but so far I have not had the time to be able to repeat the issue frequently enough to identify why (or to match the problem occurrences with an entries in the red5/log/*.log). These issues have not been too serious, closing the browser and logging back in to the room fixes most, on a few occasions I have had to reboot my PC. I have also observed more issues when the PC is wirelessly connect (wireless LAN), which could be related to my Wireless router. My hope is that if there is enough of us "users of OpenMeetings", we can identify issues, check with each other to see if the others can also create the same issue, thus confirm the problem is not just with our own environment, and be able to report an issue in a way that the developers can more easily identify and fix. I am sure that they have limited time to which the can contribute to OpenMeetings so if we can identify repeatable issues and rule out any personal environmental problems, it should help in reducing the reporting of problems which are not due to OpenMeetings itself. So my request for Dan, Sergey, Stephen and others is, "when I report an issue or a suggestion, please, when you have time, check my statements in your own OpenMeetings environements and see if what I say is correct or a worthwhile suggestion and then report back. Especially if I make a suggestion for an improvement for something that I would like but it does not make sense to you, or even better, you see an even more effective way the improvement can be implemented (e.g. let's do some brain storming). Sometimes the most simplest of ideas are the greatest. For example, "one tool that OpenMeetings whiteboad does not currently have is a highlighter, like the highlighter pens". Thanks, George Kirkham From: aplusad...@aplustutoring.com [mailto:aplusad...@aplustutoring.com] On Behalf Of Daniel Ascher Sent: Friday, 11 May 2012 2:29 AM To: openmeetings-user@incubator.apache.org Subject: Re: exclusive audio in Build #68 I would like to thank everyone who is working so hard on this project. I am not an engineer so I can't contribute any coding. But if there is anything I can do to further this effort, please let me know! Dan Ascher On Thu, May 10, 2012 at 11:59 AM, Alexei Fedotov <alexei.fedo...@gmail.com> wrote: I'm really happy seeing new faces (George, Sergey, Stephen) around with thoughtful and skillful posts - Openmeetings needs you, guys, for a strong community. The strong community is mandatory for us to leave incubation and become an full-scale Apache project. Thank you.
