What is this crazy thing?
This is a "cleanup" branch of "Eventgrinder"-- which runs some calendar aggregator sites, like dctechevents.com
It's an editorial system for calendars, which includes an iCal aggregator, user submissions, and an editorial queue.
Why does this code suck so much?
Lot's of reasons! Here's a few:
- I didn't concieve of it as open source, and it never occured to me that someone else might see the code.
- Testing? LOL
- There are a lot of half-implemented ideas in the code.
What is most broken?
The aggregator really needs to be made smarter-- particularly, it should handle events that disappear from iCal feeds (it should assume they are cancelled, postponed, or at least flag them as having possible issues)
If other people are going to hack on this and use it, a real theming system probably needs to appear. Also, the current "theme" is pretty ugly.
The current system of navigating between weeks is just dumb.
Recurring events were once supported, but it never worked very well, so I took it out. They should probably come back (done right).
How is EG different from Calagator or ElmCity?
I'm stuck on the idea of the calendar as an editorial product, that puts the expertise and interest of a person (or people, or an organization) at the nexus of many streams of events. A curator.
Calagtor is more like a wiki, and ElmCity does the aggregator thing, but there's no role for the editor beyond selecting which iCal feeds get pulled in.
- Fold in the improvements I've been working on in a seperate repo, https://github.com/rosskarchner/Share-Events/
- Instructions for spinning up an Eventgrinder instance, and starting a calendar.
- Trimming out modules that aren't used anymore.
- A decision on going all-in or all-out with Django.