From: Bastien <bzg@altern.org>
To: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
Cc: emacs-orgmode@gnu.org, Jambunathan K <kjambunathan@gmail.com>
Subject: Re: Offer for taking over maintainership
Date: Thu, 14 Feb 2013 08:37:49 +0100 [thread overview]
Message-ID: <87obfnjlok.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAEWDx5fUpwh_QY1xD20QOXvUu=n6p61FqKg=Pj+TjSXTHjAp=A@mail.gmail.com> (Jonathan Leech-Pepin's message of "Wed, 13 Feb 2013 20:16:13 -0500")
Hi Jonathan,
Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
> Either there's some
> underlying reason for your apparent dislike for Bastien and his
> approach to maintaining
> Org, or some argument in the past that I am not aware of.
For the sake of clarity (and history), here is how I understand why
Jambunathan thinks I am not a good maintainer: he was frustrated with
the way I handled the merge of the ODT export feature.
The very first ODT exporter was based on two libraries: org-lparse.el
and org-xhtml.el. org-lparse.el implemented a new export engine that
org-xhtml.el was using to produce HTML, and org-odt.el would build on
top of both librairies.
This approach was not satisfactory to me. First, because I found
org-lparse.el was ugly, mixing the wrong line-by-line approach for
parsing an Org buffer, and the better "recursive" approach (have a
look at org-lparse.el to get an idea of whether it is ugly.) Second,
because I thought having org-xhtml.el along org-html.el was confusing.
Nicolas already started to work on his new exporter, encouraged by the
first modest proof of concept I had for the recursive approach.
I took the decision to delay the merge of the ODT exporter until it
didn't rely on org-xhtml.el anymore, because I thought that relying
on org-lparse.el for two export formats (HTML and ODT) was a wrong
move, giving the wrong signal to Nicolas.
When org-xhtml.el was not in the game anymore, and when I was
confident Nicolas was deeply committed to the new exporter, I went
with the merge. I was happy! I even received kudos from Jambunathan
when I managed to solve possible copyright issues wrt merging .xml
files into Emacs (there was a confusion on whether those files were
copyrighted by OASIS and "mergeable" into Emacs.)
Maybe Jambunathan thought all this was too slow, and based on stupid
decisions. He was on a sabbatical year at the time, and had plenty of
time to work on the exporter and to put the pressure on me. I was
maintaining Org in my spare time, and tried to handle the pressure the
way I could.
I hope this is faithful to the facts -- all this is publicly available
on this mailing list anyway!
> Regardless, Bastien is doing a fine job from what I can see, he is
> certainly actively assisting
> users who post with questions or bugs, even when they occurred during
> a time where he was
> absent (with prior notice). Perhaps he has not contributed to
> certain aspects as others have,
> however his presence and monitoring of the smaller aspects does allow
> for further development
> to proceed without being interrupted by every issue.
Actually, one of the reasons I want to step down in the long run is
that I'm a bit frustrated of not having time enough to focus on big
new features. But the flow of new users and new contributors is
rewarding enough so that maintaining Org keeps being fun :)
All best,
--
Bastien
next prev parent reply other threads:[~2013-02-14 9:21 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 18:08 Offer for taking over maintainership Jambunathan K
2013-02-13 19:01 ` Jambunathan K
2013-02-13 20:45 ` John Wiegley
2013-02-13 21:31 ` Allen S. Rout
2013-02-13 21:41 ` Russell Adams
2013-02-14 0:11 ` Scott Randby
2013-02-14 9:09 ` Jambunathan K
2013-02-13 22:03 ` Charles Philip Chan
2013-02-13 22:11 ` Yagnesh Raghava Yakkala
2013-02-14 8:55 ` Jambunathan K
2013-02-14 9:53 ` Bastien
2013-02-14 9:55 ` Jambunathan K
2013-02-14 9:59 ` Bastien
2013-02-14 10:25 ` Jambunathan K
2013-02-13 22:18 ` Bastien
2013-02-14 9:18 ` Jambunathan K
2013-02-14 9:38 ` Jambunathan K
2013-02-14 9:54 ` Glyn Millington
2013-02-14 10:35 ` Jambunathan K
2013-02-14 0:06 ` François Pinard
2013-02-14 8:38 ` Ramon Diaz-Uriarte
2013-02-14 10:37 ` Jambunathan K
2013-02-14 16:31 ` François Pinard
2013-02-14 23:28 ` Carsten Dominik
2013-02-15 3:23 ` Jambunathan K
2013-02-15 4:11 ` Jambunathan K
2013-02-14 1:12 ` Takaaki ISHIKAWA
[not found] ` <CAJcAo8ueOp8dDBwq+bEufZJ1kSZLpVxY36L7eKUt4QDwRH98zQ@mail.gmail.com>
2013-02-14 1:40 ` Fwd: " Samuel Wales
2013-02-14 9:22 ` Jambunathan K
2013-02-14 1:16 ` Jonathan Leech-Pepin
2013-02-14 6:36 ` Jambunathan K
2013-02-14 6:45 ` Jambunathan K
2013-02-14 9:22 ` Rainer M Krug
2013-02-14 9:50 ` Jambunathan K
2013-02-14 9:53 ` Rainer M Krug
2013-02-14 7:37 ` Bastien [this message]
2013-02-14 10:12 ` Jambunathan K
2013-02-14 10:54 ` Jambunathan K
2013-02-14 16:07 ` François Pinard
2013-02-14 7:59 ` David Rogers
2013-02-14 10:40 ` Nicolas Richard
2013-02-14 11:37 ` Jambunathan K
2013-02-14 11:41 ` Jambunathan K
2013-02-14 11:57 ` Detlef Steuer
2013-02-14 13:26 ` Julian Burgos
2013-02-14 13:39 ` Jambunathan K
2013-02-14 11:54 ` Jambunathan K
-- strict thread matches above, loose matches on Subject: below --
2013-02-14 15:36 Jose E. Marchesi
2013-02-14 15:41 ` Allen S. Rout
2013-02-14 17:38 ` Jambunathan K
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=87obfnjlok.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=jonathan.leechpepin@gmail.com \
--cc=kjambunathan@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).