Bi-Monthly PyLadies Meeting Notes: 21st April 2021 @ 8pm UTC

[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: 21st April
• Previous meeting issue link:
• Current meeting attendees: @cecivieira @julianafalves @valerybriz @Marie-L @BethanyG @Sonacrystal

  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)

   • geopython free tickets for pyladies members

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)

4. Code of Conduct

   • Tania has been really busy
   • they are going to adopt the PSF code of conduct and then as specific things for pyladies, different escalation levels
   • The next step is to post the to the main website @econchick will this be a task for the infra team ?

5. Finance

   • plan on hold until after PyCon 2021 (PyLadies Auction)

6. Slack Moderators

7. Data

   • 1st version draft survey

8. Resources

9. Community Liaison

Review Actions Items from Last Meeting

Action Item	Owner	Relevant links
find out about bevy platform, decide what the pro and cons are - before the next finance meeting	Bethany	Tania - thinks we should go for it but we must make sure that we are not charged in future, Valery - we can introduce bevy to the chapters that don't have meet-up and see how it works before rolling it out to wider pyladies community	Bethany - chapters who use meet up would not have the same features available so agrees with valery that we should test on small group first, Tania - schedule a call/ demo and discuss an agreement, they have bevy for good, the should be able to help us with a tier system, ML - let's schedule a deadline for the call and for final decision and implement, Sarah - is a chapter lead and they don't have access to meetup, they don't have online sites to organise their events, Juliana - her chapter don't use meetup they use another site like eventbrite etc she thinks it would be good if ever chapter has a free access to a platform, ML- let's move forward and plan to test out bevy straight after call , Ana cecelia - agrees to move forward with it on small groups, schedule a call by friday 30th April @trallard will liaise @Marie-L @BethanyG post a call in the organisers #channel in slack
find out if Tania can be added to the PSF meeting invitation	Bethany, Lynn, Marie-Louise	@lorenanicole can you please add @trallard ?
finish bios in the next few days	Jessica	Doc Link task for the infra team @BethanyG @JUpani
create GH discussion for everyone to share reasons why they haven't been participating before next meeting, if people could explain what they expected	Juliana, Bethany	bethany - more happens after 48 hours of each meeting, Juliana - maybe we should have shorter meetings, change mandate of social media - until more people are recruited !!
Discuss changes about the copy for the announcement	Everybody	https://github.com/orgs/pyladies/teams/global-council/discussions/15	where should we post this ? - social media , blog post pyladies with direct link,
vote to switch to bevy platform or not - before next finance meeting	Done
request a roadmap from global advisors on what we're taking responsibility of
read through all psf finance docs
draft responses to each psf finance action point

New Business

• [ ] Financial Sponsorship Docs -- what they are what they mean, signing, reporting, etc.
• [ ] Reimbursements & expenses for PyLadies Global
  • what process do we want to follow for this? There is a grant procedure from the PSF we can look at/start with.
  • who is the team that will approve these? Suggest Finance + the Chair, w/ larger or recurring items brought to the council for discussion or vote.
  • zapier subscription for 2021 (currently paid out of PyLadies Chicago, and they'd like reimbursement from Global)
  • Meetup expenses for Paris

---

Old Business: Follow up items from prior meeting:

• [ ] github app in our private channel like #project-tech-infra ?
• [ ] PSF meeting dates ?
• [ ] update the pyladies site with our FAQs page
• [ ] Find out about sponsoring Pyladies for Job Postings
• [ ] Pyladies Paris
• [ ] PyLadies 10 year anniversary/PSF 20 years/Python 30 years

Action Items and Assignees for Next Meeting

Action Item	Owner	Relevant links

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

[caffodian]

Hi! Mariatta pointed me here and I see you discussed Bevy and PyLadies. I was part of the group that set up the demo last year. A lot has changed since then, but what has not changed is that we would love to get PyLadies up and running on Bevy. I'd love to restart those conversations and get us all reconnected. @BethanyG what's the best way for us to reach each other?

[BethanyG]

@caffodian - Apologies for the delay in getting back to you. One of our council members, @trallard was going to reach out and set up a conversation/demo between Bevy and several of our chapter leads, but I don't know where she is with that. But if that has not already happened, I would very much like to chat and go over features, demo the product etc. I can be contacted at bethany@pyladies.com. Thanks so much for reaching out.