Monthly PyLadies Meeting Notes: Thursday 6th July 2023 10PM

[MmeMarieLouise]

This template should be used (edited) the month prior and during the meeting. This will ensure we can address all topics added throughout the month; as well as provide minutes and follow up after the meeting is held.

PyLadies Global Meeting

• Date: Thursday 6th July, 2023
• Previous meeting issue link: Tuesday 6th June 2023
• Current meeting attendees:

Agenda

Please add items as needed. If you add a topic please make sure to attend the meeting.

• [x] Trademark issues & considerations (context from Slack)

• email the PSF and cc mariatta and explain that we wouldn't like for them to support this trademark by leasing or any other way

• agree on temporary PSF liaison

• [x] Ansys Donation (context from Slack)

• the donation has been received

• [x] What will be the procedure for Chapter CoC violations & escalations? (some context from Slack)

  • [x] How do we investigate, and who should investigate?
  • [x] When & how do we involve the PSF CoC workgroup? (some context from Slack)
  • [x] How do we record and track CoC issues & also keep them confidential and secure?
  • [x] What steps do we take for 1, 2, 3 ...etc. violations?

• [x] Setting up a Tech + Infra Repo for docs and infrastructure notes (context from Slack & more related)

• [x] Setting up a 1Password or equivalent password keeper for PyLadies global.

  • [x] Propose we allocate funds for a 1Password group instance (or something similar), and have the master password sit with the PSF. We can then grant access levels based on role or group for PyLadies for various workgroups and activities.
  • [x] We recently had a situation where we couldn't upgrade certain websites because we lost track of the Netlify and related passwords. (context from Slack).
  • [x] We also had discussions around new Social Media sites (and existing social media sites) - it's pretty important to not let squatters claim our names there. Its also important that access to these sites not sit with one person who may or may not stay involved with PyLadies (context from Slack).

• [ ] help with comms

Project Updates

1. Project Comms (Slack: #project-communication / Repo: https://github.com/pyladies/project-communications)

2. Project Admin & Logistics (Slack: #project-admin-logistics / Repo: https://github.com/pyladies/project-admin-logisitics )

3. Project Tech & Infra (Slack: #project-tech-infra / Repo: https://github.com/pyladies/pyladies )

Review Actions Items from Last Meeting

Action Item	Owner	Relevant links	Completed

New Business

• [ ]
• [ ]
• [ ]
• [ ]
• [ ]

Old Business: Follow up items from prior meeting:

• [ ]
• [ ]
• [ ]
• [ ]

Action Items and Assignees for Next Meeting

Action Item	Owner	Relevant links
email the PSF and cc mariatta and explain that we wouldn't like for them to support this trademark by leasing or any other way	@BethanyG
agree on temp PSF liaison - Bethany would like to do this and step in for Tania	@BethanyG @trallard
adding a poll to slack to vote on PSF liason
update the pyladies kit to let people know that all coc breaches will be referred to the PSF etc.
create a list of options for password managers (@econchick recommends Bit Warden) UPDATE: we have decided to go for Bit Warden

@pyladies/pyladies-global-contributors @pyladies/pyladies-global-admin