diff --git a/website/content/en/status/report-2025-01-2025-03/container-orchestration.adoc b/website/content/en/status/report-2025-01-2025-03/container-orchestration.adoc index bbc117a0ac..275da2aec3 100644 --- a/website/content/en/status/report-2025-01-2025-03/container-orchestration.adoc +++ b/website/content/en/status/report-2025-01-2025-03/container-orchestration.adoc @@ -1,22 +1,22 @@ === Container orchestration: Overlord, Director and AppJail Links: + -link:https://github.com/DtxdF/AppJail[AppJail on Github] URL: link:https://github.com/DtxdF/AppJail[] + -link:https://github.com/DtxdF/Director[Director on Github] URL: link:https://github.com/DtxdF/Director[] + -link:https://github.com/DtxdF/Overlord[Overlord on Github] URL: link:https://github.com/DtxdF/Overlord[] +link:https://github.com/DtxdF/AppJail[AppJail on GitHub] URL: link:https://github.com/DtxdF/AppJail[] + +link:https://github.com/DtxdF/Director[Director on GitHub] URL: link:https://github.com/DtxdF/Director[] + +link:https://github.com/DtxdF/Overlord[Overlord on GitHub] URL: link:https://github.com/DtxdF/Overlord[] Contact: Jesús Daniel Colmenares Oviedo **AppJail** is an open-source BSD-3 licensed framework entirely written in POSIX shell and C to create isolated, portable and easy to deploy environments using FreeBSD jails that behaves like an application. **Director** is a tool for running multi-jail environments on AppJail using a simple YAML specification. A Director file is used to define how one or more jails that make up your application are configured. Once you have a Director file, you can create and start your application with a single command: `appjail-director up`. **Overlord** is a fast, distributed orchestrator for FreeBSD jails oriented to GitOps. You define a file with the service intended to run on your cluster and deployment takes seconds to minutes. This orchestration tool uses AppJail, Director and can even create VMs with vm-bhyve, but as its philosophy is "deploy using code" you can create a single file once and deploy many times. Through a tree chaining system Overlord deploys jails on connected systems sharing their resources almost infinitely. See the link:https://github.com/DtxdF/Overlord/wiki[wiki] for articles that use Overlord. Sponsor: https://www.patreon.com/appjail diff --git a/website/content/en/status/report-2025-01-2025-03/discord.adoc b/website/content/en/status/report-2025-01-2025-03/discord.adoc index 3c057e450e..a40b10ba28 100644 --- a/website/content/en/status/report-2025-01-2025-03/discord.adoc +++ b/website/content/en/status/report-2025-01-2025-03/discord.adoc @@ -1,51 +1,52 @@ === FreeBSD Discord Server Links: + link:https://wiki.freebsd.org/Discord/DiscordServer[Discord Server] URL: link:https://wiki.freebsd.org/Discord/DiscordServer[] Contact: Setesh Strong -The FreeBSD Community Discord server has grown to over 5.3K members, with over 3K members active in the last month. To help support our community’s health and pursue growth in project contribution and engagement, the BSDlabs group developed the Helper program, more than two years ago now. +The FreeBSD Community Discord server has grown to over 5.3K members, with over 3K members active in the last month. +To help support our community’s health and pursue growth in project contribution and engagement, the BSDlabs group developed the Helper program, more than two years ago now. After several phases of growth, we have reached the point where the team has thrived enough that it has become necessary to divide it into three distinct functional teams. Our community health and culture helpers (@moderators) are led by Alexander Vereeken. Our newcomer onboarding and training helpers (@mentors) are led by mailto:ziaee@FreeBSD.org[Alexander Ziaee]. Our event organizer and outreach helpers (@organizers) are led by Ahmad Abdulla. Since the creation of the new teams, all of our helpers have been hard at work, driving growth within the areas of their remit within the program. We are proud to share some of the outcomes of their efforts with you, as well as several of the areas of focus and objectives we will tackle in the upcoming quarter. Antranig Vartanian led the development of our recurring series of Ask the Greybeards AMAs (Ask Me Anything) with the support of other veteran sysadmins and developers. This recurring event provides an opportunity for users and those still gaining mastery of our platform to meet and learn from the depth of experience our community offers. Special thanks to mailto:dexter@FreeBSD.org[Michael Dexter] and many others for their engagement and support of this event. Your expertise and skills help nurture the future of our ecosystem. Significant progress into onboarding new contributors has occurred through the efforts of the newcomer helper team under Alexander Ziaee’s leadership. His work has brought newly increased activity to our docs tree. At the request of mailto:imp@FreeBSD.org[Warner Losh], we have created a workspace for #google-summer-of-code on the server. This space provides a location for those engaged with GSoC to ask questions and receive feedback and assistance. In further pursuit of our desire to bridge between silos, we are in the process of establishing a matterbridge bot. This will serve to connect with the #freebsd-gsoc IRC channel, as well as other potential links in the future with FreeBSD’s IRC and Matrix communities. We are proud to welcome developers working on FreeBSD’s wifi stack to our server. We have created the #wifi-hacking workspace to facilitate their efforts. Special thanks to mailto:adrian@FreeBSD.org[Adrian Chadd] for bringing this opportunity to us, and leading the way in the thriving activity in this workspace. We are currently in the process of developing our new Co-op Study Club, driven by the leadership of mailto:jsm@FreeBSD.org[Jesper Schmitz Mouridsen]. This will provide members of our community with the opportunity to build their skills in side-by-side study, under the guidance of our newcomer helper team. As a project driven study group, it will develop our members’ passions into strengths, while building comfort and familiarity with contributing to the project via porting, src development, and documentation testing and patching. Experienced mentorship will be on hand to provide learning resources for those who join this study group, answer questions that cannot be answered by peer support, and aiding in overcoming blockers. Our objective is to provide a roadmap and environment for achieving excellence as both developers and FreeBSD contributors. Thanks to the efforts of community helper Jessica Hawkwell, with the support of events team leader Ahmad Abdulla, we have seen the addition of a #foss-ecosystem channel. This development marks the beginning of the process of bridging between the various silos, both within the FreeBSD community, and in the larger FOSS ecosystem. If you want us to add a link to your segment of the community and it is not already contained in our directory in this channel, please reach out to us. In addition to the existing tools afforded by Discord for our server, we are currently in the process of upgrading and expanding our infrastructure. This effort focuses on ensuring the availability of Discord bot infrastructure and tooling, as well as restoring etherpad and dpaste functionality for collaboration. We seek to improve support for all of the dedicated developers within the workspaces of our community. If you are a member of the FreeBSD ecosystem and have not yet connected to our Discord presence, we invite you to do so via the invite link available on the wiki at the top of this report. If you have experience or passion for any of the areas of our current helper teams, or a passion for Discord bot infrastructure development, we would love to have you on our teams. We invite you to contact us via the above contact email, or by sending a DM on Discord (@setesh.strong). diff --git a/website/content/en/status/report-2025-01-2025-03/foundation-infrastructure_modernization.adoc b/website/content/en/status/report-2025-01-2025-03/foundation-infrastructure-modernization.adoc similarity index 98% rename from website/content/en/status/report-2025-01-2025-03/foundation-infrastructure_modernization.adoc rename to website/content/en/status/report-2025-01-2025-03/foundation-infrastructure-modernization.adoc index 45d0b7d592..2d6046e32c 100644 --- a/website/content/en/status/report-2025-01-2025-03/foundation-infrastructure_modernization.adoc +++ b/website/content/en/status/report-2025-01-2025-03/foundation-infrastructure-modernization.adoc @@ -1,41 +1,41 @@ === Infrastructure Modernization -Contact: Ed Maste +Contact: Ed Maste + Contact: Alice Sowerby The project started in Q3 of 2024 and was commissioned by the Sovereign Tech Agency with a budget of $745,000, to be spent over about one year. The main goals are to improve security tools for the base system, ports, and packages, update the project's infrastructure to speed up development, enhance build security, and make it easier for new developers to get started. ==== Q1 update Three of the five work packages are now in progress, with the remaining two to start in April. The overall schedule has been re-planned to run through to December 2025, allowing for a more sustainable pace of work. ===== Work Package A: Technical Debt reduction The Foundation and the FreeBSD Project's Source Management team is working together to make bug management easier and more sustainable. There is now a link:https://grimoire.freebsd.org[bug backlog dashboard], which helps make the backlog easier to understand during "bug busting" sessions, and is already showing that more bugs are being closed than being opened. This is hosted on FreeBSD and link:https://github.com/chaoss/grimoirelab/blob/main/FreeBSD.md[documentation] has been submitted upstream to the GrimoireLab project so others can do the same. One way to learn more about the project is to listen to the link:https://podcast.chaoss.community/103[CHAOSScast episode] where we talked about this work package. We have also been upgrading Bugzilla by applying patches from 2023 onward and improving the upgrade process to ensure smoother future updates. ===== Work Package B: Zero Trust Builds Much of the foundational work has been completed to standardize all source release build cases using no-root for creation of release artifacts. We are formalizing and documenting make world and [.filename]#release.sh# to provide joined-up documentation for users. In order to get src to build reproducibly we are creating CI tests and are working with link:https://reproducible-builds.org[Reproducible-Builds.org] to restore the link:https://tests.reproducible-builds.org/freebsd/freebsd.html[FreeBSD reproducible CI]. Read their link:https://reproducible-builds.org/reports/2025-02/[February report]. ===== Work Package C: CI/CD Automation The high-level goal is to improve CI/CD automation to streamline software delivery and operations for new and existing software. Work so far is focusing on: * Improving the quality of incoming commits by providing system-agnostic tooling and documentation so that maintainers and developers can run CI without requiring a 3rd-party service (link:https://reviews.freebsd.org/D48015). * Making it possible to run pre-merge CI on proposed submissions (e.g. Pull Requests) (link:https://reviews.freebsd.org/D36257). * Documenting the CI management process to make it easier to keep tooling up to date and patched. * Updating the Source and Ports tests to include standard linters and other relevant automated analysis tools. ===== Work Package D: Security Controls in Ports and Packages and Work Package E: Improve Software Bill of Materials (SBOM) These work packages are scheduled to start in April. The Foundation has been collaborating with FreeBSD Project teams to scope the projects appropriately. Commissioning body: Sovereign Tech Agency diff --git a/website/content/en/status/report-2025-01-2025-03/hackathon-202503.adoc b/website/content/en/status/report-2025-01-2025-03/hackathon.adoc similarity index 80% rename from website/content/en/status/report-2025-01-2025-03/hackathon-202503.adoc rename to website/content/en/status/report-2025-01-2025-03/hackathon.adoc index b66b0da6d2..16ed6d10b8 100644 --- a/website/content/en/status/report-2025-01-2025-03/hackathon-202503.adoc +++ b/website/content/en/status/report-2025-01-2025-03/hackathon.adoc @@ -1,47 +1,50 @@ === Hackathon 202503 Tokyo, Japan Links: + link:https://wiki.freebsd.org/Hackathon/202503[Hackathon/202503 Wiki Page] URL: link:https://wiki.freebsd.org/Hackathon/202503[] link:https://wiki.freebsd.org/Hackathon[FreeBSD Hackathon Wiki Page] URL: link:https://wiki.freebsd.org/Hackathon[] Before the link:https://hackmd.io/@AsiaBSDCon/2025lite[AsiaBSDCon-Lite 2025] event, some members of the community gathered and held a hackathon in Tokyo. Thanks to Christoff Visser and Internet Initiative Japan Inc. who sponsored the venue. ==== The work done or progressed in the hackathon ===== Sheng-Yi Hung -- man:ipheth[4]: The iPhone tethering uses NCM on newer iOS, modified ipheth(4) to supporting it. Patch: link:https://reviews.freebsd.org/D49431[] -- Sccahe for FreeBSD base: the FreeBSD base supports ccache to cache the build result. For cross machine build, we need a distributed cache mechanism - that is - sccache. In Hackathon, the patch for adding sccache support is created: link:https://reviews.freebsd.org/D49417[] +- man:ipheth[4]: The iPhone tethering uses NCM on newer iOS, modified man:ipheth[4] to supporting it. + Patch: link:https://reviews.freebsd.org/D49431[] +- Sccahe for FreeBSD base: the FreeBSD base supports ccache to cache the build result. + For cross machine build, we need a distributed cache mechanism -- that is -- sccache. + In Hackathon, the patch for adding sccache support is created: link:https://reviews.freebsd.org/D49417[] ===== Kristof Provost Wrote a test case for bsnmpd’s snmp_pf module. This revealed that the BEGEMOT-PF-MIB.txt MIB file could not be parsed by bsnmpwalk, which was also fixed. -Commits: gitef:712309a64512c7e4ebf0e10de8a5c59d5a185ae8[repository=src], gitef:c849f533326026501c28cb2c344b16723862551a[repository=src] and gitef:36586800803d24f1137d861bbaf487a6bde16a09[repository=src] +Commits: gitref:712309a64512c7e4ebf0e10de8a5c59d5a185ae8[repository=src], gitref:c849f533326026501c28cb2c344b16723862551a[repository=src] and gitref:36586800803d24f1137d861bbaf487a6bde16a09[repository=src] ===== Aymeric Wibo - Got writing to config space of USB4 routers working and successive reads on AMD USB4 controllers. - First steps to suspending USB4 routers. - Put up a bunch of preliminary patches regarding the USB4 stuff. - Tried passing through USB4 devices to Linux guest to suspend them (did not work). ===== Mark Johnston - Worked on various syzkaller reports, e.g.: gitref:fe7fe3b175b626dd1402cd06745b1e3f070c3edd[repository=src] - Looked for races in pf after getting some vague bug reports from the OPNsense developers and, with Gleb and Kristof, found and fixed a rare race which could cause a use-after-free: gitref:8efd2acf07bc0e1c3ea1f7390e0f1cfb7cf6f86c[repository=src] ===== Philip Paeps - Fixed the libtrue website -- we now have libtrue.so :-) - Worked on clusteradm technical debt - Good progress on our LDAP update - Updated a couple of internal machines ===== Li-Wen Hsu - Project's Git infrastructure improvements, including system updating, maintenance scripts and git hooks fixes - Plan the cluster goals and roadmap for 2025 and longer with Philip Paeps Sponsor: Christoff Visser and Internet Initiative Japan Inc. for the venue diff --git a/website/content/en/status/report-2025-01-2025-03/openjdk.adoc b/website/content/en/status/report-2025-01-2025-03/openjdk.adoc index 6b92775269..74447188ac 100644 --- a/website/content/en/status/report-2025-01-2025-03/openjdk.adoc +++ b/website/content/en/status/report-2025-01-2025-03/openjdk.adoc @@ -1,26 +1,30 @@ === Improve OpenJDK on FreeBSD Links: + link:https://freebsdfoundation.org/project/improving-openjdk-on-freebsd/[Project description] URL: https://freebsdfoundation.org/project/improving-openjdk-on-freebsd/[] + link:https://github.com/freebsd/openjdk[Project repository] URL: https://github.com/freebsd/openjdk[] Contact: + Harald Eilertsen + FreeBSD Java mailing list The main goal of this project is to improve OpenJDK support on FreeBSD/amd64 and FreeBSD/arm64. Java is an important runtime environment for many high performance, critical enterprise systems. Making sure Java based applications run correctly and efficiently on FreeBSD is important to ensure that FreeBSD will continue to be a viable and attractive platform for enterprises, as well as businesses and organizations of all sizes. We released https://cgit.freebsd.org/ports/commit/?id=aa17c509fe7c4a011e832bd1e67257cf5d0ebc81[a port for OpenJDK 23] for FreeBSD at the very end of last year, and have since then fixed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284503[issues with font management] and some other minor improvements. We have also been following the development of OpenJDK 24 closely, and are just finishing a https://reviews.freebsd.org/D49354[port for it] that should be available by the time this status update is published. In parallel with porting OpenJDK 24 work has been ongoing on moving the BSD port also to the mainline OpenJDK development tree, and the first patches have been accepted upstream. Currently the focus is on reviving the https://openjdk.org/projects/bsd-port/[OpenJDK BSD port project], as well as getting a separate project repository set up under it. -A lot of the work of this quarter has gone into cleaning up the patches of the BSD port based on the development in the upstream mainline and jdk24 branches. Also a lot of time has been spent on improving the results of the built in test suites (jtreg and gtest) on FreeBSD. This has involved both changes to the tests themselves, but also various parts of the low level OpenJDK code. More work is needed to get the final few tests passing, especially on Aarch64, but compared to previous OpenJDK releases on FreeBSD the results have been improving. +A lot of the work of this quarter has gone into cleaning up the patches of the BSD port based on the development in the upstream mainline and jdk24 branches. +Also a lot of time has been spent on improving the results of the built in test suites (jtreg and gtest) on FreeBSD. +This has involved both changes to the tests themselves, but also various parts of the low level OpenJDK code. +More work is needed to get the final few tests passing, especially on Aarch64, but compared to previous OpenJDK releases on FreeBSD the results have been improving. -Finally, a significant amount of time has been spent on communicating and discussing how to approach the goal of integrating the BSD support in the mainline OpenJDK codebase. The OpenJDK project has been very open, welcoming and supportive of the effort, and seems more than willing to help make this happen in a good way. +Finally, a significant amount of time has been spent on communicating and discussing how to approach the goal of integrating the BSD support in the mainline OpenJDK codebase. +The OpenJDK project has been very open, welcoming and supportive of the effort, and seems more than willing to help make this happen in a good way. Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2025-01-2025-03/pot.adoc b/website/content/en/status/report-2025-01-2025-03/pot.adoc index 0bee35dfaa..990359cc82 100644 --- a/website/content/en/status/report-2025-01-2025-03/pot.adoc +++ b/website/content/en/status/report-2025-01-2025-03/pot.adoc @@ -1,22 +1,23 @@ === Containers and FreeBSD: Pot, Potluck and Potman Links: + -link:https://github.com/bsdpot[Pot organization on Github] URL: link:https://github.com/bsdpot[] +link:https://github.com/bsdpot[Pot organization on GitHub] URL: link:https://github.com/bsdpot[] Contact: Luca Pizzamiglio (Pot) + Contact: Bretton Vine (Potluck) + Contact: Michael Gmelin (Potman) Pot is a jail management tool that link:https://www.freebsd.org/news/status/report-2020-01-2020-03/#pot-and-the-nomad-pot-driver[also supports orchestration through Nomad]. Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad. -During this quarter, there was a new link:https://github.com/bsdpot/pot/releases/tag/0.16.1[Pot release 0.16.1] which includes a number of minor fixes. The FreeBSD port was updated accordingly. +During this quarter, there was a new link:https://github.com/bsdpot/pot/releases/tag/0.16.1[Pot release 0.16.1] which includes a number of minor fixes. +The FreeBSD port was updated accordingly. Potluck got a new link:https://github.com/bsdpot/potluck/tree/master/onlyoffice-documentserver[OnlyOffice Documentserver] image that can be used together with the link:https://github.com/bsdpot/potluck/tree/master/nextcloud-nginx-nomad[Nextcloud] image. Additionally, a large number of images have received improvements and bug fixes again, e.g. link:https://github.com/bsdpot/potluck/tree/master/nextcloud-spreed-signalling[Nextcloud Spreed], link:https://github.com/bsdpot/potluck/tree/master/grafana[Grafana], link:https://github.com/bsdpot/potluck/tree/master/vault[Vault] or link:https://github.com/bsdpot/potluck/tree/master/consul[Consul] and all images have been rebuilt for an updated base image. -Last not least, we are in the process of moving the main repository to Codeberg with Github acting as a mirror. +Last not least, we are in the process of moving the main repository to Codeberg with GitHub acting as a mirror. As always, feedback and patches are welcome. Sponsors: Nikulipe UAB, Honeyguide Group diff --git a/website/content/en/status/report-2025-01-2025-03/suspend.adoc b/website/content/en/status/report-2025-01-2025-03/suspend.adoc index 3e64478672..b72a132f58 100644 --- a/website/content/en/status/report-2025-01-2025-03/suspend.adoc +++ b/website/content/en/status/report-2025-01-2025-03/suspend.adoc @@ -1,26 +1,26 @@ === Suspend/Resume Improvement Links: + link:https://obiw.ac/s0ix/[Blog] URL: link:https://obiw.ac/s0ix/[] + link:https://youtu.be/mBxj_EkAzV0[FOSDEM talk on S0ix] URL: https://youtu.be/mBxj_EkAzV0[] + -link:https://github.com/obiwac/freebsd-s0ix[Working Repo] URL: link:https://github.com/obiwac/freebsd-s0ix[] + +link:https://github.com/obiwac/freebsd-s0ix[Working Repository] URL: link:https://github.com/obiwac/freebsd-s0ix[] + link:https://reviews.freebsd.org/D48721[Tip of the S0ix + AMD SMU stack] URL: https://reviews.freebsd.org/D48721[] + link:https://reviews.freebsd.org/D49453[USB4 suspend stack] URL: https://reviews.freebsd.org/D49453[] -Contact: obiwac +Contact: obiwac Suspend-to-idle and support for S0ix sleep is in the process of being added to FreeBSD. This will allow modern Intel and AMD laptops (e.g. AMD and newer Intel Framework laptops), some of which do not support ACPI S3 sleep, to enter low power states to increase battery life. -Suspending and resuming is working on the Framework 13 AMD Ryzen 7040 series, though the deepest S0ix state (S0i3), necessary for significant power savings, can't yet be entered on AMD systems. +Suspending and resuming is working on the Framework 13 AMD Ryzen 7040 series, though the deepest S0ix state (S0i3), necessary for significant power savings, cannot yet be entered on AMD systems. The major blocker for this at the moment is being able to suspend all the USB4 routers correctly, without which the power management firmware will refuse to enter S0i3. USB4 suspend support in FreeBSD is necessary as the BIOS wakes them up and runs a pre-OS connection manager for USB4 to work before an OS loads with its own connection manager, so they start off in an awake state. -Work has been picked up from the initial USB4 driver Scott Long started writing, but it isn't yet at a stage where the routers are being fully suspended. +Work has been picked up from the initial USB4 driver Scott Long started writing, but it is not yet at a stage where the routers are being fully suspended. An amdsmu driver was written to read last suspend statistics and sleep-state residency counters (which were unavailable in the ACPI _LPI objects). The SMU is a small coprocessor on AMD CPUs which runs the power management firmware and is ultimately what decides to enter S0i3 or not. These statistics can tell us if the system entered S0i3 during the last suspend, how much time it took to enter, and which proportion of suspended time was spent in S0i3. Sponsor: The FreeBSD Foundation diff --git a/website/content/en/status/report-2025-01-2025-03/vision-accessibility-handbook.adoc b/website/content/en/status/report-2025-01-2025-03/vision-accessibility-handbook.adoc index e62dd30340..6a37578915 100644 --- a/website/content/en/status/report-2025-01-2025-03/vision-accessibility-handbook.adoc +++ b/website/content/en/status/report-2025-01-2025-03/vision-accessibility-handbook.adoc @@ -1,31 +1,31 @@ -=== Vision Accessibility - Accessibility Handbook +=== Vision Accessibility -- Accessibility Handbook Link: + link:https://gitlab.com/alfix/freebsd-accessibility[Project Repository] URL: link:https://gitlab.com/alfix/freebsd-accessibility[] Contact: FreeBSD Accessibility mailing list + Contact: Alfonso Sabato Siciliano The FreeBSD Foundation is supporting a series of projects to enhance accessibility for users with visual impairments. FreeBSD offers several assistive technologies, thanks to the dedicated work of contributors and committers. An ongoing effort focuses on listing and documenting these accessibility features in a new handbook. Currently, the project centers on documenting features for blind, low-vision, and colorblind users, covering both PORTS and BASE system functionalities. For example: ports for screen magnification, screen readers (which aid users who cannot see the screen), as well as tools for adjusting colors in desktop environments. Additionally, accessibility features available in the BASE system to enhance visibility are also being documented with examples and tips: such as the ability to modify colors, fonts, and sizes in the system's virtual console man:vt[4]. The new handbook will be organized into sections. The first section will serve as an introduction, while the second will delve into assistive technologies for visual accessibility. The repository mentioned above provides access to the handbook's work-in-progress, including the code (in a fork of the FreeBSD "doc" repository, accessibility-book branch) and an HTML preview. Completion and review for publication are expected soon. Future plans include adding a Section 3 for hearing accessibility, a Section 4 for interaction accessibility, and a "Miscellaneous" chapter in Section 1 to cover general aspects. A discussion on this topic is available on the accessibility mailing list. Furthermore, during this quarter, the port package:www/edbrowse[] has been updated. This is a fully command-line web browser designed for compatibility with screen readers. A solution is also being developed to facilitate easy color customization for TUI utilities in the BASE system, with the potential to set high contrast directly from the system installer man:bsdinstall[8]. Tips and new ideas are welcome. If possible, send reports to the FreeBSD Accessibility mailing list, to share and to track discussions in a public place. Sponsored by: The FreeBSD Foundation diff --git a/website/content/en/status/report-2025-01-2025-03/wiki.adoc b/website/content/en/status/report-2025-01-2025-03/wiki.adoc index 9d78354f06..937cf1993d 100644 --- a/website/content/en/status/report-2025-01-2025-03/wiki.adoc +++ b/website/content/en/status/report-2025-01-2025-03/wiki.adoc @@ -1,28 +1,28 @@ === FreeBSD Wiki Links: + link:https://wiki.freebsd.org/FrontPage[FreeBSD wiki front page] URL: link:https://wiki.freebsd.org/FrontPage[] -Contact: Mark Linimon + -Contact: Wiki admin +Contact: Mark Linimon + +Contact: Wiki admin The wiki team needs new blood. Since the last status report (2024Q3) forward progress has stalled. We have given out several dozen new accounts but most of the changes by these new authors have been to individual pages, not to the overall structure. Mark Linimon still thinks the wiki could be a great resource if people were willing to put time into it. But right now, there are more complaints about stale data than there are new contributors and new ideas. It is fair to say that right now, the wiki is on autopilot. ==== Previous plans that have stalled Preliminary work was being done on updating the wiki software itself. Earlier, we were looking at switching implementations because MoinMoin development seemed to have stalled, leaving us with an unwanted hanging python2 dependency. However, MoinMoin now claims that they are nearing a 2.0 release. We have not yet tried an install of their latest beta version to test compatibility. ==== Specific short-term requests for help If anyone knows about MoinMoin markup, contact Mark.