Skip to content

feat: Add BigBlueButton video conferencing integration#28223

Closed
Awesome-wml wants to merge 1 commit intocalcom:mainfrom
Awesome-wml:feat/bigbluebutton-integration
Closed

feat: Add BigBlueButton video conferencing integration#28223
Awesome-wml wants to merge 1 commit intocalcom:mainfrom
Awesome-wml:feat/bigbluebutton-integration

Conversation

@Awesome-wml
Copy link

@Awesome-wml Awesome-wml commented Mar 1, 2026

/claim #1985


Summary by cubic

Adds BigBlueButton as a new video conferencing provider with a dynamic location link and a VideoApiAdapter to create meetings. Implements Linear #1985 by registering the app in the store and wiring up meeting creation.

  • New Features
    • New app: bigbluebuttonvideo (metadata, icon, package).
    • VideoApiAdapter to create meetings via the BigBlueButton API.
    • App keys schema for bbbHost and bbbSecret; falls back to test host if not set.
    • App store registration and exports for use under the “conferencing” variant.

Written for commit 57d10c4. Summary will update on new commits.

@Awesome-wml Awesome-wml requested a review from a team as a code owner March 1, 2026 05:05
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@graphite-app graphite-app bot added the community Created by Linear-GitHub Sync label Mar 1, 2026
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 8 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/app-store/bigbluebuttonvideo/package.json">

<violation number="1" location="packages/app-store/bigbluebuttonvideo/package.json:6">
P2: Internal @calcom dependencies should use the workspace protocol ("workspace:*") like other app-store packages. Using "*" can resolve to registry versions instead of local workspace packages, causing version drift in CI/dev.</violation>
</file>

Since this is your first cubic review, here's how it works:

  • cubic automatically reviews your code and comments on bugs and improvements
  • Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
  • Add one-off context when rerunning by tagging @cubic-dev-ai with guidance or docs links (including llms.txt)
  • Ask questions if you need clarification on any suggestion

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

@@ -0,0 +1,12 @@
{
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot Mar 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: Internal @calcom dependencies should use the workspace protocol ("workspace:") like other app-store packages. Using "" can resolve to registry versions instead of local workspace packages, causing version drift in CI/dev.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/app-store/bigbluebuttonvideo/package.json, line 6:

<comment>Internal @calcom dependencies should use the workspace protocol ("workspace:*") like other app-store packages. Using "*" can resolve to registry versions instead of local workspace packages, causing version drift in CI/dev.</comment>

<file context>
@@ -0,0 +1,12 @@
+  "version": "0.0.1",
+  "main": "./index.ts",
+  "dependencies": {
+    "@calcom/lib": "*",
+    "@calcom/types": "*"
+  },
</file context>
Fix with Cubic

@Awesome-wml
Copy link
Author

Hi @PeerRich and @calcom/foundation team,
Thank you for reviewing my PR for the BigBlueButton integration (#1985).
I'm based in China and having trouble with Algora setup.
Would it be possible to receive the $50 bounty through an alternative method like:

  • PayPal
  • Crypto wallet (I can provide an address)
  • Other methods you support
    Please let me know what works best on your end.
    Thanks!

@romitg2 romitg2 closed this Mar 1, 2026
Copy link
Member

@romitg2 romitg2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Awesome-wml attach video demo, and pr looks incomplete as i can't see any auth related code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🙋 Bounty claim community Created by Linear-GitHub Sync size/L

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants