Calendar and release schedule
Albert Astals Cid
aacid at kde.org
Mon Apr 17 16:11:04 UTC 2017
El dilluns, 17 d’abril de 2017, a les 13:33:39 CEST, Luigi Toscano va
> Albert Astals Cid ha scritto:
> > El diumenge, 16 d’abril de 2017, a les 19:18:18 CEST, Luigi Toscano va
> > escriure:
> >> Hi,
> >> (sending this to release-team@ as primary user)
> >> the sysadmins kindly enabled the Calendar application on
> >> phabricator.kde.org. It is still not stable, and marked in Phabricator
> >> documentation as "prototype":
> >> https://secure.phabricator.com/book/phabricator/article/calendar/
> >> Nevertheless, this is a good time to think about consolidating our
> >> various
> >> calendars.
> >> = Status of calendars
> >> The existing calendar page, https://www.kde.org/events/month.php
> >> aggregates:
> >> - the calendar for KDE Applications, and previously KDE SC releases,
> >> authoritative source is http://www.kde.org/releaseschedule.ics (manually
> >> generated?);
> >> - the calendar of other events (sprints/conferences?). I'm not sure where
> >> the ICS is stored.
> > It's a google calendar.
> > See $list_webcals in
> > https://websvn.kde.org/trunk/www/sites/www/events/config.inc.php?
> > view=markup&pathrev=1487214
> >> In addition, Plasma has its own
> >> (https://community.kde.org/Schedules/Plasma_5) -
> >> https://calendar.google.com/calendar/embed?src=031gkgqg1hjf8lcmj0em1d2sj8
> >> %40 group.calendar.google.com&ctz=Europe/London
> >> = Proposal
> >> I tried as exercise to import http://www.kde.org/releaseschedule.ics
> >> inside
> >> the Calendar application:
> >> https://phabricator.kde.org/calendar/import/1/
> >> But it seems that imported calendars are not so flexible (you can't
> >> associate projects/tags to them).
> >> So I'd suggest to go the other way round: define the events natively in
> >> Calendar (so that we can associate them with the proper tag/project) and
> >> export them if needed (as ICS).
> > This means that one has to manually create all the stuff instead of just
> > letting a tool do it, no?
> No, or I wouldn't have proposed it :)
> We can script it:
> Either extend this script to create also events in addition to repositories,
> or create a totally separate script:
Ok, if it's to be the same work for *me*, *I* don't have an objection :D
More information about the release-team