From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
by lore.proxmox.com (Postfix) with ESMTPS id 788A61FF168
for <inbox@lore.proxmox.com>; Tue, 4 Feb 2025 10:53:24 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id AFD4F10CF8;
Tue, 4 Feb 2025 10:53:22 +0100 (CET)
Mime-Version: 1.0
Date: Tue, 04 Feb 2025 10:52:48 +0100
Message-Id: <D7JKIHEE0XZW.1WGVRUD004T88@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
From: "Max Carrara" <m.carrara@proxmox.com>
X-Mailer: aerc 0.18.2-0-ge037c095a049
References: <20250203142801.3-1-a.zeidler@proxmox.com>
<D7IY3VJ9GQ4Y.1PVI9Q4QY950A@proxmox.com>
<D7JJVD5FQZMH.22W20LB84CWM7@proxmox.com>
In-Reply-To: <D7JJVD5FQZMH.22W20LB84CWM7@proxmox.com>
X-SPAM-LEVEL: Spam detection results: 0
AWL 0.066 Adjusted score from AWL reputation of From: address
BAYES_00 -1.9 Bayes spam probability is 0 to 1%
DMARC_MISSING 0.1 Missing DMARC policy
KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
Validity was blocked. See
https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
information.
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
Subject: Re: [pve-devel] [PATCH docs 1/6] ceph: add anchors for use in
troubleshooting section
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
On Tue Feb 4, 2025 at 10:22 AM CET, Alexander Zeidler wrote:
> On Mon Feb 3, 2025 at 5:19 PM CET, Max Carrara wrote:
> > On Mon Feb 3, 2025 at 3:27 PM CET, Alexander Zeidler wrote:
> >> Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
> >> ---
> >
> > Some high-level feedback (see comments inline and in patches otherwise):
> >
> > - The writing style is IMO quite clear and straightforward, nice work!
> Thank you for the review!
>
> >
> > - In patch 03, the "_disk_health_monitoring" anchor reference seems to
> > break my build for some reason. Does this also happen on your end? The
> > single-page docs ("pve-admin-guide.html") seem to build just fine
> > otherwise.
> Same for me, I will fix it.
>
> >
> > - Regarding implicitly / auto-generated anchors, is it fine to break
> > those in general or not? See my other comments inline here.
> >
> > - There are a few tiny style things I personally would correct, but if
> > you disagree with them, feel free to leave them as they are.
> I will look into it! Using longer link texts sounds good!
>
> >
> > All in all this seems pretty solid; the stuff regarding the anchors
> > needs to be clarified first (whether it's okay to break auto-generated
> > ones & the one anchor that makes my build fail). Otherwise, pretty good!
> See my two comments below.
>
> >
> >> pveceph.adoc | 8 ++++++++
> >> 1 file changed, 8 insertions(+)
> >>
> >> diff --git a/pveceph.adoc b/pveceph.adoc
> >> index da39e7f..93c2f8d 100644
> >> --- a/pveceph.adoc
> >> +++ b/pveceph.adoc
> >> @@ -82,6 +82,7 @@ and vocabulary
> >> footnote:[Ceph glossary {cephdocs-url}/glossary].
> >>
> >>
> >> +[[pve_ceph_recommendation]]
> >> Recommendations for a Healthy Ceph Cluster
> >> ------------------------------------------
> >
> > AsciiDoc automatically generated an anchor for the heading above
> > already, and it's "_recommendations_for_a_healthy_ceph_cluster"
> > apparently. So, there's no need to provide one here explicitly, since it
> > already exists; it also might break old links that refer to the
> > documentation.
> For this I searched our forum before, it shows 12 results, the heading
> was only added about a year ago. But apart from this specific anchor,
> IMHO it can be okay to break such links in certain cases:
>
> * The main reasons for not using the auto generated ones are, that those
> are not stable (in case of changing the title) and can also be very
> long when using it with xref:...[...]. Such lines get even longer (and
> an awkward combined name) when using it as a prefix for sub sections
> (as often done).
> * Since with the break there might have been added new or updated
> information in those chapters/sections, old forum posts may no longer
> be accurate anyway.
> * In the Ceph chapter for example, we have been using the explicit
> "pve_ceph_" or "pveceph_" for years, so IMHO it should (almost
> always?) be added with adding a new section.
>
> >
> > Though, perhaps in a separate series, you could look for all implicitly
> > defined anchors and set them explicitly..? Not sure if that's something
> > we want, though.
> This would break a lot of links at the same time, so far I am not aware
> about a notable benefit.
>
I agree with all of your points made here; so, all in all, great work!
Ping me when you shoot out v2, then I'll have one last look. :)
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel