all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Bastien Guerry <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org, Timothy <orgmode@tec.tecosaur.net>
Subject: Re: Maintenance status of individual Org libraries
Date: Sun, 06 Aug 2023 08:42:14 +0000	[thread overview]
Message-ID: <87il9simu1.fsf@localhost> (raw)
In-Reply-To: <87tttcra1p.fsf@bzg.fr>

Bastien Guerry <bzg@gnu.org> writes:

> Ihor Radchenko <yantar92@posteo.net> writes:
>
>> Should we try to make a call for maintenance at least for some of these
>> libraries?
>
> Definitely.  We should probably prioritize files in this list, then
> ask on this list *and* on the web.
>
> Let's make sure we propose this as something fun to do, not a chore.
>
> How do you want to proceed?

I have no concrete plan. Some random thoughts:

- We may run a poll on how people use various parts of Org to see
  popularity/user base for different libraries. This may be a useful
  metrics for prioritization.

- We may need to identify the core libraries that have to be maintained
  better because everything else relies upon them.

- Some people are scared of maintenance partly because they do not want
  to follow all the messages in the mailing list.

- Rather than asking straight about maintenance, we may ask about
  problem people encounter with the Org libraries they use.  Having some
  real, personal problem to solve may be a driver to get started with
  maintaining a library.

- Instead of maintenance, we can ask people to demo using some less
  popular libraries during meetups (like
  https://orgmode.org/list/87tttlflht.fsf@localhost). This may reveal
  problems better and may allow writing the often missing tests. At
  least, tests can make things more robust even if not maintained.

-- 
Ihor Radchenko // yantar92,
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/yantar92>


  reply	other threads:[~2023-08-06  8:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 13:41 Maintenance status of individual Org libraries Ihor Radchenko
2023-08-05  9:46 ` Ihor Radchenko
2023-08-06  5:53 ` Bastien Guerry
2023-08-06  8:42   ` Ihor Radchenko [this message]
2023-08-20 20:56 ` Matt
2023-08-21  8:03   ` Ihor Radchenko

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

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

  git send-email \
    --in-reply-to=87il9simu1.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=orgmode@tec.tecosaur.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.