Signals for event changes / event changelog signals

[drnlm]

Mentioned in wafer BoF.

[zoidyzoidzoid]

So Django has feed support, but complicated schedule means complicated feed.

Do we want schedule items or slots, or do we wanna add recording of changes so that the feed is the most recently updated schedule items, or instead the soonest schedule items?

[hodgestar]

Are RSS and the schedule a good match? RSS is for a stream of posts, which is somewhat different to the schedule?

[drnlm]

I think we want to publish schedule items - a tutorial spanning mutiple slots should be only 1 item in the RSS feed.

Handling schedule editing and changes in the RSS feed needs thought. We may need to have a separate "publish to rss" step, so we don't generate multiple rss updates for an item whenever the schedule is edited.

[drnlm]

RSS may not be the best solution, but it was suggested during the debconf BoF. Some easily machine-parsable export of the schedule does seem to be required, and pentabarf doesn't quite fit that use case.

[zoidyzoidzoid]

I guess just exporting of the schedule to import into calendars,etc. would be useful?

[hodgestar]

What about just adding an improved API that returns the schedule as JSON?

[drnlm]

On further though, we probably do need to have some sort of feed hooked up as well. One of the complaints was the difficulty of detecting that changes to the schedule had happened.

That leads to some sort of "scheduled has been edited" event / announcement, which should probably be extended to cover pages and other things, and a more easily parsable schedule export, which feels a bit messy.

[hodgestar]

Some sort of human & machine understandable change log API and web page would be very useful to everyone (both organizers and attendees & for display on the current-events page). Maybe that's something for a separate ticket?

[zoidyzoidzoid]

I don't know if that's for a separate ticket or if it was the initial
intent of this ticket, and then simpler exporting of the schedule should
move to another ticket?

On Tue, Jul 5, 2016 at 5:44 PM, Simon Cross [email protected]
wrote:

Some sort of human & machine understandable change log API and web page
would be very useful to everyone (both organizers and attendees & for
display on the current-events page). Maybe that's something for a separate
ticket?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#273 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/ACdAzW6OQHEeDK24o5jxLMIrq8xUur3-ks5qSnvYgaJpZM4JFEKF
.