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

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

Start by reviewing the existing conference CSV layout and the linting, validation, and data-reading scripts. Assess how the proposed conferences/.csv and meetups/.csv paths can share the current schema, then check the README and migration impact. Done means both directories are supported consistently and the repository rename and documentation plan are addressed.