On Wed, 2013-05-08 at 06:34 +0200, Bruno Wolff III wrote:
The fedora release calendar uses 24 hour meetings instead of all day events. That is not going to work too well when lots of milestones land on the same day.
It is planned (see ticket #10) but not there yet.
The fedora release calendar seems to be missing lots of stuff that is available at http://fedorapeople.org/groups/schedule/f-19/f-19-all-milestones.ics .
I replied to you for this one :)
It would be nice to have a view per team with the irc channel as the location. This is more useful for doing reminders of meetings you want to attend. (The per channel view is better for finding an empty slot.)
This one is harder: how do you define the team?
Pierre
On Wed, May 08, 2013 at 08:20:29 +0200, Pierre-Yves Chibon pingou@pingoured.fr wrote:
This one is harder: how do you define the team?
A team would be one of FESCO, the board, various SIGs and other groups. Normally at any one time these groups would only have one active recurring meeting. These wouldn't change very often. So to a first approiximaration, what I want is a way to get ICS files for a few of the recurring meetings from the calendar. If the ICS files were named for teams, then when the meeting time changed I'd pick up those changes automatically. (Assuming the same name was used.)
On Wed, 2013-05-08 at 08:06 -0500, Bruno Wolff III wrote:
On Wed, May 08, 2013 at 08:20:29 +0200, Pierre-Yves Chibon pingou@pingoured.fr wrote:
This one is harder: how do you define the team?
A team would be one of FESCO, the board, various SIGs and other groups. Normally at any one time these groups would only have one active recurring meeting. These wouldn't change very often. So to a first approiximaration, what I want is a way to get ICS files for a few of the recurring meetings from the calendar. If the ICS files were named for teams, then when the meeting time changed I'd pick up those changes automatically. (Assuming the same name was used.)
The question remains, calendar don't contain team information so how do we define a team?
A way around that might be to be able to add tags to a meeting and offer a way to filter the ical output using these tags. That's not a small change though.
Pierre
On Wed, May 08, 2013 at 15:18:35 +0200, Pierre-Yves Chibon pingou@pingoured.fr wrote:
The question remains, calendar don't contain team information so how do we define a team?
As I mentioned, just being able to grab an ICS file for a particular recurring meeting would be a good enough approximation now. There could be perhaps a link on the web page for each meeting to an ICS file just for that meeting.
A way around that might be to be able to add tags to a meeting and offer a way to filter the ical output using these tags. That's not a small change though.
That is a thought I just had as well. When people entered their meetings, they would be able to add a tag to say which team the meeting is for.
The current set up is a bit odd in that the IRC chat channels are really what would be resources in other calendar systems. Normally people don't look at resource calendars except when trying to schedule a meeting that needs a resource. They also explicitly invite a group of people to a meeting when it is created. The latter doesn't work well for us, since attenance is open ended. I would like to see the chat rooms treated more like location resources, and at least specify the chat room channel in the meeting location value. This is important if you add a way to get ICS files for particular recurring meetings, as you'll want a way to see where the meeting is being held.
On Wed, 2013-05-08 at 08:58 -0500, Bruno Wolff III wrote:
On Wed, May 08, 2013 at 15:18:35 +0200, Pierre-Yves Chibon pingou@pingoured.fr wrote:
The question remains, calendar don't contain team information so how do we define a team?
As I mentioned, just being able to grab an ICS file for a particular recurring meeting would be a good enough approximation now. There could be perhaps a link on the web page for each meeting to an ICS file just for that meeting.
So basically, each team has it own calendar but propose a list of location for the meeting place and a view for the availability of the locations.
Sounds nice, different from the current approach but also more reasonable, no idea when I will be able to work on this. Could you please fill a ticket on the trac (to keep track of it)?
Thanks
Pierre
On Wed, May 08, 2013 at 16:31:22 +0200, Pierre-Yves Chibon pingou@pingoured.fr wrote:
So basically, each team has it own calendar but propose a list of location for the meeting place and a view for the availability of the locations.
This would be for the UI when creating meetings. And at this point it could work for any meeting without worrying about teams.
Sounds nice, different from the current approach but also more reasonable, no idea when I will be able to work on this. Could you please fill a ticket on the trac (to keep track of it)?
I'll write up a ticket for this (treating chat channels as location resources) and I'll do one for generating ICS files for individual recurring meetings.
I'll also review the ones I have filed. I'll keep the -1 minute open but note a fix has been committed.
On Wed, 2013-05-08 at 09:37 -0500, Bruno Wolff III wrote:
On Wed, May 08, 2013 at 16:31:22 +0200, Pierre-Yves Chibon pingou@pingoured.fr wrote:
Sounds nice, different from the current approach but also more reasonable, no idea when I will be able to work on this. Could you please fill a ticket on the trac (to keep track of it)?
I'll write up a ticket for this (treating chat channels as location resources) and I'll do one for generating ICS files for individual recurring meetings.
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). 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.
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.
I'll also review the ones I have filed. I'll keep the -1 minute open but note a fix has been committed.
Thanks :)
Pierre
On Wed, May 08, 2013 at 16:46:22 +0200, Pierre-Yves Chibon pingou@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.
fedocal@lists.fedorahosted.org
-
Bruno Wolff III -
Pierre-Yves Chibon