Date: Mon, 30 Jan 2023 15:31:02 +0100 From: Stephane Rochoy <stephane.rochoy@stormshield.eu> 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: <861qncxffd.fsf@cthulhu.stephaner.labo.int> 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
Kurt Jaeger <pi@freebsd.org> writes: > 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=3Ddashboard.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=20 > some > queries to provide relevant stats. AFAIK, dashboards are just a way to gather data from the various applications. In our case, the relevant one is Differential which means we're limited to what its query engine [1] allow us to do. My guess is that playing with the "Repositories", "Statuses" and "Created After" fields should be OK to get to the "Bug Summary" but it would give you lists of bugs, not the amounts of bugs. The "Useful Queries" are more tricky. Maybe by putting tags (e.g., to identify required backports, etc=E2=80=A6) in use something could be done. If not, the Conduit API could be worth a look. [1] https://reviews.freebsd.org/differential/query/advanced/ Regards, -- St=C3=A9phane Rochoy O: Stormshield
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?861qncxffd.fsf>