Problem
Live Coding shows presence but not a shared purpose, so it is interesting to inspect without creating a recurring collaborative habit.
Proposed solution
Add opt-in 30-60 minute office-hour sessions around a language, repository, or contribution topic. Sessions appear on the live globe and provide a clear join action.
Acceptance criteria
- Hosts choose topic, start/end time, capacity, and public description.
- Participation is opt-in and exposes no source code, filenames, or private contact data.
- Sessions have accessible time-zone display and calendar links.
- Hosts can cancel or end sessions and participants can leave.
- Initial version uses public GitHub discussion/issue destinations rather than building video chat.
- Track views, joins, repeat attendance, and contributions started.
Success metric
Weekly developers joining at least one purposeful live session.
Related
#168 #90
Problem
Live Coding shows presence but not a shared purpose, so it is interesting to inspect without creating a recurring collaborative habit.
Proposed solution
Add opt-in 30-60 minute office-hour sessions around a language, repository, or contribution topic. Sessions appear on the live globe and provide a clear join action.
Acceptance criteria
Success metric
Weekly developers joining at least one purposeful live session.
Related
#168 #90