The &os; Core Team

From owner-svn-doc-head@FreeBSD.ORG Thu Jan 8 00:57:22 2015 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EC2EF9B3; Thu, 8 Jan 2015 00:57:21 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D1889B05; Thu, 8 Jan 2015 00:57:21 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t080vLYJ020815; Thu, 8 Jan 2015 00:57:21 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id t080vLVV020814; Thu, 8 Jan 2015 00:57:21 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201501080057.t080vLVV020814@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Thu, 8 Jan 2015 00:57:21 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r46161 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2015 00:57:22 -0000 Author: bjk Date: Thu Jan 8 00:57:20 2015 New Revision: 46161 URL: https://svnweb.freebsd.org/changeset/doc/46161 Log: Add core team report Approved by: hrs (mentor, blanket) Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml Thu Jan 8 00:50:21 2015 (r46160) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml Thu Jan 8 00:57:20 2015 (r46161) @@ -550,4 +550,72 @@ + + The &os; Core Team + + + + &os; Core Team + core@FreeBSD.org + + + + +

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.

+ +

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.

+ +

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.

+ +

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.

+ +

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.

+ +

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.

+ +

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.

+ +

During this quarter, core issued two new commit bits, and also + took two commit bits into safe-keeping.

+ + + +