From owner-freebsd-hackers@freebsd.org Sun Jan 1 21:47:38 2017 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 7974DC9A9CD; Sun, 1 Jan 2017 21:47:38 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-1.mit.edu (dmz-mailsec-scanner-1.mit.edu [18.9.25.12]) (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 F0AE9117E; Sun, 1 Jan 2017 21:47:37 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190c-27fff70000004853-34-586978efc3c3 Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 4E.B9.18515.FE879685; Sun, 1 Jan 2017 16:47:30 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id v01LlQMh023725; Sun, 1 Jan 2017 16:47:26 -0500 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v01LlNDo003151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 1 Jan 2017 16:47:25 -0500 Date: Sun, 1 Jan 2017 15:47:23 -0600 From: Benjamin Kaduk To: freebsd-hackers@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: FINAL CALL for 2016Q4 status reports Message-ID: <20170101214722.GH8460@kduck.kaduk.org> References: <20161226203144.GZ8460@kduck.kaduk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161226203144.GZ8460@kduck.kaduk.org> User-Agent: Mutt/1.6.1 (2016-04-27) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrJIsWRmVeSWpSXmKPExsUixG6novupIjPCYNtpTotd106zW8x584HJ Yvvmf4wOzB4zPs1nCWCM4rJJSc3JLEst0rdL4Mq4eX4RY8EbnoqPS4MbGPdzdTFyckgImEis nTWNqYuRi0NIoI1JYs3HM8wgCSGBDYwSh+4VQCSuMEmcnTIBLMEioCIxf9V9dhCbTUBNYv2K a2BxEQF5iX1N78HizED2r61NYLawgK7E+i0bGUFsXgFjid19C6EWGEvM6lzGBBEXlDg58wkL RK+WxI1/L4HiHEC2tMTyfxwgYU6gQ+8fWM4GYosKKEs0zHjAPIFRYBaS7llIumchdC9gZF7F KJuSW6Wbm5iZU5yarFucnJiXl1qka6iXm1mil5pSuokRFKKckjw7GM+88TrEKMDBqMTDKxCd GSHEmlhWXJl7iFGSg0lJlDdhQ0aEEF9SfkplRmJxRnxRaU5q8SFGCQ5mJRHeFSVA5bwpiZVV qUX5MClpDhYlcd5Lme4RQgLpiSWp2ampBalFMFkZDg4lCV5BYCwKCRalpqdWpGXmlCCkmTg4 QYbzAA3XBanhLS5IzC3OTIfIn2JUlBLnPVQOlBAASWSU5sH1glKIRPb+mleM4kCvCPPmgLTz ANMPXPcroMFMQIO/xqWDDC5JREhJNTBeify2aNPB1jCOi0s2bDmvtFNgdoR7d57Yixu+cwzZ nSJdpjxfJZLVoRt7I+jkK9XZQf01T3tv/mZ88WxZ5m0PVSsb1tc7pi7uTz7l5fshTjhbeeYD l/SzUmfNQl69vf73/9/IeSbyYT+OHBe4vfuUvv2EgKk35kt6RqiwfuherS3YPnFD6wVvJZbi jERDLeai4kQACrRqPPwCAAA= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2017 21:47:38 -0000 The deadline for submitting 2016Q4 entries is just a week away! -Ben On Mon, Dec 26, 2016 at 02:31:44PM -0600, Benjamin Kaduk wrote: > Dear FreeBSD Community, > > The deadline for the next FreeBSD Quarterly Status update is January 7, > 2016, for work done in October through December. > > Status report submissions do not need 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 work that is underway and > completed. 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 . > (Do be sure, though, to save the form output and not the form itself!) There > is also an XML template [2] that 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 look forward to seeing your 2016Q4 reports! > > Happy Holidays, > > Ben (on behalf of monthly@) > > [1] https://www.FreeBSD.org/cgi/monthly.cgi > [2] https://www.FreeBSD.org/news/status/report-sample.xml > [3] https://www.FreeBSD.org/news/status/howto.html > [4] https://www.FreeBSD.org/news/status/report-2016-04-2016-06.html > [5] https://www.FreeBSD.org/news/status/report-2016-07-2016-09.html