From: Ihor Radchenko <yantar92@posteo.net>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: Bastien <bzg@gnu.org>,
emacs-orgmode@gnu.org, flexibeast@gmail.com,
Nik Clayton <nik@ngo.org.uk>
Subject: Re: [MAINTENANCE] Org orphanage?
Date: Fri, 18 Aug 2023 09:19:23 +0000 [thread overview]
Message-ID: <875y5cpv1g.fsf@localhost> (raw)
In-Reply-To: <87msyphjlh.fsf@bernoul.li>
Jonas Bernoulli <jonas@bernoul.li> writes:
>> What about https://github.com/flexibeast/org-vcard and
>> https://github.com/nikclayton/ob-sql-mode ?
>
> Are you saying these packages are unmaintained and asking whether they
> should be moved to the orphanage?
https://github.com/flexibeast/org-vcard page explicitly says that it is
looking for a new maintainer at least since 9 months ago. (The author is
in CC for this thread)
The author (also CCed) of https://github.com/nikclayton/ob-sql-mode
explicitly asked for help 8 months ago in
https://list.orgmode.org/CAKJTzL5bdw=vCBk0S9O3DFh2FkASro3m++wHqMhCp9ObaphSdg@mail.gmail.com/T/#u
We got no volunteers.
>> Also, we might want to add org-json and org-redmine to
>> https://orgmode.org/worg/org-orphanage.html
>
> Yes.
Done.
https://git.sr.ht/~bzg/worg/commit/494157f6
> Unmaintained packages frequently come up on Melpa, so we have documented
> how we try to handle that. A lot of what is being said there, also
> applies when packages in need are brought up elsewhere.
>
> https://github.com/melpa/melpa/wiki/Unmaintained-Packages-and-Forks.
It will be a good idea to document these things in WORG as well. Under a
separate section in org-orphanage.org like "I want to volunteer
maintaining a package from this list".
--
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-18 9:19 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
2023-08-18 9:19 ` Ihor Radchenko [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875y5cpv1g.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=flexibeast@gmail.com \
--cc=jonas@bernoul.li \
--cc=nik@ngo.org.uk \
/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.