Skip to content

Commit 7cb34a1

Browse files
committed
deploy: beab7a9
0 parents  commit 7cb34a1

135 files changed

Lines changed: 37725 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.nojekyll

Whitespace-only changes.

_images/AWSSubAccountCreation.png

127 KB
Loading

_images/google_group_creation.png

170 KB
Loading

_sources/charter.rst.txt

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
*****************
2+
Committee Charter
3+
*****************
4+
5+
The Infrastructure Committee is established under Article 5, Sections 1-2 of the NumFOCUS Bylaws.
6+
It is overseen by the Technical Steering Committee.
7+
8+
Purpose
9+
=======
10+
11+
To assist NumFOCUS in facilitating the Fiscal Sponsorship and Affiliation program by overseeing the technical aspects of digital infrastructure available to our Projects.
12+
Digital infrastructure includes but is not limited to:
13+
14+
- Cloud accounts and credits
15+
- Domain registrations and hosting
16+
- Conference management software
17+
- CI/CD documentation and best practices
18+
19+
Mission
20+
=======
21+
22+
The Infrastructure Committee will manage project digital infrastructure in a way that is fair, equitable, and supports long-term sustainability and project development.
23+
24+
The Committee will:
25+
26+
- Advise NF staff infrastructure team on how to administer account credentials and access
27+
- Make ongoing recommendations to improve and enhance available infrastructure
28+
- Act as a liaison between sponsored projects and the NF Infrastructure Staff, (who works with vendors)
29+
- Have a representative at monthly project meetings
30+
- Triage new request, e.g., is a request a common need or one off?
31+
- Present best practices from various projects
32+
- Review its charter annually and recommend changes to the board for review
33+
34+
Duration/Type of Committee
35+
==========================
36+
37+
The committee will be a standing committee.
38+
39+
Committee Composition
40+
---------------------
41+
42+
Membership
43+
^^^^^^^^^^
44+
45+
Membership will reflect the NumFOCUS Diversity Statement by welcoming and encouraging participation by people of all backgrounds and identities and promoting and sustaining a culture that values mutual respect, acceptance, and learning.
46+
47+
The committee will consist of at least 5 members from NumFOCUS at-large community, with the following constraints:
48+
49+
- 1 member is a project contributor to a NumFOCUS sponsored project
50+
- No more than 2 members are related in employment or NumFOCUS project leadership committee
51+
- 1 member is a NumFOCUS Staff member
52+
53+
Officers
54+
^^^^^^^^
55+
56+
The Vice President will call for scheduled meetings, determine the agenda for meetings, and chair the meetings.
57+
The Secretary will record all meeting minutes and submit quarterly reports to the board of directors.
58+
59+
Selection
60+
^^^^^^^^^
61+
62+
Members will be selected by the committee's officers or current members using a rating system.
63+
The Vice President may be selected by the board of directors or elected annually by the members of the committee.
64+
The secretary will be elected by the committee's members.
65+
66+
Terms
67+
^^^^^
68+
69+
Committee members will serve a two-year term, at which time they will have the option for unlimited renewals.
70+
The Vice President will serve a two-year term with the option to renew for one additional term.
71+
The Secretary will serve a two-year term with the option to renew for one additional term.
72+
73+
Meetings
74+
========
75+
76+
The committee will meet at least once every two months.
77+
A majority of the committee members shall constitute a quorum.
78+
79+
Record Keeping and Reporting
80+
============================
81+
82+
All committee records will be kept in https://github.com/numfocus/infrastructure
83+
84+
A annual report on the state of project digital infrastructure including all committee actions will be submitted to the board of directors before the 15th of January.

_sources/ci_cd_guide/index.rst.txt

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
****************
2+
Paying for CI/CD
3+
****************
4+
5+
This guide is intended to help projects get their CI/CD paid for by NumFOCUS.
6+
7+
**WIP**
8+
9+
.. toctree::
10+
:maxdepth: 1
11+
:caption: Contents
12+
:glob:

_sources/index.rst.txt

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
*********************************
2+
NumFOCUS Infrastructure Committee
3+
*********************************
4+
5+
This site details the activities and governance of the NumFOCUS Infrastructure Committee.
6+
7+
The Committee is "responsible for managing project digital infrastructure in a way that is fair, equitable, and supports long-term sustainability and project development."
8+
9+
We also advice the NumFOCUS staff on infrastructure-related matters.
10+
11+
.. toctree::
12+
:maxdepth: 1
13+
:caption: Contents
14+
15+
charter
16+
membership
17+
meeting_notes/index
18+
review_process
19+
ci_cd_guide/index
20+
projects/index
21+
vendors/index
Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
************
2+
Oct 23, 2023
3+
************
4+
5+
* Attendees
6+
7+
- Andy Terrel, Irfan Alibay, Nabil Freij
8+
9+
* Observing
10+
11+
- Nicole Foster, Matt Moore
12+
13+
* Apologies
14+
15+
- Katrina Riehl
16+
17+
Agenda
18+
======
19+
20+
* Intros
21+
* Charter
22+
* Audit Docs
23+
24+
Notes
25+
=====
26+
27+
Introductions
28+
29+
Matt contracted to do devops types of work at NF.
30+
31+
Charter
32+
-------
33+
34+
Changes to the charter needed:
35+
36+
- Need to change the people (add Andy & Nabil & Katrina)
37+
- Elect a Vice President and Secretary
38+
- Do a proposal for positions & send through to everyone
39+
- Current proposal: Andy as VP and Nabil as Secretary
40+
41+
Proposal
42+
--------
43+
44+
Proposal for changing the charter.
45+
The original charter includes
46+
47+
1. Administer infrastructure account credentials and access;
48+
2. Make ongoing recommendations and execute changes to improve and enhance available infrastructure
49+
3. Act as a liaison between the infrastructure vendors and sponsored projects and
50+
4. Review its charter annually and recommend changes to the board for review
51+
52+
New wording
53+
54+
1. Advise NF staff infrastructure team on how to administer account credentials and access
55+
2. Make ongoing recommendations to improve and enhance available infrastructure
56+
3. Act as a liaison between sponsored projects between the NF Infrastructure Staff, (who works with vendors) and have a representative at monthly project meetings, triage new request, e.g., is a request a common need or one off.
57+
Present best practices from various projects etc
58+
4. Review its charter annually and recommend changes to the board for review
59+
60+
Proposed by Andy, Second by Irfan, approved unanimously.
61+
62+
Where to document best practices?
63+
64+
Proposal: github.com/numfocus/infrastructure
65+
66+
Make a sphinx base webpage to be hosted via (GitHub pages)
67+
68+
No vote needed
69+
70+
Audit
71+
-----
72+
73+
Andy and Matt to go through audit to see what is running
74+
75+
Nabil to start the documentation going.
76+
Committee to review in Nov meeting.
77+
78+
Where to publish notes:
79+
GitHub documentation pages that Nabil is setting up.
80+
Redact names of projects if sensitive before pushing to GitHub.
81+
82+
Action items
83+
============
84+
85+
- Andy Terrel to draft new charter based on vote above, send out to Mridul and Katrina for e-vote
86+
- Nabil Freij make documentation mvp
87+
- Andy Terrel and Matt Moore to go through infrastructure inventory
88+
- Nicole Foster Send out meeting invite
89+
- Nicole Foster to upgrade Nabil Freij's slack account to add to infrastructure
Lines changed: 99 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,99 @@
1+
************
2+
Nov 15, 2023
3+
************
4+
5+
* Attendees
6+
7+
- Andy Terrel, Irfan Alibay, Nabil Freij
8+
9+
* Observing
10+
11+
- Nicole Foster, Arliss Collins
12+
13+
* Apologies
14+
15+
- Katrina Riehl, Matt Moore, Mridul Seth
16+
17+
Notes
18+
=====
19+
20+
Approval of last month's minutes
21+
--------------------------------
22+
23+
Pending Actions:
24+
25+
Andy Terrel and Matt Moore to go through infrastructure inventory
26+
E-vote on the new charter with Katrina and Mridul
27+
Approved unanimously
28+
29+
New Charter
30+
-----------
31+
32+
https://docs.google.com/document/d/1hzaB_DAGAUdKnfI_x0ktcO6Zf1iP1Er1BtWrpo35LNM/edit
33+
Still need to talk to Katrina and Mridul
34+
35+
Docs Deploy
36+
-----------
37+
38+
https://github.com/numfocus/infrastructure/pull/18/
39+
Merge approved so we can render
40+
41+
To do
42+
43+
- Need to get a NF deploy key
44+
- Folks should review rendered version: https://numfocus.github.io/infrastructure/ (PR needs to be merged for the render to update, right now it's blank)
45+
46+
Project Infrastructure Involvement
47+
----------------------------------
48+
49+
How do projects fund infrastructure?
50+
51+
MDAnalysis had an SDG rejection, for a funding requested access to paid CI resources (macos-arm64 runners and large core count runners).
52+
The response for the paid CI part of the grant was "SDG funds are not typically granted for ongoing expenses where projects will have to come back next year".
53+
This isn't the first time this has happened (
54+
At the NF Project meeting many projects requested CI/CD resources (osx-arm64, gpus, window-arm)
55+
There is no guidance within NF as to what projects are meant to do about this - we're effectively left with a "not our problem" response without really being told whose problem it is.
56+
The SDG committee had clearly signposted this problem to us, that way we had a formal request from someone, rather than finding out through second hand feedback.
57+
58+
Does on-going funds on-going infrastructure?
59+
60+
No. We should recommend updates to the application process
61+
SDG should share infrastructure requests (summarized version) that were rejected.
62+
63+
NF Infrastructure Budget
64+
-------------------------
65+
66+
NF Infra should make a Budget Request to the Board of Directors
67+
We can campaign for funds from the general NF budget, project budgets, or raise specific funds for Infrastructure
68+
Get projects to use issues on the infra repo to document their needs.
69+
Advertise it to the projects.
70+
GPU CI/CD
71+
Pinged a lot from many projects
72+
Github Actions
73+
Private beta starting now for paid accounts but public beta in a few months. They need help justifying the use of Azure GPU machines for CI/CD purposes
74+
75+
Recommend we write a letter on how impactful GPU Hosted Runners will be to our projects
76+
Use case
77+
Projects
78+
Scikit-learn - Arlliss has already talked to Adrin about providing this.
79+
Cupy
80+
dask
81+
Reach out to other organizations
82+
OpenMM & OMSF - @irfan
83+
Linux foundation?
84+
CSS?
85+
Impact to the community
86+
Quansight GPU Cluster
87+
Iterate on their terms of service
88+
89+
Next meeting time: December 20th, 10:30 CT
90+
91+
Action items
92+
============
93+
94+
- Get requests from SDG - Nicole Foster
95+
- Add template for infrastructure request - Andy Terrel
96+
- Reach out how to onboard our projects - Andy Terrel
97+
- Add infrastructure to agenda for project bimonthly meeting - Arliss Collins
98+
- Set up a mock budget for December submission
99+
- Nicole Foster to add existing ongoing costs
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
************
2+
Dec 12, 2023
3+
************
4+
5+
* Attendees
6+
7+
- Irfan Alibay Nabil Freij
8+
9+
* Observing
10+
11+
- Nicole Foster
12+
13+
* Apologies
14+
15+
- Arliss Collins, Andy Terrel, Mridul Seth, Matt Moore, Katrina Riehl
16+
17+
Notes
18+
=====
19+
20+
SDG Infrastructure - Proposals 2022 & 2023, it lacks information if any of the projects were funded or not.
21+
22+
Infrastructure requests
23+
-----------------------
24+
25+
How involved should the committee be?
26+
27+
Review process for issues.
28+
Committee could do that.
29+
Can the committee help us decide what we should and should not support?
30+
In the past NF has agreed to support requests that aren't directly related to NF projects but as we scale, we may not have enough bandwidth.
31+
32+
Action items
33+
============
34+
35+
- Set up a mock budget for January submission (breakdown by project, select as many infrastructure projects) - Nicole Foster
36+
- Create a draft document about a system for reviewing and responding to project requests - Nabil Freij
37+
- Add information about which SDGs were funded - Nicole Foster
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
************
2+
Jan 23, 2024
3+
************
4+
5+
* Attendees
6+
7+
- Nabil Freij, Andy Terrel
8+
9+
* Observing
10+
11+
- Arliss Collins, Nicole Foster, Matt Moore
12+
13+
* Apologies
14+
15+
- Katrina Riehl, Katrina Riehl, Mridul Seth, Irfan Alibay
16+
17+
Action items
18+
============
19+
20+
- 2024 Proposed Infrastructure Budget- draft
21+
- Can we go through the SDG asks and see what should be added?
22+
- Draft review process document: Managing Infrastructure Requests
23+
- Setup GitHub Actions to process notifications
24+
- Create a review rotation
25+
- Review issues: https://github.com/numfocus/infrastructure/issues/26

0 commit comments

Comments
 (0)