I meant talking about Phab in R&D Staff at 1:30pm Pacific tomorrow,
but Kevin and I talk about Phab & prioritization process at the 7:30am
Pacific Combined staff meeting.

Agenda items I have for Combined staff are:

Visualization roadmap for EL
Product Instrumentation & Visualization goals for Q3:

   -
   
https://www.mediawiki.org/wiki/Wikimedia_Engineering/2014-15_Goals/Q3#Product_Instrumentation_and_Visualization
   -


On Mon, Dec 15, 2014 at 10:57 AM, Toby Negrin <[email protected]> wrote:

> Sure -- I need to send out an agenda for consolidated staff tomorrow, but
> perhaps you and Kevin can share your experiences and talk about the dev
> process and use of fab?
>
> [Note -- we will have staff tomorrow]
>
> -Toby
>
> On Mon, Dec 15, 2014 at 10:53 AM, Grace Gellerman <
> [email protected]> wrote:
>>
>> Should we talk more about this in our Research staff meeting on Tuesday?
>>
>> I agree that we need to figure out prioritization process first.  Also
>> keeping two systems active could lead to requests going into two places
>> which could affect the workflow of prioritization.
>>
>> I see the advantages to using Phab, but haste can sometimes, ya know,
>> make waste.  So let's talk about this more...
>>
>> On Mon, Dec 15, 2014 at 10:48 AM, Toby Negrin <[email protected]>
>> wrote:
>>
>>> To be clear - I do not want to move to Fabricator without reviewing our
>>> prioritization process.
>>>
>>> Shall we make this a Q3 goal since people seem really into it?
>>>
>>> On Dec 15, 2014, at 10:44 AM, Leila Zia <[email protected]> wrote:
>>>
>>> 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 <[email protected]
>>> > 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
>>>> [email protected]
>>>> https://lists.wikimedia.org/mailman/listinfo/analytics
>>>>
>>>> _______________________________________________
>>> Analytics mailing list
>>> [email protected]
>>> https://lists.wikimedia.org/mailman/listinfo/analytics
>>>
>>>
>>> _______________________________________________
>>> Analytics mailing list
>>> [email protected]
>>> https://lists.wikimedia.org/mailman/listinfo/analytics
>>>
>>>
>>
>> _______________________________________________
>> Analytics mailing list
>> [email protected]
>> https://lists.wikimedia.org/mailman/listinfo/analytics
>>
>>
> _______________________________________________
> Analytics mailing list
> [email protected]
> https://lists.wikimedia.org/mailman/listinfo/analytics
>
>
_______________________________________________
Analytics mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/analytics

Reply via email to