Move to Linux Foundation Charities 501(c)(3) and establish the Jupyter Foundation directed fund as part of Linux Foundation 501(c)(6)

_toc.yml

@@ -6,6 +6,7 @@ parts:
   - file: overview
   - file: executive_council
   - file: software_steering_council
+  - file: jupyter_foundation
   - file: software_subprojects
     sections:
     - file: list_of_subprojects

executive_council.md

@@ -30,7 +30,9 @@ The EC has the responsibility to:
 - Manage the Jupyter brand, including the Project-wide website, core design philosophy, design assets, trademarks, and naming.
 - Manage public communications and community activities, including social media, conferences, workshops, and community-wide resources.
 - Manage any Jupyter services, including hosted services such as nbviewer, jupyter.org, and mybinder.org.
-- Manage the Project’s relationship with NumFOCUS, its parent non-profit organization and fiscal sponsor.
+- Manage the Project’s relationship with [LF Charities](https://lf-charities.org/), which is Project Jupyter's parent nonprofit organization and legal entity. This includes ensuring the Project follows the applicable LF Charities policies.
+- Manage the Project's relationship with the [Linux Foundation](https://www.linuxfoundation.org/), which holds assets in custody for Project Jupyter.
+- Manage the Project's relationship with the [Jupyter Foundation](./jupyter_foundation.md), including serving on the Jupyter Foundation Governing Board.
 - Write an annual stakeholders letter to provide a summary of the previous year’s activities across the community and to highlight the current and future direction of the Project.
 - Mentor potential future EC members. The EC is expected to identify potential future members of the EC and proactively mentor those individuals.
 - Maintain Project-wide documentation and information to enable users to discover and navigate the resources of the Project.

jupyter_foundation.md

@@ -0,0 +1,31 @@
+# Jupyter Foundation
+
+The Jupyter Foundation is a directed fund of the Linux Foundation 501(c)(6) whose purpose is to raise, budget and spend funds in support of Project Jupyter and its mission. A draft of the Jupyter Foundation charter is linked [below](#jupyter-foundation-charter). A brief summary of relevant points from the charter is provided in this document.
+
+
+## Jupyter Foundation Governing Board
+
+The Jupyter Foundation Governing Board controls the resources of the Jupyter Foundation and works to build a healthy collaboration between the Jupyter community, Jupyter leadership, and members of the Jupyter Foundation, including for-profit organizations. The current members of the Jupyter Foundation Governing Board are listed in the [Leadership Directory](people.md#jupyter-foundation-governing-board).
+
+## Responsibilities of the Jupyter Foundation Governing Board
+
+- Support Project Jupyter and its mission.
+- Overall management of the Jupyter Foundation.
+- Approve an annual budget directing the use of Jupyter Foundation funds.
+- Approve changes to the Jupyter Foundation charter.
+
+## Membership
+
+The Jupyter Foundation Governing Board consists of:
+
+- All members of the [Jupyter Executive Council](./executive_council.md).
+- One representative from each Jupyter Foundation Premier Member.
+- Between one and three representatives total from all Jupyter Foundation General Members.
+
+## Decision making
+
+The Jupyter Foundation Governing Board follows the decision-making policies in the Jupyter Foundation charter.
+
+## Jupyter Foundation Charter
+
+A draft (as of July 2, 2024) of the Jupyter Foundation participation agreement, which establishes the relationship with foundation members, is [here](jupyter_foundation_participation_agreement_draft-20240702.pdf). The Jupyter Foundation charter is included as Exhibit B of the participation agreement.

overview.md

@@ -6,10 +6,11 @@ Jupyter transitioned from a [Benevolent Dictator For Life (BDFL) + Steering Coun
 This document provides a brief informational summary of the Project Jupyter governance model. In case of any substantive discrepancy with the official descriptions of each body, the underlying governance documents should be considered as the source of truth, and we will update this overview as needed.
 :::
 
-Jupyter’s governance model is anchored on two bodies that complement each other:
+Jupyter’s governance model is anchored on three bodies that complement each other:
 
 1. The [**Executive Council (EC)**](executive_council.md) is ultimately responsible for all dimensions of the Project (including, but not limited to, software, legal, financial, community, operations, inclusion and diversity, etc.). The members of the EC actively work to carry out the Project's mission in accordance with its values and to support operations through delegation to the Software Steering Council (SSC), Software Subprojects, Standing Committees, and Working Groups. These other bodies will report to the EC, and the EC is expected to support, oversee, manage, and ensure the success of operations across Jupyter. For more detail, see the [Executive Council document](executive_council.md).
 2. The [**Software Steering Council (SSC)**](software_steering_council.md) has jurisdiction over software-related decisions across Project Jupyter, with a primary focus on coordination across projects and decisions that have impact across many Jupyter Subprojects. It is also a mechanism for representatives of each project to share information and expertise. Technical decisions and processes where the SSC isn't explicitly involved are automatically delegated to the individual projects to manage their day-to-day activities, create new repositories in their orgs, etc., with independence and autonomy. For more details, see the [Software Steering Council document](software_steering_council.md).
+3. The [**Jupyter Foundation**](./jupyter_foundation.md) is a directed fund of the Linux Foundation 501(c)(6) that exists to provide resources and strategic counsel to Project Jupyter. The Executive Council serves on the Jupyter Foundation Governing Board. For more details, see the [Jupyter Foundation document](./jupyter_foundation.md).
 
 Additionally, the Executive Council (EC) receives input from a Community Advisory Panel. This panel advises the EC with perspectives and connections that may reach beyond the active Jupyter community.
 

people.md

@@ -8,7 +8,7 @@ Alphabetical by first name, names are followed by GitHub usernames.
 - Afshin Darian, [@afshin](https://github.com/afshin)
 - Ana Ruvalcaba, [@Ruv7](https://github.com/Ruv7)
 - Brian Granger, [@ellisonbg](https://github.com/ellisonbg)
-- Fernando Perez, [@fperez](https://github.com/fperez)
+- Fernando Pérez, [@fperez](https://github.com/fperez)
 - Jason Grout, [@jasongrout](https://github.com/jasongrout)
 - Zach Sailer, [@Zsailer](https://github.com/zsailer)
 
@@ -27,6 +27,18 @@ Alphabetical by first name, names are followed by GitHub usernames.
 | JupyterHub and Binder | Min Ragan-Kelley | [@minrk](https://github.com/minrk) |
 | Voilà | Martin Renou | [@martinRenou](https://github.com/martinRenou) |
 
+## [Jupyter Foundation](jupyter_foundation.md) Governing Board
+
+| Representative | Organization | GitHub username |
+| -------------- | ------------ | --------------- |
+| Afshin Darian | Executive Council | [@afshin](https://github.com/afshin) |
+| Ana Ruvalcaba | Executive Council | [@Ruv7](https://github.com/Ruv7) |
+| Brian Granger | Executive Council | [@ellisonbg](https://github.com/ellisonbg) |
+| Fernando Pérez | Executive Council | [@fperez](https://github.com/fperez) |
+| Jason Grout | Executive Council | [@jasongrout](https://github.com/jasongrout) |
+| Zach Sailer | Executive Council | [@Zsailer](https://github.com/zsailer) |
+
+
 ### Trademark Subcommittee
 
 - Brian Granger, [@ellisonbg](https://github.com/ellisonbg)
@@ -64,7 +76,7 @@ and a Steering Council.
 
 ### Benevolent Dictator for Life (retired December 2022)
 
-Fernando Perez ([@fperez](https://github.com/fperez)) was the Benevolent Dictator for Life (BDFL). He
+Fernando Pérez ([@fperez](https://github.com/fperez)) was the Benevolent Dictator for Life (BDFL). He
 voluntarily relinquished his role after Jupyter transitioned to a new governance model in December 2022.
 
 ### Steering Council (dissolved December 2022)
@@ -74,7 +86,7 @@ voluntarily relinquished his role after Jupyter transitioned to a new governance
 - Brian Granger, [@ellisonbg](https://github.com/ellisonbg) (Founding member, 2014-2022)
 - Carol Willing, [@willingc](https://github.com/willingc) (2017-2022)
 - Damian Avila, [@damianavila](https://github.com/damianavila) (Founding member, 2014-2022)
-- Fernando Perez, [@fperez](https://github.com/fperez) (Founding member, 2014-2022)
+- Fernando Pérez, [@fperez](https://github.com/fperez) (Founding member, 2014-2022)
 - Jason Grout, [@jasongrout](https://github.com/jasongrout) (2015-2022)
 - Jessica Hamrick, [@jhamrick](https://github.com/jhamrick) (2015-2022)
 - Jonathan Frederic, [@jdfreder](https://github.com/jdfreder) (2016-2018)
@@ -91,7 +103,7 @@ voluntarily relinquished his role after Jupyter transitioned to a new governance
 ### NumFOCUS Subcommittee (dissolved December 2022)
 
 - Ana Ruvalcaba, [@Ruv7](https://github.com/Ruv7)
-- Fernando Perez, [@fperez](https://github.com/fperez)
+- Fernando Pérez, [@fperez](https://github.com/fperez)
 - Matthias Bussonnier, [@carreau](https://github.com/carreau)
 - Stefan van der Walt (non-council member), [@stefanv](https://github.com/stefanv)
 - Thomas Kluyver, [@takluyver](https://github.com/takluyver)

trademarks.md

@@ -22,10 +22,9 @@ This document outlines the policy of the Project Jupyter ("Jupyter")
 regarding the use of its trademarks.
 Any use of any Project Jupyter trademark must be in accordance with this policy.
 
-"Jupyter" is a trademark of the NumFOCUS foundation,
-of which Project Jupyter is a part.
+"Jupyter" is a trademark of LF Charities, of which Project Jupyter is a part.
 
-The Jupyter logos (in several variants) are trademarks of NumFOCUS as well.
+The Jupyter logos (in several variants) are trademarks of LF Charities as well.
 
 The Jupyter Trademark is registered with the U.S. Patent & Trademark Office.
 
@@ -36,7 +35,7 @@ such as "JupyterDays," "JupyterLab," "JupyterHub,"
 All trademarks, even those that apply to open source software,
 must be used according to certain legal requirements.
 If these requirements are not met, the trademark may be endangered or lost.
-One of these requirements is for the trademark owner (in this case, NumFOCUS)
+One of these requirements is for the trademark owner (in this case, LF Charities)
 to maintain standards for using its trademarks,
 and to enforce acceptable use of the trademarks by taking action against parties that violate those standards.
 
@@ -56,11 +55,11 @@ Underlying Project Jupyter's trademark policy is a set of guidelines for what is
 -- and is not -- acceptable use of our trademarks,
 specifically the word mark "Jupyter", the Jupyter logos,
 and variations of those marks.
-This policy describes the uses generally approved by Jupyter and NumFOCUS for its trademarks.
+This policy describes the uses generally approved by Jupyter and LF Charities for its trademarks.
 However, if you violate this policy,
 or otherwise take actions that may compromise the reputation or trademarks of Jupyter,
-or expose NumFOCUS to liability,
-NumFOCUS may require you to cease all use of any Jupyter trademark,
+or expose LF Charities to liability,
+LF Charities may require you to cease all use of any Jupyter trademark,
 regardless of the uses allowed in this policy.
 
 
@@ -110,7 +109,7 @@ No explicit approval is needed for these uses as long as
 We understand that not everyone (including ourselves) can afford to give away merchandise
 in sufficient quantities to meet demand.
 Because of this, we would love help from the community in creating an official place to purchase
-Jupyter branded merchandise with the profits going back to the project through NumFOCUS.
+Jupyter branded merchandise with the profits going back to the project through LF Charities.
 
 If you are interested in helping out with this please get in touch with us on
 the [Jupyter Google Group][].
@@ -147,7 +146,7 @@ the following basic guidelines apply to almost any use of Jupyter's trademarks.
 0. If the word "Jupyter" or the Jupyter logos are used in certain contexts,
     the following statement should accompany its use:
 
-    > "Jupyter" and the Jupyter logos are trademarks or registered trademarks of NumFOCUS,
+    > "Jupyter" and the Jupyter logos are trademarks or registered trademarks of LF Charities,
     > used by ___________ with permission.
 
 0. For websites and documentation this can be on a "legal statements" page.