From nobody Mon Jan 30 17:06: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 4P5F2h66Qrz3bygd for ; Mon, 30 Jan 2023 17:06:36 +0000 (UTC) (envelope-from yklaxds@gmail.com) Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (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 4P5F2h475Kz4L5K; Mon, 30 Jan 2023 17:06:36 +0000 (UTC) (envelope-from yklaxds@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vs1-xe2c.google.com with SMTP id j7so13167620vsl.11; Mon, 30 Jan 2023 09:06:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.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=qxxVdtJql45H9c1FJpz32YKMsD/AXOqCznkVlhy2HdU=; b=HXrDT1OWLwvVz3wbtzauAJjq9xznNMIDcMCPOzMMF6wpH7tc+hcIsIoSWyNO/wEYof W1B6kE5SY69BkjJduFMSssHNf5/5m+tgBnF1OedkfkdFg/MmxNRpxDmwxJ0siY0+Kbz7 p3EOH+jx3/yGu9sRjfgZ+TYhDKfybbESypTbwA65TuXa7U9NE3wkMev++ffvcvcoRnf4 crpK0N4r4J8YaPL5CAJEAsnft/S3u97nmZz8dMs6SfVs9TbaOWAsGZweGGYK71T8KwK8 VC46IgtIKTVrB3y12Tj86q1zqd/eA86fQH1ejkVLUNm1k8odcdYkiG60fOr1AQbHi4rV Fa6Q== 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=qxxVdtJql45H9c1FJpz32YKMsD/AXOqCznkVlhy2HdU=; b=bVtKCOuZr/C9OKbT16Y+L+vbfghdFmfP8nnL/5ySNc582+BBFOcNID9+AhJ2bsjHdY uQRMF9w35ZA0Io17OJKRUbc1CTQ6N4XnSaYZ6/APzqS6vzMvXzdDdFkKdSr7dZGJl+G0 u8MdalbVFoptXzenECsyCyjFVqdJnzA47e71ikBEgw/2WP5X6URieU3nqDaN8VNgguQp Dt/VHBVppHHWs5v+41zoDfbEkk7A0RcVVXz4b4eTWpkwyl7LNSnjKDIzizSLj7ufx6et mA5QJHfyYQsrDjP703z76whzVwNBBzTxdtkcrFbje44CYlt641bM/CIROfqrSaQgc8Jg ZDCQ== X-Gm-Message-State: AO0yUKUUC3zv+q93ZkuyG8TDi5JYne8/iSK8STkhDiN81t9W2jZ6H/gQ NMdCCJba26ihmpjpKFDUhoIdWr351dnfYj1mtw06cXLS/lbgR0Oitnw= X-Google-Smtp-Source: AK7set+0YvWFxY/ow2/rri2o5ipKNHMAWCl2sa5/fwbH1Emgxm2BzBS+psN6msRvoEi5EKma13dtXSz09Ca0im/j8tA= X-Received: by 2002:a67:c31e:0:b0:3ed:1e92:a87f with SMTP id r30-20020a67c31e000000b003ed1e92a87fmr1836364vsj.1.1675098395499; Mon, 30 Jan 2023 09:06:35 -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> In-Reply-To: From: ykla Date: Tue, 31 Jan 2023 01:06:21 +0800 Message-ID: Subject: Re: Tooling Integration and Developer Experience To: Kurt Jaeger Cc: freebsd-current@freebsd.org Content-Type: multipart/alternative; boundary="000000000000d3e25605f37e3c7c" X-Rspamd-Queue-Id: 4P5F2h475Kz4L5K X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000d3e25605f37e3c7c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, The documentation project on reviews.freebsd.org is also very inactive. For example, it's been almost 3 months since I submitted my revision - https://reviews.freebsd.org/D37322. After I submitted it, it was neither reviewed nor approved for a long time. Now, due to changes in the FreeBSD documentation, some of my changes conflict with the current documentation and are difficult to resolve. I suppose I could spend some time going over it again and again, but if no one accepts it, it is pointless. Maybe I shouldn't make such extensive changes to the documentation.Can you advise me on how I should go about doing this? Thanks a lot. ykla Kurt Jaeger =E4=BA=8E2023=E5=B9=B41=E6=9C=8830=E6=97=A5=E5= =91=A8=E4=B8=80 18:33=E5=86=99=E9=81=93=EF=BC=9A > Hello, > > > I had a similar thing happen to me, the mailing list FreeBSD-doc seemed > to > > exist as if no one existed, and there was no one posting in it except f= or > > the automated bug reports from the bots. > > I have not had any replies to my several posts either. > > > So can the admins tell how many people actually > > subscribe to FreeBSD-doc, > > The list has 496 subscribers right now. (speaking as one of postmaster@). > > > or is this just a place to report bugs and people > > should discuss FreeBSD doc-related issues elsewhere? Or is it that almo= st > > nobody cares about the FreeBSD documentation? > > From my observation, the last few month led to a huge pile of > workload on many folks that are involved with FreeBSD stuff, so > not many folks had time to reply/think things through/answer. > I had the same problem... > > I see doc-stuff happen mostly on reviews.freebsd.org. (speaking > as one of phabric-admins). Pau Amma is the most active docs-person > as far as I can see. I have not calculated stats, just my gut feeling. > > -- > pi@opsec.eu +49 171 3101372 Now what ? > > --000000000000d3e25605f37e3c7c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,=C2=A0

The documentation = project on reviews.freebsd.org i= s also very inactive. For example, it's been almost 3 months since I su= bmitted my revision - https:= //reviews.freebsd.org/D37322. After I submitted it, it was neither revi= ewed nor approved for a long time. Now, due to changes in the FreeBSD docum= entation, some of my changes conflict with the current documentation and ar= e difficult to resolve. I suppose I could spend some time going over it aga= in and again, but if no one accepts it, it is pointless. Maybe I shouldn= 9;t make such extensive changes to the documentation.Can you advise me on h= ow I should go about doing this? Thanks a lot.

ykla

Kurt Jaeger <pi@freebsd.org&g= t; =E4=BA=8E2023=E5=B9=B41=E6=9C=8830=E6=97=A5=E5=91=A8=E4=B8=80 18:33=E5= =86=99=E9=81=93=EF=BC=9A
Hello,

> I had a similar thing happen to me, the mailing list FreeBSD-doc seeme= d to
> exist as if no one existed, and there was no one posting in it except = for
> the automated bug reports from the bots.
> I have not had any replies to my several posts either.

> So can the admins tell how many people actually
> subscribe to FreeBSD-doc,

The list has 496 subscribers right now. (speaking as one of postmaster@).
> or is this just a place to report bugs and people
> should discuss FreeBSD doc-related issues elsewhere? Or is it that alm= ost
> nobody cares about the FreeBSD documentation?

>From my observation, the last few month led to a huge pile of
workload on many folks that are involved with FreeBSD stuff, so
not many folks had time to reply/think things through/answer.
I had the same problem...

I see doc-stuff happen mostly on reviews.freebsd.org. (speaking
as one of phabric-admins). Pau Amma is the most active docs-person
as far as I can see. I have not calculated stats, just my gut feeling.

--
pi@opsec.eu=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +49 171 3101372=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Now what ?

--000000000000d3e25605f37e3c7c--