Date: Mon, 30 Jan 2023 15:00:06 +0100 From: Dmitry Salychev <dsl@mcusim.org> To: Kurt Jaeger <pi@freebsd.org> Cc: Stephane Rochoy <stephane.rochoy@stormshield.eu>, freebsd-current@freebsd.org Subject: Re: Tooling Integration and Developer Experience Message-ID: <86edrcp13z.fsf@peasant.tower.home> In-Reply-To: <Y9eepV%2B%2Bch6qMBta@home.opsec.eu> References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> <Y9eepV%2B%2Bch6qMBta@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
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). -- Dmitry Salychev
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86edrcp13z.fsf>