From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Baines Subject: Publishing news about Guix on a weekly basis Date: Sun, 03 Nov 2019 12:19:42 +0000 Message-ID: <87h83lywwx.fsf@cbaines.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:56102) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iRErF-000364-Ms for guix-devel@gnu.org; Sun, 03 Nov 2019 07:19:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iRErE-0006TL-BZ for guix-devel@gnu.org; Sun, 03 Nov 2019 07:19:49 -0500 Received: from mira.cbaines.net ([212.71.252.8]:47002) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iRErE-0006Sv-5m for guix-devel@gnu.org; Sun, 03 Nov 2019 07:19:48 -0500 Received: from localhost (cpc102582-walt20-2-0-cust14.13-2.cable.virginm.net [86.27.34.15]) by mira.cbaines.net (Postfix) with ESMTPSA id 7228B176B0 for ; Sun, 3 Nov 2019 12:19:46 +0000 (GMT) Received: from capella (localhost [127.0.0.1]) by localhost (OpenSMTPD) with ESMTP id e514eded for ; Sun, 3 Nov 2019 12:19:45 +0000 (UTC) List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org --=-=-= Content-Type: text/plain Hey, So this is something that might have come up in discussion once or twice, but I've now got around to actually building a prototype. You can see it here: http://prototype-guix-weekly-news.cbaines.net/ Now that I've actually spent some time implementing something, I feel like this has led to more questions than I've answered. Could this be a useful thing, and if so why, and to whom? Is weekly the right cadence? What information should be included? Could it be available in multiple languages? I'd be very interested to hear from anyone who has any thoughts on the above topics. One thought I've had is that whatever the cadence (1 week, 2 weeks, a month, ...), it should be stuck to, and importantly, this burden should be automated so it isn't incurred by someone. For example, this post [1] just includes a bunch of data extracted from the Guix Data Service about the period in question, and a default paragraph. Publishing this, or something like it could be completely automated. Whereas, on this post, I've added some content, and set a custom summary. 1: http://prototype-guix-weekly-news.cbaines.net/en_US/2019/41.html 2: http://prototype-guix-weekly-news.cbaines.net/en_US/2019/42.html Regarding the data taken from the Guix Data Service, that probably needs more thinking about. The list new packages for most weeks is rather too long, so maybe this needs to be abbreviated in some way. Also, the version changes list doesn't seem very useful, so maybe that should be summarised or removed. Let me know what you think, and also let me know if this is something you'd be interested in helping out with! Thanks, Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEPonu50WOcg2XVOCyXiijOwuE9XcFAl2+xd5fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcACgkQXiijOwuE 9XeccRAAg3Ag+MQp3dEO51VUmxb5DIZ8s3BWERj9IOnVe6t3fJSisUj7qtdIUXUl 3Ao1lrxP2/bDlbbmftII2a6ABUmNMKPQni+3Jgwyvb5IjvabfXjatGQFev+dWqiQ I74inwrPrl0f+95udsTvgtbcTpgutPjzVbPxxALtDOo4XJq4V09DGFNqSE09uJoT wwCucBKPlcjBjwybXG4MPDZHYe7/PmH+iIUk13QC+SFbX/qe5fhJEV5WIg7pxt1t kcfsQSY1DbIo+gjzgiqdbsFrR01Kk/MlJK7XMSjeESX7OAlZC3TgXix2Dn3LZZab DzMf6VBgh7siDJM0btNk+KmrkfUr5FhnimVu2TqVqmhthGlKqmNXS9EBCWg72jMd 8WfOd+hHJjQIqFEQerZOl17isvslxB1S2M1FwSKr88OBqbIaPLYwcf6wLiSvbLLC VjXhsAmXyoe79ktBF99FRlIyUDHPZdW+r99Uhm4fkJszONhh9dq2P6vkD4JnWHIx 2IBCGWSVEmnGOkcmYOf7A03YhneLnkWf5CZ2ZmKT9wvrEGaGazjaS7IU3vDDj/wd QvOqFBvwDrZyFMuyEfo03kYk6oepYs+JRhDtCx0lYcVUHvkzhkN9sIvkrZ8ukQ/1 127gcHfHEEZ2M7pwon723l8/ngeY1XipEeLe06F5fx/Q61A+FkA= =o/fG -----END PGP SIGNATURE----- --=-=-=--