From owner-freebsd-advocacy@freebsd.org Tue Aug 14 15:56:14 2018 Return-Path: Delivered-To: freebsd-advocacy@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9508D107C2B1; Tue, 14 Aug 2018 15:56:14 +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 2B83D763A4; Tue, 14 Aug 2018 15:56:14 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190d-897ff70000005b1d-d0-5b72fa6a7117 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 dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id 99.64.23325.A6AF27B5; Tue, 14 Aug 2018 11:51:06 -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 w7EFp5pL031878; Tue, 14 Aug 2018 11:51:05 -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 w7EFp0Y5025266 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 14 Aug 2018 11:51:03 -0400 Date: Tue, 14 Aug 2018 10:51:00 -0500 From: Benjamin Kaduk To: grarpamp Cc: freebsd-questions@freebsd.org, freebsd-advocacy@freebsd.org, monthly@freebsd.org, info@freebsdfoundation.org Subject: Re: FreeBSD Status Reports / Blog? Message-ID: <20180814155100.GC40887@kduck.kaduk.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkleLIzCtJLcpLzFFi42IR4hRV1s36VRRtcGKihcWqvnvsFi+/bmKx WPxE32LHt8uMFhNvJjuwesz4NJ/F4/3qSUweO2fdZQ9gjuKySUnNySxLLdK3S+DKOPvwIVPB Do6KC3c2szcwvmTrYuTkkBAwkZi/ZDdjFyMXh5DAYiaJK717mSCcjYwSHfsPQmWuMklMutjP DtLCIqAqsebEe7B2NgE1icd7m1lBbBEBRYkLZz+D2cwClRId3TvAaoQFtCXWfzoP1ssLtG7J 2a1gNUICARIdLw6wQsQFJU7OfMIC0aslcePfS6ArOIBsaYnl/zhAwpwCgRLN6xYzg9iiAsoS e/sOsU9gFJiFpHsWku5ZCN0LGJlXMcqm5Fbp5iZm5hSnJusWJyfm5aUW6Rrp5WaW6KWmlG5i BIeyJO8Oxn93vQ4xCnAwKvHwBlwqihZiTSwrrsw9xCjJwaQkyuuzASjEl5SfUpmRWJwRX1Sa k1p8iFGCg1lJhLf4AlCONyWxsiq1KB8mJc3BoiTOe68mPFpIID2xJDU7NbUgtQgmK8PBoSTB y/4TqFGwKDU9tSItM6cEIc3EwQkynAdouAVIDW9xQWJucWY6RP4Uoy7Hn/dTJzELseTl56VK ifMuAikSACnKKM2DmwNKQRLZ+2teMYoDvSXMOwmkigeYvuAmvQJawgS0JFmkEGRJSSJCSqqB se6ZhsIPoT8bdwVtCpxzbM/cl5PYpjUF5l0Oj2T3OlMT4WV35Fzc+XuNdrm3feoWhq/bJbG5 MfeO/CXV57vPnlz5XJGxeCVb5eKpK4/KFfuWhIqbeQTtyjQWKfmrdfGk9pGSzCdiZ+Z/4flu 5lJrmtn2bo2H17vGwylH36z90GT3uExD/hTDRyWW4oxEQy3mouJEALdTr/QcAwAA X-BeenThere: freebsd-advocacy@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: FreeBSD Evangelism List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 15:56:14 -0000 On Mon, Aug 13, 2018 at 05:58:34PM -0400, grarpamp wrote: > What happened to them? I got appointed as an IETF Security Area Director, which doesn't leave enough time to keep them going. There is recognized interest in getting some form of replacement going and some efforts underway, though I am (unsurprisingly) not directly involved in them. -Ben > It's now approaching a year since the last effective date. > While such things should be voluntarily oppurtunistic to > avoid nagging, and news based, and varied in format... > yet having no central open blog-ish for even the news media > and non user / participant / subscriber follower space seems > perhaps missing an oppurtunity to capitalize and capture therein. > Nor does it seem many might browse out to the foundation > domain for such news, for say the Journal... after all freebsd.org > is the domain most observe, and journos / interested parties might > not "subscribe" (truth: pay) to follow. Which is not to say that that > isn't also an equally valid / overlapping / supplementary model.