Date: Mon, 24 Dec 2018 10:07:27 +0000 (UTC) From: Edward Tomasz Napierala <trasz@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52717 - head/en_US.ISO8859-1/htdocs/news/status Message-ID: <201812241007.wBOA7R3j071972@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: trasz Date: Mon Dec 24 10:07:27 2018 New Revision: 52717 URL: https://svnweb.freebsd.org/changeset/doc/52717 Log: Add Quarterly Status Report for 2018Q3. Reviewed by: allanjude, bcr (mentors) Approved by: allanjude, bcr (mentors) Differential Revision: https://reviews.freebsd.org/D18639 Added: head/en_US.ISO8859-1/htdocs/news/status/report-2018-01-2018-09.xml (contents, props changed) Modified: head/en_US.ISO8859-1/htdocs/news/status/Makefile Modified: head/en_US.ISO8859-1/htdocs/news/status/Makefile ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/Makefile Mon Dec 24 08:12:04 2018 (r52716) +++ head/en_US.ISO8859-1/htdocs/news/status/Makefile Mon Dec 24 10:07:27 2018 (r52717) @@ -80,6 +80,7 @@ XMLDOCS+= report-2017-01-2017-03 XMLDOCS+= report-2017-04-2017-06 XMLDOCS+= report-2017-07-2017-09 XMLDOCS+= report-2017-10-2017-12 +XMLDOCS+= report-2018-01-2018-09 XSLT.DEFAULT= report.xsl Added: head/en_US.ISO8859-1/htdocs/news/status/report-2018-01-2018-09.xml ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2018-01-2018-09.xml Mon Dec 24 10:07:27 2018 (r52717) @@ -0,0 +1,3374 @@ +<?xml version="1.0" encoding="utf-8" ?> +<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for + Status Report//EN" + "http://www.FreeBSD.org/XML/share/xml/statusreport.dtd" > + +<!-- $FreeBSD$ --> +<!-- This file was generated with https://github.com/trasz/md2docbook --> +<!-- + Variables to replace: + %%START%% - report month start + %%STOP%% - report month end + %%YEAR%% - report year + %%NUM%% - report issue (first, second, third, fourth) + %%STARTNEXT%% - report month start + %%STOPNEXT%% - report month end + %%YEARNEXT%% - next report due year (if different than %%YEAR%%) + %%DUENEXT%% - next report due date (i.e., June 6) +--> + +<report> + <date> + <month>%%START%%-%%STOP%%</month> + + <year>%%YEAR%%</year> + </date> + + <section> + <title>Introduction</title> + + <p>With &os; having gone all the way to 12, it is perhaps + useful to take a look back at all the things that have been + accomplished, in terms of many visible changes, as well as all + the things that happen behind the scenes to ensure that &os; + continues to offer an alternative in both design, + implementation, and execution.</p> + + <p>The things you can look forward to reading about are too + numerous to summarize, but cover just about everything from + finalizing releases, administrative work, optimizations + and depessimizations, features added and fixed, and many areas + of improvement that might just surprise you a little.</p> + + <p>Please have a cup of coffee, tea, hot cocoa, or other beverage + of choice, and enjoy this culmulative set of reports covering + everything that's been done since October, 2017.</p> + + <p>—Daniel Ebdrup</p> + </section> + + <category> + <name>team</name> + + <description>&os; Team Reports</description> + + <p>Entries from the various official and semi-official teams, + as found in the <a href="&enbase;/administration.html">Administration + Page</a>.</p> + </category> + + <category> + <name>proj</name> + + <description>Projects</description> + + <p>Projects that span multiple categories, from the kernel and userspace + to the Ports Collection or external projects.</p> + </category> + + <category> + <name>arch</name> + + <description>Architectures</description> + + <p>Updating platform-specific features and bringing in support + for new hardware platforms.</p>. + </category> + + <category> + <name>ports</name> + + <description>Ports</description> + + <p>Changes affecting the Ports Collection, whether sweeping + changes that touch most of the tree, or individual ports + themselves.</p> + </category> + + <category> + <name>doc</name> + + <description>Documentation</description> + + <p>Noteworthy changes in the documentation tree or new external + books/documents.</p> + </category> + + <category> + <name>third</name> + + <description>Third-Party Projects</description> + + <p>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.</p> + </category> + + <project cat='team'> + <title>Release Engineering Team</title> + + <contact> + <person> + <name>FreeBSD Release Engineering Team</name> + <email>re@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="https://www.FreeBSD.org/releases/10.4R/announce.html">FreeBSD 10.4-RELEASE announcement</url> + <url href="https://www.FreeBSD.org/releases/11.2R/announce.html">FreeBSD 11.2-RELEASE announcement</url> + <url href="https://www.FreeBSD.org/releases/12.0R/schedule.html">FreeBSD 12.0-RELEASE schedule</url> + <url href="https://download.FreeBSD.org/ftp/snapshots/ISO-IMAGES/">FreeBSD development snapshots</url> + </links> + + <body> + <p>The FreeBSD Release Engineering Team responsibilities + include:</p> + + <ul> + <li>setting and publishing release schedules for official + project releases</li> + </ul> + + <p>of FreeBSD</p> + + <ul> + <li>announcing code slushes, freezes, and thaws</li> + + <li>maintaining the respective branches for all supported + releases</li> + </ul> + + <p> + The FreeBSD Release Engineering Team, led by Marius + Strobl, + completed the 10.4-RELEASE in early October 2017. FreeBSD + 10.4-RELEASE was the + fifth release from the <tt>stable/10</tt> branch, which + built on the + stability and reliability of 10.3-RELEASE.</p> + + <p>The FreeBSD 11.2-RELEASE cycle started April 20, 2018 with + the + announcement of the code slush. The first stage progress + was + continued throughout the rest of the quarter with the code + freeze, + followed by three BETA builds, three RC builds, and the + final release + build was announced June 27, 2018.</p> + + <p>The FreeBSD Release Engineering Team started the + 12.0-RELEASE cycle + August 10, 2018 with the announcement of the code slush. + The code + freeze followed on August 24, 2018. The tentative date for + the <tt>stable/12</tt> branch was expected to be September 21, + 2018.</p> + + <p> + Due to unforeseen circumstances with upstream code that + was necessary + to include in 12.0-RELEASE, the tentative release schedule + needed + to be adjusted several times. The API changes in the + updated version + of the upstream code required changes to be made for all + base system + utilities that linked with the upstream code. By the end + of the + 2018Q3 quarter, the <tt>stable/12</tt> branch had not been + created due to + this delay.</p> + + <p>Throughout the remainder of 2018Q3, several development + snapshots builds + were released for the <tt>head</tt>, <tt>stable/11</tt>, + and <tt>stable/10</tt> branches.</p> + + <p>Much of this work was sponsored by the FreeBSD Foundation.</p> + + </body> + + </project> + + <project cat='team'> + <title>Ports Collection</title> + + <contact> + <person> + <name>René Ladan</name> + <email>portmgr-secretary@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="https://www.FreeBSD.org/ports/">About FreeBSD Ports</url> + <url href="https://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to ports</url> + <url href="http://portsmon.FreeBSD.org/index.html">FreeBSD ports monitoring</url> + <url href="https://www.FreeBSD.org/portmgr/index.html">Ports Management Team</url> + <url href="@freebsd_portmgr)](https://twitter.com/freebsd_portmgr/">FreeBSD portmgr (@freebsd_portmgr)</url> + <url href="Facebook)](https://www.facebook.com/portmgr">FreeBSD Ports Management Team (Facebook)</url> + <url href="Google+)](https://plus.google.com/communities/108335846196454338383">FreeBSD Ports Management Team (Google+)</url> + </links> + + <body> + <p>During the first quarter of 2018, the number of ports grew + to almost 32,000. + In 2018Q1, there were + 2,100 open PRs with fewer than 600 unassigned. There were + 7,900 commits from 169 committers. Compared to last + quarter, the number + of commits grew by 18% and the number of PRs dropped by + 25%. Those are + some good numbers!</p> + + <p>During the 2018Q2 and 2018Q3 quarters, the number of ports + grew to just under + 34,000. The number of open PR grew to almost 2,500 with + fewer than 600 + of those unassigned. A total of 175 committers made almost + 14,200 commits. + Compared to the first quarter, the number of commits + dropped by 10% and + the number of PRs grew by 19%.</p> + + <p>During the last three quarters, portmgr took twelve commit + bits in for + safekeeping: daichi@, deichen@, ian@, junovitch@, kevlo@, + maho@, nemysis@, + pawel@, rea@, tabthorpe@, vg@, and wxs@.</p> + + <p>Portmgr welcomed thirteen new committers in 2018Q2 and + 2018Q3:</p> + + <ul> + <li>Devin Teske (dteske@)</li> + + <li>Eric Turgeon (ericbsd@)</li> + + <li>Fernando Apesteguía (fernape@)</li> + + <li>Fukang Chen (loader@)</li> + + <li>Gleb Popov (arrowd@)</li> + + <li>Jesper Schmitz Mouridsen (jsm@)</li> + + <li>John Hixson (jhixson@)</li> + + <li>Kevin Bowling (kbowling@)</li> + + <li>Koichiro IWAO (meta@)</li> + + <li>Mateusz Piotrowski (0mp@)</li> + + <li>Matthias Fechner (mfechner@)</li> + + <li>Sergey Kozlov (skozlov@)</li> + </ul> + + <p> + The following committers returned after a hiatus:</p> + + <ul> + <li>Ion-Mihai Tetcu (itetcu@)</li> + + <li>Kevin Lo (kevlo@)</li> + + <li>Sean Chittenden (seanc@)</li> + </ul> + + <p> + During the last three quarters, Antoine Brodin (antoine@) + ran no + fewer than 113 exp-runs against the ports tree. These runs + were + executed to test updates, perform cleanups, and make + improvements + to the framework and the base system. Most of the runs + were for + port upgrades, but others include LLD progress, changes to + the + default port versions, improved support for armv6, armv7, + and RISC-V + architectures, removed old base system functionality, new + USES, and + better matching pkg-plist with Makefile options (DOCS and + EXAMPLES).</p> + + <p>Five new USES values were introduced:</p> + + <ul> + <li>apache: handle dependencies on the Apache web server and + modules</li> + + <li>eigen: automatically depend on math/eigen2 or math/eigen3</li> + + <li>emacs: handle dependencies on the Emacs editor and + modules.</li> + + <li>gl replaces the old USE_GL from bsd.port.mk</li> + + <li>qt-dist, qt:4 and qt:5 replace the old USE_QT from + bsd.qt.mk</li> + </ul> + + <p> + The EXTRA_PATCHES functionality has been extended to + support + directories, where it will automatically apply all + patch-\* files to the port.</p> + + <p>Ports using USES=php:phpize, php:ext, php:zend, and + php:pecl have + been flavored and packages are now automatically built + for all + versions of PHP that are supported (5.6, 7.0, 7.1 or 7.2).</p> + + <p>2018Q3 had updates of major ports: pkg 1.10.5, Chromium + 65.0.3325.181, Firefox 59.0.2, Firefox-ESR 52.7.3, Ruby + 2.3.7/2.5.1 + and Qt5 5.9.4. + The default version of PHP was changed from 5.6 to 7.1. + The former + version of PHP is no longer supported by the developers. + The + default versions of Samba and GCC are now respectively 4.7 + and 7. The + Xorg ports have been reorganized and there have been + changes to + net/openntpd. Please review the UPDATING file for relevant + details.</p> + + <p>Open tasks:</p> + + <ul> + <li>The number of commits dropped somewhat over the last three + quarters, + leaving more PRs unresolved. If possible, please pick up + some PRs + and improve everyone's experience.</li> + </ul> + + </body> + + </project> + + <project cat='team'> + <title>Core Team</title> + + <contact> + <person> + <name>FreeBSD Core Team</name> + <email>core@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Much of Core's focus for the past months has been on three + items:</p> + + <p>1. Coordination between different groups to support the + upcoming 12.0 release. The timing of the OpenSSL + 1.1.1 release posed challenges, the new OpenSSL + version included API changes, many components of + the base system and ports required changes. + Staying with the older OpenSSL in 12.0 was not a + feasible option, because it would have meant + backporting many changes to a version of OpenSSL + that would be unmaintained by the upstream source.</p> + + <p>2. Discussions with the release engineering team and Scott + Long about updating the FreeBSD release process. + Topics for exploration include:</p> + + <ul> + <li>having more frequent point releases</li> + + <li>changing the support model</li> + + <li>revising and improving the tooling used to manage the tree + and releases</li> + + <li>additional topics as they are discovered</li> + </ul> + + <p>3. Gathering information to make decisions more + data-driven. For example, we are planning + developer and user surveys. If there are questions + that you think should be added to the survey, + please discuss them on freebsd-arch@. We are + exploring ways for automated user-driven hardware + usage data to understand the changing ways our + software is used and to target better hardware + support.</p> + + <p>Here are other noteworthy events (in chronological order) + since the last quarterly report.</p> + + <p>2017 Q4</p> + + <ul> + <li>Sean Eric Fagan's (sef@) commit bit was reactivated with a + period of re-mentoring under Alexander Motin + (mav@).</li> + + <li>The MIPS architecture was promoted to tier 2 status.</li> + + <li>Core approved changes to the Code of Conduct.</li> + + <li>All fortune data files, except freebsd-tips, were removed + in r325828.</li> + + <li>Core approved the adoption of a policy requiring any + license exceptions to be recorded alongside code.</li> + + <li>Gordon Tetlow (gordon@) became the new security officer.</li> + + <li>Core approved the use of SPDX tags.</li> + </ul> + + <p> + 2018 Q1</p> + + <ul> + <li>Jeb Cramer (jeb@) was awarded a src commit bit under the + mentorship of Sean Bruno (sbruno@) and Eric Joyner + (erj@).</li> + + <li>Members of the CoC Review Team were approved. The + membership is to be reviewed once per year.</li> + + <li>A vendor commit bit was awarded to Slava Shwartsman + (slavash@) of Mellanox Technologies under the + mentorship of Konstantin Belousov (kib@) and Hans + Petter Selasky (hselasky@).</li> + + <li>Walter Schwarzenfeld was awarded project membership.</li> + + <li>Brad Davis (brd@) was awarded a src commit bit under the + mentorship of Allan Jude (allanjude@) with + Baptiste Daroussin (bapt@) as co-mentor.</li> + + <li>Vincenzo Maffione (vmaffione@) was awarded a src commit + bit under the mentorship of Hiroki Sato (hrs@).</li> + + <li>Ram Kishore Vegesna (ram@) was awarded a src commit bit + under the mentorship of Kenneth D. Merry (ken@) + and Alexander Motin (mav@).</li> + </ul> + + <p>2018 Q2</p> + + <ul> + <li>Tom Jones (thj@) was awarded a src commit bit under the + mentorship of Jonathan T. Looney (jtl@).</li> + + <li>Matt Macy's (mmacy@) commit bit was restored under the + mentorship of Sean Bruno (sbruno@).</li> + + <li>Breno Leitao (leitao@) was awarded a src commit bit under + the mentorship of Justin Hibbits (jhibbits@) with + Nathan Whitehorn (nwhitehorn@) as co-mentor.</li> + + <li>Leandro Lupori (luporl@) was awarded a src commit bit + under the mentorship of Justin Hibbits (jhibbits@) + with Nathan Whitehorn (nwhitehorn@) as co-mentor.</li> + + <li>The handover from the ninth to the tenth elected Core team + took place. The tenth Core members are: Allan Jude + (allanjude@), Benedict Reuschling (bcr@), Brooks + Davis (brooks@), Hiroki Sato (hrs@), Warner Losh + (imp@), Jeff Roberson (jeff@), John Baldwin + (jhb@), Kris Moore (kmoore@), and Sean Chittenden + (seanc@).</li> + + <li>Joseph Mingrone (jrm@) was appointed the Core secretary + under mentorship of the retiring Core secretary, + Matthew Seaman (matthew@).</li> + + <li>The new team liaisons were decided. portmgr: Sean, doceng: + Hiroki, secteam: Brooks, re: John, clusteradm: + Allan, CoC: Warner, Foundation: Benedict, + bugmeister: John, CI: Sean.</li> + + <li>David Maxwell (dwm@) was awarded project membership.</li> + + <li>Daichi Goto's (daichi@) commit bit was reactivated with a + period of re-mentoring under George Neville-Neil + (gnn@).</li> + + <li>A vendor commit bit was awarded to Ben Widawsky + (bwidawsk@) of Intel under the mentorship of Ed + Maste (emaste@).</li> + </ul> + + <p> + 2018 Q3</p> + + <ul> + <li>Core decided to begin meeting twice per month in an + attempt to catch up with many new agenda items.</li> + + <li>Li-Wen Hsu (lwhsu@) was awarded a src commit bit under the + mentorship of Mark Johnston (markj@) with Ed Maste + (emaste@) as co-mentor.</li> + + <li>Samy al Bahra was awarded project membership.</li> + + <li>George Neville-Neil (gnn@) was approved to begin + co-mentoring Vincenzo Maffione (vmaffione@).</li> + </ul> + + </body> + + </project> + + <project cat='team'> + <title>The FreeBSD Foundation</title> + + <contact> + <person> + <name>Deb Goodkin</name> + <email>deb@FreeBSDFoundation.org</email> + </person> + </contact> + + <body> + <p>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, quality assurance, and release + engineering 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.</p> + + <p>Here are some highlights of what the FreeBSD Foundation + did to help FreeBSD last quarter:</p> + + <p>Partnerships and Commercial User Support</p> + + <p>As a 501(c)(3) non-profit, we don't directly support + commercial users, but we do work with them to + understand their needs and help facilitate + collaboration with the community. Last quarter we + met with a few key FreeBSD users and supporters, + to discuss pain points, how they can contribute + back to FreeBSD, and what technologies they would + like to see supported, to support FreeBSD over + more of their technologies and products.</p> + + <p>As many of you know, we formed a partnership with Intel + around one and a half years ago. Since then the + people we worked directly with left the company, + but it moved us into a new relationship with their + Open Source Technology Center (OTC).</p> + + <p>We are very encouraged that Intel has dedicated additional + resources from the OTC to work on FreeBSD in + addition to existing resources from the networking + group and other technologies such as QuickAssist. + Much of the work has been focused on security and + OS mitigations but we're also focusing on other + areas such as power management and persistent + memory. In May and again in July we traveled to + Intel's Hillsboro campus to meet with management + and engineers from OTC and the networking team. We + presented an overview of the project and + Foundation and also discussed key markets and + vendors who use FreeBSD in their products or + services and their future requirements.</p> + + <p>Intel was also interested in learning more about who + contributes to FreeBSD. Along those lines we've + done some work with OTC to create scripts and + organizational mappings to answer that question. + Note that we do need developers + to help us update and maintain the organizational + mappings as we understand that developers do tend + to move around and contractors are often working + on behalf of multiple organizations.</p> + + <p>Fundraising Efforts</p> + + <p>Our work is 100% funded by your donations. As of September + 30, we raised $328,482. Our 2018 fundraising goal + is $1,250,00 and we are continuing to work hard to + meet and exceed this goal! Please consider making + a donation to help us continue and increase our + support for FreeBSD: <a + href="https://www.FreeBSDfoundation.org/donate/">https://www.FreeBSDfoundation.org/donate/</a>.</p>; + + <p>We also have a new Partnership Program, to provide more + benefits for our larger commercial donors. Find + out more information at <a + href="https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/">https://www.FreeBSDfoundation.org/FreeBSD-foundation-partnership-program/</a>; + and share with your companies!</p> + + <p>OS Improvements</p> + + <p>The Foundation improves the FreeBSD operating system by + employing technical staff to maintain and improve + critical kernel subsystems, add features and + functionality, and fix problems. This also + includes funding separate project grants like the + arm64 port, porting the blacklistd access control + daemon, and the integration of VIMAGE support, to + make sure that FreeBSD remains a viable solution + for research, education, computing, products and + more.</p> + + <p>We kicked off or continued the following projects last + quarter:</p> + + <ul> + <li>OpenZFS RAID-Z Expansion project</li> + + <li>Headless mode out-of-the-box for embedded ARM boards like + the Beaglebone Black</li> + + <li>Performance and scalability improvements</li> + </ul> + + <p> + Having software developers on staff has allowed us to jump + in and work directly on projects to improve + FreeBSD such as:</p> + + <ul> + <li>ZFS improvements</li> + + <li>New Intel server support</li> + + <li>kqueue(2) updates</li> + + <li>64-bit inode support</li> + + <li>Stack guard</li> + + <li>Kernel Undefined Behavior Sanitizer</li> + + <li>Toolchain projects</li> + + <li>i915 driver investigation</li> + + <li>NVDIMM support in acpiconf(8)</li> + + <li>Continuous integration dashboard (web page and physical + hardware)</li> + + <li>FAT filesystem support in makefs(8)</li> + </ul> + + <p> + Continuous Integration and Quality Assurance</p> + + <p>The Foundation provides a full-time staff member who is + working on improving our automated testing, + continuous integration, and overall quality + assurance efforts.</p> + + <p>Foundation employee Li-Wen Hsu set up new CI servers to + speed up amd64 build and test jobs, to reduce the + latency between changes being committed and + results being available. Li-Wen also set up a + staging / development server in order to test + changes to the CI system itself without affecting + production results. We have also started a small + hardware test lab, currently connected to the + staging server, that tests the full boot and test + cycle on physical hardware. In the near future + additional hardware devices will be added, and + this will migrate to the production CI server.</p> + + <p>Release Engineering</p> + + <p>The Foundation provides a full-time staff member to lead + the release engineering efforts. This has provided + timely and reliable releases over the last five + years.</p> + + <p>Foundation employee Glen Barber continued leading the + efforts on the upcoming 12.0-RELEASE. For details + surrounding the work involved and progress thus + far on 12.0-RELEASE, please see the FreeBSD + Release Engineering Team section of this quarterly + status report.</p> + + <p>Supporting FreeBSD Infrastructure</p> + + <p>The Foundation provides hardware and support to improve + the FreeBSD infrastructure. Last quarter, we + continued supporting FreeBSD hardware located + around the world.</p> + + <p>FreeBSD Advocacy and Education</p> + + <p>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.</p> + + <p>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.</p> + + <p>Check out some of the advocacy and education work we did + last quarter:</p> + + <ul> + <li>Organized and ran the Essen FreeBSD Hackathon in Essen, + Germany</li> + + <li>Participated in the FreeBSD Developer Summit BSDCam, in + Cambridge, England</li> + + <li>Represented FreeBSD at the ARM Partner Meeting</li> + + <li>Presented and taught about FreeBSD at SdNOG 5 in Khartoum, + Sudan</li> + + <li>Exhibited and gave a talk at OSCON 2018 in Portland, OR</li> + + <li>Exhibited at the 2018 Grace Hopper Celebration and + sponsored as a Silver Non-Profit Sponsor</li> + + <li>Exhibited at COCON 2018 in Taipei, Taiwan</li> + + <li>Sponsored and gave presentations and tutorials at + EuroBSDCon in Bucharest, Romania</li> + + <li>Organized and ran the Bucharest FreeBSD Developer Summit</li> + + <li>Sponsored the 2018 USENIX Security Symposium in Baltimore, + MD as an Industry Partner</li> + + <li>Provided FreeBSD advocacy material</li> + + <li>Sponsored the 2018 USENIX Annual Technical Conference in + Boston, MA as an Industry Partner</li> + + <li>Sponsored the OpenZFS Developer Summit as a Silver Sponsor</li> + + <li>Presented and taught about FreeBSD at SANOG32 in Dhaka, + Bangladesh</li> + + <li>Sponsored the SNIA Storage Developer Conference 2018 as an + Association Partner</li> + + <li>Provided 11 travel grants to FreeBSD contributors to + attend many of the above events.</li> + </ul> + + <p> + We continued producing FreeBSD advocacy material to help + people promote FreeBSD around the world.</p> + + <p>Read more about our conference adventures in the + conference recaps and trip reports in our monthly + newsletters: <a + href="https://www.freebsdfoundation.org/news-and-events/newsletter/">https://www.freebsdfoundation.org/news-and-events/newsletter/</a></p>; + + <p>We help educate the world about FreeBSD by publishing the + professionally produced FreeBSD Journal. Last + quarter we published the July/August issue that + you can find at <a + href="https://www.FreeBSDfoundation.org/journal/">https://www.FreeBSDfoundation.org/journal/</a>.</p>; + + <p>You can find out more about events we attended and + upcoming events at <a + href="https://www.FreeBSDfoundation.org/news-and-events/">https://www.FreeBSDfoundation.org/news-and-events/</a>.</p>; + + <p>Legal/FreeBSD IP</p> + + <p>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.</p> + + <p>Go to <a + href="http://www.FreeBSDfoundation.org">http://www.FreeBSDfoundation.org</a>; + to find out how we support FreeBSD and how we can + help you!</p> + + </body> + + </project> + + <project cat='team'> + <title>Continuous Integration</title> + + <contact> + <person> + <name>Jenkins Admin</name> + <email>jenkins-admin@FreeBSD.org</email> + </person> + <person> + <name>Li-Wen Hsu</name> + <email>lwhsu@FreeBSD.org</email> + </person> + </contact> + + <links> + <url href="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</url> + <url href="https://artifact.ci.FreeBSD.org/">FreeBSD CI artifact archive</url> + <url href="https://wiki.FreeBSD.org/Jenkins">FreeBSD Jenkins wiki</url> + <url href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing">freebsd-testing Mailing List</url> + <url href="https://github.com/freebsd/freebsd-ci">freebsd-ci Repository</url> + </links> + + <body> + <p>The FreeBSD CI team maintains continuous integration tasks + for FreeBSD. The CI + system regularly checks the changes committed to the + project's Subversion + repository can be successfully built, and performs various + tests and analysis + with the build results. The CI team also maintains the + archive of the artifact + built by the CI system, for the further testing and + debugging needs.</p> + + <p>Starting from June 2018, the project is sponsored by the + FreeBSD Foundation in + hardware and staff. For more details of the sponsored + projects, please refer + to:</p> + + <p><a + href="https://www.freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-september-2018/">https://www.freebsdfoundation.org/news-and-events/newsletter/freebsd-foundation-update-september-2018/</a></p>; + + <p>In addition to that, we also helped checking regressions + for OpenSSL 1.1.1 + update and test continuously for 12-STABLE branch.</p> + + <p>We had meetings and working groups at two developer + summits during 2018Q3:</p> + + <ul> + <li><a + href="https://wiki.FreeBSD.org/DevSummit/201808/Testing">BSDCam + 2018</a></li> + + <li><a + href="https://wiki.FreeBSD.org/DevSummit/201809">EuroBSDCon + 2018</a></li> + </ul> + + <p> + Work in progress:</p> + + <ul> + <li>Fixing the failing test cases and builds</li> + + <li><a + href="https://ci.FreeBSD.org/job/FreeBSD-head-amd64-dtrace_test/lastCompletedBuild/testReport/">DTrace + test</a></li> + + <li><a + href="https://ci.FreeBSD.org/job/FreeBSD-head-amd64-test_zfs/lastCompletedBuild/testReport/">ZFS + test</a></li> + + <li><a + href="https://ci.FreeBSD.org/job/FreeBSD-head-amd64-gcc/">GCC + build</a></li> + + <li>Adding drm ports building test against -CURRENT</li> + + <li>Adding tests for selected project branches, e.g.: + clang700-import</li> + + <li>Adding new hardware to the embedded testbed</li> + + <li>Implementing automatic tests on bare metal hardware</li> + + <li>Planning running ztest and network stack tests</li> + </ul> + + </body> + + </project> + + <project cat='proj'> + <title>4G/4G address space split for i386</title> + + <contact> + <person> + <name>Konstantin Belousov</name> + <email>kib@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>Most 32-bit FreeBSD architectures, including i386, started + to suffer + from the rapid growth of the size of software during the + past decade. + When a 32-bit address space is enough space for a given + task, 32-bit + mode still has an intrinsic advantage over 64-bit mode, + due to less + memory traffic and more economical use of caches. It has + grown + harder to provide the self-hosting i386 system build due + to the + increase in size of the build tools.</p> + + <p>The FreeBSD i386 kernel, prior to the 12.0-RELEASE + version, split + the 4GB address space of the platform into 3GB (minus 4MB) + accessible + to userspace accesses and 1GB for kernel accesses. + Neither kernel nor userspace could access a full 4GB + address space. + Programs that require very large virtual address spaces, + such as + clang when compiling or lld when linking, could run out of + address + space: 3GB of address space was insufficient for their + operation. + The kernel also had trouble fitting into the traditional + 1GB + limitation of address space with the modern sizing for + network + buffers, ZFS and other KVA-hungry in-kernel subsystems.</p> + + <p>In FreeBSD 12, the i386 architecture has been changed to + provide + dedicated separate address spaces for userspace and + kernel, giving + each mode full access to 4GB (minus 8MB) of usable address + space. + The userspace on the i386 architecture now has access to + the same + amount of address space as the compat32 subsystem in the + amd64 + architecture kernel. The increase in kernel address space + enables + further growth and maintainability of the i386 + architecture.</p> + + <p>The split 4GB/4GB user/kernel implementation uses two page + directory + entries (PDEs) shared between modes: one for mapping the + page table, + another for the mode switching trampoline and other + required system *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201812241007.wBOA7R3j071972>