status: 2023q1: Add CI report
ClosedPublic
Actions

Authored by lwhsu on Apr 2 2023, 2:51 AM.

Details

Reviewers

salvadore

Group Reviewers

status

Commits

R9:5e28205f6974: status: 2023q1: Add CI report

Summary

status: 2023q1: Add CI report

Sponsored by:	The FreeBSD Foundation

Repository

R9 FreeBSD doc repository

Lint

Lint Not Applicable

Unit

Tests Not Applicable

lwhsu requested review of this revision.Apr 2 2023, 2:51 AM

grahamperrin added inline comments.

website/content/en/status/report-2023-01-2023-03/ci.adoc
18–19

website/content/en/status/report-2023-01-2023-03/ci.adoc
18–19	I think what is meant here is "and we also kept collaborating".
50	I remember you have already used tinyurl in past reports too, but is using it really necessary? The link will not appear anyway in the text, the clickable text will be `freebsd-testing@ related tickets`, so I do not think there is any advantage in having a short url. I recommend using direct links instead.

website/content/en/status/report-2023-01-2023-03/ci.adoc
18–19	I try to avoid the combination of and + also, even if the words are non-adjacent. Whilst there's no strict rule against the combination, there's usually a better way to structure a sentence. Food for thought: https://english.stackexchange.com/questions/171307/use-of-also-vs-and-also#comment372051_171307 and nearby comments/answers. Try this: During the first quarter of 2023 we continued working with the contributors and developers in the Project to fulfill their testing needs, and continued collaborating with external projects and companies to improve their products and FreeBSD.

website/content/en/status/report-2023-01-2023-03/ci.adoc
50	The main reason is this would be used in the email. Are we still sending the full compiled status report to mailing list? That gives a better look. Anyway I'm not insisting using shorten URL. Please let me know what's your preference.

website/content/en/status/report-2023-01-2023-03/ci.adoc
50	Yes, we still send status reports by email. However, looking at the archived version of the last status report, I see that no url appears in there: only the text `freebsd-testing@ related tickets`. https://lists.freebsd.org/archives/freebsd-announce/2023-January/000061.html Then yes please, I think it is better to use the original long URL.

website/content/en/status/report-2023-01-2023-03/ci.adoc
50	Then doesn't it mean some information lost during converting to a mail? :-) I will change to long URL and commit to the doc tree, along with other fixes. I suggest let's include the URL in the mail while sending.

website/content/en/status/report-2023-01-2023-03/ci.adoc
50	You can already add URLs to the email version as well, but not this way: you need to use `link:<URL>[]` instead. This is indeed what is used at the top of each report in the links section, where long URLs are not a problem. You might want to move your URLs to the links section. Moreover, I remind you that all emailed status report now include a link to the rendered version on the website, where all links are present. I do not have statistics about our readers, but I believe many use the email received only to get to that link.