Open user512 opened 4 years ago
This is distinct from #9 in that we can be successful with this purely by allowing our creators to create an always-on video room.
This will build on top of the work we're doing in https://github.com/zinc-collective/convene/issues/2 to automate the provisioning of a Jitsi instance by creating affordances for Organizers to create a video room they can use at any time of day.
But it also allows us to package up the work we're doing to automate provisioning and deploying of Jitsi instance(s) in #2 into a Minimal (potentially) Viable Product without adding the scope of scheduling.
I'm considering a few scenarios, and would appreciate thoughts from @zinc-collective/convene-maintainers about which of these (or others!) would be reasonable next steps for this epic.
Scenario: Organizer creates a tiny paid video room
Given an Organizer creates a tiny Video Room
When Convene programaticaly provisions the tiny Video Room
Then the Organizer can use the Video Room at any time
This scenario is slightly different, in that we assume there is no automation beyond the gathering of the Organizer's payment information and contact information.
The work of provisioning the Video Room is performed manually by an Operator (@user512 or I), and we would replace this scenario with an automated one once we've confirmed the market actually is willing to pay for private, secure video rooms.
Scenario: Organizer requests we provision a tiny paid video room
Given an Organizer requests a tiny Video Room
When an Operator provisions the Video Room
Then the Organizer can use the Video Room at any time
Thoughts @zinc-collective/convene-maintainers?
Given the conversations we're having I think Scenario: Organizer requests we provision a tiny paid video room.
Sounds great! I've updated the feature definition with that scenario, and added some check-boxes that will tell us when we can close this issue out.
I've put created a mockup and some app flow here (GD)
Once https://github.com/zinc-collective/www.zinc.coop/pull/48 is merged, I think we can check off the first checkbox! We'll still have a ways to go for getting people into the system; but at least we'll have a way for potential clients to ask to use convene!
I've scoped this down a bit in the hopes that we can bring it to completion. In particular, I wanted to:
Scenarios:
[ ] Guest Purchases a Space
[ ] Resident purchases a Space
[ ] Utilities: Stripe (TODO: Create a Ticket for Stripe Utility)
[ ] Furniture: Order Form (TODO: Create a Ticket for an Order Form furniture)