From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Peter Mao <peter.mao@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>,
Dmitry M <dmitrym@gmail.com>,
goncalossantos98@gmail.com
Subject: Re: org-noter
Date: Sun, 12 Mar 2023 07:37:26 -0400 [thread overview]
Message-ID: <CAF-FPGNtS1D=rBxe=_ha1m+LsQxoZqBmQFjab=rgyjAbU4JG9g@mail.gmail.com> (raw)
In-Reply-To: <CAEK3s1MKi=6mntAp7a4qUEzxY-pprhOb6nbJpveuNx=csv3qGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
This is really cool, but doesn't there really need to be a single repo for
distribution, issue reporting, etc.?
Do you have a plan for which fork would become primary?
On Sat, Mar 11, 2023, 11:35 PM Peter Mao <peter.mao@gmail.com> wrote:
> Dear Org maintainers:
>
> I don't think org-noter is part of any official org distribution, having
> been a MELPA-distributed package since inception (2017), but in the course
> of discussing transfer of maintenance duties with Jonas Bernoulli (in his
> MELPA-maintainer role), he suggested that we inform you of the impending
> change to the maintenance of this package.
>
> In short, Dmitry and I have stabilized new features brought into the code
> since Gonçalos' last commit in 2019 and brought in CI and a few new
> features ourselves. We have tried to contact Gonçalos since early Dec
> 2022, but have not heard from him.
>
> Here are links to the relevant "issue" tickets on MELPA and the original
> org-noter repository where we have made our proposal to maintain the
> project:
> https://github.com/weirdNox/org-noter/issues/173
> https://github.com/melpa/melpa/issues/8413
>
> No action is needed on your part, but comments and suggestions are
> welcomed.
>
> Peter
>
>
>
[-- Attachment #2: Type: text/html, Size: 2033 bytes --]
next prev parent reply other threads:[~2023-03-12 11:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 4:35 org-noter Peter Mao
2023-03-12 11:37 ` Bruce D'Arcus [this message]
2023-03-12 19:00 ` org-noter Peter Mao
-- strict thread matches above, loose matches on Subject: below --
2022-05-14 18:37 org-noter Uwe Brauer
2022-05-15 7:10 ` org-noter Colin Baxter
2022-05-15 18:58 ` org-noter Uwe Brauer
2022-05-16 8:29 ` org-noter Colin Baxter
2022-05-16 12:02 ` org-noter Ihor Radchenko
2022-05-17 13:06 ` org-noter Uwe Brauer
2022-05-17 13:07 ` org-noter Uwe Brauer
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='CAF-FPGNtS1D=rBxe=_ha1m+LsQxoZqBmQFjab=rgyjAbU4JG9g@mail.gmail.com' \
--to=bdarcus@gmail.com \
--cc=dmitrym@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=goncalossantos98@gmail.com \
--cc=peter.mao@gmail.com \
/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).