From nobody Mon Jan 30 15:33:08 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 4P5Bz76vH0z3bVF8 for ; Mon, 30 Jan 2023 15:33:23 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P5Bz74d23z429M for ; Mon, 30 Jan 2023 15:33:23 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x531.google.com with SMTP id v13so11292194eda.11 for ; Mon, 30 Jan 2023 07:33:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=JUZNKvTjSvKDI12MelwQD9cB5Rbqw8EdsRBudWXIneY=; b=QhY79fyY+kObF29K6DkFMzEkSLSC+XajK/GGt7GpX52K560gczBPPPF2pG332aJldh 9E5s0mwbU15VrsBAkP/wVHluBtbvXBkqkrwzCZrxE5PkALbDW3tXCDt7V9jIoZ2Kh5qN SiXOZ9a10gPEidHhTPWDYDegFQiIkptoHa+vOCTSdSa9epPQePg+O6O3WPmBAaE07C8k X/SI2Lnw0D7qUUlMJjm8jn784RmW6vQVIMToQnQK7gYn2+RjbHbd6uO4GC006VUmfvNe WDog3EH35KL6J+PfxoW2BPhfSCw8+bTRIdKypns8WgKYRdoSD6N7dIjV7fSMOhD+NGbN DqUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=JUZNKvTjSvKDI12MelwQD9cB5Rbqw8EdsRBudWXIneY=; b=DWa0XRxZLGv59ZHvJ+YruJMivkHO0Ku3MFAMivIskwvvlVJ1tihMEXEdJlUrtrFpCK dAEk3Yl3ckxKkFZ58j0HsK1kETp4XWjW4UT9+KhjfLFVjwKCZ/xaJ3dYRR7WjeJxbwvV nqCTYcWTq75T5PkCuyu2wq8ovmslHR7lpg8XpxF/HNx9/2HkGqvqXx0sFqLUM+55SLHc IYXK96qNahKfEvWh4KISpEK4gXjIWgmPvdbT263WpBMD+0+Y9kHXgjQo/NR6a09eVdlq w2pdDHPMmQrtvg4lz6OEb8VxN31Vm7DpYwTLY+nbM+42ITFgk0xt3nZb7oPS5NHAeZZS sCcw== X-Gm-Message-State: AO0yUKWkit0ojZ7/dIrB/Z+7FQtB+1F9dMwBHaamrf2bjSoJEXwgdcOK 5ui9z5Ho8qhkDu4FoebQHhV35vCLK1KfXimFyAsaxQ== X-Google-Smtp-Source: AK7set933+BTslcydArj6BIeGRg+eOzvy8zHs0k0jmB+cth03NrSEvb+dnxK5INeFb+B+BoTCuDHBhvlT2yyUoMGyfM= X-Received: by 2002:a05:6402:1241:b0:4a2:408e:ce5 with SMTP id l1-20020a056402124100b004a2408e0ce5mr1578032edw.24.1675092802180; Mon, 30 Jan 2023 07:33:22 -0800 (PST) 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 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> In-Reply-To: <86edrcp13z.fsf@peasant.tower.home> From: Warner Losh Date: Mon, 30 Jan 2023 08:33:08 -0700 Message-ID: Subject: Re: Tooling Integration and Developer Experience To: Dmitry Salychev Cc: Kurt Jaeger , Stephane Rochoy , freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="00000000000070b97c05f37cef62" X-Rspamd-Queue-Id: 4P5Bz74d23z429M X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000070b97c05f37cef62 Content-Type: text/plain; charset="UTF-8" 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 --00000000000070b97c05f37cef62 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Jan 30, 2023 at 7:07 AM Dmitr= y Salychev <dsl@mcusim.org> wro= te:

Hi,

Kurt Jaeger <pi@free= bsd.org> writes:

> Hi,
>
>> > On 1/30/23 02:54, Julian H. Stacey wrote:
>> >=C2=A0 =C2=A0 The main idea: to prevent information fragmentat= ion and=C2=A0 =C2=A0 improve
>> >=C2=A0 =C2=A0 discoverability, cross-referencing abilities, se= arch, etc.
>>
>> With regards to improving discoverability, Phabricator's Owner=
>> tool could be a good tactical move: it allow to bind code area to<= br> >> 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=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 some
> queries to provide relevant stats.

I'd prefer to have an automatic note via email from Phabricator if any<= br> 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).

<= div>You can easily create a herald rule to do this. I have one for all of s= rc, but others have subsets
like the boot loader. And anybody wit= h an account can do that.

Warner
=C2= =A0
--00000000000070b97c05f37cef62--