Skip to content

Co-working Sessions #9

@Wajahat43

Description

@Wajahat43

Co-working Sessions

This feature focuses on enabling scheduled co-working sessions within Circles, and optionally allowing community-wide co-working sessions. The purpose is for a group of people to share their screens and work on their tasks, providing an accountability mechanism.

Requirements (for Circles)

  • Circle leaders can create scheduled meetings at specific times.
  • Multiple members can join and share their screens.
  • Members can work together on a shared goal or individually on their own tasks.

Optional: Community-Wide Co-working

  • Any community member can create a meeting for a specific time.
  • Others can join these meetings for accountability and co-working.
  • Each participant can share their screen and work on their own tasks.
  • These meetings are not Circle-specific; anyone in the community can join.
  • We need to keep it simple and minimize load on the server. But maybe having a page that will list all the upcoming community wide co-working sessions with url for joining the session and metadata, ability to create/manage created sessions can be simple enough.

To Decide

  • Whether sessions should be monitored or moderated in any way.
  • How to verify that people are actually working or participating.
  • How to track which members joined each meeting (attendance tracking).

Technology Options

Jitsi Meet

Discord (Alternative)

  • Offers voice, video, screen sharing.
  • Since we are moving community to discord, we need to explore if sessions is possible through this feature.
  • Provides stage channels, events, and permission controls.

Additional options may be explored as needed.

Proposed Next Steps

  • Evaluate whether to use an external meeting platform or build it natively.
  • Compare Jitsi, Discord, and other options for feasibility and constraints.
  • Define minimum UI/UX flows for scheduling and joining sessions.
  • Determine data model for meetings, attendance, and permissions.
  • Create an implementation outline and break into sub-issues.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions