From owner-svn-doc-head@freebsd.org Sun Nov 24 18:32:16 2019
Return-Path: Here is the third quarterly status report for 2019. This quarter the reports team has been more active than usual thanks
+to a better organization: calls for reports and reminders have been
+sent regularly, reports have been reviewed and merged quickly (I would
+like to thank debdrup@ in particular for his reviewing work). Efficiency could still be improved with the help of our community.
+In particular, the quarterly team has found that many reports have
+arrived in the last days before the deadline or even after. I would
+like to invite the community to follow the guidelines below that
+can help us sending out the reports sooner. Starting from next quarter, all quarterly status reports will be
+prepared the last month of the quarter itself, instead of the first
+month after the quarter's end. This means that deadlines for
+submitting reports will be the 1st of January, April, July and
+October. Next quarter will then be a short one, covering the months of November
+and December only and the report will probably be out in mid January. -- Lorenzo Salvadore Entries from the various official and semi-official teams,
+ as found in the Administration
+ Page. Projects that span multiple categories, from the kernel and userspace
+ to the Ports Collection or external projects. Updates to kernel subsystems/features, driver support,
+ filesystems, and more. Updating platform-specific features and bringing in support
+ for new hardware platforms. Changes affecting the base system and programs in it. Changes affecting the Ports Collection, whether sweeping
+ changes that touch most of the tree, or individual ports
+ themselves. Many projects build upon &os; or incorporate components of
+ &os; into their project. As these projects may be of interest
+ to the broader &os; community, we sometimes include brief
+ updates submitted by these projects in our quarterly report.
+ The &os; project makes no representation as to the accuracy or
+ veracity of any claims in these submissions. The FreeBSD Core Team is the governing body of FreeBSD. The FreeBSD Release Engineering Team is responsible for
+ setting
+ and publishing release schedules for official project
+ releases
+ of FreeBSD, announcing code freezes and maintaining the
+ respective branches, among other things. During the third quarter of 2019, the FreeBSD Release
+ Engineering team
+ finished the 11.3-RELEASE cycle, with the final release
+ build started on
+ July 5th and the official announcement sent on July 9th. FreeBSD 11.3-RELEASE is the fourth release from the
+ stable/11 branch,
+ building on the stability and reliability of 11.2-RELEASE. The FreeBSD Release Engineering Team also started work on
+ the upcoming
+ 12.1-RELEASE, which started September 6th. This release
+ cycle is the
+ first "freeze-less" release from the Subversion
+ repository, and the test bed
+ for eliminating the requirement of a hard code freeze on
+ development branches.
+ Commits to the releng/12.1 branch still
+ require explicit approval from
+ the Release Engineering Team, however. At present, there have been three BETA builds, and so far,
+ two RC builds, with
+ the final 12.1-RELEASE build scheduled for November 4th. Additionally throughout the quarter, several development
+ snapshots builds
+ were released for the head and
+ stable/11 branches; snapshots for
+ stable/12 were released as well although
+ not during the 12.1-RELEASE cycle. Much of this work was sponsored by Rubicon Communications,
+ LLC (Netgate)
+ and the FreeBSD Foundation. Several members of the security team met at the Vendor
+ Summit in October to
+ formalize team structure dedicated for architecture and
+ crypto engineering in
+ addition to the existing product security incident
+ response function. Since June we have started having fortnightly conference
+ calls to discuss
+ important issues and to collaborate closely on advisories
+ and errata notices in
+ the pipeline. The FreeBSD Cluster Administration Team consists of the
+ people responsible for administering the machines
+ that the Project relies on for its distributed
+ work and communications to be synchronised. In
+ this quarter, the team has worked on the
+ following:
+ Work in progress: The FreeBSD CI team maintains continuous integration
+ system and related tasks
+ for the FreeBSD project. The CI system regularly checks
+ the committed changes
+ can be successfully built, then performs various tests and
+ analysis of the
+ results. The results from build jobs are archived in an
+ artifact server, for
+ the further testing and debugging needs. The CI team
+ members examine the
+ failing builds and unstable tests, and work with the
+ experts in that area to
+ fix the code or adjust test infrastructure. The details
+ are of these efforts
+ are available in the weekly CI reports. We had a testing working group at the 201909
+ DevSummit
+ lwhsu@ has presented the Testing/CI project status and
+ "how to work with the FreeBSD CI system", slides
+ are available at the DevSummit page.
+ Some contents have been migrated to
+ https://wiki.freebsd.org/Jenkins/Debug , extending
+ is welcomed. We continue publishing CI Weekly Report and moved the
+ archive to https://hackmd.io/@FreeBSD-CI Work in progress:
+ Please see freebsd-testing@ related tickets for more WIP
+ information. The FreeBSD Foundation is a 501(c)(3) non-profit
+ organization dedicated to
+ supporting and promoting the FreeBSD Project and community
+ worldwide.
+ Funding comes from individual and corporate donations and
+ is used to fund
+ and manage software development projects, conferences and
+ developer summits,
+ and provide travel grants to FreeBSD contributors. The
+ Foundation purchases
+ and supports hardware to improve and maintain FreeBSD
+ infrastructure and
+ provides resources to improve security and quality
+ assurance efforts;
+ publishes marketing material to promote, educate, and
+ advocate for the
+ FreeBSD Project; facilitates collaboration between
+ commercial vendors and
+ FreeBSD developers; and finally, represents the FreeBSD
+ Project in executing
+ contracts, license agreements, and other legal
+ arrangements that require a
+ recognized legal entity. Here are some highlights of what we did to help FreeBSD
+ last quarter: Partnerships and Commercial User Support
+ We help facilitate collaboration between commercial users
+ and FreeBSD
+ developers. We also meet with companies to discuss their
+ needs and bring
+ that information back to the Project. In Q3, Ed Maste and
+ Deb Goodkin met
+ with a few commercial users in the US. It is not only
+ beneficial for the
+ above, but it also helps us understand some of the
+ applications where
+ FreeBSD is used. We were also able to meet with a good
+ number of commercial
+ users at vBSDCon and EuroBSDCon. These venues provide an
+ excellent
+ opportunity to meet with commercial and individual users
+ and contributors
+ to FreeBSD. Fundraising Efforts
+ Our work is 100% funded by your donations. We are
+ continuing to work hard
+ to get more commercial users to give back to help us
+ continue our work
+ supporting FreeBSD. More importantly, we'd like to thank
+ our individual
+ donors for making $10-$1,000 donations last quarter, for
+ more than $16,000! Please consider
+ making
+ a donation to help us
+ continue and increase our support for FreeBSD! We also have the Partnership Program, to provide more
+ benefits for our
+ larger commercial donors. Find out more information at
+ www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/
+ and share with your companies. OS Improvements
+ The Foundation supports software development projects to
+ improve the FreeBSD
+ operating system through our full time technical staff,
+ contractors, and
+ project grant recipients. They maintain and improve
+ critical kernel
+ subsystems, add new features and functionality, and fix
+ problems. Over the last quarter there were 345 commits to the
+ FreeBSD base system
+ repository sponsored by the FreeBSD Foundation - this
+ represents about
+ one fifth of all commits during this period. Many of these
+ projects have
+ their own entries in this quarterly report (and are not
+ repeated here). Foundation staff member Konstantin Belousov committed many
+ improvements to
+ multiple kernel subsystems, as well as low-level 32-bit
+ and 64-bit x86
+ infrastructure. These included fixes for robust mutexes,
+ unionfs, the
+ out of memory (OOM) handler, and per-cpu allocators. Additional work included fixes for security issues and
+ introduction and
+ maintenance of vulnerability mitigations, and improving
+ POSIX conformance. Ed Maste committed a number of minor security bug fixes
+ and improvements,
+ as well as the first iteration of a tool for editing the
+ mitigation control
+ ELF note. Additional work included effort on build
+ infrastructure and the
+ tool chain. Clang's integrated assembler (IAS) is now used more
+ widely, as part of the
+ path to retiring the assembler from GNU binutils 2.17.50.
+ The readelf tool
+ now decodes some additional ELF note information. Ed also enabled the Linuxulator (Linux binary support
+ layer) on arm64, and
+ added a trivial implementation of the renameat2 system
+ call (handling common
+ options). Mark Johnston added Capsicum support to a number of ELF
+ Tool Chain utilities,
+ and committed a number of other Capsicum kernel and
+ userland fixes. Mark worked on a number of changes related to security
+ improvements, including
+ integration and support of the Syzkaller automated system
+ call fuzzer, and
+ fixing issues identified by Syzkaller. Other changes
+ included addressing
+ failures caused by refcount wraparound, improvements to
+ the prot_max memory
+ protection. Other work included NUMA, locking, kernel
+ debugging, RISC-V and
+ arm64 kernel improvements. Edward Napierala continued working on Linuxulator
+ improvements over the
+ quarter. The primary focus continued to be tool
+ improvements - strace is now
+ more usable for diagnosing issues with Linux binaries
+ running under the
+ Linuxulator. That said, as with previous work a number of
+ issues have been
+ fixed along the way. These are generally minor issues with
+ a large impact -
+ for example, every binary linked against up-to-date glibc
+ previously
+ segfaulted on startup. This is now fixed. Continuous Integration and Quality Assurance
+ The Foundation provides a full-time staff member who is
+ working on improving
+ our automated testing, continuous integration, and overall
+ quality assurance
+ efforts. During the third quarter of 2019, Foundation staff
+ continued to improve the
+ project's CI infrastructure, worked with contributors to
+ fix the failing build
+ and test cases, and worked with other teams in the Project
+ for their testing
+ needs. We added several new CI jobs and worked on getting
+ the hardware
+ regression testing lab ready. Li-Wen Hsu gave presentations "Testing/CI status update"
+ and "How to work with
+ the FreeBSD CI system" at the
+ 201909
+ DevSummit.
+ Slides are available at the DevSummit page. We continue publishing the CI weekly report on the
+ freebsd-testing@.
+ mailing list, and an archive
+ is available. See the FreeBSD CI section of this report for completed
+ work items and
+ detailed information. Supporting FreeBSD Infrastructure
+ The Foundation provides hardware and support to improve
+ the FreeBSD
+ infrastructure. Last quarter, we continued supporting
+ FreeBSD hardware
+ located around the world. FreeBSD Advocacy and Education
+ A large part of our efforts are dedicated to advocating
+ for the Project.
+ This includes promoting work being done by others with
+ FreeBSD; producing
+ advocacy literature to teach people about FreeBSD and help
+ make the path to
+ starting using FreeBSD or contributing to the Project
+ easier; and attending
+ and getting other FreeBSD contributors to volunteer to run
+ FreeBSD events,
+ staff FreeBSD tables, and give FreeBSD presentations. The FreeBSD Foundation sponsors many conferences, events,
+ and summits around
+ the globe. These events can be BSD-related, open source,
+ or technology events
+ geared towards underrepresented groups. We support the
+ FreeBSD-focused events
+ to help provide a venue for sharing knowledge, to work
+ together on projects,
+ and to facilitate collaboration between developers and
+ commercial users.
+ This all helps provide a healthy ecosystem. We support the
+ non-FreeBSD events
+ to promote and raise awareness of FreeBSD, to increase the
+ use of FreeBSD in
+ different applications, and to recruit more contributors
+ to the Project. Check out some of the advocacy and education work we did
+ last quarter:
+ We continued producing FreeBSD advocacy material to help
+ people promote
+ FreeBSD. Learn more about our recent efforts to advocate
+ for FreeBSD
+ around the world:
+ https://www.freebsdfoundation.org/blog/freebsd-around-the-world/ Our Faces of FreeBSD series is back. Check out the latest
+ post:
+ Roller
+ Angel. Read more about our conference adventures in the
+ conference recaps and trip
+ reports in our monthly newsletters:
+
+ https://www.freebsdfoundation.org/news-and-events/newsletter/ We help educate the world about FreeBSD by publishing the
+ professionally
+ produced FreeBSD Journal. As we mentioned previously, the
+ FreeBSD Journal
+ is now a free publication. Find out more and access the
+ latest issues at
+ https://www.FreeBSDfoundation.org/journal/. You can find out more about
+ events
+ we attended and upcoming events. We opened our official FreeBSD Swag Store. Get stickers,
+ shirts, mugs and
+ more at ShopFreeBSD. We have continued our work with a new website developer to
+ help us improve
+ our website. Work has begun to make it easier for
+ community members to find
+ information and to make the site more efficient. Legal/FreeBSD IP
+ The Foundation owns the FreeBSD trademarks, and it is our
+ responsibility to
+ protect them. We also provide legal support for the core
+ team to investigate
+ questions that arise. Go to http://www.FreeBSDfoundation.org to find out how we
+ support FreeBSD and
+ how we can help you! The FreeBSD X11/Graphics team maintains the lower levels
+ of the FreeBSD graphics
+ stack.
+ This includes graphics drivers, graphics libraries such as
+ the
+ MESA OpenGL implementation, the X.org xserver with related
+ libraries and
+ applications, and Wayland with related libraries and
+ applications. During the last period, several changes have been made,
+ but most of them has
+ been behind the scene.
+ We have also worked on general clean up of old xorg ports
+ that have been
+ deprecated upstream. The ports infrastructure for xorg ports and ports that
+ depend on xorg ports have
+ been updated.
+ We have switched USE_XORG and XORG_CAT
+ to use the USES framework, instead
+ of the old way of including bsd.xorg.mk from
+ bsd.port.mk.
+ This infrastructure work has been fairly substantial, and
+ new ports depending on
+ xorg ports should add USES=xorg to their
+ makefiles.
+ As part of this bsd.xorg.mk was split up, and the
+ XORG_CAT part was split
+ out to USES=xorg-cat.
+ This is used for the xorg ports themselves, and sets up a
+ common environment for
+ building all xorg ports.
+ In addition, framework for pulling xorg ports directly
+ from freedesktop.org
+ gitlab was added, which will make improve development and
+ testing, since it
+ makes it possible to create ports of unreleased versions.
+ Further improvements in this area includes framework for
+ using meson instead of
+ autotools for building xorg ports.
+ This is still a work in progress. We have also worked to clean up and deprecate several old
+ xorg ports and
+ libraries.
+ Some of these ports have already been removed, and some
+ are still waiting on
+ removal after a sufficient deprecation period.
+ Most notably amongst the deprecations are
+ x11/libXp, which required to fix
+ several dependencies.
+ Several other old libraries have also been deprecated,
+ such as x11/Xxf86misc,
+ x11-fonts/libXfontcache and
+ graphics/libGLw.
+ Some applications and drivers have also been deprecated
+ during the period.
+ With the remaining removals in this area, we should be up
+ to speed with
+ deprecations upstream.
+ We are currently investigating if there are new software
+ added upstream that we
+ need to port to FreeBSD. We have also continued our regularly scheduled bi-weekly
+ meetings. People who are interested in helping out can find us on
+ the x11@FreeBSD.org
+ mailing list, or on our gitter chat: https://gitter.im/FreeBSDDesktop/Lobby.
+ We are also available in #freebsd-xorg on EFNet. We also have a team area on GitHub where our work
+ repositories can be found:
+ https://github.com/FreeBSDDesktop The FreeBSD Project is pleased to have participated in
+ Google Summer of Code 2019 marking our 14th year of
+ participation.
+ This year we had six successful projects:
+ We thank Google for the opportunity to work with these
+ students and hope
+ they continue to work with FreeBSD in the future. About - With the introduction of VNET(9)
+ in FreeBSD, Jails are free to
+ set their IP addresses. However, this privilege may need
+ to be limited by
+ the host as per its need for multiple security reasons.
+ This project uses mac(9) for an access control framework
+ to impose
+ restrictions on FreeBSD jails according to rules defined
+ by the root of the
+ host using sysctl(8). It involves the development of a
+ dynamically loadable
+ kernel module (mac_ipacl) based on The TrustedBSD MAC
+ Framework to
+ implement a security policy for configuring the network
+ stack.
+ This project allows the root of the host to define the
+ policy rules to
+ limit the root of a jail to a set of IP (v4 or v6)
+ addresses and/or subnets
+ for a set of interfaces. Features this new MAC policy module are: Submit your entries as Pull Requests from your fork of
FreeBSD
@@ -58,6 +58,8 @@
The July
+ to September 2019 Status Report is now available. 2019 ǯ
+ 7 ·î – 9 ·î³«È¯¿ÊĽ¥ì¥Ý¡¼¥È
+ ¤¬¸ø³«¤µ¤ì¤Þ¤·¤¿¡£ The Whistle Interjet: A ``network appliance'' that acts as a
- router, web server, mailhost (and other functionality), and can be
- configured using a web browser. The underlying operating system is
- FreeBSD, and Whistle have contributed many of their code
- enhancements back to the FreeBSD project (while keeping enough of
- them proprietary that they can stay in business). Similarly to DragonflyBSD, OpenBSD was not a standalone project,
Modified: head/en_US.ISO8859-1/htdocs/copyright/freebsd-doc-license.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/copyright/freebsd-doc-license.xml Sat Nov 30 00:02:18 2019 (r53643)
+++ head/en_US.ISO8859-1/htdocs/copyright/freebsd-doc-license.xml Sat Nov 30 11:03:24 2019 (r53644)
@@ -76,8 +76,8 @@
and the original IEEE and The Open Group Standard, the original
IEEE and The Open Group Standard is the referee document. The
original Standard can be obtained online at
- http://www.opengroup.org/unix/online.html.
+
+
+
+
+
+
+
+
+ https://opensource.org/licenses/BSDplusPatent
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
From owner-svn-doc-head@freebsd.org Mon Nov 25 20:05:36 2019
Return-Path: Next Quarterly Status Report submissions (July –
- September) due: October 31th, 2019
+ Next Quarterly Status Report submissions (October –
+ December) due: January 1th, 2020
2019
+
This notice shall appear on any product containing this material.
Modified: head/en_US.ISO8859-1/htdocs/index.xsl ============================================================================== --- head/en_US.ISO8859-1/htdocs/index.xsl Sat Nov 30 00:02:18 2019 (r53643) +++ head/en_US.ISO8859-1/htdocs/index.xsl Sat Nov 30 11:03:24 2019 (r53644) @@ -325,7 +325,7 @@ The mark FreeBSD is a registered trademark of The FreeBSD Foundation and is used by The FreeBSD Project with the permission of The + href="https://www.freebsdfoundation.org/legal/trademark-usage-terms-and-conditions/">The FreeBSD Foundation. &header2.word.contact; Modified: head/en_US.ISO8859-1/htdocs/news/2002/press.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/2002/press.xml Sat Nov 30 00:02:18 2019 (r53643) +++ head/en_US.ISO8859-1/htdocs/news/2002/press.xml Sat Nov 30 11:03:24 2019 (r53644) @@ -92,22 +92,7 @@ security. -Kerneltrap speaks with Jordan Hubbard, one of the creators - of FreeBSD, and currently manager of Apple's Darwin project.
-Kerneltrap interviews Matt Dillon, one of FreeBSD's key - developers.
-