From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 7 19:32:26 2014 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EBA7AF6C; Tue, 7 Oct 2014 19:32:25 +0000 (UTC) Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6342E374; Tue, 7 Oct 2014 19:32:25 +0000 (UTC) X-AuditID: 12074423-f799d6d00000337c-7f-54343e959fc4 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id 2E.FF.13180.59E34345; Tue, 7 Oct 2014 15:27:17 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id s97JRGiC030012; Tue, 7 Oct 2014 15:27:16 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id s97JRESJ020378 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 7 Oct 2014 15:27:15 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id s97JREJS014454; Tue, 7 Oct 2014 15:27:14 -0400 (EDT) Date: Tue, 7 Oct 2014 15:27:13 -0400 (EDT) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: FreeBSD Current , FreeBSD Hackers Subject: FreeBSD 2014Q3 status reports due today! Message-ID: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKIsWRmVeSWpSXmKPExsUixG6nrjvVziTEoPmUqMWua6fZLea8+cBk sX3zP0YHZo8Zn+azBDBGcdmkpOZklqUW6dslcGVs2jORveAOT8Wh8+/ZGhhPcHUxcnJICJhI zJu6mQnCFpO4cG89WxcjF4eQwGwmiR9Xf7JDOBsYJT5dWskE4Rxkkvh59ysrSIuQQL3E0gsT 2EFsFgEtiUUrj7OB2GwCahLrV1xjhhirKLH51CQwW0QgU+LPmo9g9cIChhJr3p4Fs3kFHCX6 u68zgtiiAjoSq/dPYYGIC0qcnPkEzGYGmr98+jaWCYz8s5CkZiFJLWBkWsUom5JbpZubmJlT nJqsW5ycmJeXWqRrppebWaKXmlK6iREcei7KOxj/HFQ6xCjAwajEw7tCyzhEiDWxrLgy9xCj JAeTkigvo7lJiBBfUn5KZUZicUZ8UWlOavEhRgkOZiUR3imSQDnelMTKqtSifJiUNAeLkjjv ph98IUIC6YklqdmpqQWpRTBZGQ4OJQleM1ugRsGi1PTUirTMnBKENBMHJ8hwHqDhtiA1vMUF ibnFmekQ+VOMilLivI9sgBICIImM0jy4XlhqeMUoDvSKMO9dkCoeYFqB634FNJgJaPCqfmOQ wSWJCCmpBsZzv8Mfvklec0X7+buAFAdXd6vM+8zHVvE+1JK/E63k+Sj73ZK0olymWRdWcanF Te25fr5c+Ffe7zvS9Wuv3pG5VuQnsobBMcqt/+576d//5Y7PbFy76N4JufPclSeW/1G/wx2k 2Hn0aqRS5YJZp/oSHBvs8/7efJ/ctaGg6Xh7MONmHpHwnGglluKMREMt5qLiRAAl82dM6AIA AA== X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Oct 2014 19:32:26 -0000 Dear FreeBSD Community, As previously announced, today is the deadline for submitting items for the next FreeBSD Quarterly Status Update, covering work done in July through September. If you still need some time to prepare a submission, please note that we will continue to accept submissions as we work on assembling the report, but cannot guarantee that anything received after October 10 will be included. Status report submissions do not have to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to inform FreeBSD users and developers about what you're working on. Submission of reports is not restricted to committers. Anyone doing anything interesting and FreeBSD-related can -- and should -- write one! The preferred and easiest submission method is to use the XML generator [1] with the results emailed to the status report team at monthly@FreeBSD.org . There is also an XML template [2] which can be filled out manually and attached if preferred. For the expected content and style, please study our guidelines on how to write a good status report [3]. You can also review previous issues [4][5] for ideas on the style and format. We are looking forward to all of your 2014Q3 reports! Thanks, Ben (on behalf of monthly@) [1] http://www.freebsd.org/cgi/monthly.cgi [2] http://www.freebsd.org/news/status/report-sample.xml [3] http://www.freebsd.org/news/status/howto.html [4] http://www.freebsd.org/news/status/report-2014-01-2014-03.html [4] http://www.freebsd.org/news/status/report-2014-04-2014-06.html