|
| 1 | +# Jupyter Security Bi-weekly Meeting |
| 2 | + |
| 3 | +## November 7, 2023 |
| 4 | + |
| 5 | +| Name | affiliation| username | |
| 6 | +| -------------------| -----------|--------------| |
| 7 | +| Rick Wagner | UCSD | @rpwagner | |
| 8 | +| Joe Lucas | NVIDIA | @josephtlucas| |
| 9 | +| Rosio Reyes | Anaconda | @RRosio | |
| 10 | +| Matthias Bussonnier| Quansight | @Carreau | |
| 11 | +| David Qiu | AWS | @dlqqq | |
| 12 | +| Rollin Thomas | NERSC | @rcthomas | |
| 13 | + |
| 14 | + |
| 15 | +- Security reports directly on Jupyter/Security |
| 16 | +- HECVAT and alike report: |
| 17 | + - See |
| 18 | + https://github.com/jupyter/jupyter.github.io/pull/743/files#commit-suggestions |
| 19 | + - URL: https://library.educause.edu/resources/2020/4/higher-education-community-vendor-assessment-toolkit |
| 20 | + - Attorneys at the NSF summit |
| 21 | + - who is the legal entity, do they have attorneys. |
| 22 | + - Have both an FAQ, and a Document (pdf) signed by numfocus. |
| 23 | + |
| 24 | +- Opened an [issue (docs-team-compass#22)](https://github.com/jupyter/docs-team-compass/issues/22) for security documentation in the Documentation repo |
| 25 | + |
| 26 | +- David to contribute JupyterLab documentation on developing JupyterLab extensions. |
| 27 | + - David: I can get started on this in a few weeks, with a draft PR by early December. |
| 28 | + |
| 29 | +- Security documentation to be added to jupyter.org/security |
| 30 | + - Source: https://github.com/jupyter/jupyter.github.io |
| 31 | + - Can we have exclusive permissions to edit the "Security" page? |
| 32 | + - David's proposed process: We open changes as a draft PR, get feedback from everybody security, then open for review and ping somebody to merge the PR |
| 33 | + |
| 34 | + |
| 35 | +Matthias suggest a small read later: http://thecodelesscode.com/case/215 |
0 commit comments