Re: [Wikitech-l] Phabricator migration update
Hello Andre! teams are definitely welcome to try out the Labs instance Can you say, how is the workflow for this? My team is only me (;)) with a very little project: https://www.mediawiki.org/wiki/Extension:GoogleLogin but maybe i can test, too, while using phabricator :) Thanks for answer! Kind regards, Floian Am 2014-07-23 00:43, schrieb Andre Klapper: Hi, On Fri, 2014-07-18 at 15:29 -0700, Steven Walling wrote: When we've migrated from Bugzilla, are you looking for teams to be guinea pigs and try out Phabricator? Overall, I feel like we're not going to get the real benefit until we migrate from Gerrit and the entire toolset is on Phabricator. That said, I think Growth would be interested in provisionally giving Phabricator a try as a Trello/Bugzilla replacement. Note that mail notifications can sometimes be delayed due (bug 65861). If you are aware that fab.wmflabs.org is an unstable service until migrated to production, and if you could deal with potential data loss (which has never happened so far), teams are definitely welcome to try out the Labs instance with a small project and provide more feedback. andre ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator migration update
when do you plan to launch fabricator on production? I would like to be a guinea pig with a number of small projects (wm-bot and huggle for beginning) On Wed, Jul 23, 2014 at 12:08 PM, Florian Schmidt florian.schmidt.wel...@t-online.de wrote: Hello Andre! teams are definitely welcome to try out the Labs instance Can you say, how is the workflow for this? My team is only me (;)) with a very little project: https://www.mediawiki.org/wiki/Extension:GoogleLogin but maybe i can test, too, while using phabricator :) Thanks for answer! Kind regards, Floian Am 2014-07-23 00:43, schrieb Andre Klapper: Hi, On Fri, 2014-07-18 at 15:29 -0700, Steven Walling wrote: When we've migrated from Bugzilla, are you looking for teams to be guinea pigs and try out Phabricator? Overall, I feel like we're not going to get the real benefit until we migrate from Gerrit and the entire toolset is on Phabricator. That said, I think Growth would be interested in provisionally giving Phabricator a try as a Trello/Bugzilla replacement. Note that mail notifications can sometimes be delayed due (bug 65861). If you are aware that fab.wmflabs.org is an unstable service until migrated to production, and if you could deal with potential data loss (which has never happened so far), teams are definitely welcome to try out the Labs instance with a small project and provide more feedback. andre ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator migration update
Hi Florian, On Wednesday, July 23, 2014, Florian Schmidt florian.schmidt.wel...@t-online.de wrote: Hello Andre! teams are definitely welcome to try out the Labs instance Can you say, how is the workflow for this? See Requesting a new project https://www.mediawiki.org/wiki/Phabricator/Help Your questions (and yourselves) are welcome! -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator migration update
Am 2014-07-23 14:43, schrieb Quim Gil: Hi Florian, On Wednesday, July 23, 2014, Florian Schmidt florian.schmidt.wel...@t-online.de wrote: Hello Andre! teams are definitely welcome to try out the Labs instance Can you say, how is the workflow for this? See Requesting a new project https://www.mediawiki.org/wiki/Phabricator/Help Your questions (and yourselves) are welcome! Hi Quim! See Requesting a new project https://www.mediawiki.org/wiki/Phabricator/Help Maybe next time i read first ;) Your questions (and yourselves) are welcome! Thanks :) Kind regards, Florian ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator migration update
On Wednesday, July 23, 2014, Petr Bena benap...@gmail.com wrote: when do you plan to launch fabricator on production? I would like to be a guinea pig with a number of small projects (wm-bot and huggle for beginning) The time of the Phabricator guinea pigs is now: https://www.mediawiki.org/ wiki/Phabricator/Help :) -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator migration update
Howdy! Wiadomość napisana przez Quim Gil q...@wikimedia.org w dniu 23 lip 2014, o godz. 15:16: https://www.mediawiki.org/ wiki/Phabricator/Help I'm just fixing a link here: https://www.mediawiki.org/wiki/Phabricator/Help Bye, Michał signature.asc Description: Message signed with OpenPGP using GPGMail ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator migration update
Hi, On Fri, 2014-07-18 at 15:29 -0700, Steven Walling wrote: When we've migrated from Bugzilla, are you looking for teams to be guinea pigs and try out Phabricator? Overall, I feel like we're not going to get the real benefit until we migrate from Gerrit and the entire toolset is on Phabricator. That said, I think Growth would be interested in provisionally giving Phabricator a try as a Trello/Bugzilla replacement. Note that mail notifications can sometimes be delayed due (bug 65861). If you are aware that fab.wmflabs.org is an unstable service until migrated to production, and if you could deal with potential data loss (which has never happened so far), teams are definitely welcome to try out the Labs instance with a small project and provide more feedback. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Phabricator migration update
Hi, this is a quick status update on the planned migration of our development planning tools to Phabricator. See https://www.mediawiki.org/wiki/Phabricator for general info. Several things have been worked on and achieved in the meantime: * WMF SUL Authentication has been implemented for Phabricator. * A separate server legalpad.wikimedia.org was deployed (a tool to manage trusted users - workflow to be further defined with Legal. * A data backup system for Phabricator in place. * Code to restrict access to tasks in a certain project is in place (same as Bugzilla's Security project) * The dedicated Phabricator server was upgraded to Ubuntu Trusty. * Packaging for Debian using pkg-php-tools/dh_php5 The identified tasks are listed on the planning board at http://fab.wmflabs.org/project/board/31/ Bugzilla: When it comes to the planning of how to convert data in Bugzilla tickets to Phabricator, we are mostly done. The elements that a Bugzilla report includes are listed in http://fab.wmflabs.org/T423 with links to subtasks. Obviously, Phabricator has a different UI and different workflow concepts than Bugzilla. While it's not the goal to have complete feature parity in every possible way, I'm pretty confident that we are close enough. As people are likely more interested in what Bugzilla functionality will be different, I'll try to summarize what I'm aware of: * Bugzilla's products, components and keywords will be turned into projects / tags in Phabricator. * Bugzilla votes will be turned into tokens. * Bugzilla's Severity field itself should get dropped - for example, if there is a real need to be able to search for critical severity (which translates to crash), it can become a crash project in Phabricator (think of keywords in terms of Bugzilla here). * For those ~50 users who have used Bugzilla's private Tags feature so far (introduced in February), this feature will be dropped, but you will get warned before. Similar, some Whiteboard data will likely also get dropped (or moved into the first comment if really considered relevant). Apart from that I am not aware of any other data we might drop or lose, or any other important functionality that would not be available in Phabricator. If you are passionate about a specific topic of task management / development workflows if you think after reading existing comments in the discussion of the related task that an important aspect has not been considered yet, please feel free to provide your input. To follow the progress of our Phabricator migration and to help, please see the planning board at http://fab.wmflabs.org/project/board/31/ Regular status updates are published at https://www.mediawiki.org/wiki/Phabricator/Migration#Status As usual, big thanks to Chase and Mukunda for their work, and to many others for providing input, feedback and help. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator migration update
On Fri, Jul 18, 2014 at 11:59 AM, Andre Klapper aklap...@wikimedia.org wrote: Hi, this is a quick status update on the planned migration of our development planning tools to Phabricator. See https://www.mediawiki.org/wiki/Phabricator for general info. Several things have been worked on and achieved in the meantime: * WMF SUL Authentication has been implemented for Phabricator. * A separate server legalpad.wikimedia.org was deployed (a tool to manage trusted users - workflow to be further defined with Legal. * A data backup system for Phabricator in place. * Code to restrict access to tasks in a certain project is in place (same as Bugzilla's Security project) * The dedicated Phabricator server was upgraded to Ubuntu Trusty. * Packaging for Debian using pkg-php-tools/dh_php5 The identified tasks are listed on the planning board at http://fab.wmflabs.org/project/board/31/ Bugzilla: When it comes to the planning of how to convert data in Bugzilla tickets to Phabricator, we are mostly done. The elements that a Bugzilla report includes are listed in http://fab.wmflabs.org/T423 with links to subtasks. Obviously, Phabricator has a different UI and different workflow concepts than Bugzilla. While it's not the goal to have complete feature parity in every possible way, I'm pretty confident that we are close enough. As people are likely more interested in what Bugzilla functionality will be different, I'll try to summarize what I'm aware of: * Bugzilla's products, components and keywords will be turned into projects / tags in Phabricator. * Bugzilla votes will be turned into tokens. * Bugzilla's Severity field itself should get dropped - for example, if there is a real need to be able to search for critical severity (which translates to crash), it can become a crash project in Phabricator (think of keywords in terms of Bugzilla here). * For those ~50 users who have used Bugzilla's private Tags feature so far (introduced in February), this feature will be dropped, but you will get warned before. Similar, some Whiteboard data will likely also get dropped (or moved into the first comment if really considered relevant). Apart from that I am not aware of any other data we might drop or lose, or any other important functionality that would not be available in Phabricator. If you are passionate about a specific topic of task management / development workflows if you think after reading existing comments in the discussion of the related task that an important aspect has not been considered yet, please feel free to provide your input. To follow the progress of our Phabricator migration and to help, please see the planning board at http://fab.wmflabs.org/project/board/31/ Regular status updates are published at https://www.mediawiki.org/wiki/Phabricator/Migration#Status As usual, big thanks to Chase and Mukunda for their work, and to many others for providing input, feedback and help. Cheers, andre Thanks for the update Andre, this plan sounds great. When we've migrated from Bugzilla, are you looking for teams to be guinea pigs and try out Phabricator? Overall, I feel like we're not going to get the real benefit until we migrate from Gerrit and the entire toolset is on Phabricator. That said, I think Growth would be interested in provisionally giving Phabricator a try as a Trello/Bugzilla replacement. -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator migration update
On Fri, Jul 18, 2014 at 3:29 PM, Steven Walling steven.wall...@gmail.com wrote: That said, I think Growth would be interested in provisionally giving Phabricator a try as a Trello/Bugzilla replacement. +1 -- Rob Moen Wikimedia Foundation rm...@wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
