From owner-freebsd-hackers@freebsd.org Thu Sep 29 03:20:27 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 D0FB7BE2351; Thu, 29 Sep 2016 03:20:27 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-2.mit.edu (dmz-mailsec-scanner-2.mit.edu [18.9.25.13]) (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 6B96B1793; Thu, 29 Sep 2016 03:20:26 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190d-25fff7000000106a-50-57ec8744dfde 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 79.11.04202.4478CE75; Wed, 28 Sep 2016 23:15:16 -0400 (EDT) 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 u8T3FFmd000816; Wed, 28 Sep 2016 23:15: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 u8T3FDS9020884 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 28 Sep 2016 23:15:15 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id u8T3FChn009098; Wed, 28 Sep 2016 23:15:12 -0400 (EDT) Date: Wed, 28 Sep 2016 23:15:12 -0400 (EDT) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: freebsd-hackers@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Second Call for 2016Q3 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+NgFnrOIsWRmVeSWpSXmKPExsUixG6nouvS/ibc4M5RU4s5bz4wWWzf/I/R gcljxqf5LAGMUVw2Kak5mWWpRfp2CVwZhyeeYyn4zFPxoq+kgfEAVxcjJ4eEgIlE/+f/bF2M XBxCAm1MEhNav0I5GxklVnTOZIJwDjFJNC67yAjhNDBKbP78jgWkn0VAW+LX3qWsIDabgJrE +hXXmCHmKkpsPjUJzBYRkJfY1/SeHcRmBrK3rJ7MBmILC1hIzD6/iRHE5hRwlHjScBjM5hVw kPjY/BOolwNomYNE45QykLCogI7E6v1TWCBKBCVOznzCAjFSS2L59G0sExgFZyFJzUKSWsDI tIpRNiW3Sjc3MTOnODVZtzg5MS8vtUjXSC83s0QvNaV0EyMoPDkleXcw/rvrdYhRgINRiYe3 49TrcCHWxLLiytxDjJIcTEqivJw+b8KF+JLyUyozEosz4otKc1KLDzFKcDArifDmtgHleFMS K6tSi/JhUtIcLErivF0zDoQLCaQnlqRmp6YWpBbBZGU4OJQkeMtBGgWLUtNTK9Iyc0oQ0kwc nCDDeYCGu4ANLy5IzC3OTIfIn2JUlBLnPdsKlBAASWSU5sH1gtPHbibVV4ziQK8I84aBtPMA Uw9c9yugwUxAg5eeeAEyuCQRISXVwBj/xFzJX6h6x4LabRtei2crNG1I9AmJ42E7s/PpGyHl RyGT/T1YTDuvMljobFI9abyc0b6cLTB0+0GlRT6pLmqX5llu7pgiNXMeU3USl9R95svcHz+q eM8J4oo59eNBlsbLal7ru+UrTn42e2nPvUNgzocN212rwqOeSfU/k950Je6FeFPWaSWW4oxE Qy3mouJEADp1RXr6AgAA 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: Thu, 29 Sep 2016 03:20:27 -0000 Dear FreeBSD Community Ten days remain in the submission period -- plase send in your entries for the 2016Q3 report! More details quoted below. -Ben (on behalf of monthly@) On Wed, 7 Sep 2016, Benjamin Kaduk wrote: > Dear FreeBSD Community, > > The deadline for the next FreeBSD Quarterly Status update is October 7, > 2016, for work done in July through September. > > 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 2016Q3 reports! > > Thanks, > > 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-01-2016-03.html > [4] https://www.FreeBSD.org/news/status/report-2016-04-2016-06.html > >