Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bi-Monthly PyLadies Meeting Notes: 14th December 2020 @2pm UTC #110

Open
4 of 7 tasks
MmeMarieLouise opened this issue Feb 7, 2021 · 0 comments
Open
4 of 7 tasks
Assignees

Comments

@MmeMarieLouise
Copy link
Member

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

  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)

  • Lynn + Bethany + Sarah will lead; to figure out where to put global council information
  1. Code of Conduct

  2. Finance Work Group

  • Marie-L + Bethany + Lynn to chat about PSF+PyLadies fundraising

Review Actions Items from Last Meeting

Action Item Owner Relevant links Completed
Start the PSF liaison process to get the ball rolling (other people interested can join later, but there's some time sensitivity) Marie-Louise
Related to the one above: follow up with the PSF on “how to go about things” w/r/t logistics of liaisoning Marie-Louise
Draft up a proposal for feedback on the over-arching Working Group structure (not including the responsibilities of each WG) Ana Cecília
post in Slack #globalcouncil channel to ask for an async vote on the Resolution in new business (the governance model) Lynn ☑️
Reach out to Sarah if she’s okay with co-leading Infra WG with Lynn Lynn ☑️
Create the remaining discussion questions from this meeting as GitHub discussion threads Lynn advisor expectations and website info ☑️
Post these meeting minutes to the GitHub global council repo as well as last meeting's minutes Lynn Nov 16 and Dec 2 ☑️
Create a new meeting agenda for the next meeting (carrying over any old business) Lynn here! ☑️

New Business

  • Resolution: Publish meeting minutes directly in the global-organizing repo instead of as github issues (github discussion) (via Lynn)

    • Mini-update: a total of 6 👍 (myself plus 5 others) have agreed this is a good idea. I (Lynn) will go ahead and get started on the old meeting minutes.
    • In oct. (thread) we talked about rename the files to YYYY-MM-DD. I renamed, but didn't close the PR yet. We can adopt this new file name model in the next minutes note because it's easier to sort the files (Ana Cecília)
  • Create e-mail to council

    • Who or which workgroup will management the messages and answer it?
      We could create a e-mail to council members and redirect all messages to everyone, however I think (Ana Cecília) only one workgroup or member should answer.

Notes:

  • AI: lynn to investigate the setup of council email address with people's desired email address
  • What about info@? It currently goes to one person (Mariatta); we should figure out how to maintain this so that one person doesn't have to be responsible
    • Need to think through how information is propagated
    • @valery interested in helping
    • Can info@ be maintained by a working group? comms wg?
    • AI: Bethany to setup info@ with voluneer helpers (Valery, ...)
  • Governance Structure
    • The structure will be:
    • Roles to Chair and Vice Chair
    • This chairs need to be location and ethnic representative? We have more than a half members from south, it's important? Rotation? (Ana Cecília)

Old Business: Follow up items from prior meeting:

  • Mission, Purpose and main responsibilities
    • From previous meeting: agreed to work offline
    • Set "working group"/doc to work on
    • Schedule meeting with advisors for review

Action Items and Assignees for Next Meeting

Action Item Owner Relevant links
set up an async discussion with Lynn and Bethany about the Pyladies auction Marie-Louise #93
Re-schedule fiscal sponsorship meeting with Lorena Marie-Louise #89
provide contact details for Paris Organisers re pyladies database Marie-Louise #88
contact Ewa Marie-Louise #90
contact Phyllis Marie-Louise #91
ask everyone to update GC purpose doc Marie-Louise #77
Decide how we can communicate our chosen model to the world (ideas from Valery: produce one or multiple articles about why we agreed on the model chair, vice chair and workgroups/leaderships, explain how it is going to work, in the social network mention this article, provide a resume about how we are assigned as workgroups/leaderships and chair, vice chair in the page of pyladies, we could also post the same article or something like the agreement, maybe we can also add in the page our leaderships/workgroups responsible names so people can know who to reach out for the different things) Marie-Louise (create GitHub Discussion)

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants