Skip to content

Commit d485a63

Browse files
rcthomasrcthomas
authored
Merge pull request #51 from jupyter/notes-catchup
Notes catchup
2 parents d51abd1 + 2e8c980 commit d485a63

File tree

6 files changed

+128
-0
lines changed

6 files changed

+128
-0
lines changed

‎meetings/2022-08-30.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
# Jupyter Security Bi-weekly Meeting
2+
3+
## August 30, 2022
4+
5+
| Name | affiliation| username |
6+
| -------------------| -----------| -----------------|
7+
| Jason Weill | AWS | @jweill-aws |
8+
| Matthias Bussonnier| QuanSight | @carreau |
9+
| Rollin Thomas | NERSC | @rcthomas |
10+
| Rick Wagner | UCSD | @rpwagner |
11+
| Maxime Jublou | naas.ai | @Dr0p42 |
12+
| Isabela Presedo-Floyd | Quansight Labs | @isabela-pf |
13+
14+
- Bootstrapping official council — Jason W
15+
- See docs: https://github.com/jupyter/governance/blob/master/bootstrapping_decision_making.md
16+
- We should have a list of members provided for Jupyter governance within the next month (see [Google Sheet](https://docs.google.com/spreadsheets/d/1RdqRp1CIM9t-sy8xz9f_tu6BFfmrzwCM663d2p4e99U/edit#gid=1859802494))
17+
- We also need to select one member to represent us at the Software Steering Council (SSC)
18+
- Action item: We will nominate our SSC rep at our next meeting, on Sep 13
19+
- 2FA follow-up (due Oct 1)
20+
- For future, push 2FA outward toward scientific python stack, etc
21+
- Periodic review to ensure it doesn't get disabled, new projects have it turned on
22+
-

‎meetings/2022-09-13.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# Jupyter Security Bi-weekly Meeting
2+
3+
## September 13, 2022
4+
5+
| Name | affiliation| username |
6+
| -------------------| -----------| -----------------|
7+
| Rick Wagner | UCSD | @rpwagner |
8+
| Jason Weill | AWS | @jweill-aws |
9+
| Matthias Bussonnier| QuanSight | @carreau |
10+
| Rollin | NERSC | @rcthomas |
11+
12+
- Security questionnaire
13+
- Establish process for how to answer a security questionnaire from a potential user (e.g., FSRA Ontario)
14+
- Matthias to attend NumFOCUS summit next week; can discuss security questions there
15+
- Software Steering Council (SSC) rep
16+
- We need to name and submit an SSC rep by October 3
17+
- Update our team-compass
18+
- Rick W to serve for one year
19+
- 2FA
20+
- Should be enforced in JupyterLab by our next meeting (Sep 27)
21+
- Jason W to bring up at JupyterLab meeting tomorrow

‎meetings/2022-09-27.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# Jupyter Security Bi-weekly Meeting
2+
3+
## September 27, 2022
4+
5+
| Name | affiliation| username |
6+
| -------------------| -----------| -----------------|
7+
| Rick Wagner | UCSD | @rpwagner |
8+
| Jason Weill | AWS | @jweill-aws |
9+
| Rollin | NERSC | @rcthomas |
10+
11+
- [Security roadmap](https://github.com/rpwagner/security/blob/roadmap/docs/roadmap.md)
12+
- 2FA: Needs to be enabled in JupyterLab
13+
- Security workshop

‎meetings/2022-10-11.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# Jupyter Security Bi-weekly Meeting
2+
3+
## October 11, 2022
4+
5+
| Name | affiliation| username |
6+
| -------------------| -----------| -----------------|
7+
| Rick Wagner | UCSD | @rpwagner |
8+
| Rollin | NERSC | @rcthomas |
9+
| Matthias Bussonnier| QuanSight | @carreau |
10+
||||
11+
||||
12+
13+
- Meeting w/Intigriti
14+
- Customers
15+
- Researchers
16+
17+
- How is Intigriti interfacing with Jupyter ?
18+
- 2 months ... trial period w/EC
19+
- Multiple programs, one from the EC.
20+
- Would Jupyter be a good fit.
21+
- What can be tested, will be tested will determine if we can be tested.
22+
- Sounds like issues identified external to their researchers they fund are not covered.
23+
- Cross communication between researchers
24+
- Would need to be a bit organized on putting CVE publications
25+
26+
- Post meeting
27+
- Rick's suggestion
28+
- Start small with a set of limited repos that are released
29+
- Communicates what key initial packages are
30+
- Matthias suggests
31+
- to scope even further to types of vulnerabilities and specific package
32+
- further more might be too vague
33+
-

‎meetings/2022-12-06.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
# Jupyter Security Bi-weekly Meeting
2+
3+
## December 6, 2022
4+
5+
| Name | affiliation| username |
6+
| -------------------| -----------| -----------------|
7+
| Jason Weill | AWS | @jweill-aws |
8+
| Sritej Attaluri | Bloomberg | |
9+
| Rick Wagner | UCSD | @rpwagner |
10+
| Rollin Thomas | NERSC | @rcthomas |
11+
| Rosio Reyes | Anaconda | @RRosio |
12+
13+
- Triage
14+
- Email list status?
15+
- https://github.com/jupyter/security/issues/50
16+
- Appears to be a permissions issue with the ipython-security mailing list not accepting external messages (from non-group members)
17+
- Issues
18+
- Review request: https://github.com/jupyter/security/issues/49
19+
- Haven't done this review before, need to discuss process
20+
- nbclassic (jupyter-notebook subproject)
21+
- Confirm w/developers
22+
- Respond to reporter
23+
- Above could be shortened by ensuring developers are looped into sec reports
24+
- Can we document guidelines about when we do backports/sec updates for existing releases vs telling people to wait for next major version
25+
- Funding & Involvement
26+
- Onboarding newcomers interested in helping with security
27+
- What steps are there?
28+
- Maybe fleshing out the README with onboarding details would be a good idea
29+
30+
- Integriti
31+
- PEARC23 CfP?
32+
- Thought:
33+
- Subprojects should have a designated security contact
34+
- Designated security contact is subscribed to appropriate mailing lists, etc

‎meetings/README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,11 @@ What this meeting is about:
1717

1818
## Meeting Minutes
1919

20+
* [2022-12-06](2022-12-06.md)
21+
* [2022-10-11](2022-10-11.md)
22+
* [2022-09-27](2022-09-27.md)
23+
* [2022-09-13](2022-09-13.md)
24+
* [2022-08-30](2022-08-30.md)
2025
* [2022-08-16](2022-08-16.md)
2126
* [2022-08-02](2022-08-02.md)
2227
* [2022-07-05](2022-07-05.md)

0 commit comments

Comments
 (0)