From nobody Mon Jan 30 21:09:21 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 4P5LVT18NQz3cZ4S for ; Mon, 30 Jan 2023 21:12:33 +0000 (UTC) (envelope-from dsl@mcusim.org) Received: from mcusim.org (mcusim.org [IPv6:2a00:dd80:3c::e63]) (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 4P5LVS6GvLz3wLG; Mon, 30 Jan 2023 21:12:32 +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 16BA28B689; Mon, 30 Jan 2023 22:12:30 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mcusim.org; s=default; t=1675113150; bh=wSfGNKYDNa/tGZLc7fsuk42JVvLVNj0StzzYs8aiibE=; h=References:From:To:Cc:Subject:Date:In-reply-to; b=trxC6fZcT91uxRTpS6TP+7IGfxpuu6ZMnctXqm43ezV/TlTWNHFDHRDzigKHavuUp 9Ez8cPyCGDaspbf/92zjPYXdJOVmb9sqxa01cEJbGjn2wCn0OgUAz5RCJUHOhEOBTr YECPLlaJ9ux45YDgWZlsV2FKJ3POE1jM+xwzZMZA= References: <202301300254.30U2sm0k061914@dell.no.berklix.net> <97020cad-f913-2985-2093-e4c23bf671e3@antonovs.family> <86357sxsly.fsf@cthulhu.stephaner.labo.int> <86edrcp13z.fsf@peasant.tower.home> <86zga0nf1q.fsf@peasant.tower.home> User-agent: mu4e 1.6.10; emacs 28.2 From: Dmitry Salychev To: Warner Losh Cc: Kurt Jaeger , Stephane Rochoy , freebsd-current@freebsd.org Subject: Re: Tooling Integration and Developer Experience Date: Mon, 30 Jan 2023 22:09:21 +0100 In-reply-to: Message-ID: <86sffrohfn.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: 4P5LVS6GvLz3wLG X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36236, ipnet:2a00:dd80:3c::/48, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N Maybe, but my laziness won't let me keep it that simple :) https://reviews.freebsd.org/H185 should do the trick, I think. Warner Losh writes: > I think just "sys/dev/dpaa2" is all you need when adding the Herald rule. :) > > More generally, no, there's no way that I've found to only match files that match certain regexp. > > Warner > > On Mon, Jan 30, 2023 at 9:49 AM Dmitry Salychev wrote: > > Warner Losh writes: > > > On Mon, Jan 30, 2023 at 7:07 AM Dmitry Salychev wrote: > > > > 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). > > > > 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 > > Looks really useful, thanks for a hint. Is there any way to test regexp > matching for files content? Btw, there could be a carefully selected set > of pre-defined Herald rules added to any new committer's account. > > -- > Dmitry Salychev -- Dmitry Salychev