emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: emacs-orgmode@gnu.org
Subject: Re: org-drill futures
Date: Sun, 02 Jun 2019 18:52:01 +0100	[thread overview]
Message-ID: <87muiznada.fsf@russet.org.uk> (raw)
In-Reply-To: <WM!090c4ba5a896c4ed29d157d8725771c53d7f62973be201e8f0b2cf919c5d1902b13274cd55dd445dbbd0c45b7dc291e8!@mailhub-mx4.ncl.ac.uk> (Nicolas Goaziou's message of "Sun, 2 Jun 2019 19:22:25 +0200")

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> phillip.lord@russet.org.uk (Phillip Lord) writes:
>
>> I've launched an fork of org-drill. I have tried to reach Paul Sexton,
>> the original author, and had some feedback (he was happy for my take
>> over), but not managed to get the repository moved.
>>
>> https://gitlab.com/phillord/org-drill/
>>
>> I'd like to have this be the version that ends up in contrib. Can anyone
>> tell me how to achieve this?
>
> I would suggest the opposite: move it to GNU ELPA, for example, so we
> can remove it from contrib.
>
> WDYT?


Yes, I am quite happy with that also -- it would save the effort of
syncing it. It would have to be MELPA though, because I don't think we
have papers (I can check). This does have the disadvantage of requiring
people to update their config/installed packages, but it's probably
okay.

I'd plan to incorporate org-learn into org-drill -- I suspect everyone
using org-learn is using it via org-drill, so winding it in makes sense,
so I'd need to remove both.

I'll see how MELPA are with adding my fork there; if they are happy,
once that it up and running it could be pulled from contrib.

Phil

  parent reply	other threads:[~2019-06-02 17:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-16 14:31 org-drill futures Phillip Lord
2019-03-17  5:59 ` stardiviner
     [not found] ` <WM!e2dda79f98b3905819d845394cd0057dd51e6bcd9c6e5b8d74f505b8ace51a0599b05780fb519bfc33cf9aea7a758159!@mailhub-mx5.ncl.ac.uk>
2019-06-02 15:48   ` Phillip Lord
2019-06-02 17:22     ` Nicolas Goaziou
     [not found]       ` <WM!090c4ba5a896c4ed29d157d8725771c53d7f62973be201e8f0b2cf919c5d1902b13274cd55dd445dbbd0c45b7dc291e8!@mailhub-mx4.ncl.ac.uk>
2019-06-02 17:52         ` Phillip Lord [this message]
2019-06-18 20:18           ` Stig Brautaset
     [not found]             ` <WM!aaeec6f285e7a8a3396a58673506c679258f3a632bfb142ae94cd64dc73eff085b6e7ec61aeb828295c13b4f544377e4!@mailhub-mx2.ncl.ac.uk>
2019-06-19  9:08               ` Phillip Lord
2019-06-19 10:23                 ` Stig Brautaset
     [not found]           ` <WM!66798c151063ae53ad069c85a3e84b4efd410c2e9f2c32c86aefebbb6d70de8de2fe83f611a9dccabfdc57667e342d33!@mailhub-mx1.ncl.ac.uk>
2019-06-29 15:43             ` Phillip Lord

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=87muiznada.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --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).