This is one of the actions of the WMF-Call-To-Action, part of Support innovation & new knowledge.
More details to come.
This is one of the actions of the WMF-Call-To-Action, part of Support innovation & new knowledge.
More details to come.
Status | Subtype | Assigned | Task | |
---|---|---|---|---|
· · · | ||||
Invalid | None | T98348 Implement the Wikimedia Foundation Call to Action 2015 | ||
Invalid | None | T98358 WMF to integrate, consolidate, and pause or stop stalled initiatives | ||
Duplicate | None | T18 Plan to migrate code review from Gerrit to Phabricator | ||
Resolved | RobH | T100503 Close wikitech-announce mailing list | ||
Resolved | Aklapper | T101686 Goal: Define potential actions to reduce code review queues and waiting times | ||
Resolved | • Elitre | T106720 Team to "decommission" scarcely used team pages/communication venues | ||
Open | Feature | None | T66793 Make compact interlanguage links default | |
Resolved | MaxSem | T128896 Decide what to do with Wikidiff3 | ||
· · · |
@greg, I was about to list T18: Plan to migrate code review from Gerrit to Phabricator as blocker of this task but I thought about asking you first. :)
Is not "stalled" == "paused" or "stopped"? But, specifically, it (Gerrit -> Differential) is paused (though there is "20% time" spent on it) for now until next quarter.
Sorry, what I meant was: the investment in Gerrit is stalled and it's a dead end for us, hence the investment in integrating and consolidating code review in Phabricator, together with the project management processes already migrated.
I was checking what was the involvement of my team in each point of the Call to Action, and the association between this task and the code review migration came to mind. I find that projects contributing to the Call to Action have a double reason to be approved and executed, so there. :)
AAhhhhhhhhhhhhhh
I was checking what was the involvement of my team in each point of the Call to Action, and the association between this task and the code review migration came to mind. I find that projects contributing to the Call to Action have a double reason to be approved and executed, so there. :)
:) +1
Now that the project information template automatically adds quarter categories, it would be useful to check whether it's true that all this stuff is worked on (and if not, set the appropriate end date): https://www.mediawiki.org/wiki/Category:WMF_Projects_2015q3 currently has 106 members.
Ok, people had helped remove some 10 pages and now I've set an end for about 30 more: https://www.mediawiki.org/w/index.php?title=Special:Contributions&dir=prev&offset=20150727064345&limit=30&target=Nemo+bis
FINCH (see T76809#1592472 and following) might be an example here for a "pause/stalled" WMF initiative combined with potentially unclear responsibilities.
I don't feel like I know whether to archive the Phabricator project and decline its tasks or not, and its extension homepage is outdated vaporware.
...or T115430: Undeploy the 'Cologne Blue' and 'Modern' skins from Wikimedia production, as no-one is keeping them working which is about the open question which skins to have available on Wikimedia wikis.
Those skins are not a WMF initiative though, is this task for everyone's initiatives?