From bd95facf19c655ab573ad8b8c2544513e1e0c71f Mon Sep 17 00:00:00 2001 From: Dimitrie Hoekstra Date: Wed, 4 Feb 2026 17:48:43 +0100 Subject: [PATCH 1/2] Clarify #feature-demos vs #proj- channel usage in handbook Distinguish the purpose of #feature-demos (demos of work ready to be delivered, for a wide cross-functional audience) from #proj- channels (intermediate demos and scope discussions among directly involved stakeholders). --- src/handbook/company/communication.md | 6 +++++- src/handbook/development/project-management.md | 2 +- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/src/handbook/company/communication.md b/src/handbook/company/communication.md index 41fe0a84ff..c3ed49e7ea 100644 --- a/src/handbook/company/communication.md +++ b/src/handbook/company/communication.md @@ -98,7 +98,7 @@ Our recommended Slack (light) theme is: You will not automatically join every Slack channel when you start. Below are some helpful channels you may want to join depending on your interests and work. - `#announcements` for company-wide announcements. -- `#feature-demos` for product updates. Everyone should stay aware of product changes, no matter their role. +- [`#feature-demos`](https://flowfuse.slack.com/archives/C04GW82DJFK) for product demos of sprint and release deliveries, showcased to a wide audience (marketing, sales, product strategy, leadership). Everyone should stay aware of product changes, no matter their role. - `#ops-metrics` for sales and engagement metrics. - `#virtual-coffee` to join the coffee call rotation. - `#gh-handbook` to follow updates to the handbook. @@ -120,6 +120,10 @@ We recommend organizing these channels into [custom Slack sections](https://slac We also have channels for specific groups, such as `#people-managers` for managers and `#us-hr` for HR topics specific to US team members. +##### `#proj-` channels + +Project channels are created for continuous work discussion within a product lane with a clear scope. Use them for day-to-day coordination, intermediate demos, design feedback, and scope discussions among the directly involved stakeholders. When a feature is ready to be delivered, the final demo should be posted to [`#feature-demos`](https://flowfuse.slack.com/archives/C04GW82DJFK) instead. This keeps `#feature-demos` focused on what is ready for a wider audience, and `#proj-` channels focused on what is still in progress. + When you create a new channel, add a clear description. This helps everyone browse channels and decide which ones are relevant to their work. ### GitHub diff --git a/src/handbook/development/project-management.md b/src/handbook/development/project-management.md index 449be261f5..ed97aa0746 100644 --- a/src/handbook/development/project-management.md +++ b/src/handbook/development/project-management.md @@ -321,7 +321,7 @@ Demos should consist of: - A short (< 5 minute where possible) screen capture walk through of the feature with commentary. - It should cover the feature from a users perspective - what value do they get from it. - The video should be uploaded to, or linked to, in the relevant issue. - - A link should be posted to the `#feature-demos` channel in slack. This will allow the whole team to be notified of the demo without having to subscribe to every issue comment. + - To be posted to the [`#feature-demos`](https://flowfuse.slack.com/archives/C04GW82DJFK) channel in Slack for work that is ready to be delivered. Intermediate demos for fine-tuning current sprint scope should be shared in the relevant `#proj-` channel instead (see [Communication](/handbook/company/communication/#proj--channels)). For some features, it may be necessary to create multiple demos of different aspects. From 861ffc5fef5f5f435f299ff8ef46bd6be0b6a82d Mon Sep 17 00:00:00 2001 From: Dimitrie Hoekstra Date: Wed, 4 Feb 2026 19:15:27 +0100 Subject: [PATCH 2/2] Fix broken anchor link for project channels heading --- src/handbook/company/communication.md | 2 +- src/handbook/development/project-management.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/handbook/company/communication.md b/src/handbook/company/communication.md index c3ed49e7ea..6e25f27f42 100644 --- a/src/handbook/company/communication.md +++ b/src/handbook/company/communication.md @@ -120,7 +120,7 @@ We recommend organizing these channels into [custom Slack sections](https://slac We also have channels for specific groups, such as `#people-managers` for managers and `#us-hr` for HR topics specific to US team members. -##### `#proj-` channels +##### Project channels Project channels are created for continuous work discussion within a product lane with a clear scope. Use them for day-to-day coordination, intermediate demos, design feedback, and scope discussions among the directly involved stakeholders. When a feature is ready to be delivered, the final demo should be posted to [`#feature-demos`](https://flowfuse.slack.com/archives/C04GW82DJFK) instead. This keeps `#feature-demos` focused on what is ready for a wider audience, and `#proj-` channels focused on what is still in progress. diff --git a/src/handbook/development/project-management.md b/src/handbook/development/project-management.md index ed97aa0746..5615ccd74e 100644 --- a/src/handbook/development/project-management.md +++ b/src/handbook/development/project-management.md @@ -321,7 +321,7 @@ Demos should consist of: - A short (< 5 minute where possible) screen capture walk through of the feature with commentary. - It should cover the feature from a users perspective - what value do they get from it. - The video should be uploaded to, or linked to, in the relevant issue. - - To be posted to the [`#feature-demos`](https://flowfuse.slack.com/archives/C04GW82DJFK) channel in Slack for work that is ready to be delivered. Intermediate demos for fine-tuning current sprint scope should be shared in the relevant `#proj-` channel instead (see [Communication](/handbook/company/communication/#proj--channels)). + - To be posted to the [`#feature-demos`](https://flowfuse.slack.com/archives/C04GW82DJFK) channel in Slack for work that is ready to be delivered. Intermediate demos for fine-tuning current sprint scope should be shared in the relevant `#proj-` channel instead (see [Communication](/handbook/company/communication/#project-channels)). For some features, it may be necessary to create multiple demos of different aspects.