From 95e2b25f85414703eaaa7d94cc07b24fdca3d021 Mon Sep 17 00:00:00 2001 From: Benjamin Kaduk Date: Fri, 16 Oct 2015 02:24:19 +0000 Subject: [PATCH] Add core team report --- .../news/status/report-2015-07-2015-09.xml | 60 +++++++++++++++++++ 1 file changed, 60 insertions(+) diff --git a/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml b/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml index 18025a19fb..625b0b79fd 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml @@ -1460,4 +1460,64 @@ + + The &os; Core Team + + + + &os; Core Team + core@FreeBSD.org + + + + +

The biggest task handled by the Core Team during this quarter + was developing and publishing the new Code of Conduct. The Code + of Conduct describes how people are expected to behave on all &os; + official communication channels, as well as how developers and other + people involved with the project are to behave when representing the + project in public.

+ +

The Code of Conduct was generally well received and elicited + numerous comments and suggestions for improvements from the + community, many of which have been integrated.

+ +

The next task handled by Core was the restoration of Babak + Farrokhi's ports commit bit. Babak is an Iranian resident and + consequently had run afoul of US trade sanctions, which the + project had initially been advised would make it illegal + for him to contribute. After several years, Core was asked to + revisit the issue. On the advice of counsel, Core decided that + it could restore commit privileges to commmitters resident in + Iran.

+ +

The CTM service came under security review. Given that the lack of + use of routine authenticity checking made the injection of + trivial exploit code relatively easy, the service was held to be + too risky to continue as an official part of the &os; base system. + CTM has very few remaining users but they should be able to + install CTM from the Ports Collection in order to continue doing + so.

+ +

Core learned that ISC was ceasing its hosting service, which has + entailed a rapid rework of plans on the movement of significant + portions of the &os; cluster to that datacentre. Cluster + administration has taken ownership of the situation and is making + progress.

+ +

Core fielded an enquiry about NextBSD and whether this + should be the future direction for the whole &os; project. Core's + position is that NextBSD is an interesting project, and we regard + it, like the other BSD projects, as a potential source of good + ideas. However, we currently have no plans to adopt NextBSD as + the official &os; distribution.

+ +

Beyond these issues, Core also spent time in various routine + activities. During this quarter we issued three new + src commit bits, and took none in for safekeeping. Welcome to + &a.allanjude;, &a.aurajo;, and &a.avos;. +

+ + +