From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: Monthy emacs-devel digest, similar to "This month in Org" Date: Sat, 02 Sep 2023 19:17:16 +0000 Message-ID: <87ttsce66b.fsf@posteo.net> References: <87il9kksqz.fsf@dfreeman.email> <83350ncbns.fsf@gnu.org> <87cyzrjbd8.fsf@dfreeman.email> <83zg2vav46.fsf@gnu.org> <87o7j99304.fsf@dfreeman.email> <97224c4f-fad4-ae01-46c1-5755d97d9a92@gutov.dev> <87fs3ztq38.fsf@localhost> <87cyz3qwba.fsf@posteo.net> <8734zztmiz.fsf@localhost> <87sf7zqs3l.fsf@yahoo.com> <87il8vs6e7.fsf@localhost> <87jztbqrc9.fsf@yahoo.com> <877cpbs5a0.fsf@localhost> <87fs3zqqgj.fsf@yahoo.com> <874jkfs4o0.fsf@localhost> <87y1hroz47.fsf@posteo.net> <87edjiryi5.fsf@localhost> <877cpavw8h.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3787"; mail-complaints-to="usenet@ciao.gmane.io" To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 02 21:18:10 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qcW8I-0000nh-F3 for ged-emacs-devel@m.gmane-mx.org; Sat, 02 Sep 2023 21:18:10 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qcW7c-0001sK-BZ; Sat, 02 Sep 2023 15:17:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qcW7a-0001sC-Rb for emacs-devel@gnu.org; Sat, 02 Sep 2023 15:17:26 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qcW7W-0001sA-6j for emacs-devel@gnu.org; Sat, 02 Sep 2023 15:17:26 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 59369240027 for ; Sat, 2 Sep 2023 21:17:18 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1693682238; bh=2YEFtJV9Dddf0axWcJqk7A1nU05YJCJDjDnGC//sWsQ=; h=From:To:Subject:Autocrypt:Date:Message-ID:MIME-Version: Content-Transfer-Encoding:From; b=EvXMBRNbC6tkihPZGIHR5qe8FNXqEC3WruF9Q96RFRjsPCc/aeh/J4TIoJwW6aYfu Er/5xU6KqspX8yaN4fr/OMLEy3z/yGm7l2fwggPx9FmVmeqjXQ6A+BpazmUCzuGUQd M8eeP6C8dut2KhWHv5XbYJ/FlmHioGHJTIJFFJO+zySujolwvgUWb/qxJkEpU+PzyI iVVKZ9HInvevudAI0cS6XIEweBGuZbLCCFcuQaq7nMf1ntqG61BG816oTwR5sXmrl3 N1mbBx4gPsN2pca4Nt17X3QKZ2+yWd7nj8Xge2TPbNe7lRUvWXkN5hs4UUipPOIn3J z2DHAy/YLPiJw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4RdPmF68Hrz6tw7 for ; Sat, 2 Sep 2023 21:17:17 +0200 (CEST) In-Reply-To: <877cpavw8h.fsf@posteo.net> (Philip Kaludercic's message of "Fri, 01 Sep 2023 15:50:06 +0200") Autocrypt: addr=philipk@posteo.net; keydata= mDMEZBBQQhYJKwYBBAHaRw8BAQdAHJuofBrfqFh12uQu0Yi7mrl525F28eTmwUDflFNmdui0QlBo aWxpcCBLYWx1ZGVyY2ljIChnZW5lcmF0ZWQgYnkgYXV0b2NyeXB0LmVsKSA8cGhpbGlwa0Bwb3N0 ZW8ubmV0PoiWBBMWCAA+FiEEDg7HY17ghYlni8XN8xYDWXahwukFAmQQUEICGwMFCQHhM4AFCwkI BwIGFQoJCAsCBBYCAwECHgECF4AACgkQ8xYDWXahwulikAEA77hloUiSrXgFkUVJhlKBpLCHUjA0 mWZ9j9w5d08+jVwBAK6c4iGP7j+/PhbkxaEKa4V3MzIl7zJkcNNjHCXmvFcEuDgEZBBQQhIKKwYB BAGXVQEFAQEHQI5NLiLRjZy3OfSt1dhCmFyn+fN/QKELUYQetiaoe+MMAwEIB4h+BBgWCAAmFiEE Dg7HY17ghYlni8XN8xYDWXahwukFAmQQUEICGwwFCQHhM4AACgkQ8xYDWXahwukm+wEA8cml4JpK NeAu65rg+auKrPOP6TP/4YWRCTIvuYDm0joBALw98AMz7/qMHvSCeU/hw9PL6u6R2EScxtpKnWof z4oM Received-SPF: pass client-ip=185.67.36.65; envelope-from=philipk@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:309905 Archived-At: Here is a demonstration of how this kind of a medium could look like: https://amodernist.com/eaez/ This is just a mockup, but it seems like something that can be reasonably maintained as long as I continue to regularly follow the mailing list and track new additions to ELPA. Philip Kaludercic writes: > Ihor Radchenko writes: > >> Philip Kaludercic writes: >> >>> There comes a point where people have to accept that mailing lists >>> What I think the Org project does well is the "This month in Org" line >>> of posts, that help highlight contributions from newcomers and >>> familiarise those familiar with a mailing list with the procedures going >>> on here. >> >> This is actually quite an effort. AFAIK, the author had difficulties >> allocating time to write more posts for TMiO. >> >> Also, for reference, we are talking about >> https://blog.tecosaur.com/tmio/2022-05-31-folding.html > > TMiO might be too detailed and reliant on a single person, which might > be part of the problem in keeping it rolling. I cannot evaluate that, > because I didn't follow the project in too much detail. > > My initial plan (see https://amodernist.com/texts/elpa-zine.html) was > just to focus on ELPA-related development, such as new packages or > updates, since this is what most users are probably also interested in. > An idea that was discussed, and that might be emphasises in greater > detail could be to have a sort of "builtin-board" for announcements of > more important news or help requests from core ELPA development. > > I think it is obvious, that this kind of a thing would have to be a > collaborative effort. While it only requires a single or just a few > people to compile this kind of a post/newsletter,=20 > >>> ... I have mentioned the idea of a ELPA >>> newsletter somewhere around here once, but upon reflection, it seems >>> like a TMIO-like idea should be implemented to the entire >>> core-development, not just the ELPAs. Would anyone here be interested >>> in working on something like that? >> >> A somewhat relevant effort is by Sacha Chua: >> https://sachachua.com/blog/2023/08/2023-08-28-emacs-news/ >> >> It is less detailed (just an outline), but I find it pretty useful. > > Crucially it is incomplete, when it comes to core development. There > are frequently longer discussions and bugs that never get mentioned on > the newsletter, even though they *should* be highlighted *and* explained > for an average user, especially if their feedback is what is needed. > > On the other hand, the newsletter is as complete as it gets wrt all the > other news (I am under the impression that it summarises every > blog-post, reddit-submission, video, etc. published on the topic of > Emacs over the last week), which is not what I am interested in. > > Timothy writes: > >> Hi Ihor, >> >>> This is actually quite an effort. AFAIK, the author had difficulties >>> allocating time to write more posts for TMiO. >>> >>> Also, for reference, we are talking about >>> >> >> Each post took several hours to do, despite how short they were. The maj= or >> difficulty is in making sure that I=E2=80=99ve read as much as I can in = that month, and >> trying to feel like I=E2=80=99ve treated most contributions =E2=80=9Cfai= rly=E2=80=9D (i.e. not missing >> people out) which requires looking at the ML + git log since the last TM= iO. >> >> For what it=E2=80=99s worth, once the org-latex-preview branch gets merg= ed, I plan on >> doing another TMiO with the disclaimer that I may have missed out a bunc= h of >> things in that edition. >> >> Something else we could do is have some sort of =E2=80=9Ccommunity draft= =E2=80=9D as is now >> being done on the Julia discourse, which could help reduce the individual >> workload (ref: ). > > I am not sure what this means, does one person create a summary of what > has been going on and others comment on it before it is published on a > proper blog? > >> All the best, >> Timothy > > John Yates writes: > >> Writing new content (=C3=A0 la Linux Weekly News) is a massive effort. = I would >> expect any attempt at such a product to peter out in short order. >> >> A big, big +1 for Sacha's weekly Emacs News. I find it just the right >> level of detail. It directs one to Emacs mail threads, upcoming events = and >> get togethers, blogs and Reddit posts, Youtube videos, etc. And, IIRC, = she >> is even set up to accept contributions from others. Let's support her. > > I am not proposing an alternative toe Emacs News in any sense. What I > am trying to convince people in joining me bootstrap is a medium that is > published less frequently, goes into more detail on core-development and > ELPA news and ideally wouldn't be written by a single person, but > feature more guest posts. > >> /john