Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Oct 2015 02:24:19 +0000 (UTC)
From:      Benjamin Kaduk <bjk@FreeBSD.org>
To:        doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org
Subject:   svn commit: r47584 - head/en_US.ISO8859-1/htdocs/news/status
Message-ID:  <201510160224.t9G2OJIM036936@repo.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: bjk
Date: Fri Oct 16 02:24:19 2015
New Revision: 47584
URL: https://svnweb.freebsd.org/changeset/doc/47584

Log:
  Add core team report

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml	Fri Oct 16 02:23:29 2015	(r47583)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml	Fri Oct 16 02:24:19 2015	(r47584)
@@ -1460,4 +1460,64 @@
     </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 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.</p>
+
+      <p>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.</p>
+
+      <p>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.</p>
+
+      <p>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.</p>
+
+      <p>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.</p>
+
+      <p>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.</p>
+
+      <p>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;.
+      </p>
+    </body>
+  </project>
+
 </report>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201510160224.t9G2OJIM036936>