From owner-freebsd-current@freebsd.org Sun Oct 8 03:42:31 2017 Return-Path: Delivered-To: freebsd-current@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 EEE85E24B8E; Sun, 8 Oct 2017 03:42:31 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-7.mit.edu (dmz-mailsec-scanner-7.mit.edu [18.7.68.36]) (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 18A4A6AF1B; Sun, 8 Oct 2017 03:42:30 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074424-a2dff70000001b86-e4-59d99d71dbca Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id E9.3F.07046.17D99D95; Sat, 7 Oct 2017 23:37:21 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id v983bKiX009792; Sat, 7 Oct 2017 23:37:21 -0400 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 v983bHj4030520 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 7 Oct 2017 23:37:19 -0400 Date: Sat, 7 Oct 2017 22:37:17 -0500 From: Benjamin Kaduk To: freebsd-hackers@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: Second Call for 2017Q3 quarterly status reports Message-ID: <20171008033717.GL96685@kduck.kaduk.org> References: <20170928142925.GG96685@kduck.kaduk.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3U8TY7m7wOx7RL1F" Content-Disposition: inline In-Reply-To: <20170928142925.GG96685@kduck.kaduk.org> User-Agent: Mutt/1.8.3 (2017-05-23) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrIKsWRmVeSWpSXmKPExsUixCmqrVs492akwe17ehZz3nxgsti++R+j A5PHjE/zWQIYo7hsUlJzMstSi/TtErgyXs+8z1ZwTbRi4bb7bA2MJ4W6GDk5JARMJLYcOMfe xcjFISSwmEniwPX7LBDOBkaJaU+PsUE4V5gkmhduZQRpYRFQkTj7czaYzQZkN3RfZgaxRQTk JfY1vWcHsZmB7F9bm8BsYQELiSM7vrOC2LxA61Yu38gEYgsB2R+OP2GBiAtKnJwJYTMLlElM XHYaaD4HkC0tsfwfB0iYU8BU4v38R2AjRQWUJebtW8U2gVFgFpLuWUi6ZyF0Q4S1JG78e8mE IawtsWzha2YI21Zi3br3LAsY2VcxyqbkVunmJmbmFKcm6xYnJ+blpRbpmuvlZpbopaaUbmIE hT67i8oOxu4e70OMAhyMSjy8DzRuRgqxJpYVV+YeYpTkYFIS5RWdBRTiS8pPqcxILM6ILyrN SS0+xKgCtOvRhtUXGKVY8vLzUpVEeJnTgOp4UxIrq1KL8mHKpDlYlMR5twXtihQSSE8sSc1O TS1ILYLJynBwKEnw1s8BahQsSk1PrUjLzClBSDNxcB5ilODgARpeNxtkeHFBYm5xZjpE/hSj opQ471OQhABIIqM0D64XlLIksvfXvGIUB3pLmFcAZAUPMN3Bdb8CGswENJix+AbI4JJEhJRU AyOf+63w+pnOX0p5ihyTXpy8tOnuivSDO27LeCn/m+qXcitsgnTUHYN1+nWnXy5bzzrdTSTd M6i2NLX4tsm59AkerKUfrmx5Y7qpQ6E2yNlf38vy6TZ23Y2xTwWmb3tyev7uueY1p0sONGyc eS7YqWbLHa9wNfVY37+cvVGL+I/1200V2sORF6/EUpyRaKjFXFScCACNwlkONAMAAA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2017 03:42:32 -0000 --3U8TY7m7wOx7RL1F Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Just a reminder: with the extended submission deadline for 2017Q3 entries, two weeks remain in the submission period. -Ben On Thu, Sep 28, 2017 at 09:29:25AM -0500, Benjamin Kaduk wrote: > Dear FreeBSD Community, >=20 > The deadline for the next FreeBSD Quarterly Status update is October 21, > 2017, for work done in July through September. >=20 > 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 gr= eat > 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! >=20 > 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! In > particular, the Google Chrome "save as" function does not save the genera= ted > output for some reason.) 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. >=20 > We look forward to seeing your 2017Q3 reports! >=20 > Thanks, >=20 > Ben (on behalf of monthly@) >=20 > [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-2017-01-2017-03.html > [5] https://www.FreeBSD.org/news/status/report-2017-04-2017-06.html >=20 >=20 --3U8TY7m7wOx7RL1F Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQG3BAABCgAdFiEE2WGV4E2ARf9BYP0XKNmm82TrdRIFAlnZnWcACgkQKNmm82Tr dRK0bAwdH0aieF+hTINOeQpErQ7NKOK8HfFWntG2q20blTn3L1FK5d2qmCveOhdF kb3COT2J7Zo7NCfq1NME8zYiuhO2PmKENuaT2tfHaFEJcGWJ44nHfu2VVNzXAvaN HkF7RQlDdNTsuShO8bbULtNcH9aCfZHRknYHFOo2Z+6GpjMiL2p83K7n3GRHDgtC 5sqnRuzZF9tEAd8E3uNulscr2iN+6qluZUCTeA1Agd4q3xPjzOGqE01CK98jdVtf n33cd/3X2V+q7xf2SPTPRKcCoP2YhYYeSbxBgwbm3ao4gM7TDTXshtdnruIYwsNr wu3ocAP50frpUKZIcHNzGzIALFP6FUtM/lkxtRTEISXcv41UGvzwluy9wOCpLPNQ 8l0WWdJg/3/VK2E+9VGsJH94dqnRxvKoPpPUpzfxGApu5Cd3rAHV9Qe2t7kbETgF sqzyBn1649CMUaJ9JCdSYa61KQhBxARJq/I4hFUfS0pZGds280e/8FNAtW+y1mxE 2recASLoTKZncw== =s8ce -----END PGP SIGNATURE----- --3U8TY7m7wOx7RL1F--