Skip to content

Commit 93f4214

Browse files
authored
Create 2023-10-03.md
Add 2023-10-03 notes
1 parent 741df99 commit 93f4214

File tree

1 file changed

+29
-0
lines changed

1 file changed

+29
-0
lines changed

meetings/2023-10-03.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
# Jupyter Security Bi-weekly Meeting
2+
3+
## October 3, 2023
4+
5+
| Name | affiliation| username |
6+
| -------------------| -----------|-------------|
7+
| Matthias Bussonnier| Quansight | @Carreau |
8+
| Rick Wagner | UCSD | @rpwagner |
9+
| Jason Weill | @AWS | @JasonWeill |
10+
| David Qiu | @AWS | @dlqqq |
11+
| Rollin Thomas | NERSC | @rcthomas |
12+
| Rosio Reyes | Anaconda | @RRosio |
13+
14+
Agenda:
15+
16+
* Email from the Community Building Group:
17+
- Process to source input from subprojects to identify area were help is needed to maintain a robust community. Identifi Commmunity building practices. There are interview scripts, and invite to join calls on thursday.
18+
- Some of us are going to attend on October 19th.
19+
20+
* We know have an Jupyter Security Sandbox environment.
21+
* It will likely be used for the Jupyter/Zeek workshop on Octover 223rd
22+
* The NSF has a program called [CloudBank](https://www.cloudbank.org/). Targetted for cyberinfra and DS. But also grants for training activities.
23+
* It does allow federated logging.
24+
* currently $2k
25+
* Suggest to have this as public information,
26+
* And let the SSC know.
27+
* See https://github.com/jupyter/executive-council-team-compass/issues/13
28+
29+
Sorry I think I ended the meeting for all... not sure how as I should not have been admin ...

0 commit comments

Comments
 (0)