From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Fu Yuan Newsgroups: gmane.emacs.devel Subject: Re: Monthy emacs-devel digest, similar to "This month in Org" Date: Fri, 1 Sep 2023 09:56:17 -0700 Message-ID: References: <877cpavw8h.fsf@posteo.net> Mime-Version: 1.0 (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="19521"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Ihor Radchenko , Timothy , Sacha Chua , Po Lu , Dmitry Gutov , Stefan Kangas , Danny Freeman , Eli Zaretskii , emacs-devel@gnu.org, manuel.uberti@inventati.org To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Sep 01 18:57:27 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 1qc7SY-0004u5-6b for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Sep 2023 18:57:26 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qc7Ro-0003Fi-Rt; Fri, 01 Sep 2023 12:56:40 -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 1qc7Ri-0003Dm-Tr for emacs-devel@gnu.org; Fri, 01 Sep 2023 12:56:35 -0400 Original-Received: from mail-pf1-x42c.google.com ([2607:f8b0:4864:20::42c]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qc7Rf-0000WT-1y; Fri, 01 Sep 2023 12:56:34 -0400 Original-Received: by mail-pf1-x42c.google.com with SMTP id d2e1a72fcca58-68bec3a1c0fso1878968b3a.1; Fri, 01 Sep 2023 09:56:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693587389; x=1694192189; darn=gnu.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=a1VJhPspU3nESxIKJGhp7sbtxKJ4k8VG/6aTG/5WCuU=; b=qllzKFqxQZ9iajahMJTTHF7rw5lRwbHyeLO0I7vRaIwgN+hHQAvMsspGjFWFMgEsnj xhLHL4gwp3qnzvGp6QNhttemLtvNgVNW46Z8o4a6TlAlL0hDvjLsAiM8b7pj5D+zUp7K fYIszcqCmBkDi4Ye4Y7EMuYZusXfYj7swWNjALU4RkprWQEwJ+EbEOCn5zO/zD0iUQbx etXOQSsiZjz8MlLoLt7GJ7xWXd0XNVYW+TChrui7nWBkLUEr5yyFQ2PZWquEIXmG2D5W D6aTwyADok6VWWLBHffO8SulEtHZ5N0CVFe5aKTC8vpOQCeLmNLXOLJMFm48J+YXIn+n T9zQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693587389; x=1694192189; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=a1VJhPspU3nESxIKJGhp7sbtxKJ4k8VG/6aTG/5WCuU=; b=jZclmQeG1005q0EhRe/RtAwQhUDkFoY+2Slu3fqMGcq6ZxePDNqSceBSRiXgoQ6NF2 gI/YfYe6Fcz4+6lCNzEkLndyTDZN7y8QHVV2syZdPRxTeygFMXwEPaAzRItApMFLh2Pr T9vjOlKGBG1bMwdrqJ1LyeAnKZUah/5J58a6RGihJ5CcUwvh9kzsVVPo2Fn2U/JSzQKe Jzozr/5AXbrUqmR1R+aClSdTlfcwZ6MfWrQnuvBX+M2sL3b3K2gAw5Av43QD/R3nrVVy vTbsvYGnHEwRowSCe/khDMT9e9jRcffapsz9EWYmtF6WsTMzCs42k6RiP5G/CUJ8QUs+ IkEw== X-Gm-Message-State: AOJu0Yx1I9GXCI2+GQxZTpmRzkjKGwdwsp3S7OscpBhH11PKbRuA7QPs OmQzh0lfLnLG4DtipBZ7HVarclHAH/b4WQ== X-Google-Smtp-Source: AGHT+IFMzsKXWesEmmoV4deoYb2U/hZqnZqR1Bt3qdrPAZnV6pvcm/TfxaFhgjvqevlX65A9G1nwDQ== X-Received: by 2002:a05:6a00:844:b0:682:b6c8:2eb with SMTP id q4-20020a056a00084400b00682b6c802ebmr3578265pfk.1.1693587388648; Fri, 01 Sep 2023 09:56:28 -0700 (PDT) Original-Received: from smtpclient.apple (cpe-172-117-161-177.socal.res.rr.com. [172.117.161.177]) by smtp.gmail.com with ESMTPSA id y19-20020a62b513000000b0068c65da7b1esm3161452pfe.159.2023.09.01.09.56.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 01 Sep 2023 09:56:28 -0700 (PDT) In-Reply-To: <877cpavw8h.fsf@posteo.net> X-Mailer: iPhone Mail (20G75) Received-SPF: pass client-ip=2607:f8b0:4864:20::42c; envelope-from=casouri@gmail.com; helo=mail-pf1-x42c.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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:309820 Archived-At: >>=20 >>> 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. >>=20 >> This is actually quite an effort. AFAIK, the author had difficulties >> allocating time to write more posts for TMiO. >>=20 >> Also, for reference, we are talking about >> https://blog.tecosaur.com/tmio/2022-05-31-folding.html >=20 > 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. >=20 > 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. >=20 > 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 That would be valuable for Emacs development. For example, sometimes I wish t= here is an official channel in which I can post progress of tree-sitter func= tionalities, and ask for help for adding certain features, and conclusion of= general tree-sitter discussions and direction forward. I think other featur= es/submodules could benefit the same. >>> ... 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? >>=20 >> A somewhat relevant effort is by Sacha Chua: >> https://sachachua.com/blog/2023/08/2023-08-28-emacs-news/ >>=20 >> It is less detailed (just an outline), but I find it pretty useful. >=20 > 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. >=20 > 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. >=20 > Timothy writes: >=20 >> Hi Ihor, >>=20 >>> This is actually quite an effort. AFAIK, the author had difficulties >>> allocating time to write more posts for TMiO. >>>=20 >>> Also, for reference, we are talking about >>> >>=20 >> Each post took several hours to do, despite how short they were. The majo= r >> difficulty is in making sure that I=E2=80=99ve read as much as I can in t= hat month, and >> trying to feel like I=E2=80=99ve treated most contributions =E2=80=9Cfair= ly=E2=80=9D (i.e. not missing >> people out) which requires looking at the ML + git log since the last TMi= O. >>=20 >> For what it=E2=80=99s worth, once the org-latex-preview branch gets merge= d, I plan on >> doing another TMiO with the disclaimer that I may have missed out a bunch= of >> things in that edition. >>=20 >> 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: ). >=20 > 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? >=20 >> All the best, >> Timothy >=20 > John Yates writes: >=20 >> 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. >>=20 >> 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 a= nd >> get togethers, blogs and Reddit posts, Youtube videos, etc. And, IIRC, s= he >> is even set up to accept contributions from others. Let's support her. >=20 > 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. >=20 >> /john >=20