Re: Tooling Integration and Developer Experience

On Mon, Jan 30, 2023 at 7:07 AM Dmitry Salychev <dsl@mcusim.org> wrote:

>
> Hi,
>
> Kurt Jaeger <pi@freebsd.org> writes:
>
> > Hi,
> >
> >> > On 1/30/23 02:54, Julian H. Stacey wrote:
> >> >    The main idea: to prevent information fragmentation and    improve
> >> >    discoverability, cross-referencing abilities, search, etc.
> >>
> >> With regards to improving discoverability, Phabricator's Owner
> >> tool could be a good tactical move: it allow to bind code area to
> >> peoples in order to automatically add them to reviews.
> >
> > If you know phabricator in more detail, is there any kind of tool
> > to understand the activity going on ?
> >
> > In bugs.freebsd.org, there is the dashboard:
> >
> > https://bugs.freebsd.org/bugzilla/page.cgi?id=dashboard.html
> >
> > I think we might need something similar to help us understand
> > the current state of the phabricator instance and the work
> > being done.
> >
> > Phab allows Dashboards, but no-one had the time to configure some
> > queries to provide relevant stats.
>
> I'd prefer to have an automatic note via email from Phabricator if any
> file with my copyright was modified/patched/improved in a newly opened
> review.
>
> I don't think that people tend to ignore changes to those parts of code
> they've written (or touched at least).
>

You can easily create a herald rule to do this. I have one for all of src,
but others have subsets
like the boot loader. And anybody with an account can do that.

Warner