From owner-freebsd-hackers@freebsd.org Thu Jul 7 05:15:14 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 26C7DB75CE1; Thu, 7 Jul 2016 05:15:14 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (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 B4E1F1CE5; Thu, 7 Jul 2016 05:15:13 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074423-cafff70000006b63-be-577de42b8390 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id F4.B1.27491.B24ED775; Thu, 7 Jul 2016 01:10:03 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id u675A2RY001487; Thu, 7 Jul 2016 01:10:03 -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 u6759xsK021350 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 7 Jul 2016 01:10:02 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id u6759wPw002618; Thu, 7 Jul 2016 01:09:58 -0400 (EDT) Date: Thu, 7 Jul 2016 01:09:58 -0400 (EDT) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: freebsd-hackers@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Last call for 2016Q2 quarterly status reports In-Reply-To: Message-ID: References: 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+NgFnrGIsWRmVeSWpSXmKPExsUixCmqrKv9pDbcYO0ha4s5bz4wWWzf/I/R gcljxqf5LAGMUVw2Kak5mWWpRfp2CVwZZz6cYS3o5q34vKKRrYHxAlcXIyeHhICJxIKJG5i7 GLk4hATamCRenPrBAuFsYJT4fusxVOYgk8SE9VeBHA4gp17i2LMQkG4WAS2JH79mMYHYbAJq EutXXGOGmKoosfnUJDBbREBeYl/Te3YQmxnI3rJ6MhvIGGEBM4nbR1lAwpwCThKPpv0GK+EV cJA48eE7mC0k4CjxoeMiK4gtKqAjsXr/FBaIGkGJkzOfsECM1JJYPn0bywRGwVlIUrOQpBYw Mq1ilE3JrdLNTczMKU5N1i1OTszLSy3SNdPLzSzRS00p3cQICk52F+UdjC/7vA8xCnAwKvHw /sirDRdiTSwrrsw9xCjJwaQkyrvnLlCILyk/pTIjsTgjvqg0J7X4EKMEB7OSCO/eR0A53pTE yqrUonyYlDQHi5I4LyMDA4OQQHpiSWp2ampBahFMVoaDQ0mCl/UxUKNgUWp6akVaZk4JQpqJ gxNkOA/QcDaQGt7igsTc4sx0iPwpRkUpcV4vkIQASCKjNA+uF5w8djOpvmIUB3pFmHc3yG08 wMQD1/0KaDAT0OCfLtUgg0sSEVJSDYwTYuTnlUfGLD4Rv6ve6NOBw90b25a+kngUvLHvfYNa WFH1wph/jKz5Ild0y4o4q3yOc4dqvrn1frnX/CdcsYnSwatXL1f95NYUlizcVydlq8f2+r9O xtR5CaZ/vrJ29D2PWef/wGSWc9XavKCOdR8OGq16WpZy8uAVxQTVs5NDUkTi39ws8lViKc5I NNRiLipOBADNoPxK+QIAAA== X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jul 2016 05:15:14 -0000 Reminder: we're still looking for more submissions for the 2015Q2 status report! Please let us know if you wish to write an entry, even if it will not be finished by today. Thanks, Ben (for the monthly@ team) On Tue, 21 Jun 2016, Benjamin Kaduk wrote: > Dear FreeBSD Community, > > The deadline for the next FreeBSD Quarterly Status update is July 7, > 2016, for work done in April through June. > > 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 at > 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 2016Q2 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-2015-10-2015-12.html > [4] http://www.freebsd.org/news/status/report-2016-01-2016-03.html > >