- Mentioned In
- T862: Redesign Phabricator login page: LDAP login too prominent; position of MediaWiki SUL login not prominent enough
T180: Organize the "Wikimedia Phabricator Day 1 Project"
T697: Converting "See Also" Bugzilla links to Phabricator tasks
T188: Communicate the launch of Wikimedia Phabricator Day 1
T535: Document all the steps that need to be done during the Bugzilla migration
- Mentioned Here
- T552: https://bugzillapreview.wmflabs.org/ migration preview instance
T463: Enable registration for everybody at phabricator.wikimedia.org
T243: configure inbound email to go to iridium for phabricator.wikimedia.org
T199: Import non-test projects from fab.wmflabs.org to the official Wikimedia Phabricator
T373: get certificate for phab.wmfusercontent.org
T368: Upstream mediawiki oauth provider for Phabricator
T258: Publicly show which MediaWiki.org account a Phabricator account is associated with
T171: Determine license of the content submitted to Phabricator
T52: Phabricator should let you interact with external (non-Phabricator) users via email
T50: Restricting access to tasks based on project membership
T197: Proof of Concept the bugzilla and rt issue migration for mapping bug/tickets
qgil wrote on 2014-06-02 22:18:14 (UTC)
Turns out that we will pre-launch the official Wikimedia Phabricator instance with the Trusted User Tool, not Day 1. :) We have some to figure out the details.
qgil wrote on 2014-06-03 21:15:13 (UTC)
I have updated https://www.mediawiki.org/wiki/Phabricator/Plan#Migration_plan reflecting the two steps agreed prior to Day 1:
- Deploy Phabricator in a production server only with Wikimedia SUL enabled for log-in testing. T294 T314
- Deploy the Trusted User Tool using the Legalpad app only. T364
We still have to define / commit to @Rush's proposal to enable Maniphest and move just a few projects in a controlled environment. This would happen after the deployment of Trusted User Tool and before Day 1. Andre, Rush, if you still want pursue this, please create a task to discuss the details.
qgil wrote on 2014-07-21 16:14:36 (UTC)
Sorry for the dance of blocking tasks, whose objective was to have here an overview of the tasks / family of tasks that need to be completed in order to launch phabricator.wikimedia.org. There are many other critical tasks, but they should be subtasks of one of these.
qgil wrote on 2014-08-29 16:27:17 (UTC)
According to the plans, we have about five weeks to go before the launch of Wikimedia Bugzilla. Significant updates to this plan will be reflected in this task.
Many things happened since my last comment above and the migration from fab to phab. Summarizing:
WMF Engineering management (namely Erik and Rob) told us that it was good that we felt time pressure, but seeing all the progress done they recommended us to focus on a high quality and smooth release, at the expense of a later date if needed, "as long as we are talking about weeks and not months". Aspects like communication and "socialization" of the launch and the migration shouldn't be underestimated, they told us.
If we look at the wider context of Day 1, a WMF release, we can see how other software releases were received with a lot more push-back than expected, also with more bugs and unplanned problems than expected, which didn't help. If we look at our step from fab to phab we can see a bit of that as well. We didn't have the push-back, but the migration did go differently than expected by ourselves. This is why it is worth taking more time to plan properly, implement properly, test properly, communicate properly, and listen properly.
Now the migration timeline suggests a couple of dates, but dates are not what define that timeline anymore. What really matters is to move forward, making sure that every step is well completed. When Comms and Community Engagement asked us about the date of the launch, we asked them whether knowing it two weeks in advance was enough, ad they kind of agreed. I would say, let's focus on completing the production instance and the RT migration, and all the tiny bits of the Bugzilla migration. Then, when the main task is basically the migration itself, let's fix the date and let's put all our attention on this.
We have many "in progress" tasks (and many more if we look here in more detail). We can put date aside and focus on making steps forward focusing on resolving tasks for good. The next clear milestone is clear: T463: Enable registration for everybody at phabricator.wikimedia.org. What about focusing on its tasks kind of forgetting about the rest?
https://phabricator.wikimedia.org is now open to all Wikimedia users. The Phabricator-Production-Instance project is being archived after all its original tasks have been either resolved or pushed to the RT and/or Bugzilla migration projects.
The current plan is still to implement de RT migration and then the Bugzilla migration, although we need to work a bit in parallel because both projects require review periods from third parties.
The next task with a high public impact is T552: https://bugzillapreview.wmflabs.org/ migration preview instance.