The Amsterdam Hackathon, many QA weekly goals and many other events last more than one day. How should this be reflected in the calendar?
Project talk:Calendar
The templates could be extended to support more date formats, including events spanning several days, and those happening at a specific time. I didn't implement all that in the first version of the templates because they were a proof of concept, and I didn't want to make them too complex. I do think it's feasible, though, and perhaps my opportunity to get into Lua :)
In the meantime... should we edit the date field with plain text e.g. "May 22-24" or create one event for each day?
The template doesn't support plain text as an entry format for dates, only formats supported by the {{#time:}}
parser function. So the only solution right now is one event for each day.
Silly question but... why do we need to use that time parser function? Is there any operation done with that data field as of today?
We need it to format times depending on the context. Project:Calendar and Template:New opportunities/Content display dates differently; the parser function allows us to use the same date input and display it differently on those pages. Since you haven't transitioned Template:New opportunities/Content to use the calendar, I guess the answer "as of today" is "no".
That said, if this is urgent to you, I can try to quickly hack support for events longer than a day in the template. It will be done without Lua, but it'll work, and we can transition to Lua later.
2-3 day events still look ok repeating days but the problem comes with the QA weekly activities...
Of course the best solution is to make the template support multiple day events, but if you are busy I'm fine having the same data format used in Calendar and New opportunities.
I've modified the templates, and {{event}} now supports "end dates". It's not perfect, but it should meet your needs. Basically, you just need to add an enddate
parameter to the event's entry, in the same format as the date
parameter, and it should show (example). If there isn't an end date, nothing should show. I'll update the documentation now.
Does it make sense to reverse the order of events on this page? Or perhaps keep the most current year at the top? I'm happy to update the page, but wanted to discuss it first.
I'd say just go for it. All these past events could even by archived now. Since Guillaume stopped looking after this page due to other obligations there is only very low activity. I just figured recently that EMWCon may be worth a listing.
Edit: After archiving there is currently nothing left to order. ;)
Check Phab:T1035 - Consolidate the many tech events calendars in Phabricator's calendar.
While I'm very interested to bring my help on this topic, I'm currently quite busy with some other subjects. I'll do my best to participate, hopefully in accurate times.
What is the best way to deal with past events? I would like to keep a record of of those at least at QA/Weekly goals.
Currently, events from past months are archived, e.g. at Project:Calendar/2013/01 for January 2013.
Show past events in a separate table
It's possible to show past QA events on QA/Weekly goals with a syntax similar to the one used to show upcoming events, by specifying the archive pages instead, e.g. for January:
{{event header}} {{#lst:Project:Calendar/2013/01|QA}} {{table footer}}
- will show QA-related events in January:
[[<tvar|calendar>Special:MyLanguage/Project:Calendar</>|edit or add events]]</translate>] [ ] [<translate>
[[<tvar|identity>Special:MyLanguage/Project:Visual identity</>|view credits]]</translate>] <translate>
Date</translate> |
<translate>
Type</translate> |
<translate>
Event</translate> |
<translate>
Contact</translate> |
---|---|---|---|
Jan 28 | QA: Review 250 open bugs unchanged for more than one year | AKlapper, Valeriej | |
Jan 28 | QA: VisualEditor: Testing Non-Latin Characters Input and Behavior | Cmcmahon, Siebrand, Qgil | |
- The transclusion system was designed to primarily work with upcoming events, so it's not totally optimized for archives (meaning, you'll have to manually include each past month, whereas for upcoming events you only need to include the calendar page) but it works.
- You can then add February once it's been archived, and each month after that once it's archived:
{{event header}} {{#lst:Project:Calendar/2013/01|QA}} {{#lst:Project:Calendar/2013/02|QA}} {{#lst:Project:Calendar/2013/03|QA}} ... {{table footer}}
Show past and upcoming events in the same table
If, instead of showing past events separately, you want to show past and upcoming events together, you need to include past months as well as the current calendar:
{{event header}} {{#lst:Project:Calendar/2013/01|QA}} /* list all previous months here */ {{#lst:Project:Calendar|QA}} /* and this will show upcoming events */ {{table footer}}
- will show them all together:
[[<tvar|calendar>Special:MyLanguage/Project:Calendar</>|edit or add events]]</translate>] [ ] [<translate>
[[<tvar|identity>Special:MyLanguage/Project:Visual identity</>|view credits]]</translate>] <translate>
Date</translate> |
<translate>
Type</translate> |
<translate>
Event</translate> |
<translate>
Contact</translate> |
---|---|---|---|
Jan 28 | QA: Review 250 open bugs unchanged for more than one year | AKlapper, Valeriej | |
Jan 28 | QA: VisualEditor: Testing Non-Latin Characters Input and Behavior | Cmcmahon, Siebrand, Qgil | |
Hope that helps. Let me know if you have other questions :)
Yes, I also want to have consistent icons for the areas defined at How to contribute. In fact I have collected many, see the slides for I'm drafting this week for FOSDEM.
Nice! I like many of your choices. I hope that we'll come to a point where we have a set of reusable, consistent and recognizable icons across mediums (wiki pages, blog posts, slides, etc.).
Don't forget to add the proper credits in your slides where required. It's easy to do in a presentation, but it's a bit trickier to show credits on wiki pages, because when we use them as icons, we usually use the link=
parameter to hijack the image's link (that would otherwise have led to the image credits). For events and the calendar, I've found a good enough workaround (credits are listed on Template:Event/doc and linked to from Template:Event header), but we'll need to make sure we show or link to proper credits wherever we use those icons.
Perhaps we should start listing the icons somewhere (other than the template's doc) to have a central place both to define our visual language, and also to list proper credits. Maybe Project:Visual identity?
Nemo started a topic at Talk:How_to_contribute#Icons_23333 so let's move the discussion there. I'm happy to agree on good ideas about proper attribution and link=. I'm not familiar with Project: pages and the deal about them, but as usual I trust you. :) Let's just make sure it is linked with Wikimedia Foundation Design/Agora Icon Set and that is shared at the Design list.
Thanks; I've copied my message there to avoid splitting the discussion.
.ics file, shared Google Calendar etc.
Hi. I'm pretty sure it's possible, similarly to how m:IRC office hours does it, but I haven't gotten around to looking into it yet. If you or someone else wants to look into it in the meantime, help would be much appreciated.