Date: Fri, 13 Jan 2017 06:26:34 +0000 (UTC) From: Benjamin Kaduk <bjk@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r49845 - head/en_US.ISO8859-1/htdocs/news/status Message-ID: <201701130626.v0D6QYUR094936@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: bjk Date: Fri Jan 13 06:26:34 2017 New Revision: 49845 URL: https://svnweb.freebsd.org/changeset/doc/49845 Log: Add the core entry from matthew Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml Fri Jan 13 05:52:33 2017 (r49844) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml Fri Jan 13 06:26:34 2017 (r49845) @@ -670,4 +670,113 @@ list on GitHub.</task> </help> </project> + + <project cat='team'> + <title>The &os; Core Team</title> + + <contact> + <person> + <name>&os; Core Team</name> + <email>core@FreeBSD.org</email> + </person> + </contact> + + <body> + <p>The major concern for Core during the last quarter of 2016 has + been about maintaining the effectiveness of secteam. The team is + primarily in need of better project management, both to improve + communication generally and to allow the other team members to + concentrate on the technical aspects of handling + vulnerabilities.</p> + + <p>To that end, there has been agreement in principle for either + the FreeBSD Foundation or one of the companies that are major + &os; users to employ someone specifically in this role.</p> + + <p>Core confirmed that the new support model would go into effect + with 11.0-RELEASE despite the postponement of the switch to a + packaged base release mechanism. For details of the new support + model, please follow the links from the <a + href="https://www.FreeBSD.org/security/security.html">security</a>; + page of the &os; website.</p> + + <p>Core requested the removal of the <tt>misc/jive</tt> port, on + the grounds that it had no function other than to turn text into + an offensively racist parody. This proved controversial, with + many seeing this as a first step in bowdlerizing the entire ports + tree. That is certainly not Core's intention. Core's aim here is + to help secure the future of the &os; project by making it + welcoming to all contributors, regardless of ethnicity, gender, + sexuality or other improper bases for discrimintation. While + <tt>misc/jive</tt> may once have been seen as harmless fun, today + the implicit approval implied by having it in the ports tree sends + a message at odds with the project's aims.</p> + + <p>The Marketing team and the associated marketing@FreeBSD.org + mailing list were wound up, due to lack of activity. Messages to + marketing@FreeBSD.org will be forwarded to the + FreeBSD Foundation's marketing team instead.</p> + + <p>Core member Allan Jude, who was already the clusteradm liason, + became a full member of clusteradm.</p> + + <p>An emergency correction to the 11.0 release notes was + authorised, as it was giving the misleading impression that + 802.11n wireless support had only just been added, and this + misapprehension was being repeated in the press. In reality, &os; + has had 802.11n support for many years, and the announcement + should have said that support had been added to many additional + device drivers.</p> + + <p>Discussions about a proposal to improve Unicode support are + on-going. &os; is already standards conformant, but the + propsal is to switch to a <tt>__STDC_ISO_10646_</tt> + implementation, similar to what Linux glibc currently uses. + Opinions are divided on the technical merits of the new + approach.</p> + + <p>There were the usual quota of queries about licensing and other + legal matters:</p> + + <ul> + <li>Plans to create a GPLv3 overlay for the base system were + shelved in the light of faster than expected progress at + enabling building the world using an external toolchain.</li> + + <li>The trademarks page on the website was updated to show the + current owners of a number of trademarks in their approved + form.</li> + + <li>In the absense of a tool to extract and summarize all of the + relevant information, the obligation in the BSD license that + "Redistributions in binary form must reproduce the above + copyright notice, this list of conditions and the following + disclaimer in the documentation and/or other materials provided + with the distribution." is fulfilled by providing a tarball of + the system sources with their embedded copyright + statements.</li> + + <li>The European Court of Justice's "Right to be + Forgotten" only applies to search engines, and the &os; + project is not one of those, so need not take any action.</li> + + <li>Core is following closely discussions within the LLVM + project regarding a change of license which if implemented, + might require an audit of the + entire ports tree to discover all packages that contain binaries + linked against libc++ and ensure that they are licensed + compatibly with LLVM. However, indications are that the LLVM + project will not adopt such changes.</li> + + <li>The "Open Source Exception" in the firmware + license means that committing a "binary blob" driver + for the Nvidia Jetson TK1 XHCI device is acceptable.</li> + </ul> + + <p>During this quarter four new commit bits were awarded. Please + welcome Dexuan Cui, David Bright, Konrad Witaszczyk, and Piotr + Stefaniak. We were sorry to see Edwin Lansing hang up his commit + bits and step down from portmgr.</p> + </body> + </project> </report>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201701130626.v0D6QYUR094936>