From nobody Mon Jan 30 10:40:37 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P54TN3RzYz3cCKB for ; Mon, 30 Jan 2023 10:40:40 +0000 (UTC) (envelope-from pi@freebsd.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4P54TN304lz40p1 for ; Mon, 30 Jan 2023 10:40:40 +0000 (UTC) (envelope-from pi@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: from pi by home.opsec.eu with local (Exim 4.95 (FreeBSD)) (envelope-from ) id 1pMRaX-0004pU-Vs; Mon, 30 Jan 2023 11:40:37 +0100 Date: Mon, 30 Jan 2023 11:40:37 +0100 From: Kurt Jaeger To: Stephane Rochoy Cc: freebsd-current@freebsd.org Subject: Re: Tooling Integration and Developer Experience Message-ID: References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86357sxsly.fsf@cthulhu.stephaner.labo.int> X-Rspamd-Queue-Id: 4P54TN304lz40p1 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N 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. -- pi@opsec.eu +49 171 3101372 Now what ?