From: TRS-80 <lists.trs-80@isnotmyreal.name>
To: emacs-orgmode@gnu.org
Subject: Re: Is there a maintained calf-calendar fork?
Date: Wed, 04 May 2022 21:02:17 -0400 [thread overview]
Message-ID: <87tua423mu.fsf@isnotmyreal.name> (raw)
In-Reply-To: 0b823d04-c117-ae98-fec2-17c4c3708528@gmail.com
Ypo <ypuntot@gmail.com> writes:
> within a calendar: https://github.com/kiwanami/emacs-calfw
>
> But it seems to be unmaintained.
>
> Is there some *recommended *fork on Github with corrected bugs or new
> functions?
I don't know about *recommended*, however I do see at least a couple
names I recognize in the list of forks (jweigley, syohex)[0].
I do not know of a way, in the GitHub UI (or through their API) to see
which one of those forks might be ahead by the most number of
commits[1]. Which means instead clicking on each one manually and
looking at it. If there is some better way, I would love to know about
it.
> Offtopic if the answer to the above question is affirmative: could it
> be on MELPA? Can MELPA change to new forks?
I also see emacsmirror in the list. Maybe raise an issue there (or at
Emacs Orphanage, etc.), maybe they know something more.
Finally, there is always the option of picking up maintenance yourself.
It often begins simply enough, fixing something that broke for
yourself... Next thing you know you are sharing those patches, before
you know it... you are suddenly maintaining a package. :)
Just some food for thought.
Cheers,
TRS-80
[0] https://github.com/kiwanami/emacs-calfw/network/members
[1] Not that this is a guarantee of anything, but it is one indication.
prev parent reply other threads:[~2022-05-05 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 22:03 Is there a maintained calf-calendar fork? Ypo
2022-03-28 11:15 ` Detlef Steuer
2022-05-05 1:02 ` TRS-80 [this message]
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=87tua423mu.fsf@isnotmyreal.name \
--to=lists.trs-80@isnotmyreal.name \
--cc=emacs-orgmode@gnu.org \
/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).