2023Q1/Status: Add intro.adoc

[salvadore]

Sorry, but I had zero inspiration. If anyone is willing to add something, please do it.

[carlavilla]

LGTM, only two minor things, the first is a total personal thing

website/content/en/status/report-2023-01-2023-03/intro.adoc

2

I'll remove the "here is the", sounds better for me, but I'm not a native speaker

4

Avoid the use of "you"

[grahamperrin]

In D39602#901381, @salvadore wrote:

Sorry, but I had zero inspiration.

Oh dear! Relax, take a break, clear your head :-)

If anyone is willing to add something, please do it.

I'll be willing, later. In the meantime, I guess that inspiration can spring from 13.2-RELEASE. Whilst the announcement came during the second quarter, the final release candidate was neatly in the first quarter:

• https://cgit.freebsd.org/src/log/?h=releng/13.2

– the one and only commit in April was administrative.

In addition to the eight highlights in the announcement, which we need not repeat in a status intro, I'd cherry-pick at least:

1. improvements to iwlwifi(4) for Intel
2. the introduction of rtw88(4) for Realtek
3. the introduction of graphics/drm-515-kmod (that is, intentionally a link to the FreshPorts page, not cgit), lead into this quarter's report for DRM drivers (i.e. GPU drivers)

– plus anything else that demonstrates FreeBSD becoming compatible with a (much) broader range of modern hardware.

Express the sum of last year's 13.1 leaps in compatibility plus this year's 13.2 leaps in compatibility as A Very Good Thing.

---

IMHO the greatest of last year's leaps was improved UEFI boot for amd64.

(I'm biased, because releases prior to 13.1 simply could not boot any of the new laptops that passed through my hands in my day job.)

[salvadore]

• Avoid using 'you'.
• Add some more details about 13.2-RELEASE.

[salvadore]

In D39602#901429, @grahamperrin wrote:

In D39602#901381, @salvadore wrote:

Sorry, but I had zero inspiration.

Oh dear! Relax, take a break, clear your head :-)

Maybe as a non-native English speaker I have given the impression that the situation is worse than it is: I only meant that I had no idea what to write in the introduction. Do not worry, I am fine :)

1. improvements to iwlwifi(4) for Intel
2. the introduction of rtw88(4) for Realtek

I have used those two suggestions to improve the introduction: they fit well since in the past we had reports about these topics. I think now the introduction is good enough.

website/content/en/status/report-2023-01-2023-03/intro.adoc

2

I prefer to keep it as otherwise the line would look as a second title. I have also merged the sentence with the next one to avoid another use of you.

[grahamperrin]

website/content/en/status/report-2023-01-2023-03/intro.adoc

4

5

driver (singular)

[salvadore]

• Fixes suggested by grahamperrin

[grahamperrin]

website/content/en/status/report-2023-01-2023-03/intro.adoc

2

Is one more expected?

I count 25 reports:

{F59706173}

[salvadore]

• Fix number of reports

Thanks @grahamperrin, I had miscounted. Maybe I counted intro.adoc as a report.