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: May 7th, 2024
Previous meeting issue link: #146
Current meeting attendees: @BethanyG @JUpani @MmeMarieLouise @econchick

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 )

Review Actions Items from Last Meeting

Action Item	Owner	Relevant links	Completed

New Business

[x] website specification
- include kit.pyladies.com in scope
- make sure kit.pyladies.com and pyladies.com are more strongly linked together
- make sure that the new site is easy to maintain.
  - what does that look like for us? esp since energy / volunteers ebb and flows
- possibility: use django (or django plugin of some sort) to build a static site
- stick to static, make it collaborative
  - same "format" for collaboration (contribute blog posts, new chapters, learning resources)
  - mynt is no longer maintained
  - options: Hugo (Go), django-distill (Python, Django), Jekyll (Ruby), pelican Python, 11ty(node, JavaScript)
- cookiecutter repo for chapters (or refresh the existing one)
- problem to solve: "what do i need to do to make this change?"
  - many repos, many possible places to make changes; netlify vs heroku vs what else
  - chapter meetup or meetup equivalent posts
  - add my chapter's twitter / mastodon
  - add my chapter's info
  - add my chapter to the world map
  - add a blog post
  - add a resource
  - aggregator of chapters' blog posts
- probably want to maintain same/similar content structure / info architecture
- design needs: clean, nice, not trendy, mobile friendly; "stands test of time"; supports dark mode
- community:
  - what content do we want on there?
  - what's no longer needed?
  - what do you want to see as a pylady?
  - do we localize?
- sprints:
  - come away with a rough timeline
[ ] mastodon acct/server
[ ]
[ ]
[ ]

Old Business: Follow up items from prior meeting:

[x] conclude https://github.com/pyladies/pyladies/issues/649
[ ]
[ ]
[ ]

Action Items and Assignees for Next Meeting

Action Item	Owner	Relevant links
review @MmeMarieLouise microfunding proposal for next meeting	@MmeMarieLouise

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

pyladies / global-organizing

Monthly PyLadies Meeting Notes: Tuesday, May 7th, 2024 10PM UTC #147