Hi Oliver,
I'd like to give Phabricator a try. I suggest the following steps if we
decide to do it:
1. We block a 15-min team time in December during which R&D will play
with Phabricator in
https://phab-01.wmflabs.org/ If we all feel
reasonably comfortable, then,
2. We switch to Phabricator in January, at the beginning of Q3, and we
aim to try it for one quarter [1]. If it works, great, if not,
3. We go back to Trello.
Leila
[1] During the quarter, we keep Trello but we don't update it. If we figure
out some time during the quarter that we can't work with Phabricator at
all, we switch back to Trello and all we need to do is to add Q3's tasks
back to it.
On Mon, Dec 15, 2014 at 7:48 AM, Dan Andreescu <dandreescu(a)wikimedia.org>
wrote:
So those are the reasons I have, off the top of my head. Other reasons?
Counter-arguments? Post em here.
Agreed, Phabricator is a good tool, and great if it creates a single place
where we manage our projects.
It's not all great though. Trello has a much more refined notification
system and much prettier interface. Mingle has more powerful queries,
Asana is more to the point, etc. We've been over these and decided as an
organization to move towards Phabricator, I'm certainly not trying to dig
up old wounds. I do want to say though: bring those positive experiences
when you switch from a system you like. Because Phabricator is open source
and the Facebook team that maintains it has been super friendly and helpful
to us during our migration. If we criticize it constructively, Phabricator
will only get better.
_______________________________________________
Analytics mailing list
Analytics(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics