os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Partially restructure the core team report

Browse source 
Split out the two major issues into enumerated portions for greater
clarity.  Reorder content within the security team reorganization portion
of the entry in order to make more prominent the actual nature of the
restructuring, and improve clarity on the motivation and ramifications
of the changes.

Discussed with: koobs
This commit is contained in:
Benjamin Kaduk 2016-01-19 03:16:56 +00:00
parent b18f6313e0
commit aacfdead69
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=48066
1 changed files with 66 additions and 53 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

73
en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml
View file

@ -2483,47 +2483,58 @@
</contact> </contact>
<body> <body>
<p>Two major concerns have occupied much of core's attention <p>Two major issues have occupied much of core's attention
during the last quarter: the reorganisation of the Security during the last quarter: the reorganisation of the Security
Team and the question of whether to import GPLv3 licensed code Team and the question of whether to import GPLv3 licensed code
into the source repository.</p> into the source repository.</p>
<p>The Security Team reorganisation, first proposed to Core <ol>
during a meeting at BSDCan this year by Gleb Smirnoff &mdash; core <li>
member and newly-appointed deputy Security Officer (SO) &mdash; has now <p>The idea of reorganizing the Security team was first
been accomplished. In order to improve the project's proposed to Core during a meeting at BSDCan this year by
responsiveness to security alerts, to maintain security on Gleb Smirnoff &mdash; core member and newly-appointed deputy
privileged information received in confidence before general Security Officer (SO). The &quot;Security Team&quot;, which
publication and, not least, to reduce the work load on the previously could contain several people (a varying number
security officer, the role of the SO team has been redefined as over time, but more than two) has been refashioned into just
the controller of the distribution of security sensitive two roles: Security Officer and Deputy Security Officer.
information within the project; they are responsible for Accordingly, the role of the SO team has been redefined to
interfacing with external bodies and individuals reporting be the controller of the distribution of security sensitive
security problems, and connecting them with appropriate information into and within the project; they are
individuals within the project with the technical expertise to responsible for interfacing with external bodies and
address the identified concerns. The SO team was cut down to just individuals reporting security problems to the project, and
the Security Officer and their deputy, assisted by a secretary, and connecting those reports to the appropriate individuals
with input and help in drafting security advisories from former within the project with the technical expertise to address
and any potential future Security Officers plus liasons with Core, the identified concerns. These changes will improve the
Cluster Administration and Release Engineering.</p> project's responsiveness to security alerts, help maintain
security on privileged information received in confidence
before general publication and, not least, reduce the work
load on the security officer. The SO team will continue to
benefit from liasons with the Core, Cluster Administration,
and Release Engineering teams, and will be assisted by a
secretary; they will also be able to obtain input and
assistance in drafting security advisories from former and
potential future (Deputy) Security Officers.</p>
<p>Core would particularly like to thank the former members of <p>Core would particularly like to thank the
the Security Team group for their past contributions, now that former members of the Security Team group for their past
the Security Team role has been merged into the Security contributions, now that the Security Team role has been
Officer's responsibilities.</p> merged into the Security Officer's responsibilities.</p>
</li>
<li>
<p>The other large question concerning Core is how to provide a <p>The other large question concerning Core is how to provide a
modern toolchain for all supported achitectures. Tier 1 modern toolchain for all supported achitectures. Tier 1
architectures are required to ship with a toolchain architectures are required to ship with a toolchain
unencumbered by onerous license terms. This is currently unencumbered by onerous license terms. This is currently
provided for i386 and arm64 by the LLVM suite, including the provided for i386 and arm64 by the LLVM suite, including the
Clang compiler, LLD and LLDB. However LLVM support for other Clang compiler, LLD and LLDB. However LLVM support for
(Tier 2 or below) architectures is not yet of sufficient quality other (Tier 2 or below) architectures is not yet of
to be viable, and the older but pre-existing GPLv2 toolchain sufficient quality to be viable, and the older but
cannot support some of the interesting new architectures such pre-existing GPLv2 toolchain cannot support some of the
as arm64 and RISC V. Pragmatically, in order for the project interesting new architectures such as arm64 and RISC V.
to support these, until LLVM support arrives we must turn to the Pragmatically, in order for the project to support these,
GNU project's GPLv3 licenced toolchain.</p> until LLVM support arrives we must turn to the GNU project's
GPLv3 licenced toolchain.</p>
<p>The argument here is whether to import GPLv3 licensed code <p>The argument here is whether to import GPLv3 licensed code
into the &os; src repository with all of the obligations on into the &os; src repository with all of the obligations on
@ -2545,6 +2556,8 @@
circulation amongst all interested parties in order to judge circulation amongst all interested parties in order to judge
community opinion on the matter. Core welcomes feedback from community opinion on the matter. Core welcomes feedback from
all interested parties on the subject.</p> all interested parties on the subject.</p>
</li>
</ol>
<p>Beyond these two big questions, Core has handled a number of <p>Beyond these two big questions, Core has handled a number of
lesser items:</p> lesser items:</p>