From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Release 8.0 Date: Mon, 22 Apr 2013 20:32:38 +0200 Message-ID: References: <87ehe7yenk.fsf@bzg.ath.cx> <8738ukdreu.fsf@mean.albasani.net> <87y5ccnhgq.fsf@bzg.ath.cx> <87sj2ipjs0.fsf@bzg.ath.cx> 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]:38056) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UULXh-0007W1-9Q for emacs-orgmode@gnu.org; Mon, 22 Apr 2013 14:32:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UULXf-0002Io-Nd for emacs-orgmode@gnu.org; Mon, 22 Apr 2013 14:32:45 -0400 In-Reply-To: <87sj2ipjs0.fsf@bzg.ath.cx> 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: Bastien Cc: emacs-orgmode@gnu.org, Memnon Anon , Jay Kerns On 22.4.2013, at 19:17, Bastien wrote: > Hi Jay, > > Jay Kerns writes: > >> On Sun, Apr 21, 2013 at 9:25 AM, Bastien wrote: >>> Hi Memnon, >>> >>> Memnon Anon writes: >> >> [ snip ] >> >> Quick question: is it true, now that Org 8.0 has been released, that >> the engine which publishes Worg is now Org 8.0, too? > > No, not yet. > >> In other words, is it now safe to publish to Worg all of that stuff >> which was written compatible with the new exporter, without breaking >> Worg in the process? > > No. Someone needs to carefully check he can exports his local clone > of worg.git with the new exporter, fix the wrong syntax, then commit > it. This surely deserves a public branch of Worg, which people can > hack together. Thanks Bastien, I was about to write about this. We need a volunteer who is willing to coordinate the conversion of Worg to the new exporter. This is an important task. Dogfooding Worg to the new exporter will be a good way to find remaining bugs in the parser/exporter setup. This task would entail: 1. Creating a public branch of Worg for this work. 2. Creating and maintaining a file that contains a site map of Worg, with all files that need publishing 3. Organizing contributors who will look at one page after the other and implementing any changes needed to make the page export (not yet publish) cleanly with the new exporter. In this way we need to walk through all Worg files, and someone needs to keep the tabs on this. 4. When all this is done, see what changes have to be made to the publishing setup to fix the automatic publishing. Any takers? Once we are done with this, we also need the orgmode.org website, but that contains fewer pages, so it should be a lot simpler. - Carsten