From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thorsten Jolitz Subject: Re: Release 8.0 Date: Mon, 22 Apr 2013 22:17:56 +0200 Message-ID: <87sj2ijp57.fsf@gmail.com> 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 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:40334) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUNBp-0000Co-8U for emacs-orgmode@gnu.org; Mon, 22 Apr 2013 16:18:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UUNBo-0005Tu-5E for emacs-orgmode@gnu.org; Mon, 22 Apr 2013 16:18:17 -0400 Received: from plane.gmane.org ([80.91.229.3]:53326) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UUNBn-0005Tq-UT for emacs-orgmode@gnu.org; Mon, 22 Apr 2013 16:18:16 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UUNBh-0006Ha-Gq for emacs-orgmode@gnu.org; Mon, 22 Apr 2013 22:18:09 +0200 Received: from e178189220.adsl.alicedsl.de ([85.178.189.220]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 22 Apr 2013 22:18:09 +0200 Received: from tjolitz by e178189220.adsl.alicedsl.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 22 Apr 2013 22:18:09 +0200 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 John Hendy writes: >>> 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. >> 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: [...] >> 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. > > Not sure we totally need to organize this. I'm wondering about > something like an "editor" property in the file from #2. Contributors > could self-assign by adding their name to that property in the tracker > file and then push. Perhaps an agenda view or simply column view could > quickly show who is assigned to what file? >> Any takers? I don't know if this would put a huge work load on somebody who contributed *much* content to Worg, but otherwise I would propose for this step that all authors of Worg articles/pages take care of their own pages. In my case that would be e.g. half a dozen of pages, not that much of a problem. Once most Worg authors have fixed their own pages, another round of fixing the (few?) remaining pages by some volunteers could be started. Just my 2cents -- cheers, Thorsten