Skip to content

Commit 8bb2fd7

Browse files
authored
Merge pull request #4387 from FlowFuse/knolleary-patch-1
Document GitHub usage and core repositories
2 parents b3795d9 + ec74287 commit 8bb2fd7

1 file changed

Lines changed: 20 additions & 1 deletion

File tree

src/handbook/operations/index.md

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,26 @@ or go bankrupt a table is maintained with where to go in case of service disrupt
2727
| Google Meet / Zoom | External video calls | Google Meet / Zoom | - |
2828
| [Google Appointment Schedules](https://support.google.com/calendar/answer/10729749?hl=en) | Scheduling meetings with external parties | Calendly | - |
2929
| AWS | Hosting for FlowFuse Cloud | ? | - |
30+
| GitHub | Task management, planning and code development | - | - |
3031

3132
## Email
3233

33-
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@.
34+
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@.
35+
36+
## GitHub
37+
38+
We use GitHub for task management, planning and code development across the company. The following is a high-level guide to the core repositories.
39+
40+
The Engineering team maintains a large number of repositories related to individual components of the product.
41+
42+
| Repository | Purpose | Public/Private |
43+
| -- | -- | -- |
44+
| FlowFuse/admin | Company Admin tasks; onboarding/offboarding employees, access requests, release checklists | private |
45+
| FlowFuse/website | The FlowFuse Website, including handbook | public |
46+
| FlowFuse/CloudProject | Task management for FlowFuse Cloud platform | private |
47+
| FlowFuse/customer | Task management for events and customer-specific work; webinars, artwork requests | private |
48+
| FlowFuse/dev-env | FlowFuse development environment tooling | public |
49+
| FlowFuse/flowfuse | The core product code repository| public |
50+
| FlowFuse/node-red | A planning repository for upstream Node-RED tasks | private |
51+
52+
To create a new repository, first open an issue in the [Admin](https://github.com/FlowFuse/admin) repository using the New Repository checklist. This ensures all required security controls are applied.

0 commit comments

Comments
 (0)