emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Updating Worg: call to Worg authors
Date: Wed, 24 Apr 2013 09:25:12 +0200	[thread overview]
Message-ID: <20130424072512.GB28898@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <CAFiLVrZWAaT-U1coA-3_UjhTMHrYQ5OsO-eCC=MTVaD9ZK1K7w@mail.gmail.com>

On Tue, Apr 23, 2013 at 04:57:20PM -0400, Jay Kerns wrote:


> - Please checkout the worg-new-exporter branch and update those files
>   which are yours.
> - Please mark DONE or INPROGRESS files in worgmap.org.
> - If you cannot or are not able to update your files, please say so on
>   the mailing list so other volunteers can update them instead.
>   Alternatively, you can mark your files as ABANDONED in worgmap.org.

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



Open source is the future. It sets us free.

  reply	other threads:[~2013-04-24  7:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 20:57 Updating Worg: call to Worg authors Jay Kerns
2013-04-24  7:25 ` Suvayu Ali [this message]
2013-04-24  7:44   ` Bastien
2013-04-24  7:52     ` Suvayu Ali
2013-04-24  7:53 ` Carsten Dominik
2013-04-24  9:25 ` Thorsten Jolitz
2013-04-25 23:18   ` Jay Kerns
2013-04-25 23:26     ` Jay Kerns

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130424072512.GB28898@kuru.dyndns-at-home.com \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).