From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Thomas S. Dye" Subject: Re: [RFC] Moving "manual.org" into core Date: Mon, 05 Mar 2018 23:57:10 -1000 Message-ID: <876069y1ah.fsf@tsdye.com> References: <87bmhooaj9.fsf@nicolasgoaziou.fr> <87y3j8dw45.fsf@bzg.fr> <87lgf8f93b.fsf@nicolasgoaziou.fr> <87lgf89lro.fsf@gnu.org> <87k1uq4n90.fsf@nicolasgoaziou.fr> <87k1uql7it.fsf@tsdye.com> <87r2oy57tq.fsf@bzg.fr> Mime-Version: 1.0 Content-Type: text/plain; format=flowed Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33501) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1et9Li-0005D2-5m for emacs-orgmode@gnu.org; Tue, 06 Mar 2018 04:57:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1et9Lf-00071O-Jv for emacs-orgmode@gnu.org; Tue, 06 Mar 2018 04:57:34 -0500 Received: from gproxy2-pub.mail.unifiedlayer.com ([69.89.18.3]:55488) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1et9Lf-00070w-AL for emacs-orgmode@gnu.org; Tue, 06 Mar 2018 04:57:31 -0500 Received: from cmgw4 (unknown [10.0.90.85]) by gproxy2.mail.unifiedlayer.com (Postfix) with ESMTP id 0FE191E080F for ; Tue, 6 Mar 2018 02:57:27 -0700 (MST) In-reply-to: <87r2oy57tq.fsf@bzg.fr> 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" To: Bastien Guerry Cc: Glenn Morris , Achim Gratz , Org Mode List , Nicolas Goaziou Aloha Bastien, Bastien Guerry writes: > Maybe this is where some misunderstanding arose: to me, there > was no > _project_ to migrate to manual.org -- it was an idea in the air > after > you made your experiment and we now have the decision at hand > because > the project is, well, DONE. > > We could have done it another way: we could have discussed it as > a > project, then anticipated that it will prevent Org's code to > migrate > to Emacs repository, then discussed the pros and cons before > investing > more time. Thanks for pointing out this alternative. Several of us working on the manual did recently discuss various issues on the list. Nicolas had several messages, I responded to most of them, and others chimed in on particular parts: Achim Gratz, Kyle Meyer, and Kaushal Modi come to mind immediately, but there may have been others. In the past, we could have been assured Carsten would join the discussion in one way or another as maintainer, working to keep us on track and guide us to the most productive use of our time. However, you have chosen to fulfill the duties of maintainer in a different way, one that does not involve day-to-day interaction with the volunteers who are themselves choosing to spend time trying to augment and improve Org mode. I don't argue with this decision of yours, but to my mind, this is why we are where we are today. Certainly, if I had understood in 2013 that my efforts would eventually work against Org mode by preventing migration of its code to Emacs repository (an issue that I don't understand fully but accept as valid), then I would have saved that time for other pursuits. But, you did not say this at the time, as far as I remember. My memory is that you were mostly silent. Similarly, it was clear to me from lurking on the list last year that Nicolas was going to revive the project. I believe it was also clear to the others who participated in the conversation on list, but I don't want to speak for them. You either did not read that discussion or you did read it and chose not to participate. Work on the manual project wasn't a secret. >From my point of view, your involvement has come at the 11th hour, well after much effort has been expended on what several of our colleagues believe is a contribution to Org mode. I'm pleased that you are willing to give the project a try, but I want to insist that you take some responsibility for where we are in this discussion. I cannot accept that the maintainer scolds me and others who worked on the project that "we could have done it another way." This is exactly the responsibility I want to insist the maintainer accept. We look to the maintainer for guidance. Please give it to us in a timely manner. All the best, Tom -- Thomas S. Dye http://www.tsdye.com