Add core team report

Approved by:	hrs (mentor, blanket)
This commit is contained in:
Benjamin Kaduk 2015-01-08 00:57:20 +00:00
parent ac2bf3dc8e
commit 57c026d7ca
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=46161

View file

@ -550,4 +550,72 @@
</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>During the fourth quarter of 2014, the &os; Core team saw the
culmination of a long-running project to rebuild the &os;
Forums. The chosen solution was to license XenForo; core would
like to thank the FreeBSD Foundation for paying the licensing
costs of this software.</p>
<p>Much discussion ensued concerning the "New Support Model"
following Core's meeting at EuroBSDCon in September. It was
recognised that trying to change the model immediately before
10.1-RELEASE was far too late, and the change will be targeted
at 11.0-RELEASE.</p>
<p>In order to ensure that 10.1-RELEASE shipped with support for
up-to-date X Windows and KDE4, core approved the switch to 'new
Xorg' as the default in time for building the packages for that
release.</p>
<p>Git was officially promoted from beta to an officially
supported version control system. Git is available as a
read-only resource for downstream consumers and contains an
exported copy from SVN, the primary and only read-write
repository. The &os; git repositories (exported from the
master SVN version control) will shortly be available at
https://git.freebsd.org/, and core has been active
in ensuring that there is a sufficient body of Git
administrators available with access to appropriate
documentation in order to maintain a good git service.</p>
<p>Core mediated in disputes between a number of committers over
some updates to system sources, and fielded complaints about
code quality of some other work in critical areas.
While such disagreements will occasionally occur, core is
promoting the routine use of the phabricator service in order to
review work before committal. Catching problems early is in the
project's best interests, and discussion of changes in an open
review context should minimize confrontational demands for
immediate back-out of changes.</p>
<p>Core is working on a charter for a proposed new QA team, to
encompass members of the Release Engineering and Security teams,
as well as committers with interests in standards compliance.
It is envisioned that the QA team will take responsibility for
merging code from HEAD into the STABLE branches, run integration
testing against those updates and handle merging patches and
bug-fixes submitted to the &os; project from third parties.</p>
<p>During this quarter, core issued two new commit bits, and also
took two commit bits into safe-keeping.</p>
</body>
</project>
</report>