Date: Wed, 1 May 2024 11:12:42 GMT From: Lorenzo Salvadore <salvadore@FreeBSD.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org Subject: git: 7a677104e3 - main - Status/2024Q1: Fixes Message-ID: <202405011112.441BCgDH018811@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by salvadore: URL: https://cgit.FreeBSD.org/doc/commit/?id=7a677104e33fbec6a2827252ecc5c806013af1a8 commit 7a677104e33fbec6a2827252ecc5c806013af1a8 Author: Lorenzo Salvadore <salvadore@FreeBSD.org> AuthorDate: 2024-05-01 11:12:06 +0000 Commit: Lorenzo Salvadore <salvadore@FreeBSD.org> CommitDate: 2024-05-01 11:12:42 +0000 Status/2024Q1: Fixes Fixes suggested by vale linting tool. --- website/content/en/status/report-2024-01-2024-03/bhyve.adoc | 2 +- .../content/en/status/report-2024-01-2024-03/freebsd-foundation.adoc | 2 +- website/content/en/status/report-2024-01-2024-03/freshports.adoc | 2 +- website/content/en/status/report-2024-01-2024-03/libsys.adoc | 5 +++-- website/content/en/status/report-2024-01-2024-03/pot.adoc | 2 +- website/content/en/status/report-2024-01-2024-03/wireless.adoc | 2 +- 6 files changed, 8 insertions(+), 7 deletions(-) diff --git a/website/content/en/status/report-2024-01-2024-03/bhyve.adoc b/website/content/en/status/report-2024-01-2024-03/bhyve.adoc index 44b96ae426..2de6c27dfe 100644 --- a/website/content/en/status/report-2024-01-2024-03/bhyve.adoc +++ b/website/content/en/status/report-2024-01-2024-03/bhyve.adoc @@ -5,7 +5,7 @@ link:https://callfortesting.org/[bhyve production users calls] URL: link:https:/ link:https://wiki.freebsd.org/EnterpriseWorkingGroup[FreeBSD Wiki - Enterprise Working Group] URL: link:https://wiki.freebsd.org/EnterpriseWorkingGroup[] + link:https://wiki.freebsd.org/ChrisMoerz/bhyve_management[FreeBSD Wiki - EWG - bhyve and jails management tooling] URL: link:https://wiki.freebsd.org/ChrisMoerz/bhyve_management[] + link:http://static.bultmann.eu/s6-talk/#(1)[Jan Bramkamp's work on s6rc] URL:http://static.bultmann.eu/s6-talk/#(1)[] + -link:https://github.com/christian-moerz/vmstated[vmstated on Github] URL: link:https://github.com/christian-moerz/vmstated[] + +link:https://github.com/christian-moerz/vmstated[vmstated on GitHub] URL: link:https://github.com/christian-moerz/vmstated[] + link:https://www.youtube.com/watch?v=f60NCrunXyw[YouTube - vmstated explained] URL: link:https://www.youtube.com/watch?v=f60NCrunXyw[] Contact: Chris Moerz <freebsd@ny-central.org> diff --git a/website/content/en/status/report-2024-01-2024-03/freebsd-foundation.adoc b/website/content/en/status/report-2024-01-2024-03/freebsd-foundation.adoc index 87cf09e0a1..6fbd95e971 100644 --- a/website/content/en/status/report-2024-01-2024-03/freebsd-foundation.adoc +++ b/website/content/en/status/report-2024-01-2024-03/freebsd-foundation.adoc @@ -95,7 +95,7 @@ To this end, the Foundation is working on a FreeBSD Impact Report that will aggr Our community is stepping up in innumerable ways, including to make sure FreeBSD supports industry-standard containerized workloads -- check out the link:https://github.com/opencontainers/wg-freebsd-runtime[Open Container Initiative FreeBSD runtime extension working group]. -The recently-opened hardware vendor support survey will feed into a hardware support guide that reflects the collective experience of all respondents that is intended to help everyone identify hardware vendors that prioritize FreeBSD; it will also help focus Partnerships' outreach on the priority vendors. +The recently opened hardware vendor support survey will feed into a hardware support guide that reflects the collective experience of all respondents that is intended to help everyone identify hardware vendors that prioritize FreeBSD; it will also help focus Partnerships' outreach on the priority vendors. To close, please *TELL THE WORLD YOU USE FREEBSD AND WHY. There is no wrong way to do this* -- put it on your blog, on your favorite social media channel, list FreeBSD on your company’s Open Source page, contact the Foundation about a Case Study, etc. diff --git a/website/content/en/status/report-2024-01-2024-03/freshports.adoc b/website/content/en/status/report-2024-01-2024-03/freshports.adoc index 5abd4feebc..088670806e 100644 --- a/website/content/en/status/report-2024-01-2024-03/freshports.adoc +++ b/website/content/en/status/report-2024-01-2024-03/freshports.adoc @@ -20,7 +20,7 @@ All of this is useful for both users and developers of ports. One of the original features of FreshPorts is notification of ports updates. You can create a list of ports and receive notifications about those ports. This new feature can also notify when a new package is available for that port. -The use case: a known security vuln has been patched. +The use case: a known security vulnerability has been patched. FreshPorts will tell you the port has been patched, and then you wait for the package. This new feature will tell you when that package is available. diff --git a/website/content/en/status/report-2024-01-2024-03/libsys.adoc b/website/content/en/status/report-2024-01-2024-03/libsys.adoc index 46275eb7aa..791aed0974 100644 --- a/website/content/en/status/report-2024-01-2024-03/libsys.adoc +++ b/website/content/en/status/report-2024-01-2024-03/libsys.adoc @@ -17,7 +17,7 @@ I landed the first batch of changes on February 5th. Since then I have made a number of refinements to the way we link `libsys` as well as which symbols are provided in which library. Thanks to mailto:kib@FreeBSD.org[Konstantin Belousov] for many rounds of review and feedback as well as runtime linker fixes. -Thanks to mailto:markj@FreeBSD.org[Mark Johnston] for runtime linker debugging and mailto:dim@FreeBSD.org[Dimitry Andric] for sanitizer fixes. +Thanks to mailto:markj@FreeBSD.org[Mark Johnston] for runtime linker debugging and mailto:dim@FreeBSD.org[Dimitry Andric] for sanitizer fixes. Thanks also to everyone who reported bugs and helped debug issues. ==== Known issues (as of the end of the reporting period) @@ -31,7 +31,8 @@ Thanks also to everyone who reported bugs and helped debug issues. * Update man:intro[2] for `libsys`. * Finalize the ABI. I am likely to reduce the set of `_` (underscore) prefixed symbols we expose. - * MFC the existence of `libsys`? It is not clear this is practical, but it might be possible to MFC something useful for language runtimes. + * MFC the existence of `libsys`? + It is not clear this is practical, but it might be possible to MFC something useful for language runtimes. ==== Help wanted diff --git a/website/content/en/status/report-2024-01-2024-03/pot.adoc b/website/content/en/status/report-2024-01-2024-03/pot.adoc index dc41c68822..1bb3823a5a 100644 --- a/website/content/en/status/report-2024-01-2024-03/pot.adoc +++ b/website/content/en/status/report-2024-01-2024-03/pot.adoc @@ -14,7 +14,7 @@ During this quarter, there were no new link:https://github.com/bsdpot/pot[Pot] r Potluck saw quite some activity though. Not only have the images been rebuilt for FreeBSD 14, but also the new link:https://github.com/bsdpot/potluck/tree/master/adminer[Adminer] container has been submitted by first-time contributor link:https://github.com/Sidicer[Sidicer]. -Additionally a large number of additional features, updates and fixes have been committed to containers like link:https://github.com/bsdpot/potluck/tree/master/haproxy-consul[HAProxy-Consul], link:https://github.com/bsdpot/potluck/tree/master/grafana[Grafana], link:https://github.com/bsdpot/potluck/tree/master/postgresql-patroni[PostgreSQL-Patroni], or link:https://github.com/bsdpot/potluck/tree/master/prometheus[Prometheus]. +Additionally a large number of additional features, updates and fixes have been committed to containers like link:https://github.com/bsdpot/potluck/tree/master/haproxy-consul[HAProxy-Consul], link:https://github.com/bsdpot/potluck/tree/master/grafana[Grafana], link:https://github.com/bsdpot/potluck/tree/master/postgresql-patroni[PostgreSQL-Patroni], or link:https://github.com/bsdpot/potluck/tree/master/prometheus[Prometheus]. For the link:https://github.com/bsdpot/potluck/tree/master/mastodon-s3[Mastodon container], a link:https://honeyguide.eu/posts/run-your-own-mastodon-server/[blog post] has been published explaining how to use it to run your own instance. diff --git a/website/content/en/status/report-2024-01-2024-03/wireless.adoc b/website/content/en/status/report-2024-01-2024-03/wireless.adoc index 0f77129009..43c585d683 100644 --- a/website/content/en/status/report-2024-01-2024-03/wireless.adoc +++ b/website/content/en/status/report-2024-01-2024-03/wireless.adoc @@ -15,7 +15,7 @@ Massive thanks to everyone who tested, reported back, updated PRs and helped oth I have also slowly started to "categorise" more (old) wireless problem reports and will try to continue with some spring cleaning throughout the year. -If you have questions or feedback please use the link:freebsd-wireless mailing list[https://lists.freebsd.org/subscription/freebsd-wireless]. +If you have questions or feedback please use the link:https://lists.freebsd.org/subscription/freebsd-wireless[freebsd-wireless mailing list]. That way everyone will see, be able to join in, and the answers will be publicly archived. Sponsor: minipci.biz (BE200 hardware)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202405011112.441BCgDH018811>