From: Ihor Radchenko <yantar92@posteo.net>
To: Jonas Bernoulli <jonas@bernoul.li>, Timothy <orgmode@tec.tecosaur.net>
Cc: Corwin Brust <corwin@bru.st>,
krupalinbox@gmail.com, Bastien <bzg@gnu.org>,
emacs-orgmode@gnu.org, flexibeast@gmail.com
Subject: Re: [MAINTENANCE] Org orphanage?
Date: Fri, 25 Aug 2023 10:07:00 +0000 [thread overview]
Message-ID: <87y1hzfnaz.fsf@localhost> (raw)
In-Reply-To: <87o7iw9u78.fsf@bernoul.li>
Jonas Bernoulli <jonas@bernoul.li> writes:
> Thanks for offering to help out Corwin!
>
>>> Speaking for myself, I can help:
>>> [...]
>>> - review the bonafides (experience/involvement and, via Eli/SM,
>>> assignment status ) for prospective adopting maintainers
>>
>> Not sure about emacsorphanage side, but for things we decide to manage
>> on sr.ht, we can all discuss new maintainers on this mailing list. The
>> maintenance requests should also go here.
>
> The orphanage is often first brought up in the package's issue tracker,
> or on Melpa's issue tracker. Sometimes I bring it up, sometimes a user
> of a package makes us aware of a stale package.
How do you determine when to bring up the issue? If we have a clear
criterion, I can see how Corwin or other volunteers may help - by
contacting the package authors by email/on forge they use.
> If you are interested in that kind of work looked through the list of
> orphaned packages for something that interests you and then offer to
> maintain that.
That reminds me of Emacs survey. Since the best source of maintainers is
package's own user base, may it be a good idea to ask in Emacs survey if
people use some orphaned packages?
>>> Irrespective of whether worg curators should help with this (or some
>>> other vols, or just the org maintainers, or...), I think it would make
>>> sense to document these "responsibilities" (and the detail of the
>>> plans made in this thread, in general), along with the whos and hows.
>>
>> +1
>
> I'll try collecting existing resources and maybe write some new ones,
> but I have a lot on my plate, so this will likely take a while.
A draft might be prepared by volunteers. Will it make things easier for
you?
--
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>
next prev parent reply other threads:[~2023-08-25 10:12 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 8:17 [MAINTENANCE] Org orphanage? Ihor Radchenko
2022-11-21 11:02 ` Bastien
2022-11-21 11:53 ` Ihor Radchenko
2022-11-22 0:45 ` Alexis
2022-12-11 10:29 ` Ihor Radchenko
2022-12-29 16:13 ` Bastien
2022-12-31 12:31 ` Ihor Radchenko
2023-01-02 15:07 ` Bastien
2023-01-02 15:12 ` Ihor Radchenko
2023-01-02 15:28 ` Bastien
2023-01-03 10:45 ` Ihor Radchenko
2023-01-04 9:30 ` Bastien
2023-01-05 11:02 ` Ihor Radchenko
2023-01-05 11:30 ` Bastien
2023-01-06 1:54 ` Samuel Wales
2023-01-06 8:09 ` Greg Minshall
2023-01-06 8:23 ` Bastien Guerry
2023-01-06 16:51 ` Ihor Radchenko
2023-01-06 17:06 ` tomas
2023-01-07 10:07 ` Bastien
2023-01-07 10:19 ` Bastien Guerry
2023-02-04 13:57 ` Ihor Radchenko
2023-08-16 15:33 ` Jonas Bernoulli
2023-08-17 12:28 ` Ihor Radchenko
2023-07-31 11:13 ` Ihor Radchenko
2023-08-13 15:11 ` Jonas Bernoulli
2023-08-13 15:36 ` Htmlize support, maintenance, and Org mode (was: [MAINTENANCE] Org orphanage?) Ihor Radchenko
2023-08-14 1:30 ` Samuel Wales
2023-08-14 13:15 ` Jonas Bernoulli
2023-08-14 13:35 ` Ihor Radchenko
2023-08-14 16:17 ` Htmlize support, maintenance, and Org mode Bastien Guerry
2023-08-14 16:22 ` Ihor Radchenko
2023-08-14 16:30 ` Bastien Guerry
2023-08-15 10:21 ` Timothy
2023-08-14 13:58 ` Philip Kaludercic
2023-08-14 14:14 ` Ihor Radchenko
2023-08-14 14:18 ` Philip Kaludercic
2023-08-14 14:32 ` Ihor Radchenko
2023-08-14 16:20 ` Bastien Guerry
2023-08-14 16:24 ` Ihor Radchenko
2023-08-15 10:27 ` [MAINTENANCE] Org orphanage? Hrvoje Nikšić
2023-08-15 16:12 ` Ihor Radchenko
2023-08-20 20:41 ` Hrvoje Nikšić
2023-08-16 15:16 ` Jonas Bernoulli
2023-08-17 12:27 ` Ihor Radchenko
2023-08-17 13:41 ` Jonas Bernoulli
2023-08-17 15:08 ` Corwin Brust
2023-08-21 7:46 ` Ihor Radchenko
2023-08-24 18:22 ` Jonas Bernoulli
2023-08-25 10:07 ` Ihor Radchenko [this message]
2023-08-18 9:19 ` Ihor Radchenko
2023-08-18 13:32 ` Alexis
2023-08-22 15:13 ` Bastien Guerry
2023-08-24 17:49 ` Jonas Bernoulli
2023-08-24 18:24 ` Bastien Guerry
2022-11-21 22:19 ` Tim Cross
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=87y1hzfnaz.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bzg@gnu.org \
--cc=corwin@bru.st \
--cc=emacs-orgmode@gnu.org \
--cc=flexibeast@gmail.com \
--cc=jonas@bernoul.li \
--cc=krupalinbox@gmail.com \
--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 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).