Page MenuHomePhabricator

Schedule Bug-a-thon
Open, Stalled, Needs TriagePublic3 Story Points


The Q4 timeplan is now up so it should be possible to start looking for suitable deployments to tie this to. It might also be worth taking a look at Q3 goals to identify anything which might get done in Q4 instead and/or which might have matured enough to be deployed during Q4.

Related Objects


Event Timeline

A quick read of Q4 suggests the following might be possibilities.

ContentTranslationend of Q4
New PDF renderingend of Q4
3D (on beta cluster)end of Q4
Syntax highlighting in classic wiki text editorend of Q4
Jopparn changed the task status from Open to Stalled.Jan 5 2018, 11:34 PM

This will be done in 2018 instead. The task will be moved to WMSE-Bug-Reporting-and-Translation-2018.

Before moving we should re-evaluate which quarter we want to do this in.

seeing this to stalled. Any scheduling needs to be redone with the 2018 deployment schedule in mind.

@Jopparn This is currently not in the timeplan for the Bug reporting project. By contrast T164485: Hold a translate-a-thon is penned in for November.

I would suggest cancelling the Bug-a-thon for 2018 and, considering the available technical manpower in November, aiming for the translate-a-thon to primarily be a volunteer event with us inviting and coordinating and possibly preparing some suggested focus areas. While staff who don't know how MediaWiki translation works could join to learn that is complicated by a volunteer event having to be organised outside of regular work hours.