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: 24th February
Previous meeting issue link: #112
Current meeting attendees: @cecivieira @julianafalves @valerybriz @JUpani @trallard @Marie-L @BethanyG
Meeting Lead: @Marie-L covering for @sonacrystal
Notetaker: @valerybriz
Agenda
Please add items as needed. If you add a topic please make sure to attend the meeting.
@pyladies-mod bot for messaging users about CoC violations
Code of Conduct
@lorenamesa has commented (in light of recent Slack moderation needs) that the current PyLadies CoC lacks some specificty and is less enforcable than we might want. Suggests using the PSF CoC, or revising the PyLadies CoC.
Finance
meeting with PSF accounting team
Slack Moderation
We have a Slack Moderators group (currently 6 members who are also workspace admins) that monitors/enforces the CoC for Slack. This group recently had to warn a member for DM-ing others persistantly.
This group now has a bot and a tracking sheet for reporting/responding to CoC and "problem" reports.
We need a general policy around what information we are going to track, and what kind of transparency reports (if any) we're going to file/keep.
We also need to make sure we have consistent rules and procedures around reporting, responding to reports, and who is going to act as moderators.
Data
initial discussions (async)
Resources
[name=Bethany] to join the team.
Key areas: Slack, Github, PyLadies website and G-Drive.
Community Liaison
Summary of suggested responsibilities:
Organize monthly or quarterly group meetings for chapter organisers.
Be involved in Slack moderation.
CoC enforcement - slack admins and moderators group
"active" in Slack - answering unaswered community questions (maybe an every other day checkin?), starting periodic conversations (once or twice a month?)
holding chats/checkins with the chaper organizers group/channel
posting items of interest centered on OSS, Python, chapter work/activity (once a month, maybe??)
Be involved in the development/refinement of the CoC’s.
Be involved in the new chapter materials.
Any other areas that touch on “community building” / “Community relations”.
Review Actions Items from Last Meeting
Action Item
Owner
Relevant links
request that everyone adds their ideas to the GC purpose doc before the next meeting
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
Agenda
Please add items as needed. If you add a topic please make sure to attend the meeting.
Project Updates
Project Comms (Slack: #project-communication / Repo: https://github.com/pyladies/project-communications)
Project Admin & Logistics (Slack: #project-admin-logistics / Repo: https://github.com/pyladies/project-admin-logisitics )
Project Tech & Infra (Slack: #project-tech-infra / Repo: https://github.com/pyladies/pyladies)
@pyladies-modbot for messaging users about CoC violationsCode of Conduct
@lorenamesahas commented (in light of recent Slack moderation needs) that the current PyLadies CoC lacks some specificty and is less enforcable than we might want. Suggests using the PSF CoC, or revising the PyLadies CoC.Finance
Slack Moderation
Data
Resources
Community Liaison
Summary of suggested responsibilities:
Review Actions Items from Last Meeting
New Business
Old Business: Follow up items from prior meeting:
Action Items and Assignees for Next Meeting
@pyladies/pyladies-global-contributors @pyladies/pyladies-global-admin