From nobody Mon Jan 30 14:00:06 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 4P594B4G0Bz3bHVm for ; Mon, 30 Jan 2023 14:07:38 +0000 (UTC) (envelope-from dsl@mcusim.org) Received: from mcusim.org (mcusim.org [176.58.93.53]) (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 4P594B2KWQz3hNs; Mon, 30 Jan 2023 14:07:38 +0000 (UTC) (envelope-from dsl@mcusim.org) Authentication-Results: mx1.freebsd.org; none Received: from localhost (unknown [193.164.254.100]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mcusim.org (Postfix) with ESMTPSA id 902408A333; Mon, 30 Jan 2023 15:07:29 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mcusim.org; s=default; t=1675087649; bh=o93dmjfiLK1obY99IWV5urvPPRs1zqrHUayX+QrNJ78=; h=References:From:To:Cc:Subject:Date:In-reply-to; b=xA61RPxTZL32qWYZAq5rqexAM5bvmhC8fvgfCjCT/RzNjH4zGlaIxIBSq8t6p8ouA igE9jFf8ik5ZOcmWXi6UNcQMTtvmHU2PI+IfHNW93P6AePt8Fzv6oIrOwA207oXrKh dBfK2/J9tXRCn+UjAC4Z8iQwnQBhk0ncBSyud9Ng= References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> User-agent: mu4e 1.6.10; emacs 28.2 From: Dmitry Salychev To: Kurt Jaeger Cc: Stephane Rochoy , freebsd-current@freebsd.org Subject: Re: Tooling Integration and Developer Experience Date: Mon, 30 Jan 2023 15:00:06 +0100 In-reply-to: Message-ID: <86edrcp13z.fsf@peasant.tower.home> 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 X-Rspamd-Queue-Id: 4P594B2KWQz3hNs X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36236, ipnet:176.58.93.0/24, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Hi, Kurt Jaeger 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