Proposal: Rename repository to “Python Events” and include conferences + meetups with a shared schema

[piotrgredowski]

Hi all!

I’d like to propose evolving this repository from a conferences-only list into a broader Python events dataset that includes both conferences and meetups in one place.

Motivation

• Many people (speakers, sponsors, attendees, organizers) look for both conferences and meetups.
• Keeping both event types in one repository makes discovery easier and centralizes maintenance.
• We can keep compatibility with existing tooling by reusing the current CSV format.

Proposal

1. Rename the repository from conferences to events. Github should (I believe) handle redirection by itself for http requests.
2. Organize data into two directories:
   • conferences/<year>.csv
   • meetups/<year>.csv
3. Use the same CSV schema for both categories (same headers as today):
   • Subject, Start Date, End Date, Location, Country, Venue, Tutorial Deadline, Talk Deadline, Website URL, Proposal URL, Sponsorship URL
4. Keep non-applicable fields empty for meetup entries (e.g., CFP/sponsorship deadlines).
5. Update lint/validation/scripts to read both directories.

Why this structure

• Single source of truth for Python events.
• Minimal migration risk (no breaking schema redesign).
• Easy filtering by directory while preserving consistent data ingestion.

If this direction sounds good, I’m happy to help with a follow-up PR for:

• README updates
• directory migration plan
• linter/script path updates

[invisibleroads]

Hi @piotrgredowski

Thank you for this proposal.

It is an interesting idea, but I'm concerned that there will be too many meetups to track. There used to be an official site that tracked Python user groups.

I think there should be a threshold based on the number of attendees and whether people would be willing to travel from far to either present or participate in the event.

Otherwise, this repository could get messy and there would be work involved in verifying whether the meetup is still active.