You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 22, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: _posts/2015-04-05-road-map.md
+25-9Lines changed: 25 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,26 +57,38 @@ The latest release is [BigBlueButton 2.2](/2.2/install.html), which provides a f
57
57
58
58
This section covers the enhancements to BigBlueButton’s core.
59
59
60
-
## High Quality Audio
60
+
## Show Slide Thumbnails
61
61
62
-
Thanks to web real-time communications (WebRTC) support in FireFox and Chrome, we've achieved high quality low-latency audio in BigBlueButton.
62
+
At this time the slide navigation does not show thumbnails when using the slide menu to navigate to specific slides.
63
63
64
-
## Presentation
64
+
## Managing webcams
65
65
66
-
Support full-screen mode, similar to hitting F5 in power point. Full screen mode should have optional notifications of new chat messages or join/leave events ([1627](https://github.com/bigbluebutton/bigbluebutton/issues/1627)). Full screen mode should switch back and forth between slides and desktop sharing (depending on whether the presenter is sharing their desktop or not).
66
+
The Flash client allowed users to individually close webcams. This feature is not yet implemented in the HTML5 client.
67
+
68
+
## Links in slides not clickable
69
+
70
+
When uploading slides with clickable links, they could be clicked in the Flash client. Currently, they are not clickable in the HTML5 client.
71
+
72
+
## Layout Dropdown
73
+
74
+
The Flash client had a layout menu that let moderators push down layout changes in windows to all viewers. The HMTL5 client does not use windows (it uses panels that show/hide). We are going to add capabilities for the moderator to show/hide the presentation area in a future update.
75
+
76
+
## Track users in breakout rooms
77
+
78
+
The Flash client would inform moderators of which users were in which breakout room.
79
+
80
+
## Show Slide Thumbnails
81
+
82
+
At this time the slide navigation does not show thumbnails when using the slide menu to navigate to specific slides.
67
83
68
84
## Whiteboard
69
85
70
-
Support ability to move/edit whiteboard objects ([2351](https://github.com/bigbluebutton/bigbluebutton/issues/2351)). Support multi-user editing of whiteboard objects ([2055](https://github.com/bigbluebutton/bigbluebutton/issues/2055)). Support keyboard input of text and symbols ([1346](https://github.com/bigbluebutton/bigbluebutton/issues/1346)).
86
+
Support ability to move/edit whiteboard objects ([2351](https://github.com/bigbluebutton/bigbluebutton/issues/2351)).
71
87
72
88
## Closed Captioning
73
89
74
90
Enable the posting of a sub-rip title file (SRT) to the BigBlueButton server to add captions after the meeting is done (see [3864](https://github.com/bigbluebutton/bigbluebutton/issues/3864)).
75
91
76
-
## Record and playback
77
-
78
-
Add a playback format that creates a single video from the session (see [1655](https://github.com/bigbluebutton/bigbluebutton/issues/1655)).
79
-
80
92
# General Requirements
81
93
82
94
The items below are not specific to any one feature but are more about the overall quality of the project.
@@ -93,6 +105,10 @@ Ensure all classes in BigBlueButton, both on the server (Java) and client (Actio
93
105
94
106
Ensure all classes are documented to the level where another programmer could understand their intent. Create easy-to-navigate documentation that enables other developers to understand the design and purpose of the code.
95
107
108
+
## Compatibility
109
+
110
+
Screen sharing on mobile for iOS and Android. (see [8576](https://github.com/bigbluebutton/bigbluebutton/issues/8576#issue-557890044))
111
+
96
112
## Stability
97
113
98
114
Close all critical, high, and medium stability issues. In general, keep testing to ensure each release is more stable than the previous.
0 commit comments