Change Details

Tracking Wikimedia-wide projects and when we expect they will arrive (see columns on the workboard). Criteria for adding a task to this project: * Task should only be added when describing a significant new piece of user-facing functionality (Features) or the launch of a new API or service (Platform). No bug fixes, refactoring, test coverage work, minor modifications, small UI tweaks or tracking tasks that cover huge time ranges. * Tasks have an initial expected date for this task that is agreed upon by the responsible project lead. If the date confidence is low, this should be indicated in the task description. When the date is revised, an explanation is added to the task. ** Tasks you want to make sure //get// on the roadmap ASAP can be added to the "Unscheduled" column, but should not remain there for more than a couple of weeks. Adding a task to the "unscheduled" column means a lot of people will poke you to get it scheduled, even with a rough ETA. :) * The short task description should be clear and understandable to anybody not being a member of the team. * The task either is connected to the team's workflows (i.e. it has relevant tasks as dependencies), or links into another tool like Trello when absolutely necessary. Many, but not all, of these tasks will be tagged #epic -- even when a feature has been well-tested and it's just a straightforward configuration switch to enable it, if/when we enable it in more languages/projects, we should ensure this is reflected in the roadmap.

Tracking Wikimedia-wide projects and when we expect they will arrive (see columns on the workboard). Criteria for adding a task to this project: * Task should only be added when describing a significant new piece of user-facing functionality (Features) or the launch of a new API or service (Platform). No bug fixes, refactoring, test coverage work, minor modifications, small UI tweaks or tracking tasks that cover a large backlog of work over huge time ranges. * Tasks have an initial expected date for this task that is agreed upon by the responsible project lead. If the date confidence is low, this should be indicated in the task description. When the date is revised, an explanation is added to the task. ** Tasks you want to make sure //get// on the roadmap ASAP can be added to the "Unscheduled" column, but should not remain there for more than a couple of weeks. Adding a task to the "unscheduled" column means a lot of people will poke you to get it scheduled, even with a rough ETA. :) * The short task description should be clear and understandable to anybody not being a member of the team. * The task either is connected to the team's workflows (i.e. it has relevant tasks as dependencies), or links into another tool like Trello when absolutely necessary. Many, but not all, of these tasks will be tagged #epic -- even when a feature has been well-tested and it's just a straightforward configuration switch to enable it, if/when we enable it in more languages/projects, we should ensure this is reflected in the roadmap.

Tracking Wikimedia-wide projects and when we expect they will arrive (see columns on the workboard). Criteria for adding a task to this project: * Task should only be added when describing a significant new piece of user-facing functionality (Features) or the launch of a new API or service (Platform). No bug fixes, refactoring, test coverage work, minor modifications, small UI tweaks or tracking tasks that cover a large backlog of work over huge time ranges. * Tasks have an initial expected date for this task that is agreed upon by the responsible project lead. If the date confidence is low, this should be indicated in the task description. When the date is revised, an explanation is added to the task. ** Tasks you want to make sure //get// on the roadmap ASAP can be added to the "Unscheduled" column, but should not remain there for more than a couple of weeks. Adding a task to the "unscheduled" column means a lot of people will poke you to get it scheduled, even with a rough ETA. :) * The short task description should be clear and understandable to anybody not being a member of the team. * The task either is connected to the team's workflows (i.e. it has relevant tasks as dependencies), or links into another tool like Trello when absolutely necessary. Many, but not all, of these tasks will be tagged #epic -- even when a feature has been well-tested and it's just a straightforward configuration switch to enable it, if/when we enable it in more languages/projects, we should ensure this is reflected in the roadmap.