From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Changing the maintainer Date: Fri, 19 Apr 2013 00:07:50 +0200 Message-ID: <72A14A3B-42A1-4974-A51F-82436A623B8C@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:38188) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1USwzj-0003hW-0v for emacs-orgmode@gnu.org; Thu, 18 Apr 2013 18:07:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1USwzh-00040p-Ik for emacs-orgmode@gnu.org; Thu, 18 Apr 2013 18:07:54 -0400 Received: from mail-we0-x229.google.com ([2a00:1450:400c:c03::229]:54815) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1USwzh-00040g-Cm for emacs-orgmode@gnu.org; Thu, 18 Apr 2013 18:07:53 -0400 Received: by mail-we0-f169.google.com with SMTP id x43so2894814wey.14 for ; Thu, 18 Apr 2013 15:07:52 -0700 (PDT) Received: from 192.168.2.2 ([86.85.85.170]) by mx.google.com with ESMTPSA id du2sm57939wib.0.2013.04.18.15.07.50 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Apr 2013 15:07:51 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "emacs-orgmode@gnu.org list" Hello everyone, as Bastien has written in a related thread, the current idea is that I will take over the maintainership of Org-mode once more. I have seen no objections so far, so I am assuming that we should go ahead with this plan. Let me start by extending my (and I am sure, everyones) gratitude to Bastien. I think he has done an incredible job over the last two years, keeping Org-mode on course and also supporting significant changes that we have seen with the release of version 8.0. Bastien's activity has been unmatched. He has answered a huge amount of questions in the mailing list, fixed an uncounted number of bugs and he has been designing and applying changes over the entire breadth of the Org code base. This is no easy feat and I really admire his work. Besides this, he has done amazing work keeping the community together and making sure that the mailing list remains IMO one of the prime places on the internet. THANK YOU, Bastien. I will leave the donations button on his name until the end of April, so if you want to express your thanks to him in this way, you have that possibility. If not, writing to him and expressing your amazement with his achievements in the last two years will probably make him as happy. One of the main things Bastien has done is to make space for other developers, while making sure that the development maintains a maximum of compatibility, usability and hackability. It has taken a long time to get the new exporter into the main stream, and I clearly think it was worth the wait. We now have a complete set of exporters, immediately in the first release that is based on the new parser and exporter framework. What Nicolas has achieved I still cannot fully comprehend. The exporter side of Org-mode was very usable, but it was an unmaintainable mess, without clarity. Now, writing a new exporter has become extremely simple, everyone can do it. Due to the ingenious filter and inheritance system, new exporters can be written with very little code. Maintenance will be simple, since this is ONE parser, one framework. When I handed over the maintainership to Bastien two years ago, I was worn down. In the mean time, my life has not become less full, and so this time around, I will make sure that the project does not swallow me. I hope very much that we as a community can continue on the path Bastien has set, with a growing number of people taking responsibility for specific parts of Org. I need to re-familiarize myself with many things, I am not up to speed with some of the new developments, so I need to study. But when this is done, I will approach some of you and ask for help, it would be great if some of you can say yes and work with me. I will see my own task mainly in removing obstacles for everyone, and in coordinating releases. I also have coding ideas and plans, but those will have second priority. I am really glad that Bastien has promised to stick around, and he will still lead the round of fixes that usually follow after a major release. I am looking forward to again interact more with you all. Cheers - Carsten