From mboxrd@z Thu Jan  1 00:00:00 1970
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Subject: Re: Updating Worg: call to Worg authors
Date: Wed, 24 Apr 2013 09:52:14 +0200
Message-ID: <20130424075214.GD28898@kuru.dyndns-at-home.com>
References: <CAFiLVrZWAaT-U1coA-3_UjhTMHrYQ5OsO-eCC=MTVaD9ZK1K7w@mail.gmail.com>
	<20130424072512.GB28898@kuru.dyndns-at-home.com>
	<878v484bkv.fsf@bzg.ath.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:60626)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <fatkasuvayu+linux@gmail.com>) id 1UUuV5-0004A8-Pl
	for emacs-orgmode@gnu.org; Wed, 24 Apr 2013 03:52:24 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <fatkasuvayu+linux@gmail.com>) id 1UUuV3-0001CS-Oe
	for emacs-orgmode@gnu.org; Wed, 24 Apr 2013 03:52:23 -0400
Content-Disposition: inline
In-Reply-To: <878v484bkv.fsf@bzg.ath.cx>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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 <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org

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.