On Wed, May 08, 2013 at 16:46:22 +0200,
Pierre-Yves Chibon <pingou(a)pingoured.fr> wrote:
I'm not sure about this last one. If you are only interested in one
recursive meeting, then just create it yourself to your calendar. The
iCal feed is only interested if you want to gather multiple meetings
which may change over time, so you want all the meetings of a team or a
location (which is basically the two types of calendar we have atm).
I do that now, but I think it's about as much work to set up the import. Plus
depending on how the meeting is updated later, the same link could potentially
pick up changes at DST/ST changes or when the meeting time needs to be
shifted.
If we generate a iCal feed for a particular recursive meeting (say
board) and then the meeting gets changed (time, location,
description...), we have no way of telling if the user still wants to
have this information or not.
I would expect you'd want to at least note the change. It may be that'd
you'd drop the meeting if it moved to a bad time.
Atm, the board can create a 'Board' calendar, fill it with
its
meetings/events and duplicate (until changed) the meetings happening on
the IRC channels. Then someone can access the board ical feed or the
fedora-meeting ical feed.
So, I'm not convinced yet about ical feed for single recursive meetings.
That would be a short term proxy for team meetings (perhaps implemented
with tags).
P.S. Note that you probably mean "recurring" rather than "recursive".
Recurring is repeating in a pattern. Recursing is a self reference.