Re: Updating Worg: call to Worg authors

[Suvayu Ali <fatkasuvayu+linux@gmail.com>]

Hi Bastien,

On Wed, Apr 24, 2013 at 09:44:32AM +0200, Bastien wrote:
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> 
> > I'm not clear about the workflow.  Why is there a need for a separate
> > branch?  I thought there was already a consensus to document the new
> > exporter under exporters/ox-<backend>.org or exporters/<exporter>/*.org
> > depending on whether a single file is sufficient or a directory is
> > needed for examples and other stuff.  How does this new plan go with the
> > above, do I make changes in this new branch, or do I keep working on
> > master?
> 
> There are two different things:
> 
> - the exporters/ directory in Worg is for documenting how the new
>   export engine and each exporter work
> 
> - the new public branch is for updating Worg's pages so that the new
>   exporter can publish them correctly (e.g., change the syntax of the
>   #+attr_html lines, etc.)
> 
> For adding new content to Worg (and for adding documentation to
> exporters/), just use Worg's master branch, as usual.
> 
> For fixing the syntax of existing pages, go on the dedicated branch
> and do the fixes.  We will merge this branch into master when it
> publishes fine with Org 8.0.

That clears it up :).

Thanks,

-- 
Suvayu

Open source is the future. It sets us free.