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

Add the Core report from Matthew Seaman <m.seaman@FreeBSD.org>.

Browse source
This commit is contained in:
Warren Block 2015-07-14 07:01:30 +00:00
parent a55862be98
commit 8a1f3de453
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=46964
1 changed files with 73 additions and 0 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-04-2015-06.xml
View file

@ -833,4 +833,77 @@
</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 &os; Core Team constitutes the project's "Board of
Directors", responsible for deciding the project's overall
goals and direction as well as managing specific areas of the
&os; project landscape.</p>
<p>In order to help attract fresh developer talent to &os;, Core
has a general policy to make available an up-to-the-minute
suite of developer tools and services. Core has long been
encouraging &os; committers to make full use of the project's
Phabricator instance at
<a href="https://reviews.FreeBSD.org/">https://reviews.FreeBSD.org</a>,
and now has supported the Phabricator admins in opening access
to anyone interested enough to sign up for an account.</p>
<p>Further developments under consideration include setting up a
FreeBSD.org oauth2 provider and permitting oauth-style Single
Sign-On access to most FreeBSD web-based services. Developers
and members of the public would additionally be able to use
credentials from other providers such as GitHub, Twitter, or
Google to authenticate themselves to &os; web services.</p>
<p>Mark Murray raised a problem he has been having for some time
with getting adequate security review of his proposed changes
to <tt>random(9)</tt>. This is an extremely security
sensitive area of the kernel where errors can have disastrous
consequences. Core has been able to drum up a number of
reviewers and they have made significant progress in
simplifying the design, eliminating some difficult portions of
code, and reducing any potential attack surface. Work is
still ongoing and Core remains open to the idea of bringing in
external reviewers with specialist cryptographic
knowledge.</p>
<p>Dag-Erling Sm&oslash;rgrav resigned as Security Officer
towards the end of May. Core was sorry to see him step down,
but unanimously pleased to welcome his nominee and former
deputy, Xin Li, as his successor. Xin has since appointed
Gleb Smirnoff (who also happens to be a current member of
core) as his new deputy. Between them and Core they have some
fairly radical ideas under discussion about how to improve the
project's responsiveness to security issues.</p>
<p>Shortly after BSDCan in mid-June, Warner Losh proposed a
change to <tt>style(9)</tt> which resulted in some lively
discussion. An informal poll was conducted via Phabricator
and the change was committed within a couple of days.
Unfortunately, this did not meet with universal approval and
Core was called upon to arbitrate. Warner backed out the
change, recognizing that there had not been enough time
allowed for proper discussion. Many people were still in
transit from BSDCan, and the voting arrangements did not suit
everyone. A new poll has since been held, with votes either
by e-mail or the Slowvote facility of Phabricator. This
resulted in approval of the change by a wide margin.</p>
<p>During this period we had two new commit bits awarded, and
one taken in for safekeeping. Welcome aboard to Chris Torek
and Mariusz Zeborski, and we were very sorry indeed to see
Steve Kargl decide to call it a day.</p>
</body>
</project>
</report>