Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Declined | None | T164483 Hold a Bug-a-thon | |||
Declined | None | T164487 Schedule Bug-a-thon |
Event Timeline
A quick read of Q4 suggests the following might be possibilities.
topic | ETA |
ContentTranslation | end of Q4 |
New PDF rendering | end of Q4 |
3D (on beta cluster) | end of Q4 |
Syntax highlighting in classic wiki text editor | end of Q4 |
This will be done in 2018 instead. The task will be moved to WMSE-Bug-Reporting-and-Translation-2018.
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.
The previous comments don't explain who or what (task?) exactly this task is stalled on ("If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on"). Hence I am boldly resetting task status.
(Smallprint, as general orientation for task management: If you wanted to express that nobody is currently working on this task, then the assignee should be removed and/or priority could be lowered instead. If work on this task is blocked by another task, then that other task should be added via Edit Related Tasks... → Edit Subtasks.