freebsd / freebsd-quarterly

FreeBSD quarterly reports

FreeBSD Quarterly Status Reports

This repository was used to collect and review FreeBSD quarterly status reports from 2017Q4 through 2022Q4. It is now archived.

Please check the FreeBSD status reports webpage for up to date information about FreeBSD status reports collection, reviewing and publication.

freebsd-quarterly's Issues

Migrate from github to cgit.f.o/doc

Following up on #323, it is now possible to migrate from github to cgit.f.o/doc, but there's a couple of things that need to be addressed before this can happen, if it is to happen.

First, we need to address the elephant in the room, which is that there's no longer any pull requests.

For commiters, means they'll need approval for adding to the status report folder - this can, and should, be a blanket approval for any file which isn't _index.adoc (doceng@ may need to approve this?).
It it helped along by the tooling available, in that textproc/rubygem-asciidoctor can serve as a linter, and reviews.f.o can be used as a staging area for collaborative entries, which itself is helped along by src/tools/tools/git/git-arc.sh and it's manual page which are available simply by doing make build and make install

For contributors, this means suggesting either using reviews.f.o for easy feedback from the status report team, or collaboration with other contributors, or the use of git format-patch to craft patches can be sent via email, as this creates mailbox format patch (which can be applied with git am) that keeps the all the relevant meta-data.

All of the necessary information should be collected in status/howto.adoc which should be accessible from here or somewhere equally centrally located. @sergio-carlavilla should probably be involved, since at present the howto doesn't appear to work.

Possible typo in Foundation report

Open system call path handling support for O_BENEATH, O_RESLOVE_BENEATH

Shouldn't that last one be O_RESOLVE_BENEATH instead?

Policy regarding links in description

Hey!

Historically, status reports had a link section before the actual status report text, and no links in the status report text itself. I think it was a limitation due to the XML files we had to generate to send status reports.

Does this limitation still applies, or are we free to use the markdown markup to add links to the text of new status reports (like this one)?

Missing RSS feed

Not sure this is the right place to report this, but I have been unable to locate an RSS feed for the reports - but would very much like to have one.

Can you please advise where the right place to make such a bug report would be?

Thanks in advance

2020q3/nfsovertls.md missing period.

There's a period missing in 2020q3/nfsovertls.md, after the https://people.freebsd.org/~rmacklem/nfs-over-tls-setup.txt raw URL. I'm not sure how to fix it without the . being taken as part of the URL, though. Is there a reference somewhere for whatever markdown flavor the quarterly reports use, or somewhere I could glean the proper syntax to delimit URLs from? I can submit a pull request, if there is.

2020q4/embedded-lab.md nits

Submitting this as an issue instead of a pull request because I'm not sure for the first what exactly was meant, and the last may not be an error at all.

• "have a basic set of FreeBSD installed that matches the board." Possible fixes: s/FreeBSD/FreeBSD packages/ or s/set of // (or, if neither is applicable, perhaps explain what "a basic set" means here)
• "with a environment due to power issues" s/ a / an /
• "opt-isolated" s/opt/opto/ maybe?

Avoid breakage of URLs in plain text representations of quarterly reports

An example:

• https://www.freebsd.org/status/report-2022-04-2022-06/#_freebsd_on_microsoft_hyperv_and_azure appears OK
• http://markmail.org/message/ppab5mirschfew7s the URL at the tail of one long line is misrepresented as https://wiki.freebsd.org/ (the wrong address), followed by a single line with no related link:

MicrosoftAzure

Another example of breakage within the same report:

---

An example from the previous report, four URLs broken in the report from The FreeBSD Foundation:

– archived at https://markmail.org/message/wu5qp6kwmxajcxq5 (there's coincidental additional breakage, which is beyond the scope of this issue #530).

---

…

Building on FreeBSD Wiki is still not accessible

https://wiki.freebsd.org/BuildingOnNonFreeBSD

Missing link

in https://github.com/freebsd/freebsd-quarterly/blob/master/2018q3/00_REPORT.md:

This data has been updated through Q3 and is available (here). It

(here) does not link to anything.

tools/sendcalls: Too many recipients

The sendcalls script now works by sending one single mail to freebsd-quarterly-calls@ and CCing all the submitters for the precedent quarter. This creates a mail with lots of recipients which is then moderated on our mailing lists.
Another approach is needed which sends mails to less recipients, so that no manual intervention is required.

2020q3/graphics.md

There have also been several updates to various libraries, both in the graphics
and input stacks, and several userland drivers have been updated.
Libraries such as libdrm and libevdev which includes new FreeBSD support
developed by team members and added upstream.

The second sentence in that paragraph seems to lack a main clause but I'm not sure what the fix is. Possible changes that came to mind are:

• s/which includes/include/ (second sentence) if that sentence is meant to stand on its own.
• Merge both sentences using : if the second sentence is actually meant to list the updated userland drivers and libevdev is the only one that includes new FreeBSD support.
• Merge both sentences using : and s/includes/include/ if the second sentence is actually meant to list the updated userland drivers and both libdrm and liibevdev include new FreeBSD support.

md2docbook.pl handling of double-space+newline

MarkDown supports a syntax with double-space+newline leading to a new line being created without inserting a new paragraph, as shown here
Talking with salvadore@ on IRC, it sounds as if md2docbook.pl doesn't handle this appropriately, and it sounds like the fix it to have it insert a simple
for the doublespace+newline syntax.