Move team structure before team administration

You have to establish what the teams are before you can establish how
they are maintained

1 files changed, 33 insertions, 33 deletions

diff --git a/modules/Teams/pages/index.adoc b/modules/Teams/pages/index.adoc
index 667e915..9560dc3 100644
--- a/modules/Teams/pages/index.adoc
+++ b/modules/Teams/pages/index.adoc
@@ -24,6 +24,39 @@ Team Admins are marked in *bold* in official team listings.
 There is no distinction between technical and non-technical team members. Both are valued, and any useful distinctions are left to the discretion of individual teams.
 ====
 
+== Team Structure
+
+=== Internal Organization
+Teams organize themselves internally however they want.
+However, all teams must have at least 1 admin, and at most 3.
+This document does contain multiple recommendations, which, if followed, will make external relations easier.
+Further, team administrators must follow non-team-local expectations.
+
+=== Creating a New Team
+An existing team member within the project may propose creating a new team.
+In that scenario, the process will be the same as in <<_becoming_a_team_administrator>>.
+If the vote passes, the new team is formed, with the sponsor member as the only administrator.
+
+=== Dissolution of Teams
+A team is dissolved if it has no more members.
+If a team has no more administrators, one must be nominated, as in <<_becoming_a_team_administrator>>.
+If the vote does not pass, the team is dissolved as well.
+
+== The Base Team
+The Base team is purely an administrative one.
+It is also the only team that shall not have admins, and has a static number of members.
+The Base team must always have exactly 3 members, to guarantee quorum.
+The Base team technically owns Alpine.
+Alpine's policies apply to them, but they have the power to bypass them in case of extreme need.
+
+It is expected that the Base team does not do anything unless prompted.
+Violation of this without there being a strong need is effectively a violation of trust of the entire rest of the project.
+Similarly, the Base team is expected to trust team admins and members to do the correct thing on their own.
+
+Base team members are elected through a project-wide {votelink}[Vote].
+A term is 3 years long, and the terms are staggered (each year, a new Base team member must be elected).
+Term cycling is allowed - you cannot replace yourself, but you can replace the next person to rotate out.
+
 == Membership
 
 === Being a Member
@@ -65,36 +98,3 @@ Removing members (and especially administrators) is an extreme measure.
 In most cases, it is possible to solve issues through other means.
 It is highly recommended that the removal of anyone from the project be strongly considered before it is suggested.
 ====
-
-== Team Structure
-
-=== Internal Organization
-Teams organize themselves internally however they want.
-However, all teams must have at least 1 admin, and at most 3.
-This document does contain multiple recommendations, which, if followed, will make external relations easier.
-Further, team administrators must follow non-team-local expectations.
-
-=== Creating a New Team
-An existing team member within the project may propose creating a new team.
-In that scenario, the process will be the same as in <<_becoming_a_team_administrator>>.
-If the vote passes, the new team is formed, with the sponsor member as the only administrator.
-
-=== Dissolution of Teams
-A team is dissolved if it has no more members.
-If a team has no more administrators, one must be nominated, as in <<_becoming_a_team_administrator>>.
-If the vote does not pass, the team is dissolved as well.
-
-== The Base Team
-The Base team is purely an administrative one.
-It is also the only team that shall not have admins, and has a static number of members.
-The Base team must always have exactly 3 members, to guarantee quorum.
-The Base team technically owns Alpine.
-Alpine's policies apply to them, but they have the power to bypass them in case of extreme need.
-
-It is expected that the Base team does not do anything unless prompted.
-Violation of this without there being a strong need is effectively a violation of trust of the entire rest of the project.
-Similarly, the Base team is expected to trust team admins and members to do the correct thing on their own.
-
-Base team members are elected through a project-wide {votelink}[Vote].
-A term is 3 years long, and the terms are staggered (each year, a new Base team member must be elected).
-Term cycling is allowed - you cannot replace yourself, but you can replace the next person to rotate out.