One on one webcam chat roomswith no sign in
As with any open source project, the continued growth of the community depends on the quality of the software.
The quality of the software, in turn, depends on the developers involved and the process we use to build a release.
To further this goal, we are in the process of putting together an independent not-for-profit Big Blue Button organization (similar to the Eclipse Foundation) to oversee and accelerate the growth of the Big Blue Button project.
There is a very active Big Blue Button community of members on the developer mailing list (over 2000 members and counting! In the Big Blue Button community at-large all the members, users, developers, educational institutions, and commercial companies are all collaborating together on using and improving Big Blue Button.
Since the core group is still small and the committers are communicating during development, Richard and others know when any major pull requests are coming.
The submitter of the pull request is responsible for ensuring the feature works correctly against Master.
As an open source project, you are welcome to fork Big Blue Button and build your own applications upon it. Some of the open source components we build on use different licenses, such as red5phone uses the GPL license. We started Big Blue Button as an open source project, and we intend to keep it that way.
One of the main goals we had was to create a large open source community around the project.
We’ve seen examples where there have been 21 webcams shared in a session!Modularity enables components of Big Blue Button to be developed, refactored, and upgraded in parallel.During each release we invariably rewrite parts of Big Blue Button to improve modularity.Each committer works on a fork of the Big Blue Button Master.When a feature is ready for commit, the committer sends a pull request to merge the work into the Master branch.