Operations

This covers how we run our business and deliver service to our customers.

Services used at FlowFuse

At FlowFuse there's a couple of services that are vital to the operation of the business. As a matter of having a plan before these services are taken offline or go bankrupt a table is maintained with where to go in case of service disruption.

Primary service Goal Backup Service Do not use
Slack Emphemeral internal communication Google Spaces (in Gmail) Email (only for legal items)
Slack Huddles Internal face to face commuication Google Meet -
Google Meet / Zoom External video calls Google Meet / Zoom -
Google Appointment Schedules Scheduling meetings with external parties Calendly -
AWS Hosting for FlowFuse Cloud ? -
GitHub Task management, planning and code development - -

Email

While there are a number of email aliases and google groups used throughout the organization, there is some activities across operations, people operations, and finance management that requires that activities be done with external parties. As a redundancy, rather than use a person's individual email (e.g. zj@), we use a google group to avoid the risk of information getting lost. For example, for some government filings, we use ops@.

GitHub

We use GitHub for task management, planning and code development across the company. The following is a high-level guide to the core repositories.

The Engineering team maintains a large number of repositories related to individual components of the product.

Repository Purpose Public/Private
FlowFuse/admin Company Admin tasks; onboarding/offboarding employees, access requests, release checklists private
FlowFuse/website The FlowFuse Website, including handbook public
FlowFuse/CloudProject Task management for FlowFuse Cloud platform private
FlowFuse/customer Task management for events and customer-specific work; webinars, artwork requests private
FlowFuse/dev-env FlowFuse development environment tooling public
FlowFuse/flowfuse The core product code repository public
FlowFuse/node-red A planning repository for upstream Node-RED tasks private

To create a new repository, first open an issue in the Admin repository using the New Repository checklist. This ensures all required security controls are applied.