Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Acquisition: Demoing Convene #61

Closed
3 of 5 tasks
zspencer opened this issue Aug 2, 2020 · 0 comments
Closed
3 of 5 tasks

Acquisition: Demoing Convene #61

zspencer opened this issue Aug 2, 2020 · 0 comments
Labels
⛰️ epic Work we expect will take multiple patches to complete ✨ feature Reduces Client's Burden or Grants them Benefits

Comments

@zspencer
Copy link
Member

zspencer commented Aug 2, 2020 •
edited
Loading 

Feature: Demoing Convene
  In order to determine if Convene is a product I would like to use
  I want to walk through it's value proposition for my particular context


Scenario: Prospective Client Schedules a Demo
  Given I am on the Convene landing page
  When I schedule a demo
  Then an email is sent to my email address with the demo information and a calendar invite 
  And an email is sent to convene-customer-team@zinc.coop with the demo information and a calendar invite


Scenario: Customer Team Member May Perform a Demo
  Given a fresh Convene deployment
  When I visit the fresh deployment
  Then there is a Convene-Demo Workspace
  And the Convene-Demo Workspace has a Room named "Vivek's Desk"
  And the Convene-Demo Workspace has a Room named "Zee's Desk"
  And the Convene-Demo Workspace has a Room named "Water Cooler"
  And the Convene-Demo Workspace has a Room named "The Ada Lovelace Room"
  And I can access the `convene-demo` workspace directly via `https://convene-demo.{{ deploymentDomain }}`

TODO

  • Put the feature tests in the repo
  • Create a Convene Demo workspace
  • Smoke test! Ensure convene-demo.zinc.coop lands us in the convene-demo workspace on production
  • Wire in the step definitions so the feature tests work
  • Integrate the Convene Demo calendly into the Convene landing page somehow
@zspencer zspencer added code ✨ feature Reduces Client's Burden or Grants them Benefits ⛰️ epic Work we expect will take multiple patches to complete labels Aug 2, 2020
zspencer added a commit that referenced this issue Aug 2, 2020
@zspencer
Create demo workspace on deploy to demo environments
03524d7 
See #61

This is a relatively large commit, but the gist is:

1. We pulled in `dotenv` so that we could use an environment variable to
   determine whether or not an environment should have the demo
   workspace
2. We sprouted a `Feature` model so we could begin to place logic for
   feature flagging in a bit of code under our control.
3. We added a `release:after_build` task so that it can perform any
   post-build but pre-deploy logic, such as populating the demo
   workspace.
4. And we created a `DemoWorkspace` model to take responsibility for
   ensuring we can idempotently create a DemoWorkspace within the
   database for our Customer team to use.
@zspencer zspencer mentioned this issue Aug 2, 2020
Merged
user512 pushed a commit that referenced this issue Aug 2, 2020
@zspencer
Sprout a Convene Demo Workspace (#65)
0019b5b 
* Frame in feature test for demo workspace functionality

As we do more customer development, it seems like investing in a
convene-demo workspace that is consistent across deployments makes some
sense.

* Create demo workspace on deploy to demo environments

See #61

This is a relatively large commit, but the gist is:

1. We pulled in `dotenv` so that we could use an environment variable to
   determine whether or not an environment should have the demo
   workspace
2. We sprouted a `Feature` model so we could begin to place logic for
   feature flagging in a bit of code under our control.
3. We added a `release:after_build` task so that it can perform any
   post-build but pre-deploy logic, such as populating the demo
   workspace.
4. And we created a `DemoWorkspace` model to take responsibility for
   ensuring we can idempotently create a DemoWorkspace within the
   database for our Customer team to use.

* We should prepare the database after we build it
@zspencer zspencer added this to the 1.0 - Andromeda milestone Aug 2, 2020
zspencer added a commit that referenced this issue Aug 2, 2020
@zspencer
Workspaces may be entered via Branded Domain
c688f4a 
See: #61

Branded Domains allow Visitors to bypass hitting the `/workspaces/:slug`
path and drop them right in the Workspaces Lobby.

For example, `convene-demo.zinc.coop` is a branded domain for the
`Convene Demo` workspace. `meet.zinc.coop` is a branded domain for the
Zinc workspace.
@zspencer zspencer mentioned this issue Aug 3, 2020
Merged
zspencer added a commit that referenced this issue Aug 3, 2020
@zspencer
Workspaces may be entered via Branded Domain
b26b3cf 
See: #61

Branded Domains allow Visitors to bypass hitting the `/workspaces/:slug`
path and drop them right in the Workspaces Lobby.

For example, `convene-demo.zinc.coop` is a branded domain for the
`Convene Demo` workspace. `meet.zinc.coop` is a branded domain for the
Zinc workspace.
zspencer added a commit that referenced this issue Aug 3, 2020
@zspencer
Workspaces may be entered via Branded Domain
6628586 
See: #61

Branded Domains allow Visitors to bypass hitting the `/workspaces/:slug`
path and drop them right in the Workspaces Lobby.

For example, `convene-demo.zinc.coop` is a branded domain for the
`Convene Demo` workspace. `meet.zinc.coop` is a branded domain for the
Zinc workspace.
zspencer added a commit that referenced this issue Aug 3, 2020
@zspencer
Workspaces may be entered via Branded Domain (#67)
23009f7 
See: #61

Branded Domains allow Visitors to bypass hitting the `/workspaces/:slug`
path and drop them right in the Workspaces Lobby.

For example, `convene-demo.zinc.coop` is a branded domain for the
`Convene Demo` workspace. `meet.zinc.coop` is a branded domain for the
Zinc workspace.

* Add DNS records for the Convene-Demo client

* Add name and domain validations to the Workspace model
@zspencer zspencer mentioned this issue Aug 7, 2020
Merged
zspencer added a commit that referenced this issue Aug 7, 2020
@zspencer
Videobridges live at convene-videobridge-$client.zinc.coop (#76)
ebbb617 
This allows us to use meet.zinc.coop for our convene domain for Zinc, as well as
renames the `jitsi` folder and other references to `videobridge` 

#61 
#74
zspencer added a commit that referenced this issue Aug 7, 2020
@zspencer
Make correct assertion re: Which videobridge convene-demo uses
d890d4e 
#61
@zspencer zspencer changed the title Demoing Convene Acquisition: Demoing Convene Aug 23, 2021
@zspencer zspencer removed this from the 1.0 - Andromeda milestone Sep 18, 2022
@zspencer zspencer closed this as completed Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
⛰️ epic Work we expect will take multiple patches to complete ✨ feature Reduces Client's Burden or Grants them Benefits
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zspencer