From 41d754cc91909e3273b23a946a7456f2a8317f6f Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Tue, 13 Oct 2020 15:38:10 +1300
Subject: [PATCH 01/14] Draft of an official Governance structure

---
 _config.yml         |   2 +
 pages/governance.md | 280 ++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 282 insertions(+)
 create mode 100644 pages/governance.md

diff --git a/_config.yml b/_config.yml
index e2f532a..1dba913 100644
--- a/_config.yml
+++ b/_config.yml
@@ -111,6 +111,8 @@ css_inline: false # Will insert all styles into a single <style> block in the <h
 navigation_header:
 - title: Home
   url: /
+- title: Governance
+  url: /pages/governance
 - title: Code
   url: /pages/code/
 - title: Documentation
diff --git a/pages/governance.md b/pages/governance.md
new file mode 100644
index 0000000..52b57ed
--- /dev/null
+++ b/pages/governance.md
@@ -0,0 +1,280 @@
+---
+title:  "Governance Structure"
+---
+
+This document describes the formal governance structure of the JuMP project.
+
+For the purpose of this document, "JuMP" includes all repositories in the
+[JuMP-dev Github organization].
+
+## Mission
+
+The mission of the JuMP project is to provide a free, open-source, and
+high-performance software stack for mathematical optimization.
+
+## Code of Conduct
+
+The JuMP community strongly values inclusivity and diversity. Everyone should
+treat others with the utmost respect. Everyone in the community must adhere to
+the [NumFOCUS Code of Conduct](https://numfocus.org/code-of-conduct) and the
+[Julia Community Standards](https://julialang.org/community/standards/), which
+reflect the values of our community. Both these links have information on how to
+confidentially report a violation.
+
+## Entities
+
+This section outlines the different entities that exist within the JuMP project,
+their basic role, and how membership of each entity is determined.
+
+### BDFL
+
+Due to his role in the creation of JuMP, [Miles Lubin](https://github.com/mlubin)
+holds the role of [BDFL](https://en.wikipedia.org/wiki/Benevolent_dictator_for_life).
+
+### Core Contributors
+
+Core contributors lead the technical development of the JuMP project, and they
+are the ultimate authority on the direction of the JuMP project.
+
+The current core contributors are:
+
+* Miles Lubin (@mlubin)
+* Benoît Legat (@blegat)
+* Joaquim Dias Garcia (@joaquimg)
+* Joey Huchette (@joehuchette)
+* Oscar Dowson (@odow)
+
+A new core contributor may be added by consensus of the current core
+contributors and notification to the [Steering Council].
+
+Before becoming a core contributor, it is expected that the community member is
+a [repository maintainer](#repository-maintainers) of several repositories.
+
+### Emeritus Core Contributors
+
+Emeritus core contributors are community members who were [core contributors],
+but have stepped back to a less active role.
+
+The emeritus core contributors are:
+
+* Iain Dunning (@iainnz)
+
+A core contributor may choose to switch to emeritus status by informing the
+other [core contributors] and the [Steering Council].
+
+### Repository Maintainers
+
+Repository maintainers are trusted members of the community who help the [core
+contributors] by managing a limited number of repositories in the [JuMP-dev
+Github organization].
+
+Any core contributor has individual authority to appoint a community member as a
+repository maintainer of a repository with notification to the other [core
+contributors].
+
+Before becoming a repository maintainer, it is expected that the community
+member will have been an active participant in the development and maintenance
+of a repository for a sustained period of time. This includes triaging issues,
+proposing and reviewing pull requests, and updating any binary dependencies as
+needed.
+
+Community members may be maintainers of multiple repositories at the same time.
+
+Repository maintainers can step back from their role at any time by informing a
+core developer. Furthermore, [core contributors], by consensus, can choose to
+remove repository maintainers for any reason (typically inactivity).
+
+### NumFOCUS
+
+JuMP is a [fiscally sponsored project of NumFOCUS](https://numfocus.org/project/jump),
+a 501(c)(3) public charity in the United States. NumFOCUS provides JuMP with
+fiscal, legal, and administrative support to help ensure the health and
+sustainability of the project.
+
+### Steering Council
+
+The Steering Council supports the [core contributors] by representing JuMP in
+all interactions with [NumFOCUS](#numfocus), e.g., by attending NumFOCUS's
+annual summit. In addition, the Steering Council:
+
+* Approves expenditures related to JuMP and paid through the NumFOCUS account.
+* Negotiates and approves contracts between NumFOCUS and external contractors
+  who provide paid work to JuMP.
+
+The current members of the Steering Council are:
+
+* Miles Lubin, Google (@mlubin)
+* Juan Pablo Vielma, Google (@juan-pablo-vielma)
+* Joey Huchette, Rice University (@joehuchette)
+* Oscar Dowson (@odow)
+* Changhyun Kwon, U. South Florida (@chkwon)
+
+A member of the Steering Council may leave the council by notifying the Steering
+Council and [core contributors]. The remaining members, in consultation with the
+[core contributors], will invite a member of the community to join in order to
+maintain a quorum of five members.
+
+## Decision Making Process
+
+This section outlines how financial and non-financial decisions are made in the
+JuMP project.
+
+### Financial Decisions
+
+All financial decisions are made by the [Steering Council] to ensure any funds
+are spent in a manner that furthers the [mission](#mission) of JuMP. Financial
+decisions require majority approval by [Steering Council] members.
+
+Community members proposing decisions with a financial aspect should contact the
+[Steering Council] directly, or table their proposal as an agenda item for
+discussion on a [monthly developer call](#monthly-developer-call).
+
+### Non-financial Decisions
+
+All non-financial decisions are made via consensus of the [core contributors]
+and relevant [repository maintainers]. [Emeritus core contributors](#emeritus-core-contributors)
+ are not considered to be [core contributors] for this purpose.
+
+Code-related decisions, such when a pull request is ready to be accepted and
+merged, should be discussed via the relevant Github issues and pull requests. If
+consensus cannot be achieved, the community member proposing the change may be
+invited by a core contributor to present their proposal at a [monthly developer
+call](#monthly-developer-call) for further discussion and community input.
+
+Non-code-related decisions, such long-term strategic planning for JuMP, should
+either be discussed in a Github issue, or tabled as an agenda item and discussed
+on a [monthly developer call](#monthly-developer-call).
+
+If consensus on a non-financial decision cannot be achieved, the final decision
+will be made by the [BDFL](#bdfl).
+
+The [Steering Council] can gain addition decision-making power if the [core
+contributors] decide to delegate.
+
+### Conflict of Interest
+
+It is expected that community members will be employed at a wide range of
+companies, universities and non-profit organizations. Because of this, it is
+possible that members will have conflicts of interest. Such conflicts of
+interest include, but are not limited to:
+
+* Financial interests, such as investments, employment or contracting work,
+  outside of JuMP that may influence their work on JuMP.
+* Access to proprietary information of their employer that could potentially
+  leak into their work with JuMP.
+
+All members of the [Steering Council] shall disclose to the [Steering Council]
+any conflict of interest they may have. Members with a conflict of interest in a
+particular issue may participate in [Steering Council] discussions on that
+issue, but must recuse themselves from voting.
+
+[Core contributors](#core-contributors) and [repository maintainers] should also
+disclose conflicts of interest with other [core contributors] and step back from
+decisions when conflicts of interests are in play.
+
+## Github Permissions
+
+[Github permissions][permissions] are used to control access to repositories in
+the [JuMP-dev Github organization].
+
+Anyone with commit access to a repository is trusted to use it in a way that is
+consistent with the [non-financial decisions](#non-financial-decisions) process.
+Those with permissions should prefer pull requests over direct pushes, ask for
+feedback on changes if they are not sure there is a consensus, and follow JuMP's
+[style guide](https://jump.dev/JuMP.jl/stable/style/) and development processes.
+
+### Core Contributors
+
+[Core contributors](#core-contributors) are added as [Owners][owner-permission]
+of the [JuMP-dev Github organization] and have [Admin][permissions] permission
+to every repository.
+
+### Emeritus Core Contributors
+
+[Emeritus core contributors](#emeritus-core-contributors) retain the same commit
+rights as [core contributors], unless they choose to surrender them.
+
+### Repository Maintainers
+
+[Repository maintainers](#repository-maintainers) have [Maintain][permissions]
+rights to an individual repository as an outside collaborator. Among other
+rights, this allows them to push code to a branch in the
+[JuMP-dev Github organization] instead of their personal fork, merge pull
+requests, and close issues.
+
+## Community Involvement
+
+The JuMP project highly values the contributions made by members of the
+community. As an open-source project, JuMP is both made for the community, and
+by the community.
+
+There are four main channels that JuMP uses to engage with the community.
+
+### Community Forum
+
+The community forum is a place for community members to post questions and
+receive help.
+
+The current forum is the "Optimization (Mathematical)" section of the
+[Julia Discourse Forum](https://discourse.julialang.org/c/domain/opt/13).
+
+### Developer Chatroom
+
+The developer chatroom is a chatroom for developer-focused discussions about
+JuMP.
+
+The current chatroom is the [JuMP-dev Gitter channel](https://gitter.im/JuliaOpt/JuMP-dev).
+
+### Monthly Developer Call
+
+The [Steering Council] hosts a monthly developer call to discuss JuMP-related
+business.
+
+The calls are currently scheduled on the fourth Thursday of every month at 14:00
+Eastern. For information on how to take part, join the [developer chatroom] and
+ask `@odow` or `@mlubin` for an invite to the monthly developer call.
+
+### JuMP-dev Workshops
+
+The [Steering Council] will periodically choose a Chair to organize a JuMP-dev
+workshop.
+
+Previous workshops include [Santiago, 2019](https://jump.dev/meetings/santiago2019/),
+[Bordeaux, 2018](https://jump.dev/meetings/bordeaux2018/), and [Boston, 2017](https://jump.dev/meetings/mit2017/).
+
+Announcements of future workshops will be communicated through the
+[community forum] and via the [jump.dev](https://jump.dev) website.
+
+## Transferring repositories to jump-dev
+
+The [JuMP-dev Github organization] exists to simplify the management of Github
+permissions on JuMP-related repositories. It is not a curation of all
+JuMP-compatible solvers and supporting packages.
+
+Instead, community members who develop new pure-Julia solvers or solver-wrappers
+should first add their package to the list of supported solvers in the
+[Installation Guide](https://jump.dev/JuMP.jl/stable/installation/#Getting-Solvers-1)
+of the JuMP documentation.
+
+Note that when developing a new solver or JuMP-extension, the [core
+contributors] request that you not use "JuMP" in the name without prior consent.
+
+Even once a package has matured, the bar for transferring repositories to the
+[JuMP-dev Github organization] is high, and can be summarized by the following:
+
+* The maintainance of the package would be simplified if [core contributors]
+  have [Admin permission][permissions] to the repository.
+
+Community members wishing to transfer a repository from their personal account
+to the [JuMP-dev Github organization] should contact the [core contributors]
+via the [developer chatroom].
+
+[community forum]: https://discourse.julialang.org/c/domain/opt/13
+[developer chatroom]: https://gitter.im/JuliaOpt/JuMP-dev
+[JuMP-dev Github organization]: https://github.com/jump-dev
+[permissions]: https://docs.github.com/en/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level
+[owner-permission]: https://docs.github.com/en/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#permission-levels-for-an-organization
+
+[core contributors]: #core-contributors
+[repository maintainers]: #repository-maintainers
+[Steering Council]: #steering-council

From 0247da6c0717a2913fd5b9ba36c37e24c7bcf02c Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Tue, 20 Oct 2020 17:45:43 +1300
Subject: [PATCH 02/14] Add annoucement to go with governance structure

---
 _posts/2020-10-20-governance.md | 39 +++++++++++++++++++++++++++++++++
 1 file changed, 39 insertions(+)
 create mode 100644 _posts/2020-10-20-governance.md

diff --git a/_posts/2020-10-20-governance.md b/_posts/2020-10-20-governance.md
new file mode 100644
index 0000000..fb8d709
--- /dev/null
+++ b/_posts/2020-10-20-governance.md
@@ -0,0 +1,39 @@
+---
+layout: post
+title:  "Formalizing a governance structure"
+date:   2020-10-20
+categories: [announcements]
+---
+
+Recently, JuMP turned eight years old. (The [first commit](https://github.com/jump-dev/JuMP.jl/commit/688b732c13abf7182e438ca22b0b00890a08be63)
+for "Julp" was made on 10 October 2012!) It has come a long way since it's
+creation as a side-project of two graduate students at MIT, and as we approach
+a 1.0 release, we thought it was time to formalize our governance structure.
+
+You can find the resulting document under the [Governance tab](/pages/governance)
+at [jump.dev](https://jump.dev).
+
+The highlights include:
+
+ * Appointing Miles Lubin as our [BDFL](https://en.wikipedia.org/wiki/Benevolent_dictator_for_life).
+
+ * Defining entities such as the core contributors, emeritus core contributors,
+   repository maintainers, and the Steering Council, along with their roles, and
+   how membership is determined for each entity.
+
+ * Clarifying our decision-making process, by describing who gets to decide what
+   when.
+
+ * Listing what Github permissions different entities have to the repositories
+   in the [jump-dev](https://github.com/jump-dev) Github organization.
+
+ * Outlining channels of community involvement, including the poorly publicized
+   fact that we hold a monthly developer call.
+
+ * Formalizing a process for transferring repositories to the
+   [jump-dev](https://github.com/jump-dev) Github organization.
+
+We belive this document strengthens the foundation of JuMP, and sets it up for
+a sustainable, long-term future.
+
+Stay tuned for more progress!

From 67006f04f0eae8ab6c63b6d0bcb219666763b625 Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Wed, 21 Oct 2020 09:22:32 +1300
Subject: [PATCH 03/14] Further refinements to governance.md

---
 pages/governance.md | 15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/pages/governance.md b/pages/governance.md
index 52b57ed..d26a6e6 100644
--- a/pages/governance.md
+++ b/pages/governance.md
@@ -9,8 +9,8 @@ For the purpose of this document, "JuMP" includes all repositories in the
 
 ## Mission
 
-The mission of the JuMP project is to provide a free, open-source, and
-high-performance software stack for mathematical optimization.
+The mission of the JuMP project is to provide a free, open-source, easy-to-use
+and powerful software stack for mathematical optimization.
 
 ## Code of Conduct
 
@@ -26,10 +26,10 @@ confidentially report a violation.
 This section outlines the different entities that exist within the JuMP project,
 their basic role, and how membership of each entity is determined.
 
-### BDFL
+### Benevolent Dictator For Life
 
 Due to his role in the creation of JuMP, [Miles Lubin](https://github.com/mlubin)
-holds the role of [BDFL](https://en.wikipedia.org/wiki/Benevolent_dictator_for_life).
+holds the role of [Benevolent Dictator For Life (BDFL)](https://en.wikipedia.org/wiki/Benevolent_dictator_for_life).
 
 ### Core Contributors
 
@@ -48,7 +48,8 @@ A new core contributor may be added by consensus of the current core
 contributors and notification to the [Steering Council].
 
 Before becoming a core contributor, it is expected that the community member is
-a [repository maintainer](#repository-maintainers) of several repositories.
+a [repository maintainer](#repository-maintainers) of several repositories in
+the [JuMP-dev Github organization].
 
 ### Emeritus Core Contributors
 
@@ -133,7 +134,7 @@ discussion on a [monthly developer call](#monthly-developer-call).
 
 All non-financial decisions are made via consensus of the [core contributors]
 and relevant [repository maintainers]. [Emeritus core contributors](#emeritus-core-contributors)
- are not considered to be [core contributors] for this purpose.
+are not considered to be [core contributors] for this purpose.
 
 Code-related decisions, such when a pull request is ready to be accepted and
 merged, should be discussed via the relevant Github issues and pull requests. If
@@ -234,6 +235,8 @@ The calls are currently scheduled on the fourth Thursday of every month at 14:00
 Eastern. For information on how to take part, join the [developer chatroom] and
 ask `@odow` or `@mlubin` for an invite to the monthly developer call.
 
+The invite contains information on how to table agenda items for upcoming calls.
+
 ### JuMP-dev Workshops
 
 The [Steering Council] will periodically choose a Chair to organize a JuMP-dev

From 818ee47e3aa58b265d46d128b4dfff984c7b5232 Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Wed, 21 Oct 2020 09:30:03 +1300
Subject: [PATCH 04/14] Add Social Media

---
 pages/governance.md | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/pages/governance.md b/pages/governance.md
index d26a6e6..605a791 100644
--- a/pages/governance.md
+++ b/pages/governance.md
@@ -209,15 +209,15 @@ The JuMP project highly values the contributions made by members of the
 community. As an open-source project, JuMP is both made for the community, and
 by the community.
 
-There are four main channels that JuMP uses to engage with the community.
+There are five main channels that JuMP uses to engage with the community.
 
 ### Community Forum
 
 The community forum is a place for community members to post questions and
 receive help.
 
-The current forum is the "Optimization (Mathematical)" section of the
-[Julia Discourse Forum](https://discourse.julialang.org/c/domain/opt/13).
+The current forum is the ["Optimization (Mathematical)" section of the
+Julia Discourse Forum](https://discourse.julialang.org/c/domain/opt/13).
 
 ### Developer Chatroom
 
@@ -246,7 +246,12 @@ Previous workshops include [Santiago, 2019](https://jump.dev/meetings/santiago20
 [Bordeaux, 2018](https://jump.dev/meetings/bordeaux2018/), and [Boston, 2017](https://jump.dev/meetings/mit2017/).
 
 Announcements of future workshops will be communicated through the
-[community forum] and via the [jump.dev](https://jump.dev) website.
+[community forum], [social media](#social-media), and via the
+[jump.dev](https://jump.dev) website.
+
+### Social Media
+
+The JuMP Twitter handle is [@JuMPjl](https://twitter.com/JuMPjl).
 
 ## Transferring repositories to jump-dev
 
@@ -272,12 +277,12 @@ Community members wishing to transfer a repository from their personal account
 to the [JuMP-dev Github organization] should contact the [core contributors]
 via the [developer chatroom].
 
-[community forum]: https://discourse.julialang.org/c/domain/opt/13
-[developer chatroom]: https://gitter.im/JuliaOpt/JuMP-dev
 [JuMP-dev Github organization]: https://github.com/jump-dev
 [permissions]: https://docs.github.com/en/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level
 [owner-permission]: https://docs.github.com/en/free-pro-team@latest/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization#permission-levels-for-an-organization
 
+[community forum]: #community-forum
+[developer chatroom]: #developer-chatroom
 [core contributors]: #core-contributors
 [repository maintainers]: #repository-maintainers
 [Steering Council]: #steering-council

From f29e7196f3d92b124b89c9933aefacd908b1ca4d Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Wed, 21 Oct 2020 11:51:06 +1300
Subject: [PATCH 05/14] Typo fix and date bump

---
 _posts/{2020-10-20-governance.md => 2020-10-21-governance.md} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename _posts/{2020-10-20-governance.md => 2020-10-21-governance.md} (93%)

diff --git a/_posts/2020-10-20-governance.md b/_posts/2020-10-21-governance.md
similarity index 93%
rename from _posts/2020-10-20-governance.md
rename to _posts/2020-10-21-governance.md
index fb8d709..3e84867 100644
--- a/_posts/2020-10-20-governance.md
+++ b/_posts/2020-10-21-governance.md
@@ -1,7 +1,7 @@
 ---
 layout: post
 title:  "Formalizing a governance structure"
-date:   2020-10-20
+date:   2020-10-21
 categories: [announcements]
 ---
 
@@ -33,7 +33,7 @@ The highlights include:
  * Formalizing a process for transferring repositories to the
    [jump-dev](https://github.com/jump-dev) Github organization.
 
-We belive this document strengthens the foundation of JuMP, and sets it up for
+We believe this document strengthens the foundation of JuMP, and sets it up for
 a sustainable, long-term future.
 
 Stay tuned for more progress!

From 332e128d2c881da88465212eb28b6683ca4c9bc3 Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Wed, 21 Oct 2020 12:04:19 +1300
Subject: [PATCH 06/14] More tweaks

---
 pages/governance.md | 45 ++++++++++++++++++++++++---------------------
 1 file changed, 24 insertions(+), 21 deletions(-)

diff --git a/pages/governance.md b/pages/governance.md
index 605a791..77b979c 100644
--- a/pages/governance.md
+++ b/pages/governance.md
@@ -60,8 +60,8 @@ The emeritus core contributors are:
 
 * Iain Dunning (@iainnz)
 
-A core contributor may choose to switch to emeritus status by informing the
-other [core contributors] and the [Steering Council].
+A [core contributor](#core-contributors) may choose to switch to emeritus status
+by informing the other [core contributors] and the [Steering Council].
 
 ### Repository Maintainers
 
@@ -69,9 +69,9 @@ Repository maintainers are trusted members of the community who help the [core
 contributors] by managing a limited number of repositories in the [JuMP-dev
 Github organization].
 
-Any core contributor has individual authority to appoint a community member as a
-repository maintainer of a repository with notification to the other [core
-contributors].
+Any [core contributor](#core-contributors) has individual authority to appoint a
+community member as a repository maintainer of a repository with notification to
+the other [core contributors].
 
 Before becoming a repository maintainer, it is expected that the community
 member will have been an active participant in the development and maintenance
@@ -82,8 +82,9 @@ needed.
 Community members may be maintainers of multiple repositories at the same time.
 
 Repository maintainers can step back from their role at any time by informing a
-core developer. Furthermore, [core contributors], by consensus, can choose to
-remove repository maintainers for any reason (typically inactivity).
+[core contributor](#core-contributors). Furthermore, [core contributors], by
+consensus, can choose to remove repository maintainers for any reason (typically
+inactivity).
 
 ### NumFOCUS
 
@@ -95,8 +96,9 @@ sustainability of the project.
 ### Steering Council
 
 The Steering Council supports the [core contributors] by representing JuMP in
-all interactions with [NumFOCUS](#numfocus), e.g., by attending NumFOCUS's
-annual summit. In addition, the Steering Council:
+all interactions with [NumFOCUS](#numfocus), e.g., by attending [NumFOCUS's
+annual summit](https://numfocus.org/blog/numfocus-summit-2019). In addition, the
+Steering Council:
 
 * Approves expenditures related to JuMP and paid through the NumFOCUS account.
 * Negotiates and approves contracts between NumFOCUS and external contractors
@@ -104,16 +106,16 @@ annual summit. In addition, the Steering Council:
 
 The current members of the Steering Council are:
 
-* Miles Lubin, Google (@mlubin)
-* Juan Pablo Vielma, Google (@juan-pablo-vielma)
-* Joey Huchette, Rice University (@joehuchette)
+* Miles Lubin, _Google_ (@mlubin)
+* Juan Pablo Vielma, _Google_ (@juan-pablo-vielma)
+* Joey Huchette, _Rice University_ (@joehuchette)
 * Oscar Dowson (@odow)
-* Changhyun Kwon, U. South Florida (@chkwon)
+* Changhyun Kwon, _U. South Florida_ (@chkwon)
 
 A member of the Steering Council may leave the council by notifying the Steering
-Council and [core contributors]. The remaining members, in consultation with the
-[core contributors], will invite a member of the community to join in order to
-maintain a quorum of five members.
+Council and [core contributors]. The remaining Steering Council members, in
+consultation with the [core contributors], will invite a member of the community
+to join in order to maintain a quorum of five members.
 
 ## Decision Making Process
 
@@ -128,7 +130,7 @@ decisions require majority approval by [Steering Council] members.
 
 Community members proposing decisions with a financial aspect should contact the
 [Steering Council] directly, or table their proposal as an agenda item for
-discussion on a [monthly developer call](#monthly-developer-call).
+discussion on a [monthly developer call].
 
 ### Non-financial Decisions
 
@@ -139,15 +141,15 @@ are not considered to be [core contributors] for this purpose.
 Code-related decisions, such when a pull request is ready to be accepted and
 merged, should be discussed via the relevant Github issues and pull requests. If
 consensus cannot be achieved, the community member proposing the change may be
-invited by a core contributor to present their proposal at a [monthly developer
-call](#monthly-developer-call) for further discussion and community input.
+invited by a [core contributor](#core-contributors) to present their proposal at
+a [monthly developer call] for further discussion and community input.
 
 Non-code-related decisions, such long-term strategic planning for JuMP, should
 either be discussed in a Github issue, or tabled as an agenda item and discussed
-on a [monthly developer call](#monthly-developer-call).
+on a [monthly developer call].
 
 If consensus on a non-financial decision cannot be achieved, the final decision
-will be made by the [BDFL](#bdfl).
+will be made by the [BDFL](#benevolent-dictator-for-life).
 
 The [Steering Council] can gain addition decision-making power if the [core
 contributors] decide to delegate.
@@ -286,3 +288,4 @@ via the [developer chatroom].
 [core contributors]: #core-contributors
 [repository maintainers]: #repository-maintainers
 [Steering Council]: #steering-council
+[monthly developer call]: #monthly-developer-call

From 10caa6fe8e28c66202e9f68863d0961e11b4c2bd Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Wed, 21 Oct 2020 14:35:13 +1300
Subject: [PATCH 07/14] Council -> Committee

---
 _posts/2020-10-21-governance.md |  4 ++--
 pages/governance.md             | 42 ++++++++++++++++-----------------
 2 files changed, 23 insertions(+), 23 deletions(-)

diff --git a/_posts/2020-10-21-governance.md b/_posts/2020-10-21-governance.md
index 3e84867..bebc22b 100644
--- a/_posts/2020-10-21-governance.md
+++ b/_posts/2020-10-21-governance.md
@@ -18,8 +18,8 @@ The highlights include:
  * Appointing Miles Lubin as our [BDFL](https://en.wikipedia.org/wiki/Benevolent_dictator_for_life).
 
  * Defining entities such as the core contributors, emeritus core contributors,
-   repository maintainers, and the Steering Council, along with their roles, and
-   how membership is determined for each entity.
+   repository maintainers, and the Steering Committee, along with their roles,
+   and how membership is determined for each entity.
 
  * Clarifying our decision-making process, by describing who gets to decide what
    when.
diff --git a/pages/governance.md b/pages/governance.md
index 77b979c..9fae0f0 100644
--- a/pages/governance.md
+++ b/pages/governance.md
@@ -45,7 +45,7 @@ The current core contributors are:
 * Oscar Dowson (@odow)
 
 A new core contributor may be added by consensus of the current core
-contributors and notification to the [Steering Council].
+contributors and notification to the [Steering Committee].
 
 Before becoming a core contributor, it is expected that the community member is
 a [repository maintainer](#repository-maintainers) of several repositories in
@@ -61,7 +61,7 @@ The emeritus core contributors are:
 * Iain Dunning (@iainnz)
 
 A [core contributor](#core-contributors) may choose to switch to emeritus status
-by informing the other [core contributors] and the [Steering Council].
+by informing the other [core contributors] and the [Steering Committee].
 
 ### Repository Maintainers
 
@@ -93,18 +93,18 @@ a 501(c)(3) public charity in the United States. NumFOCUS provides JuMP with
 fiscal, legal, and administrative support to help ensure the health and
 sustainability of the project.
 
-### Steering Council
+### Steering Committee
 
-The Steering Council supports the [core contributors] by representing JuMP in
+The Steering Committee supports the [core contributors] by representing JuMP in
 all interactions with [NumFOCUS](#numfocus), e.g., by attending [NumFOCUS's
 annual summit](https://numfocus.org/blog/numfocus-summit-2019). In addition, the
-Steering Council:
+Steering Committee:
 
 * Approves expenditures related to JuMP and paid through the NumFOCUS account.
 * Negotiates and approves contracts between NumFOCUS and external contractors
   who provide paid work to JuMP.
 
-The current members of the Steering Council are:
+The current members of the Steering Committee are:
 
 * Miles Lubin, _Google_ (@mlubin)
 * Juan Pablo Vielma, _Google_ (@juan-pablo-vielma)
@@ -112,10 +112,10 @@ The current members of the Steering Council are:
 * Oscar Dowson (@odow)
 * Changhyun Kwon, _U. South Florida_ (@chkwon)
 
-A member of the Steering Council may leave the council by notifying the Steering
-Council and [core contributors]. The remaining Steering Council members, in
-consultation with the [core contributors], will invite a member of the community
-to join in order to maintain a quorum of five members.
+A member of the Steering Committee may leave the committee by notifying the
+Steering Committee and [core contributors]. The remaining Steering Committee
+members, in consultation with the [core contributors], will invite a member of
+the community to join in order to maintain a quorum of five members.
 
 ## Decision Making Process
 
@@ -124,12 +124,12 @@ JuMP project.
 
 ### Financial Decisions
 
-All financial decisions are made by the [Steering Council] to ensure any funds
+All financial decisions are made by the [Steering Committee] to ensure any funds
 are spent in a manner that furthers the [mission](#mission) of JuMP. Financial
-decisions require majority approval by [Steering Council] members.
+decisions require majority approval by [Steering Committee] members.
 
 Community members proposing decisions with a financial aspect should contact the
-[Steering Council] directly, or table their proposal as an agenda item for
+[Steering Committee] directly, or table their proposal as an agenda item for
 discussion on a [monthly developer call].
 
 ### Non-financial Decisions
@@ -151,7 +151,7 @@ on a [monthly developer call].
 If consensus on a non-financial decision cannot be achieved, the final decision
 will be made by the [BDFL](#benevolent-dictator-for-life).
 
-The [Steering Council] can gain addition decision-making power if the [core
+The [Steering Committee] can gain addition decision-making power if the [core
 contributors] decide to delegate.
 
 ### Conflict of Interest
@@ -166,10 +166,10 @@ interest include, but are not limited to:
 * Access to proprietary information of their employer that could potentially
   leak into their work with JuMP.
 
-All members of the [Steering Council] shall disclose to the [Steering Council]
-any conflict of interest they may have. Members with a conflict of interest in a
-particular issue may participate in [Steering Council] discussions on that
-issue, but must recuse themselves from voting.
+All members of the [Steering Committee] shall disclose to the [Steering
+Committee] any conflict of interest they may have. Members with a conflict of
+interest in a particular issue may participate in [Steering Committee]
+discussions on that issue, but must recuse themselves from voting.
 
 [Core contributors](#core-contributors) and [repository maintainers] should also
 disclose conflicts of interest with other [core contributors] and step back from
@@ -230,7 +230,7 @@ The current chatroom is the [JuMP-dev Gitter channel](https://gitter.im/JuliaOpt
 
 ### Monthly Developer Call
 
-The [Steering Council] hosts a monthly developer call to discuss JuMP-related
+The [Steering Committee] hosts a monthly developer call to discuss JuMP-related
 business.
 
 The calls are currently scheduled on the fourth Thursday of every month at 14:00
@@ -241,7 +241,7 @@ The invite contains information on how to table agenda items for upcoming calls.
 
 ### JuMP-dev Workshops
 
-The [Steering Council] will periodically choose a Chair to organize a JuMP-dev
+The [Steering Committee] will periodically choose a Chair to organize a JuMP-dev
 workshop.
 
 Previous workshops include [Santiago, 2019](https://jump.dev/meetings/santiago2019/),
@@ -287,5 +287,5 @@ via the [developer chatroom].
 [developer chatroom]: #developer-chatroom
 [core contributors]: #core-contributors
 [repository maintainers]: #repository-maintainers
-[Steering Council]: #steering-council
+[Steering Committee]: #steering-committee
 [monthly developer call]: #monthly-developer-call

From 36a6f4428bde84555198b7d5e427ec3563c422d6 Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Wed, 21 Oct 2020 15:01:14 +1300
Subject: [PATCH 08/14] Fix typos

---
 pages/governance.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/pages/governance.md b/pages/governance.md
index 9fae0f0..4270919 100644
--- a/pages/governance.md
+++ b/pages/governance.md
@@ -144,14 +144,14 @@ consensus cannot be achieved, the community member proposing the change may be
 invited by a [core contributor](#core-contributors) to present their proposal at
 a [monthly developer call] for further discussion and community input.
 
-Non-code-related decisions, such long-term strategic planning for JuMP, should
-either be discussed in a Github issue, or tabled as an agenda item and discussed
-on a [monthly developer call].
+Non-code-related decisions, such as long-term strategic planning for JuMP,
+should either be discussed in a Github issue, or tabled as an agenda item and
+discussed on a [monthly developer call].
 
 If consensus on a non-financial decision cannot be achieved, the final decision
 will be made by the [BDFL](#benevolent-dictator-for-life).
 
-The [Steering Committee] can gain addition decision-making power if the [core
+The [Steering Committee] can gain additional decision-making power if the [core
 contributors] decide to delegate.
 
 ### Conflict of Interest

From ba6e0c5a19dde197e5b8d29d0a7e56759c5f98bb Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Wed, 21 Oct 2020 15:06:44 +1300
Subject: [PATCH 09/14] More typo fixes

---
 pages/governance.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/pages/governance.md b/pages/governance.md
index 4270919..a4e79b3 100644
--- a/pages/governance.md
+++ b/pages/governance.md
@@ -267,12 +267,13 @@ should first add their package to the list of supported solvers in the
 of the JuMP documentation.
 
 Note that when developing a new solver or JuMP-extension, the [core
-contributors] request that you not use "JuMP" in the name without prior consent.
+contributors] request that you do not use "JuMP" in the name without prior
+consent.
 
 Even once a package has matured, the bar for transferring repositories to the
 [JuMP-dev Github organization] is high, and can be summarized by the following:
 
-* The maintainance of the package would be simplified if [core contributors]
+* The maintenance of the package would be simplified if [core contributors]
   have [Admin permission][permissions] to the repository.
 
 Community members wishing to transfer a repository from their personal account

From 4db70349aca92b40760124a5806dcc6e10a42583 Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Wed, 21 Oct 2020 15:13:50 +1300
Subject: [PATCH 10/14] Teak commit access wording

---
 pages/governance.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/governance.md b/pages/governance.md
index a4e79b3..90bca49 100644
--- a/pages/governance.md
+++ b/pages/governance.md
@@ -181,7 +181,7 @@ decisions when conflicts of interests are in play.
 the [JuMP-dev Github organization].
 
 Anyone with commit access to a repository is trusted to use it in a way that is
-consistent with the [non-financial decisions](#non-financial-decisions) process.
+consistent with the [Decision Making Process](#decision-making-process).
 Those with permissions should prefer pull requests over direct pushes, ask for
 feedback on changes if they are not sure there is a consensus, and follow JuMP's
 [style guide](https://jump.dev/JuMP.jl/stable/style/) and development processes.

From 2fa009f7b8e23054c0045904c399f3f763a6257b Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Wed, 21 Oct 2020 15:16:45 +1300
Subject: [PATCH 11/14] Bow to the will of the BDFL

---
 pages/governance.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/governance.md b/pages/governance.md
index 90bca49..626a963 100644
--- a/pages/governance.md
+++ b/pages/governance.md
@@ -29,7 +29,7 @@ their basic role, and how membership of each entity is determined.
 ### Benevolent Dictator For Life
 
 Due to his role in the creation of JuMP, [Miles Lubin](https://github.com/mlubin)
-holds the role of [Benevolent Dictator For Life (BDFL)](https://en.wikipedia.org/wiki/Benevolent_dictator_for_life).
+holds the title of [Benevolent Dictator For Life (BDFL)](https://en.wikipedia.org/wiki/Benevolent_dictator_for_life).
 
 ### Core Contributors
 

From 43d682944b165d556bed68e47bf8cb6ec9284381 Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Fri, 23 Oct 2020 10:41:40 +1300
Subject: [PATCH 12/14] Update mission

---
 pages/governance.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pages/governance.md b/pages/governance.md
index 626a963..a9b2fa6 100644
--- a/pages/governance.md
+++ b/pages/governance.md
@@ -9,8 +9,8 @@ For the purpose of this document, "JuMP" includes all repositories in the
 
 ## Mission
 
-The mission of the JuMP project is to provide a free, open-source, easy-to-use
-and powerful software stack for mathematical optimization.
+The mission of the JuMP project is to provide a free, open-source software stack
+for mathematical optimization based on the JuMP modeling language.
 
 ## Code of Conduct
 

From 9ff589d9805e25b0c696cdd0f1424e76710febbe Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Sat, 24 Oct 2020 09:49:05 +1300
Subject: [PATCH 13/14] Change navigation header

---
 _config.yml | 18 +++++++++++-------
 1 file changed, 11 insertions(+), 7 deletions(-)

diff --git a/_config.yml b/_config.yml
index 1dba913..629294a 100644
--- a/_config.yml
+++ b/_config.yml
@@ -111,12 +111,16 @@ css_inline: false # Will insert all styles into a single <style> block in the <h
 navigation_header:
 - title: Home
   url: /
-- title: Governance
-  url: /pages/governance
-- title: Code
-  url: /pages/code/
 - title: Documentation
   url: https://jump.dev/JuMP.jl/stable/
+- title: Community
+  items:
+  - title: Forum
+    url: https://discourse.julialang.org/c/domain/opt
+  - title: Chatroom
+    url: https://gitter.im/JuliaOpt/jump-dev
+  - title: Ecosystem
+    url: /pages/code/
 - title: Workshops
   items:
    - title: 2020
@@ -127,9 +131,9 @@ navigation_header:
      url: /meetings/bordeaux2018
    - title: 2017
      url: /meetings/mit2017
-- title: Forum
-  url: https://discourse.julialang.org/c/domain/opt
-- title: News
+- title: Governance
+  url: /pages/governance
+- title: Blog
   url: /pages/news/
 
 # TODO

From 39f414fffc2313a598e86bd32a8addd34c83053c Mon Sep 17 00:00:00 2001
From: odow <o.dowson@gmail.com>
Date: Mon, 26 Oct 2020 11:21:32 +1300
Subject: [PATCH 14/14] Remove chatroom from navigation

---
 _config.yml | 2 --
 1 file changed, 2 deletions(-)

diff --git a/_config.yml b/_config.yml
index 629294a..ddf0a59 100644
--- a/_config.yml
+++ b/_config.yml
@@ -117,8 +117,6 @@ navigation_header:
   items:
   - title: Forum
     url: https://discourse.julialang.org/c/domain/opt
-  - title: Chatroom
-    url: https://gitter.im/JuliaOpt/jump-dev
   - title: Ecosystem
     url: /pages/code/
 - title: Workshops