From 4ff27f040745edb974e76477670f886cb85ca0dd Mon Sep 17 00:00:00 2001
From: Chloe Kudryavtsev <toast@toastin.space>
Date: Mon, 25 Mar 2019 14:09:06 -0400
Subject: [teams] Add a BIG warning about team specificity

---
 modules/ROOT/pages/index.adoc | 9 +++++++++
 1 file changed, 9 insertions(+)

(limited to 'modules/ROOT/pages/index.adoc')

diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
index e49ba72..1422e9a 100644
--- a/modules/ROOT/pages/index.adoc
+++ b/modules/ROOT/pages/index.adoc
@@ -31,6 +31,15 @@ You should know your fellow team members well, and cooperate with them (and pote
 As a team, you may request various workspaces, such as a separate irc channel, git namespace, dedicated host, and more.
 As a team, it is up to you how you manage yourselves internally, but the contents of this document should serve as guidelines.
 
+[WARNING]
+====
+Some teams are strict supersets of others.
+For example, the packaging team handles all packages, but the core team handles the `main/` repository and the python team handles python-related packages.
+Teams with the more concrete scope (core and python in this example) are given priority over their domain.
+If you are part of the generic team, but are not part of the specific team, you should communicate with the specific team if you wish to change something within their domain.
+Doing otherwise (especially if it has negative consequences) can be considered abuse of your power, and may even lead to you being removed from the team.
+====
+
 === Being a Team Administrator
 As a team admin, you have more powers, and thus more responsibility.
 Since you have the power to vote (e.g in nominating other team admins), you are expected to be present for meetings and voting sessions.
-- 
cgit v1.2.3

