├── README.md
├── CITATION.rst
├── maintenance
    └── data_upload_instructions.md
├── CONTRIBUTING.rst
├── CODE_OF_CONDUCT.md
├── LICENSE
└── governance.md


/README.md:
--------------------------------------------------------------------------------
1 | # SimPEG community
2 | 
3 | This repository containts documents on governance, code of conduct, and contributor guides for SimPEG 
4 | 


--------------------------------------------------------------------------------
/CITATION.rst:
--------------------------------------------------------------------------------
 1 | Citing SimPEG
 2 | -------------
 3 | 
 4 | There is a `paper about SimPEG <http://dx.doi.org/10.1016/j.cageo.2015.09.015>`_, if you use this code, please help our scientific visibility by citing our work!
 5 | 
 6 | 
 7 |     Cockett, R., Kang, S., Heagy, L. J., Pidlisecky, A., & Oldenburg, D. W. (2015). SimPEG: An open source framework for simulation and gradient based parameter estimation in geophysical applications. Computers & Geosciences.
 8 | 
 9 | 
10 | BibTex:
11 | 
12 | .. code::
13 | 
14 |     @article{cockett2015simpeg,
15 |       title={SimPEG: An open source framework for simulation and gradient based parameter estimation in geophysical applications},
16 |       author={Cockett, Rowan and Kang, Seogi and Heagy, Lindsey J and Pidlisecky, Adam and Oldenburg, Douglas W},
17 |       journal={Computers \& Geosciences},
18 |       year={2015},
19 |       publisher={Elsevier}
20 |     }
21 | 
22 | 


--------------------------------------------------------------------------------
/maintenance/data_upload_instructions.md:
--------------------------------------------------------------------------------
 1 | # Upload Tutorial Data for SimPEG
 2 | 
 3 | If you have permission to access the cloud storage repository,
 4 | uploading data and linking to tutorials in documentation is done as follows:
 5 | 
 6 | 1. **Access the google cloud** using the following URL https://console.cloud.google.com/ . If you have access, you should be taken to a Google Cloud Platform landing page.
 7 | 
 8 | 2. **Finding storage bucket:** In the *Resources* panel, selected *Storage*
 9 |    --> From the list of storage locations, select the *simpeg* storage bucket
10 |    --> Within this bucket, go to the *doc-assets* directory
11 |    
12 | 3. **Uploading files:** Drag and drop the file into this directory. We expect that for the most part files are compressed to *tar.gz*
13 | 
14 | 4. **Setting permissions:** For the file you have just uploaded, open the *object overflow menu*. This is the 'three dots' on the right side of the screen for the file.
15 |    --> Go to *Edit permissions*
16 |    --> Click *Add entry* and set *Entity* = Public, *Name* = allUsers and *Access* = Reader for the new entity
17 |    --> Click *SAVE*
18 | 
19 | 5. **URL for download link:** Click *COPY URL* to copy the downloable link to clipboard.
20 | 


--------------------------------------------------------------------------------
/CONTRIBUTING.rst:
--------------------------------------------------------------------------------
 1 | .. _contributing:
 2 | 
 3 | Contributing to SimPEG
 4 | =======================
 5 | 
 6 | First of all, we are glad you are here! We welcome contributions and input
 7 | from the community.
 8 | 
 9 | This document is a set of guidelines for contributing to the repositories
10 | hosted in the `SimPEG <https://github.com/simpeg>`_ organization on GitHub.
11 | These repositories are maintained on a volunteer basis.
12 | 
13 | 
14 | .. _questions:
15 | 
16 | Questions
17 | ---------
18 | 
19 | Please do not create an issue to ask a question. You will get a faster
20 | response by posting on our Discourse discussion forum:
21 | https://simpeg.discourse.group/. If you prefer real-time chat,
22 | you can join our Mattermost Team at
23 | https://mattermost.softwareunderground.org/simpeg.
24 | 
25 | .. _bugs:
26 | 
27 | 
28 | Bugs
29 | ----
30 | 
31 | When reporting an issue, please be as descriptive and provide sufficient
32 | detail to reproduce the error. Whenever possible, if you can include a small
33 | example that produces the error, this will help us resolve issues faster.
34 | 
35 | 
36 | .. _suggesting_enhancements:
37 | 
38 | Suggesting enhancements
39 | -----------------------
40 | 
41 | We welcome ideas for improvements on SimPEG! When writing an issue to suggest
42 | an improvement, please
43 | 
44 | - use a descriptive title,
45 | - explain where the gap in current functionality is,
46 | - include a pseudocode sketch of the intended functionality
47 | 
48 | We will use the issue as a place to discuss and provide feedback. Please
49 | remember that SimPEG is maintained on a volunteer basis. If you suggest an
50 | enhancement, we certainly appreciate if you are also willing to take action
51 | and start a pull request!
52 | 
53 | 
54 | .. _contributing_new_code:
55 | 
56 | Contributing new code
57 | ---------------------
58 | 
59 | If you have an idea for how to improve SimPEG, please first create an issue
60 | and :ref:`suggest an enhancement <suggesting_enhancements>`. We will use the
61 | issue as a place to discuss and make decisions on the suggestion. Once you are
62 | ready to take action and commit some code to SimPEG, please check out
63 | :ref:`Getting Started for Developers <getting_started_developers>` for
64 | tips on setting up a development environment and :ref:`Practices <practices>`
65 | for a description of the development practices we aim to follow. In particular,
66 | 
67 | - :ref:`testing <testing>`
68 | - :ref:`documentation <documentation>`
69 | - :ref:`code style <style>`
70 | 
71 | are aspects we look for in all pull requests. We do code reviews on pull
72 | requests, with the aim of promoting best practices and ensuring that new
73 | contributions can be built upon by the SimPEG community.
74 | 
75 | 
76 | Licensing
77 | *********
78 | 
79 | The contributed code will be licensed under SimPEG's license
80 | (https://github.com/simpeg/simpeg/blob/master/LICENSE). If you did not write
81 | the code yourself, it is your responsibility to ensure that the existing
82 | license is compatible and included in the contributed files or you can obtain
83 | permission from the original author to relicense the code.
84 | 
85 | 
86 | 
87 | 
88 | 
89 | 


--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
 1 | # Contributor Covenant Code of Conduct
 2 | 
 3 | ## Our Pledge
 4 | 
 5 | In the interest of fostering an open and welcoming environment, we as
 6 | contributors and maintainers pledge to making participation in our project and
 7 | our community a harassment-free experience for everyone, regardless of age, body
 8 | size, disability, ethnicity, sex characteristics, gender identity and expression,
 9 | level of experience, education, socio-economic status, nationality, personal
10 | appearance, race, religion, or sexual identity and orientation.
11 | 
12 | ## Our Standards
13 | 
14 | Examples of behavior that contributes to creating a positive environment
15 | include:
16 | 
17 | * Using welcoming and inclusive language
18 | * Being respectful of differing viewpoints and experiences
19 | * Gracefully accepting constructive criticism
20 | * Focusing on what is best for the community
21 | * Showing empathy towards other community members
22 | 
23 | Examples of unacceptable behavior by participants include:
24 | 
25 | * The use of sexualized language or imagery and unwelcome sexual attention or
26 |  advances
27 | * Trolling, insulting/derogatory comments, and personal or political attacks
28 | * Public or private harassment
29 | * Publishing others' private information, such as a physical or electronic
30 |  address, without explicit permission
31 | * Other conduct which could reasonably be considered inappropriate in a
32 |  professional setting
33 | 
34 | ## Our Responsibilities
35 | 
36 | Project maintainers are responsible for clarifying the standards of acceptable
37 | behavior and are expected to take appropriate and fair corrective action in
38 | response to any instances of unacceptable behavior.
39 | 
40 | Project maintainers have the right and responsibility to remove, edit, or
41 | reject comments, commits, code, wiki edits, issues, and other contributions
42 | that are not aligned to this Code of Conduct, or to ban temporarily or
43 | permanently any contributor for other behaviors that they deem inappropriate,
44 | threatening, offensive, or harmful.
45 | 
46 | ## Scope
47 | 
48 | This Code of Conduct applies both within project spaces and in public spaces
49 | when an individual is representing the project or its community. Examples of
50 | representing a project or community include using an official project e-mail
51 | address, posting via an official social media account, or acting as an appointed
52 | representative at an online or offline event. Representation of a project may be
53 | further defined and clarified by project maintainers.
54 | 
55 | ## Enforcement
56 | 
57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
58 | reported by contacting the project team at conduct@simpeg.xyz; this email is 
59 | accessible by [@lheagy](https://github.com/lheagy) and [@rowanc1](https://github.com/rowanc1). 
60 | All complaints will be reviewed and investigated 
61 | and will result in a response that is deemed necessary and appropriate to the 
62 | circumstances. The project team is obligated to maintain confidentiality with regard 
63 | to the reporter of an incident. Further details of specific enforcement policies may 
64 | be posted separately.
65 | 
66 | Project maintainers who do not follow or enforce the Code of Conduct in good
67 | faith may face temporary or permanent repercussions as determined by other
68 | members of the project's leadership.
69 | 
70 | ## Attribution
71 | 
72 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
73 | available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
74 | 
75 | [homepage]: https://www.contributor-covenant.org
76 | 
77 | For answers to common questions about this code of conduct, see
78 | https://www.contributor-covenant.org/faq
79 | 


--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
  1 | # Creative Commons CC0 License
  2 | 
  3 | ## Statement of Purpose
  4 | The laws of most jurisdictions throughout the world
  5 | automatically confer exclusive Copyright and Related Rights
  6 | (defined below) upon the creator and subsequent owner(s) (each
  7 | and all, an "owner") of an original work of authorship and/or
  8 | a database (each, a "Work").
  9 | 
 10 | Certain owners wish to permanently relinquish those rights
 11 | to a Work for the purpose of contributing to a commons of
 12 | creative, cultural and scientific works ("Commons") that the
 13 | public can reliably and without fear of later claims of
 14 | infringement build upon, modify, incorporate in other works,
 15 | reuse and redistribute as freely as possible in any form
 16 | whatsoever and for any purposes, including without limitation
 17 | commercial purposes. These owners may contribute to the
 18 | Commons to promote the ideal of a free culture and the further
 19 | production of creative, cultural and scientific works, or to
 20 | gain reputation or greater distribution for their Work in part
 21 | through the use and efforts of others.
 22 | 
 23 | For these and/or other purposes and motivations, and
 24 | without any expectation of additional consideration or
 25 | compensation, the person associating CC0 with a Work (the
 26 | "Affirmer"), to the extent that he or she is an owner of
 27 | Copyright and Related Rights in the Work, voluntarily elects
 28 | to apply CC0 to the Work and publicly distribute the Work
 29 | under its terms, with knowledge of his or her Copyright and
 30 | Related Rights in the Work and the meaning and intended legal
 31 | effect of CC0 on those rights.
 32 | 
 33 | **1. Copyright and Related Rights.**
 34 | A Work made available under CC0 may be protected by
 35 | copyright and related or neighboring rights ("Copyright and
 36 | Related Rights"). Copyright and Related Rights include, but
 37 | are not limited to, the following:
 38 | 
 39 | 
 40 | 1. the right to reproduce, adapt, distribute, perform,
 41 | display, communicate, and translate a Work;
 42 | 2. moral rights retained by the original author(s) and/or
 43 | performer(s);
 44 | 3. publicity and privacy rights pertaining to a person's
 45 | image or likeness depicted in a Work;
 46 | 4. rights protecting against unfair competition in regards
 47 | to a Work, subject to the limitations in paragraph 4(a),
 48 | below;
 49 | 5. rights protecting the extraction, dissemination, use and
 50 | reuse of data in a Work;
 51 | 6. database rights (such as those arising under Directive
 52 | 96/9/EC of the European Parliament and of the Council of 11
 53 | March 1996 on the legal protection of databases, and under
 54 | any national implementation thereof, including any amended
 55 | or successor version of such directive); and
 56 | 7. other similar, equivalent or corresponding rights
 57 | throughout the world based on applicable law or treaty, and
 58 | any national implementations thereof.
 59 | 
 60 | **2. Waiver.** To the greatest extent
 61 | permitted by, but not in contravention of, applicable law,
 62 | Affirmer hereby overtly, fully, permanently, irrevocably and
 63 | unconditionally waives, abandons, and surrenders all of
 64 | Affirmer's Copyright and Related Rights and associated claims
 65 | and causes of action, whether now known or unknown (including
 66 | existing as well as future claims and causes of action), in
 67 | the Work (i) in all territories worldwide, (ii) for the
 68 | maximum duration provided by applicable law or treaty
 69 | (including future time extensions), (iii) in any current or
 70 | future medium and for any number of copies, and (iv) for any
 71 | purpose whatsoever, including without limitation commercial,
 72 | advertising or promotional purposes (the "Waiver"). Affirmer
 73 | makes the Waiver for the benefit of each member of the public
 74 | at large and to the detriment of Affirmer's heirs and
 75 | successors, fully intending that such Waiver shall not be
 76 | subject to revocation, rescission, cancellation, termination,
 77 | or any other legal or equitable action to disrupt the quiet
 78 | enjoyment of the Work by the public as contemplated by
 79 | Affirmer's express Statement of Purpose.
 80 | 
 81 | **3. Public License Fallback.** Should any
 82 | part of the Waiver for any reason be judged legally invalid or
 83 | ineffective under applicable law, then the Waiver shall be
 84 | preserved to the maximum extent permitted taking into account
 85 | Affirmer's express Statement of Purpose. In addition, to the
 86 | extent the Waiver is so judged Affirmer hereby grants to each
 87 | affected person a royalty-free, non transferable, non
 88 | sublicensable, non exclusive, irrevocable and unconditional
 89 | license to exercise Affirmer's Copyright and Related Rights
 90 | in the Work (i) in all territories worldwide, (ii) for the
 91 | maximum duration provided by applicable law or treaty
 92 | (including future time extensions), (iii) in any current or
 93 | future medium and for any number of copies, and (iv) for any
 94 | purpose whatsoever, including without limitation commercial,
 95 | advertising or promotional purposes (the "License"). The
 96 | License shall be deemed effective as of the date CC0 was
 97 | applied by Affirmer to the Work. Should any part of the
 98 | License for any reason be judged legally invalid or
 99 | ineffective under applicable law, such partial invalidity or
100 | ineffectiveness shall not invalidate the remainder of the
101 | License, and in such case Affirmer hereby affirms that he or
102 | she will not (i) exercise any of his or her remaining
103 | Copyright and Related Rights in the Work or (ii) assert any
104 | associated claims and causes of action with respect to the
105 | Work, in either case contrary to Affirmer's express Statement
106 | of Purpose.
107 | 
108 | **4. Limitations and Disclaimers.**
109 | 
110 | 1. No trademark or patent rights held by Affirmer are
111 | waived, abandoned, surrendered, licensed or otherwise
112 | affected by this document.
113 | 2. Affirmer offers the Work as-is and makes no
114 | representations or warranties of any kind concerning the
115 | Work, express, implied, statutory or otherwise, including
116 | without limitation warranties of title, merchantability,
117 | fitness for a particular purpose, non infringement, or the
118 | absence of latent or other defects, accuracy, or the present
119 | or absence of errors, whether or not discoverable, all to
120 | the greatest extent permissible under applicable law.
121 | 3. Affirmer disclaims responsibility for clearing rights of
122 | other persons that may apply to the Work or any use thereof,
123 | including without limitation any person's Copyright and
124 | Related Rights in the Work. Further, Affirmer disclaims
125 | responsibility for obtaining any necessary consents,
126 | permissions or other rights required for any use of the
127 | Work.
128 | 4. Affirmer understands and acknowledges that Creative
129 | Commons is not a party to this document and has no duty or
130 | obligation with respect to this CC0 or use of the Work.
131 | 


--------------------------------------------------------------------------------
/governance.md:
--------------------------------------------------------------------------------
  1 | # SimPEG Project Governance
  2 | 
  3 | The purpose of this document is to formalize the governance process used in both ordinary and extraordinary situations. It is also meant to clarify how decisions are made. 
  4 | 
  5 | ## The Project
  6 | 
  7 | The SimPEG Project (The Project) is a community-driven project that develops and maintains open-source software for simulations and inversions of geophysical data. Software repositories include those in the [SimPEG github organization](https://github.com/simpeg). They are developed openly and hosted on public repositories. Software developed by The Project is released under the MIT (or similar) open source license. 
  8 | 
  9 | The Project is developed by a team of distributed developers, called Contributors. Contributors are individuals who have contributed code, documentation, designs, examples, or other work to The Project, including answering questions and participating on discussion forums. Anyone can be a Contributor. Contributors can be affiliated with any legal entity or none. Contributors participate in the project by submitting, reviewing, and discussing GitHub Pull Requests and Issues and participating in open and public Project discussions on GitHub, discussion forums, and other channels. 
 10 | 
 11 | The Project Community consists of all Contributors and Users of The Project. Contributors work on behalf of and are responsible to the larger Project Community and we strive to keep the barrier between Contributors and Users as low as possible.
 12 | 
 13 | The Project is not a legal entity, nor does it currently have any formal relationships with legal entities.
 14 | 
 15 | ## Governance 
 16 | 
 17 | This section describes the governance and leadership model of The Project.
 18 | 
 19 | The Project roles are:
 20 | - Founders
 21 | - BDFL
 22 | - Maintainers
 23 | - Owners
 24 | - Community
 25 | 
 26 | ### Founders 
 27 | The project founders are the people who started SimPEG. They hold no special authority in The Project, other than if a successor to the BDFL is not able to be appointed. They are consulted on decisions concerning project leadership, governance, and vision. The project founders are:
 28 | - Rowan Cockett ([@rowanc1](https://github.com/rowanc1))
 29 | - Lindsey Heagy ([@lheagy](https://github.com/lheagy))
 30 | - Seogi Kang ([@sgkang](https://github.com/sgkang))
 31 | 
 32 | ### Benevolent Dictator for Life (BDFL)
 33 | 
 34 | This person is responsible for planning, organization, and direction of the organization's operations and programs. There is an expectation that this person invests efforts in community & organizational strategy as well as in working with the community to develop and act on the long-term vision of the project.
 35 | 
 36 | The role of a BDFL (Benevolent Dictator for Life) is common in other open-source projects. As Dictator, they, have the authority to make all final decisions for The Project. As Benevolent, they, in practice, chooses to defer that authority to the consensus of the community discussion channels (see below). It is expected, and in the past has been the case, that the BDFL will only rarely assert their final authority. Because rarely used, we refer to the BDFL’s final authority as a “special” or “overriding” vote. When it does occur, the BDFL override typically happens in situations where there is a deadlock in building concensus among the Community. The Project encourages others to fork the project if they disagree with the overall direction the BDFL is taking. The BDFL may delegate their authority on a particular decision or set of decisions to any other Contributor at their discretion.
 37 | 
 38 | The BDFL can appoint their successor, but it is expected that the Community (through the community discussion channels) would be consulted on this decision. If the BDFL is unable to appoint a successor, the Founding Team will make this decision - preferably by consensus, but if needed, by a majority vote.
 39 | 
 40 | Note that the BDFL can step down at any time, and acting in good faith, will also listen to serious calls to do so. 
 41 | 
 42 | The current BDFL is 
 43 | - Lindsey Heagy ([@lheagy](https://github.com/lheagy))
 44 | 
 45 | 
 46 | ### Maintainers
 47 | 
 48 | Maintainers help facilitate pull request reviews, triaging of issues, and software releases. Note that this doesn’t mean that they have to do all of the Pull Request Reviews and Releases; they can delegate or request involvement from other Project Contributors. Maintainers are included in the [Admin Team](https://github.com/orgs/simpeg/teams/simpeg-admins) on GitHub. They have administrative rights on all repositories in the SimPEG GitHub organization. They also have admin rights on PyPI and Conda Forge. 
 49 | 
 50 | Maintainers are appointed by the BDFL, in consultation with current maintainers and project Founders.
 51 | 
 52 | These people are “Maintainers” in the SimPEG GitHub organization: 
 53 | - Joseph Capriotti ([@jcapriot](https://github.com/jcapriot))
 54 | - Santiago Soler ([@santisoler](https://github.com/santisoler))
 55 | 
 56 | ### Owners
 57 | Owners have the permissions as outlined in the [GitHub docs](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners). To ensure continuity of ownership, as a project, we will always have a minimum of 2 owners, with one being the BDFL. 
 58 | 
 59 | These people are the “Owners” of the SimPEG GitHub organization: 
 60 | - Rowan Cockett ([@rowanc1](https://github.com/rowanc1))
 61 | - Lindsey Heagy ([@lheagy](https://github.com/lheagy))
 62 | 
 63 | ### Community Discussion Channels 
 64 | 
 65 | Conversation and consensus building are an important part of SimPEG governance, and thus here, we specify the main communication channels used by The Project. 
 66 | - The [SimPEG Mattermost Team][mattermost] is the main place for day-to-day communication and chat. This is where meeting links are circulated, and development discussions prompted.
 67 | - Meetings are held weekly. The video-conferencing link is circulated in the #meetings channel on Mattermost prior to the meeting. All meetings are recorded and available on [youtube](https://www.youtube.com/playlist?list=PLd9tNwsUm9jOagLQEnxdeIPE4L4bx5Ujg)
 68 | - [Discourse](https://simpeg.discourse.group/) is used as a forum for asking and answering questions among the community. 
 69 | 
 70 | ### Institutional Partners
 71 | 
 72 | Multiple stakeholders from academia, industry, and non-profit sectors participate in The Project as contributors and community members. No outside institution, individual, or legal entity has the ability to own, control, usurp, or influence the project other than by participating in The Project as Contributors. However, because institutions can be an important funding mechanism for The Project and people who contribute to it, it is important to formally acknowledge institutional participation in the project. These are Institutional Partners.
 73 | 
 74 | An Institutional Contributor is any individual Project Contributor who contributes to the project as part of their official duties at an Institutional. An Institutional Partner is any recognized legal entity in any country that employs at least 1 Institutional Contributor. Institutional Partners can be for-profit or non-profit entities.
 75 | 
 76 | Institutions become eligible to become an Institutional Partner by employing individuals who actively contribute to The Project as part of their official duties. To state this another way, the only way for a Partner to influence the project is by actively contributing to the open development of The Project, in equal terms to any other member of the community of Contributors. Merely using Project Software in institutional context does not allow an entity to become an Institutional Partner. Financial gifts do not enable an entity to become an Institutional Partner. However, they can be acknowledged on The Project website. Once an institution becomes eligible for Institutional Partnership, any Contributor can nominate them; nominations are approved by the BDFL.
 77 | 
 78 | If, at some point, an existing Institutional Partner stops having any contributing employees, then a one year grace period commences. If, at the end of this one-year period, they continue not to have any contributing employees, then their Institutional Partnership will lapse, and resuming it will require going through the normal process for new Partnerships.
 79 | 
 80 | An Institutional Partner is free to pursue funding for their work on The Project through any legal means. This could involve a non-profit organization raising money from private foundations and donors or a for-profit company building proprietary products and services that leverage Project Software and Services. Funding acquired by Institutional Partners to work on The Project is called Institutional Funding. However, no funding obtained by an Institutional Partner can override the BDFL. If a Partner has funding to do SimPEG work and the Community and BDFL decides to not pursue that work as a project, the Partner is free to pursue it on their own. However, in this situation, that part of the Partner’s work will not be under the SimPEG umbrella and cannot use The Project trademarks in any way that suggests a formal relationship.
 81 | 
 82 | Institutional Partner benefits are:
 83 | - acknowledgement on the SimPEG website and in talks
 84 | - ability to acknowledge their own funding sources on the SimPEG website and in talks
 85 | - ability to influence the project through the participation
 86 | - invitation of the Council Members to SimPEG Developer Meetings
 87 | 
 88 | A list of current Institutional Partners is maintained at TODO.
 89 | 
 90 | ### Changes to Governance
 91 | 
 92 | The authority to change the governance model is held by the BDFL, but any changes to the governance model will be done in a consensus building process between the BDFL, Maintainers and the Community. 
 93 | 
 94 | Suggestions to governance processes can always be raised in the interm at weekly meetings, in the `~governance` channel on [Mattermost][mattermost], or directly to the BDFL. 
 95 | 
 96 | ## Document History
 97 | 
 98 | - 2024 Mar 20: update governance to retire "Director" titles in favour of Maintainers (replacing the "Director of Operations") and a BDFL (replacing the "Managing Director"). This brings SimPEG more in line with BDFL language used by other projects. Changes were made in https://github.com/simpeg/community/pull/18.
 99 | - 2021 Apr 5: SimPEG governance suggested next steps [doc](https://docs.google.com/document/d/1Y8FZjDGZFC0dJveh-JNRuCXkOrtbrSFpZ55xi5VXDQ4/edit#), [video recording](https://youtu.be/EeoqqxmBGf0)
100 | - 2020 Dec 10: Governance sketch [doc](https://docs.google.com/document/d/1O9jiYvKClRvV0tcrQOA5PgEoTZ4e-gvAut2sgYM_-ho/edit#), [video recording](https://youtu.be/oLUHdmpbHNI)
101 | 
102 | ## Acknowledgement
103 | 
104 | Substantial portions of this document were adapted from the [Jupyter/IPython project governance document](https://github.com/jupyter/governance/blob/master/governance.md), the [NumPy governance document](https://github.com/numpy/numpy/blob/master/doc/source/dev/governance/governance.rst) and the [SciPy governance document](https://docs.scipy.org/doc/scipy/reference/dev/governance/governance.html). 
105 | 
106 | ## License 
107 | 
108 | To the extent possible under law, the authors have waived all copyright and related or neighboring rights to the SimPEG project governance document, as per the [CC-0 public domain dedication / license](https://creativecommons.org/publicdomain/zero/1.0/).
109 | 
110 | 
111 | [mattermost]: https://mattermost.softwareunderground.org/simpeg
112 | 


--------------------------------------------------------------------------------