Also a random reply.

I think this kind of effort is more likely to be successful if it gets
input and buy-in from the key stakeholders.  In this case that would be the
most frequent reviewers.

It would be nice to run a bugzilla query to find the top 10 or 20
reviewers.  Talk to these folks, solve their problems, and get buy-in for a
solution.  The rest of the org will likely follow their lead.

Right now, though, I talk to people who spend all day reviewing and they
tell me no one ever talked to them.

I know feedback was collected, but maybe not from this group.

Anyway, just a suggestion.

Ben

On Jul 14, 2017 11:34 AM, "Milan Sreckovic" <msrecko...@mozilla.com> wrote:

> Replying in general, to a random message :)
>
> I don't have the numbers, but I imagine reviews are happening in the
> hundreds every day (if we land almost 300 patches.)  So, I wouldn't expect
> the conversation about adding/removing/changing tools involved in reviews
> to be any less complicated, passionate and involved as what we're having
> here :)
>
> I believe Mark is putting together an e-mail to give us a better place to
> continue these conversations; something with meta bugs for "enable
> phabricator", "disable splinter", etc.  This should let us track the issues
> that are raised, discuss decisions as to which of those should be blockers,
> and have a better record of what actually gets resolved and how.
>
> This should leave us *just* with the decision making and communication
> rollout issues that were raised; I know we are continuously discussing
> those and trying to get better at it, but it is a separate conversation
> from the technical issues, so it's probably OK that it remains separate.
>
>
> On 13-Jul-17 15:41, Randell Jesup wrote:
>
>> To answer the other part of your question, MozReview will be disabled for
>>>>> active use across the board, but it is currently used by a small
>>>>> number of
>>>>> projects.  Splinter will be disabled on a per-product basis, as there
>>>>> may be
>>>>> some projects that can't, won't, or shouldn't be migrated to
>>>>> Phabricator.
>>>>>
>>>> Splinter is still a nice UI to look at patches already attached to bugs.
>>>> Please don't disable it.
>>>>
>>> excellent point; thanks for that feedback.
>>>
>>> instead of disabling splinter for phabricator backed products, we could
>>> make it a read-only patch viewer.
>>>
>> I would consider it a massive fail if we disabled at least read-only
>> splinter viewing of patches.  As noted before.....  let's make sure we
>> don't lose things we agreed on as issues.
>>
>>
> --
> - Milan (mi...@mozilla.com)
>
> _______________________________________________
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to