Add 2017Q2 core@ entry from matthew
This commit is contained in:
Benjamin Kaduk
parent
6f24f9b098
commit
d176322bb0
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=50617
1 changed files with 147 additions and 0 deletions
|
|
@ -2494,4 +2494,151 @@
|
|||
above.</p>
|
||||
</body>
|
||||
</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>Core's activities during the second quarter culminated in
|
||||
the introduction of two new initiatives during BSDCan:</p>
|
||||
|
||||
<ul>
|
||||
<li>Extending &os; Project Membership</li>
|
||||
|
||||
<li>The &os; Community Process</li>
|
||||
</ul>
|
||||
|
||||
<h3>&os; Project Members</h3>
|
||||
|
||||
<p>&os; Project Membership being extended to more than just
|
||||
committers is a step that enables the Project to recognise and
|
||||
reward people who support us in ways other than by writing
|
||||
code. People that organise conferences or user groups; who
|
||||
are prominent supporters on social media; who triage bug
|
||||
reports and who test changes; and many others who contribute
|
||||
in various ways, are deserving of recognition of the support
|
||||
that they give to the Project. Core hopes that this will both
|
||||
encourage more people to volunteer their time and effort on
|
||||
behalf of the project, and encourage those who do to stick
|
||||
with the Project, if not become more deeply involved.</p>
|
||||
|
||||
<p>The naming for the new group of non-committer Project members
|
||||
took a few tries to get right: having tried, and rejected
|
||||
"Contributor" and then "Associate", Core
|
||||
took the view that since what they were offerring was formal
|
||||
Project Membership, then that was the right thing to call it.
|
||||
Committers thus become those Project Members with access to
|
||||
commit to the Project's Code repositories. Project Members
|
||||
receive an @FreeBSD.org e-mail address, access to various
|
||||
Project hardware, access to internal mailing lists and other
|
||||
communications channels, and invitations to attend Developer
|
||||
Summits in their own right. Committers in addition have
|
||||
commit rights in the Subversion repositories and GitHub, and
|
||||
active Committers can vote in Core team elections.</p>
|
||||
|
||||
<h3>The &os; Community Process</h3>
|
||||
|
||||
<p>This is an idea that has a long pedigree within other projects,
|
||||
and &os; is very consciously modelling its implementation on
|
||||
what has worked elsewhere. When a significantly disruptive or
|
||||
wide-scale change is proposed, we should have a formal
|
||||
mechanism for documenting the change and what it implies.
|
||||
Interested parties can then respond and the change can be
|
||||
evolved into the best fit for all users, or else it can be
|
||||
found to be impracticable and withdrawn. The documentation of
|
||||
the change will remain as a point of reference should the same
|
||||
or a similar proposal come up in the future. Creating a more
|
||||
formal process should help avoid endless sterile arguments
|
||||
about what needs to be done, without anyone feeling they have
|
||||
sufficient investment in the idea nor backing from the
|
||||
majority of the project to justify putting in the work to
|
||||
achieve the desired result.</p>
|
||||
|
||||
<p>The very first FCP — FCP 0 — describes the
|
||||
process itself. At the time of writing, Core is voting on
|
||||
accepting the initial document, which can be viewed in the
|
||||
Projects <a
|
||||
href="https://github.com/freebsd/fcp/blob/master/fcp-0000.md">Github
|
||||
repository</a>. Two new mailing lists have been created:
|
||||
fcp@FreeBSD.org is the channel for receiving notifications of
|
||||
new FCP proposals and discussing their content, whilst
|
||||
fcp-editors@FreeBSD.org exists to provide help with the
|
||||
process of drafting the FCP documents.</p>
|
||||
|
||||
<h3>Other Core activities</h3>
|
||||
|
||||
<p>Core is delighted to announce that Gordon Tetlow has joined
|
||||
the Security Officer team, and will be working on managing the
|
||||
Secteam caseload, freeing up other members to concentrate on
|
||||
the more technical aspects of vulnerability remediation. In
|
||||
addition, Ed Maste has joined secteam and is available to
|
||||
assist the Security Officers where necessary.</p>
|
||||
|
||||
<p>Although Florian Smeets had to step down, the postmaster team
|
||||
has now recruited three new members and is now back up to
|
||||
strength.</p>
|
||||
|
||||
<p>Considering the desirability of a number of fixes that have
|
||||
been merged into 10-STABLE since the 10.3 release, core has
|
||||
approved a 10.4 release to occur shortly after the 11.1
|
||||
release. This will be a normal support-lifetime release,
|
||||
unlike the extended lifetime of the 10.3 release, so the
|
||||
overall support lifetime for the 10.x branch will not be
|
||||
significantly extended.</p>
|
||||
|
||||
<p>During this quarter, Core has approved issuing three new
|
||||
commit bits. Please welcome:</p>
|
||||
|
||||
<ul>
|
||||
<li>Vladimir Kondratyev</li>
|
||||
|
||||
<li>Ryan Libby</li>
|
||||
|
||||
<li>Kyle Evans</li>
|
||||
</ul>
|
||||
|
||||
<p>Also, during this quarter, we had one person give up their
|
||||
commit bit:</p>
|
||||
|
||||
<ul>
|
||||
<li>Jordan Hubbard</li>
|
||||
</ul>
|
||||
|
||||
<p>It is always unsettling when one of the Project's founder
|
||||
members decides to move on, but Jordan's interests have
|
||||
migrated away from &os; related projects and he has decided to
|
||||
hang up his bit once and for all.</p>
|
||||
|
||||
<p>Core would like to thank NTTA (formerly Verio) for providing
|
||||
hosting for a cvsup mirror for many years, and also for their
|
||||
kind offer to provide ongoing hosting for a machine in their
|
||||
Seattle facility. Since we have no need for additional North
|
||||
America hosting, we have declined their offer.</p>
|
||||
|
||||
<p>As usual, a number of questions have been raised about code
|
||||
licensing and other matters related to intellectual property.
|
||||
Ed Maste has registered "freebsd" on behalf of the
|
||||
FreeBSD Foundation on the Mastodon social media network. The
|
||||
"Unlicense" is suitable for code being imported into
|
||||
libc. We still have some code published under the old
|
||||
4-clause style BSD license, where the extra clause refers
|
||||
specifically to the University of California. While UC has
|
||||
generally approved removing that clause, we need to check with
|
||||
all copyright holders before changing any remaining 4-clause
|
||||
licensing.</p>
|
||||
|
||||
<p>Core, along with Secteam, are monitoring developments
|
||||
concerning the "Stack Clash" vulnerability that hit
|
||||
the headlines during June. Changes to the stack-guard
|
||||
mitigation system are underway as a consequence of the
|
||||
proof-of-concept published by Qualys.</p>
|
||||
</body>
|
||||
</project>
|
||||
</report>
|
||||
|
|
|
|||
Loading…
Reference in a new issue