Page MenuHomePhabricator
Create Task
Maniphest T146749

Consider using Phabricator Calendar events to schedule Wikimedia Developer Summit sessions
Closed, DeclinedPublic
Actions

Description

Let's explore the idea of using Phabricator Calendar to schedule Wikimedia-Developer-Summit (2017) sessions. Potential advantages:

  • Phabricator Calendar is arguably easier to handle than big wiki tables, and may provide more flexibility through search queries.
  • Easier to show people's interest in attending a session, might help distributing sessions in rooms with the right size.
  • Expected features not available today include .ics export, maybe sync with Google Calendar.
  • Other?

Disadvantages:

  • Calendar in a Phabricator page instead of a MediaWiki.org page?
  • Other?

See also: T1035: Consolidate the many tech events calendars in Phabricator's calendar

Related Objects
Search...

Event Timeline

Qgil created this task.Sep 27 2016, 10:55 AM
Qgil updated the task description. (Show Details)Sep 27 2016, 10:58 AM
Qgil mentioned this in T1035: Consolidate the many tech events calendars in Phabricator's calendar.Sep 27 2016, 1:05 PM
Qgil moved this task from Backlog to October on the Developer-Advocacy (Oct-Dec-2016) board.Sep 27 2016, 1:08 PM
greg subscribed.Sep 27 2016, 10:04 PM
Qgil moved this task from Backlog to Organization on the Wikimedia-Developer-Summit board.Oct 5 2016, 9:11 AM
• RobLa-WMF added a comment.Oct 6 2016, 5:57 AM

We should do this. Phab events are designed for meetings, so even without the .ics support, this would be helpful.

Phab events do timezone conversion based on account preference. That could be a mixed blessing for someone flying in from another country or planning from outside PST timezone. The timezone conversion would be great for people participating remotely, though.

Why Phab events are great: here's the ArchCom IRC meetings for 2016

QuarterMonth 1Month 2Month 3
FY15-16Q3January: E133, E134, E135, E137February: E138, E140, E143, E144March: E146, E147, E148, E150
FY15-16Q4April: E152, E158, E159, E162, E168May: E169, E171, E184, E187June: E198, E203, E213, E218, E224,
FY16-17Q1July: E226, E228, E235, E237August: E251, E259, E261, E263, E266September: E269, E271, E273, E285
FY16-17Q2October: E287, E316November:December

The remarkup to generate that was pretty easy to write, and it's not terrible to read (it's not great, but not terrible). We won't always have the benefit of three digit event numbers, but we should take advantage of it for Wikimedia-Developer-Summit (2017), even though we'll probably have 4 digit ids by Wikimedia-Developer-Summit (2018)

The point is that even if the automatic calendars are kind of weird, we could compensate with an annotated table dense with a lot of information.

Qgil raised the priority of this task from Low to Medium.Nov 25 2016, 9:49 AM
Qgil moved this task from October to December on the Developer-Advocacy (Oct-Dec-2016) board.Dec 1 2016, 9:16 AM
Qgil added a parent task: T147955: Organize unconference at the Wikimedia Developer Summit 2017 .Dec 7 2016, 11:50 AM
Qgil raised the priority of this task from Medium to High.Dec 22 2016, 9:25 PM
Qgil edited projects, added Developer-Advocacy (Jan-Mar-2017); removed Developer-Advocacy (Oct-Dec-2016).Dec 23 2016, 3:33 PM
Qgil moved this task from Backlog to January on the Developer-Advocacy (Jan-Mar-2017) board.
• Elitre subscribed.Jan 4 2017, 5:45 PM
Qgil closed this task as Declined.Jan 7 2017, 3:31 PM
Qgil added a subscriber: • mmodell.

I started too late and now I get what I believe is an upstream bug...

  1. Create a query for events under Wikimedia-Developer-Summit (2017) within the Summit dates: https://phabricator.wikimedia.org/calendar/query/dk6FB_UafmPC/
  2. Click "Use results"... Export queary as .ics
  3. Give a name to the export and set the Mode to Public.
  4. The result I got is https://phabricator.wikimedia.org/calendar/export/3/

EXPECTED

This link works: https://phabricator.wikimedia.org/calendar/export/ics/mm23glmgilu3rbgwwir6/wikidev_test_calendar.ics

ACTUALLY

An error message appears:

Event queries which generate ghost events must include either a result limit or an end date, because they may otherwise generate an infinite number of results. This query has neither.

Which is not true, because an end date is defined (and the form doesn't have any option to set a search limit anyway).

48h before the event (and 0 working hours before the event), I am stuck. I have to give up for the Summit. :(((

At least I have learned how this is supposed to work. I think it can be useful not only in conferences with multiple sessions, also i.e. to get Tech Talks automatically added to your calendar.

Anyway, declining this one and CCing @Aklapper and @mmodell just in case they want to have a look and/or report upstream.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits