emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: outorg issue
Date: Tue, 08 Sep 2015 22:09:12 +0200	[thread overview]
Message-ID: <87r3m8oeqf.fsf@gmail.com> (raw)
In-Reply-To: CAFyQvY1ufHM_vqXSDagZvXMRuB_D-nvxm7dbHCm4x+roJ0+-tw@mail.gmail.com

Kaushal <kaushal.modi@gmail.com> writes:

Hi all, Hi Bastien,


> I don't know the outshine and outorg code in and out. But I wouldn't
> mind keeping it maintained with the pull requests I get.
>
> That said, adding Thorsten Jolitz to this discussion.
> @Thorsten Would you mind making me (
> https://github.com/tj64/outshine/pull/46 ) a temporary maintainer of
> your outshine package on github. Or do you have anyone in mind you
> would take this up? Thanks.

sorry for being so late to the party, I didn't even notice the cc'd
messages, probably because I used to read this mailing list only via
gmane and filtered the posts from my mail inbox.

I feel bad anyway for the issues on github not taken care of, and while
I started to touch Emacs once in a while again, I'm afraid I won't be
much of a maintainer for these libraries in the future due to lack of
time and energy.
I used to simply apply patches untested on github, but that wasn't a
popular decision either.

So I'm very happy if somebody would like to take over (permanent)
maintainershisp. For me  outshine.el, outorg.el and navi-mode.el always
belonged together as the 'outshine suite', so to say, so I would prefer
to give them away as a bundle to a new maintainer (whoever that might
be, I'll leave that up to the Org Community and Maintainers).

I still find them quite usefull, I used them almost all the time when
programming or writing emails with emacs, and will do so in the future
whenever I touch Emacs.

So thanks in advance to the new maintainer, let me know (PM?) if I have
to do something in the course of changing maintainership

>     I'd also like to second Bastien's suggestion, it would be
>     excellent to
>     see this useful extension maintained again.

1+

-- 
cheers,
Thorsten

      reply	other threads:[~2015-09-08 20:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 21:51 outorg issue Andreas Leha
2015-08-13 14:30 ` John Kitchin
2015-08-13 14:37   ` Andreas Leha
2015-08-18 16:28 ` Bastien
2015-08-18 19:53   ` Andreas Leha
2015-08-18 20:11     ` Kaushal
2015-08-18 22:26       ` Bastien
2015-08-19  7:53       ` Andreas Leha
2015-08-18 20:35     ` Pip Cet
2015-08-19  8:10       ` Andreas Leha
2015-08-19 14:23         ` Pip Cet
2015-08-19 19:08           ` Kaushal
2015-09-08 20:09             ` Thorsten Jolitz [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=87r3m8oeqf.fsf@gmail.com \
    --to=tjolitz@gmail.com \
    --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).