Some minor changes to affiliates page

Author: jaspervdj

resources/content/pages/affiliates/affiliates-en.md

@@ -15,6 +15,27 @@ about_content:
     We believe that this will help us grow towards being a more open and
     welcoming community.
 
+    ### Who Has Affiliated?
+
+    The following groups are affiliated with the Haskell Foundation:
+
+     -  The [Haskell IDE Team](https://github.com/haskell/haskell-language-server)
+     -  The [GHC Steering Committee](https://github.com/ghc-proposals/ghc-proposals)
+     -  [Haskell Weekly](https://haskellweekly.news/)
+
+    The following groups are in the process of affiliating.  This means they
+    endorse the Haskell Foundation but are still in the process of adopting the
+    new guidelines:
+
+     -  The [Core Libraries Committee](https://wiki.haskell.org/Core_Libraries_Committee)
+     -  The [Haskell.org Committee](https://www.haskell.org/haskell-org-committee)
+     -  The Haskell Admins
+     -  [Cabal](https://www.haskell.org/cabal/)
+
+    This is not a closed list!  We very much want the Haskell Foundation to be
+    something by _all of us_.  Please [contact](/en/contact/) us if you are
+    interested in joining us in our quest to make Haskell better for everyone.
+
     ### What Does Affiliation Entail?
 
     Affiliation means that the group supports the goals of the Haskell Foundation, and, in return, the Haskell Foundation supports this group.
@@ -23,41 +44,35 @@ about_content:
 
     Affiliation does not mean that the HF is taking over control of that group’s bailiwick. The group’s powers and responsibilities remain unchanged, although it would be reasonable to expect the group to take into account the views of the HF.
 
-    Note that the rules laid out below are still a draft, and we expect to iterate and refine them as we contact more and more groups.
-
     We make a distinction between projects and committees.
 
     #### Affiliated Committees
 
     ##### Transparency
 
-    * Group must have some website that makes it clear what the purpose of this group is
-    * All technical discussions must be stored in a publicly accessible location
+    * Group must have some website that makes it clear what the goals and responsibilities of this group are
+    * All technical discussions must be stored in a publicly accessible location, for example:
         - GitHub issues
         - GitLab issues
         - Mailing list archives
-    * Obvious exception for confidential matters such as
-        - Financial information
-        - Security related information
-    * It should be clear what decisions the group has taken, and what are under discussion (if it’s that kind of group). Eg the GHC Steering Committee has GitLab PRs.
+      There is an obvious exception for confidential matters such as financial and security related information
+    * It should be clear what decisions the group has taken, and what are under discussion (if it’s that kind of group).  A good example of this are the GHC Steering Committee proposals, but a simple email to a public list can also suffice.
     * The group must have a voting system in place in case it cannot reach unanimity. Votes must be accompanied by reasoning, and a tie-breaking mechanism should be in place.
 
     ##### Membership
 
     * The group’s website should list its members (with their affiliations and terms), and the membership rules.
-    * Groups should appoint a chair (or co-chairs) or contact for Haskell Foundation
-    * Groups should ensure a turnover of membership, for example by setting terms
+    * Groups should appoint a chair (or co-chairs) or a contact for Haskell Foundation.
+    * Groups should ensure a turnover of membership, for example by setting terms.
         - This only makes sense for "decision-making" bodies, not really for groups that just focus on doing work.
-    * The process for appointing new members should be clearly set out.
+    * The process for appointing new members should be clearly set out:
         - There should be a “way in” for new members who are not already part of the “in crowd”; for example, a regular opportunity to self-nominate.
         - Criteria for new members should be written down, so that new members can address them in writing a self-nomination.
         - A reasonably broad group of people should be involved in making appointment decisions (e.g. not just the chair).  Typically the whole group votes on appointing new members.
 
     ##### Code of Conduct
 
-    Groups must adopt the [Guidelines for Respectful Communication](/guidelines-for-respectful-communication). This is a very "light" CoC since it focuses on positive aspiration rather than negative policing.
-
-    Groups may additionally adopt other guidelines & CoCs that are stronger; as long as they do not conflict with the GRC.
+    Groups must adopt the [Guidelines for Respectful Communication](/guidelines-for-respectful-communication).  Groups may additionally adopt other guidelines & CoCs that are stronger; as long as they do not conflict with the GRC.
 
     Why make a code of conduct as part of HF affiliation?
     * We want the Haskell community to be welcoming, diverse, and inclusive.  Having explicit guidelines for respectful communication signals that desire, and makes it more explicit and concrete.
@@ -70,26 +85,4 @@ about_content:
     * The project must be open to community discussion about possible features and contributions.
     * The project should encourage new contributors and members, i.e. there should be "a way in".
     * Just like committees, the project must adopt the [Guidelines for Respectful Communication](/guidelines-for-respectful-communication) as a code of conduct.
-
-
-    ### Who Has Affiliated?
-
-    The following groups are affiliated with the Haskell Foundation:
-
-     -  The [Haskell IDE Team](https://github.com/haskell/haskell-language-server)
-     -  The [GHC Steering Committee](https://github.com/ghc-proposals/ghc-proposals)
-     -  [Haskell Weekly](https://haskellweekly.news/)
-
-    The following groups are in the process of affiliating.  This means they
-    endorse the Haskell Foundation but are still in the process of adopting the
-    new guidelines:
-
-     -  The [Core Libraries Committee](https://wiki.haskell.org/Core_Libraries_Committee)
-     -  The [Haskell.org Committee](https://www.haskell.org/haskell-org-committee)
-     -  The Haskell Admins
-     -  [Cabal](https://www.haskell.org/cabal/)
-
-    This is not a closed list!  We very much want the Haskell Foundation to be
-    something by _all of us_.  Please [contact](/en/contact/) us if you are
-    interested in joining us in our quest to make Haskell better for everyone.
 ---