-
Notifications
You must be signed in to change notification settings - Fork 68
Closed
Description
I think we have to give up on the quest of sharing conferences... let's simplify things by removing the automation work that was pulling in new conferences...
We should also remove the GitHub issue templates for new events.
Lastly we should still use the _data/conferences.json but maybe expand that to _data/events.json and have it include our regular coffee and code meetups as well the monthly meetup and conferences THAT WE ARE SPONSORING.
I think we can also use that to cross promote events from our partners like PRELUDE.tech.
Jekyll Site Action Items Checklist
Conference Automation
- Remove existing conference automation scripts
- Disable any automatic conference data pulling mechanisms
- Remove all conferences that have passed
GitHub Repository
- Delete existing GitHub issue templates for new events
Data Management
- Rename
_data/conferences.jsonto_data/events.json - Expand the events JSON structure to include:
- Meetups
- Add Coffee and Code
- Add Monthly Meetup
- Conferences
- Partner events (e.g., from PRELUDE.tech)
- Meetups
Example:
{
"conferences": [
{
"name": "PyCon US",
... # more data here
}
],
"events": [
{
"name": "Coffee and Code",
...
}
]
}Event Data Structure Considerations
- Define a flexible JSON schema for events that can accommodate different types of events
- Include fields such as:
- Event name
- Date
- Location
Documentation
- Update CONTRIBUTING.MD or documentation to reflect new event management approach
- Create guidelines for manually adding events to
_data/events.json
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels