Alright, let's find a compromise: we will make sure that any Architecture task fitting in Bugzilla will have a Bugzilla report. We will continue using Phabricator for all the rest. Let's talk again when we have a Phabricator instance in production (in a few weeks, according to plans).
For instance,"Schedule wednesday rfc meeting for european team next week Aug 13" http://fab.wmflabs.org/T528 could be closed as a perfectly INVALID report in Bugzilla, yet it has a function in our little project in Phabricator. If Labs goes down, we will manage. PS: It is a fact that we have "real work" projects in fab.wmflabs.org today, and thanks to this we are learning and testing a lot. It would have been crazy to go from "Test Foo Blah" tasks to Phabricator Day 1 without this phase of experimentation and compromises in between. On Fri, Aug 8, 2014 at 6:10 PM, Chad <[email protected]> wrote: > It's unfortunate that it's being used for prod data. I never intended that > when it was set up. > > So yeah +1 to waiting until we have a real prod service. > > -Chad > On Aug 8, 2014 3:07 PM, "Quim Gil" <[email protected]> wrote: > > > Collateral summary: a transition to Phabricator has started, and this > > project is just taking advantage of it. > > > > On Fri, Aug 8, 2014 at 1:14 PM, Legoktm <[email protected]> > > wrote: > > > > > Can we please not use Phabricator until it's an actual production > > > service? We still don't have IRC notifications, mailing lists, > > > documentation, etc. Most people don't even look at it because, well, > > > it's a test instance, not an actual thing people should be using. > > > > > > > Phabricator is supposed to become an actual production service within a > few > > weeks. We are using it here for tracking tasks more than tracking bugs, > and > > the workboard is a useful interface to see at a glance which RfCs are > ready > > to be reviewed. > > > > Lack of IRC notifications is not a dealbreaker in this project, since we > > didn't have it either in the purely MediaWiki-base process we had before. > > Mailing lists... will be used in the same way. Documentation... what do > you > > need? Please check and ask at > > https://www.mediawiki.org/wiki/Phabricator/Help > > > > Most people probably don't need to look at this project. For the > architects > > and the few other people that have to follow it, I'm sure that > > notifications will work just fine. > > > > I'm also reminded of Mark's comments in [1]: If a URL has "wmflabs.org" > > > in it...don't put anything, ANYTHING, important there. > > > > > > > For what is worth, some projects are posting important information in > this > > Phabricator instance, and its content is being backed up periodically. > > _______________________________________________ > > Wikitech-l mailing list > > [email protected] > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
