Re: Release 8.0

[Carsten Dominik <carsten.dominik@gmail.com>]

On 22.4.2013, at 19:17, Bastien <bzg@gnu.org> wrote:

> Hi Jay,
> 
> Jay Kerns <gjkernsysu@gmail.com> writes:
> 
>> On Sun, Apr 21, 2013 at 9:25 AM, Bastien <bzg@gnu.org> wrote:
>>> Hi Memnon,
>>> 
>>> Memnon Anon <gegendosenfleisch@googlemail.com> 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