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
On Fri, 8 Aug 2014, at 22:14, Legoktm wrote:
> Just use Bugzilla, most RfCs are already using it to track issues anyways.
>
> -- Legoktm
+1
I find some folks use Trello. I can't even darned add a comment there.
Svetlana
___
Wikitech-l mailing list
Wi
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" wrote:
> Collateral summary: a transition to Phabricator has started, and this
> project is just takin
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 wrote:
> Can we please not use Phabricator until it's an actual production
> service? We still don't have IRC notifications, mailing lists,
> docu
There is a Phabricator IRC bot, actually, but it was taken down because it
was just repeating information from other bots.
W dniu piątek, 8 sierpnia 2014 Legoktm
napisał(a):
> On 8/8/14, 12:14 PM, Quim Gil wrote:
> > From now on, Architecture RfC related tasks are handled in a Phabricator
> > pr
On 8/8/14, 12:14 PM, Quim Gil wrote:
> From now on, Architecture RfC related tasks are handled in a Phabricator
> project:
>
> http://fab.wmflabs.org/project/board/72/
>
> While the RfCs themselves will continue to be documented at
> https://www.mediawiki.org/wiki/Requests_for_comment , in Phabri
Yesterday at the Wikimania Hackathon, Brion, Gabriel, Quim, Rachel, Robla,
Tim, agreed on a series of little improvements to the Architecture RfC
process in order to distribute the effort and move the driving force from
the Engineering Community Team to the Architecture Committee.
From now on, Arc
