Page MenuHomeFreeBSD

Status/2024Q4: Add _index and minor fixes
AbandonedPublic

Authored by salvadore on Jan 25 2025, 7:12 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Nov 27, 5:19 AM
Unknown Object (File)
Sun, Nov 23, 7:03 PM
Unknown Object (File)
Nov 8 2025, 2:15 AM
Unknown Object (File)
Nov 6 2025, 5:23 AM
Unknown Object (File)
Nov 2 2025, 7:24 AM
Unknown Object (File)
Oct 30 2025, 5:19 AM
Unknown Object (File)
Oct 30 2025, 12:37 AM
Unknown Object (File)
Oct 26 2025, 6:59 AM
Subscribers
None

Details

Summary

Adding intro and grouping entries; fixing minor syntax issues.
There are missing entries:

  • core
  • ci

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

We have the srcmgr report. Please put that one in the Teams section.

Thanks!

website/content/en/status/report-2024-10-2024-12/_index.adoc
16–20 ↗(On Diff #149969)

I would move the authors file earlier. The result should be the same, but it feels more logical to me.

Moreover, if in a future report an author is referenced in the introduction, the author entity would already be defined. (I believe such entities need to be defined before use, but I do not know it for sure.)

44–52 ↗(On Diff #149969)

The Teams section is for the most official FreeBSD teams, i.e. those in https://www.freebsd.org/administration/ (except doceng which goes into the documentation section). Other reports, even when they are the work of teams, are usually found in other sections. For example, we have a KDE team, but their work affects only ports, so their reports go in the Ports section.

Hence I would move the foundation-* reports elsewhere, but leave the freebsd-foundation.adoc report in the Teams section.

222 ↗(On Diff #149969)

We usually put this one in the Third Party section.

233 ↗(On Diff #149969)

This report is about work affecting the kernel, it is better to move it in the Kernel section.

website/content/en/status/report-2024-10-2024-12/intro.adoc
1–11 ↗(On Diff #149969)

I might have been unclear in a preceding e-mail about the introduction. Could you please write a brand new one, different from 2023Q4?

Keep only the first line with the number of entries. For the rest of the text, there are no rules nor traditions. You can check older introductions by other authors too to see different styles.

Feel free to sign it with your name and on behalf of the Status Team.

This revision now requires changes to proceed.Jan 28 2025, 11:32 AM

Updating after feedback

  • rearranged items
  • reworked _intro
  • addes srcmgr report

Thanks for the feedback, Lorenzo!
Now core and ci are the only ones left, if I'm not mistaken.

This revision was not accepted when it landed; it landed in state Needs Review.Feb 14 2025, 9:39 AM
This revision was automatically updated to reflect the committed changes.

Reopen revision automatically closed: we still miss to merge the _index.adoc file.

@freebsd_ny-central.org: It is better to do different commits for different kind of changes; likewise, it is better to have one single review for each single commit. Thus in this case it would have been better to have a review for the fixes, one for adding the introduction and one for adding the _index.adoc file.
Thanks for your work!

salvadore abandoned this revision.
salvadore edited reviewers, added: freebsd_ny-central.org; removed: salvadore.

Actually, on second thought, it is better to close this review: it has been automatically updated removing the _index.adoc file that we still need to merge...

@freebsd_ny-central.org: Could you please open a new review with that file? Thanks!