emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Timothy <orgmode@tec.tecosaur.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Philip Kaludercic <philipk@posteo.net>,
	Sacha Chua <sacha@sachachua.com>, Po Lu <luangruo@yahoo.com>,
	Dmitry Gutov <dmitry@gutov.dev>,
	Stefan  Kangas <stefankangas@gmail.com>,
	Danny Freeman <danny@dfreeman.email>,
	Eli  Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org, emacs-orgmode@gnu.org,
	manuel.uberti@inventati.org
Subject: Re: TMiO (was: "Re: Monthy emacs-devel digest, similar to "This month in Org")
Date: Fri, 01 Sep 2023 18:54:23 +0800	[thread overview]
Message-ID: <87edjixije.fsf@tec.tecosaur.net> (raw)
In-Reply-To: <87edjiryi5.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

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
> <https://blog.tecosaur.com/tmio/2022-05-31-folding.html>

Each post took several hours to do, despite how short they were. The major
difficulty is in making sure that I’ve read as much as I can in that month, and
trying to feel like I’ve treated most contributions “fairly” (i.e. not missing
people out) which requires looking at the ML + git log since the last TMiO.

For what it’s worth, once the org-latex-preview branch gets merged, I plan on
doing another TMiO with the disclaimer that I may have missed out a bunch of
things in that edition.

Something else we could do is have some sort of “community draft” as is now
being done on the Julia discourse, which could help reduce the individual
workload (ref: <https://discourse.julialang.org/t/this-month-in-julia-world-2023-08/103242>).

All the best,
Timothy

-- 
Timothy (‘tecosaur’/‘TEC’), Org mode contributor.
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/tec>.

           reply	other threads:[~2023-09-01 14:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87edjiryi5.fsf@localhost>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87edjixije.fsf@tec.tecosaur.net \
    --to=orgmode@tec.tecosaur.net \
    --cc=danny@dfreeman.email \
    --cc=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=manuel.uberti@inventati.org \
    --cc=philipk@posteo.net \
    --cc=sacha@sachachua.com \
    --cc=stefankangas@gmail.com \
    --cc=yantar92@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).