#91 schedule ics files take up 2 years or more of whole day entries
Opened a year ago by petersen. Modified 10 months ago

I just imported:

https://fedorapeople.org/groups/schedule/f-38/f-38-key.ics

into Google Calendar.

I also have the corresponding F37 calendar imported.

For whatever reason they both seems to start 9 Nov 2021.

I guess my real question is: would it be possible for them not to have an whole-day entry for every single day. Or is there another variant of the calendar which doesn't have that?


For whatever reason they both seems to start 9 Nov 2021.

That's due to a shift in the wallpaper process. It looks like F38+ has a more "normal" start point.

I guess my real question is: would it be possible for them not to have an whole-day entry for every single day. Or is there another variant of the calendar which doesn't have that?

I'm not sure what you mean by "a whole-day entry for every single day". Can you elaborate on that?

Metadata Update from @bcotton:
- Issue assigned to bcotton

a year ago

I think the approach here is to use the --flat argument to schedule convert on the ics file the way I do with the html. This will remove the "container" tasks and leave just the leaf tasks and milestones. This would not affect the tasks in the json file.

I don't think this would affect how people use the schedule ics files, but I'll share it across a variety of mailing lists and Fedora Discussion for feedback before I make that change.

For comparison

I looked into the ics file a long time ago and the amount of noise in that calendar was quite silly, so I decided not to use it. Thanks for this!

The new (flat) calendar is quite an improvement, but still, to make it even more usable, may I suggest the following?

  • Make most of the "date based" events full-day, please.

Currently, e.g. Change Checkpoint: 100% Code Complete Deadline is set for 08:00 UTC which is confusing (and looks bad as well when looking at the week view in the calendar).

Some events, like Bodhi updates-testing activation point or Current Final Target date might make sense as actually timed (e.g. to 14:00 UTC), but they are still set for 08:00 UTC.

Similarly, multiple-days events (e.g. Beta Freeze (starts at 1400 UTC)) start and end at 08:00 UTC. This again is quite confusing for an event that literally says "starts at 1400 UTC" in the title.

Hope that's actually possible because that would make the calendar usable for me.

Make most of the "date based" events full-day, please.

I'll look into that. It should be possible to do, but it may have unintended consequences. I think that may be the a distinction between having 0 duration (thus a milestone) and 1 day duration (thus a task). There's some semantic importance in that distinction, and I'm not sure if the tooling would handle them differently. I believe at least some paths may care.

As for the time, I have not been able to find a way to change that. I feel your pain, though, as all of the tasks I import to my todo list end up with a due time of 03:00 local.

I guess my real question is: would it be possible for them not to have an whole-day entry for every single day. Or is there another variant of the calendar which doesn't have that?

I'm not sure what you mean by "a whole-day entry for every single day". Can you elaborate on that?

For F38 I see "Fedora Linux 38 release" all day event throughout
9 November 2021, 16:00 – 22 May 2024, 16:00

Well I am not worried about the start/end days: I guess I am asking if this could be removed entirely (for sub-calendars)? Maybe it is not practical, but if so it would greatly reduce the overall footprint of the calendar

So this sat because @frantisekz had said a whlle back that it could affect the packager dashboard but he was out of the office. When he got back, neither of us picked this back up. Unfortunately, I'm not going to be able to continue this, so I'll unassign myself for now and leave it open as future work.

Metadata Update from @bcotton:
- Assignee reset

10 months ago

Login to comment on this ticket.

Metadata