busy-beaver-dev/busy-beaver

Multitenancy

alysivji opened this issue · 1 comments

#88 requires a lot more work to be done. In order to keep things structured, let's split into multiple epics, prioritize, and get things done as time permits.

We are currently able to install Busy Beaver in multiple workspaces, but only some features are enabled.

Progress

  • GitHub Summary Feature
    • MVP (working in multiple workspaces + onboarding experience) -- #187
    • automate the creation of a job that posts daily summaries for each new workspace; currently, this is manually done... but we're in the beta phase
    • add field that signals if feature enabled or not
  • Upcoming events -- spun out as #290
  • Retweeter -- feature has been deleted via #323
  • Interface for workspace admins to configure settings -- spun out as #202
  • GitHub Webhook (no changes)
  • External integration (no changes)

Things to think about

  • uninstalling app, app_uninstall -- spun out as #324
  • Add install button to README.md
  • Slack app store -- spun out #325

This issue is complete. The items that are not complete have been spun out into their own tickets.