BigBlueButton 0.8-beta-3 released

[Fred Dixon]

We've release BigBlueButton 0.8-beta-3.  For instructions to
install/upgrade, see

  http://code.google.com/p/bigbluebutton/wiki/08InstallationUbuntu  In
addition to bug fixing (see below), this release includes the ability
for a student to un-mute/mute themselves using a 'push to talk'
button. See

http://code.google.com/p/bigbluebutton/wiki/08Overview#Push_To_Talk
Lots of small bugs fixed in this iteration, but two major ones that
are worth pointing out. The first was the HTTP tunnelling bug (see
initial post http://bit.ly/uZZb5l).  This bug was subtle, hard to
reproduce, and once we figured it out the fix required us to submit a
patch to red5 itself.  See
  http://groups.google.com/group/red5interest/browse_thread/thread/f0a8fa298ad5af8b
 After the red5 team accepted our patch (thanks guys!), we upgraded
BigBlueButton 0.8-beta-3 to red5 master (head of their development
tree).  We've been testing this for over a week on
demo.bigbluebutton.org and everything looks stable.  There have been a
lot of bug fixes gone into red5 since the last RC1 release (dated Feb
2, 2011) which we used for 0.8-beta-2. We are *very* appreciative of
the red5 team's effort to build a solid server.  See
   http://groups.google.com/group/red5interest/msg/557917700bd27954
The second bug was a GC Memory Exceeded bug that would randomly appear
using desktop sharing.  Thanks to YourKit's CPU and Memory profiler
for Java, we narrowed down the root cause and fixed it. See
  http://code.google.com/p/bigbluebutton/issues/detail?id=1032     We
still have 31 outstanding issues to resolve for BigBlueButton 0.8, but
we're getting close.  We're now increasingly focusing on stability and
anything that might prevent a recorded lecture from being processed.
We appreciate the bug posts in bigbluebutton-dev and thank in
particular those that have given us (temporary) remote access to their
servers to help us investigate and resolve issues.

Needless to say, if you find *any* bugs in BigBlueButton 0.8-beta-3,
let us know.

Regards,.. Fred
--
BigBlueButton Developer
http://bigbluebutton.org/
http://code.google.com/p/bigbluebutton

[Adefemi Debo-Omidokun]

Hey Fred,

 

Great job!

 

Br//

 

Femi

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To post to this group, send email to bigblueb...@googlegroups.com.
To unsubscribe from this group, send email to bigbluebutton-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/bigbluebutton-dev?hl=en.

--
Omoba Adefemi 'Debo-Omidokun


"In prayer; expect setbacks, but refuse retreat." Never Give Up!. Never Back Down!!. Never Lose Faith!!!

[Christophe Savery]

Great work !!! I'm going to test it extensively and let you know guys. Christophe

[Kirill Bukin]

Hi Fred and bbb team,

Very glad to see last news, thank you alot. But must say that there is still bug with push to talk button in Russian locale. Text doesn't fit to the button area and horizontal scrollbar appears.

Hope it will be fixed as well =) Wish you well and luck =)

2011/11/22 Adefemi Debo-Omidokun <omob...@gmail.com>

[Floh]

Hi Fred, just a small hint on the following page:
http://code.google.com/p/bigbluebutton/

There it says 0.8 Beta-3 is released on 7th October 2011 which is of
course wrong.

Keep going good work. :)
cu Floh

[hooface]

Thanks .Great job!

2011/11/22 Fred Dixon <ffd...@gmail.com>

[Fred Dixon]

Hi Kirill,

Thanks for pointing this out. We'll definitely fix!

http://code.google.com/p/bigbluebutton/issues/detail?id=1080

Regards,... Fred

--
BigBlueButton Developer
http://bigbluebutton.org/
http://code.google.com/p/bigbluebutton

[Devarah]

Exciting news!! We were considering putting beta-2 into production but
so glad beta-3 is here. We will test and post findings as they may
show up. Thank you Fred and all the committers and contributors for
your hard work, we appreciate you!

On Nov 21, 9:42 pm, Fred Dixon <ffdi...@gmail.com> wrote:
> We've release BigBlueButton 0.8-beta-3.  For instructions to
> install/upgrade, see
>
>  http://code.google.com/p/bigbluebutton/wiki/08InstallationUbuntu  In
> addition to bug fixing (see below), this release includes the ability
> for a student to un-mute/mute themselves using a 'push to talk'
> button.  See
>
>    http://code.google.com/p/bigbluebutton/wiki/08Overview#Push_To_Talk
> Lots of small bugs fixed in this iteration, but two major ones that
> are worth pointing out.   The first was the HTTP tunnelling bug (see

> initial posthttp://bit.ly/uZZb5l).  This bug was subtle, hard to

> reproduce, and once we figured it out the fix required us to submit a
> patch to red5 itself.  See

>  http://groups.google.com/group/red5interest/browse_thread/thread/f0a8...

[Mike]

Fred, Great news! I am so exited with this release and definitely test
on it. I will let BBB team know any issues coming out my demo server.

[Séverin TERRIER]

Thanks Fred (and other developpers) for all this good work :-)

French translation completed (with new strings comming with beta3) :-)

Would be good if it could be integrated on BBB tests servers, to allow
an in place verification (for too long strings, bad translation within
context...).

Séverin

[Pablo Sotomayor]

Hey Fred, Great News! Great Job!

Pablo

[Fred Dixon]

Hi Kirill,

We've fixed this bug

http://code.google.com/p/bigbluebutton/issues/detail?id=1080#c2

We've pushed the update the public repository for 0.8-beta-3. You can
update your server with

sudo apt-get update
sudo apt-get dist-upgrade

Try it out and let us know if fixes the problem on your end.

Regards,... Fred

--
BigBlueButton Developer
http://bigbluebutton.org/
http://code.google.com/p/bigbluebutton

On Tue, Nov 22, 2011 at 1:16 AM, Kirill Bukin <comp...@gmail.com> wrote:

[sbubb]

Hi Fred

To you and your Team, great work.

I upgrade from 0.8-beta2 to Beta3 without any problems.
The push to talk works well. I will continue to use to this v0.8 beta3
with small test groups in the weeks to come.

Regards
Steve

On Nov 22, 4:42 am, Fred Dixon <ffdi...@gmail.com> wrote:
> We've release BigBlueButton 0.8-beta-3.  For instructions to
> install/upgrade, see
>
>  http://code.google.com/p/bigbluebutton/wiki/08InstallationUbuntu  In
> addition to bug fixing (see below), this release includes the ability
> for a student to un-mute/mute themselves using a 'push to talk'
> button.  See
>
>    http://code.google.com/p/bigbluebutton/wiki/08Overview#Push_To_Talk
> Lots of small bugs fixed in this iteration, but two major ones that
> are worth pointing out.   The first was the HTTP tunnelling bug (see

> initial posthttp://bit.ly/uZZb5l).  This bug was subtle, hard to

> reproduce, and once we figured it out the fix required us to submit a
> patch to red5 itself.  See

>  http://groups.google.com/group/red5interest/browse_thread/thread/f0a8...

[Kirill Bukin]

Hello guys,

I had already been mentioning that but once again: I like push-to-talk idea and it works good but how about a case when you hava a large group of people and all of them have to be locked to mute/unmute themselves? Moderator has to push lock button opposite each username? Or I do not understand somethnig? Why would not to implement kinda "lock all" button which also forces new comming users to be locked as well?
Thank you =)

2011/11/24 sbubb <ste...@inhep.com>

[Fred Dixon]

Hi Kirill,

At the moment, all users join in an unlocked state, and hence have the
rights to mute/un-mute themselves. This probably covers most of the
use cases when users are mature enough to mute/un-mute themselves.

If you have scenarios where user is in a noisy area and is not muting
themselves, or un-muting themselves when they shouldn't (such as in a
K12 scenario), a moderator can lock the user to prevent them from
further changing their mute/un-mute state.

The above two use cases cover a lot of ground. We believe the use
cases that remain are in the minority. Specifically, having class in
which the moderator wants to lock everyone (with a 'lock all' button)
which also locks new users so they join as muted/un-muted (depending
if 'mute all' button is also engaged).

We haven't implemented a 'lock all' button to avoid making the UI to
complex. Keep in mind that for BigBlueButton "a large group of
people" is 25 users or less. That's our target class sizes for the
user interface. In that scenario, if everyone needs to be locked, it
only takes a moment for a moderator to do so, and we realize that you
have to manually lock new users if necessary.

We get a *lot* of feedback that people like the simplicity of
BigBlueButton. In the above breakdown, you can see we're consciously
trading off simplicity for the general use cases (where lock all is
not needed) against adding more UI to support the minority use case.

That's our thinking right now on the 'lock all' button. We welcome
your feedback Kirill on whether you think we're making the right
choice.

Regards,... Fred

P.S. There are certainly many areas of BigBlueButton where we want to
continue to improve the usability. For a breakdown of issues tagged
by usability, see: http://bit.ly/jr79ig

--
BigBlueButton Developer
http://bigbluebutton.org/
http://code.google.com/p/bigbluebutton

[Kirill Bukin]

Hmm, your ideas are pretty clear for me now and I very appreciate your help. Thank you alot Fred.

2011/11/24 Fred Dixon <ffd...@gmail.com>

[Fu Jiantao]

Hi Fred,

Is there any tag of this release?

Thanks!

2011/11/25 Kirill Bukin <comp...@gmail.com>

[Marc Laporte]

Hi!

We tested 0.8-beta-3 for a collaborative planning meeting. We were 7-9
people for over 2 hours.

In one word, BBB was "excellent".

Feedback:
* Uploaded PDF and PPT slides: was fine
** PPT animations weren't converted but this is not surprising
* We mostly used audio. Sound was mostly excellent. Easy muting is really nice.
* Sound check before entering the conference is really nice
* Everybody was using web interface, no one called in
* We didn't test the recording or screensharing

Only 1 bug noticed: Two users could get kicked out (kick themsleves
out) of the room when clicking (not all the time though) on certain
things
1-> next link in the slideshow
2-> hyperlink in the chat

If you're curious, the meeting was about:
https://dev.tiki.org/Online+Publishing+House+-+December+2011+Web+conference

Congrats to the BBB dev team!

Best regards,

M ;-)

> --
> You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
> To post to this group, send email to bigblueb...@googlegroups.com.
> To unsubscribe from this group, send email to bigbluebutton-...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/bigbluebutton-dev?hl=en.
>

--
--
M ;-)

Marc Laporte
http://tiki.org/

[Fred Dixon]

Hi Marc

> Only 1 bug noticed: Two users could get kicked out (kick themsleves> out) of the room when clicking (not all the time though) on certain> things> 1-> next link in the slideshow> 2-> hyperlink in the chat

Thanks for the feedback! We've not seen (1) before, but we'd like to
figure out if it's reproducible. How often did the users get kicked
out? Would be willing to try it with out to duplicate the error
(e-mail me directly if you want to schedule a time).

All the best,... Fred

--
BigBlueButton Developer
http://bigbluebutton.org/
http://code.google.com/p/bigbluebutton