From ada7990f8e4e7e64c2078e38d4316210599b1abc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pablo=20Correa=20G=C3=B3mez?= Date: Thu, 11 Jun 2026 16:42:02 +0200 Subject: [PATCH] docs: add that lowering main or community devices requires communication MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Pablo Correa Gómez Part-of: --- docs/packaging/device-categorization.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/packaging/device-categorization.md b/docs/packaging/device-categorization.md index 2ed48673d..543df94cd 100644 --- a/docs/packaging/device-categorization.md +++ b/docs/packaging/device-categorization.md @@ -241,7 +241,10 @@ the date of the branching. If the maintainers cannot be contacted, or if two weeks and any additionally requested time pass and the device still does not meet the criteria, a merge -request to move them to the now appropriate category should be opened. +request to move them to the now appropriate category should be opened. If the +device being demoted is in the main or community category is in the main or +community category, the community shall be notified through Fediverse and +blog posts (edge blog post, release notes, or next monthly blog post). Merge requests moving a device to a lower category are subject to the standard [pmaports approval rules](../merge-requests/approval-rules).