emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Jay Kerns <gjkernsysu@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Updating Worg: call to Worg authors
Date: Wed, 24 Apr 2013 09:53:10 +0200	[thread overview]
Message-ID: <1F6A18AD-B971-42CE-A06E-373402CD137C@gmail.com> (raw)
In-Reply-To: <CAFiLVrZWAaT-U1coA-3_UjhTMHrYQ5OsO-eCC=MTVaD9ZK1K7w@mail.gmail.com>


On 23.4.2013, at 22:57, Jay Kerns <gjkernsysu@gmail.com> wrote:

> Hello there,
> 
> I started some work on this and pushed a worg-new-exporter branch to
> Worg.  I followed Carsten's advice which I will repeat here for
> convenience:




Hi Jay,

thank you and John for getting this started.

- Carsten

> 
> Given an existing Worg repository obtained by
> 
> $ git clone worg@orgmode.org:worg.git
> 
> Everybody else can hook onto this branch with
> 
> $ git checkout --track -b worg-new-exporter origin/worg-new-exporter
> 
> and then work in this branch and push it whenever they want.  Note you
> will need commit access to the worg repository at orgmode.org; see
> here for more info:
> 
> http://orgmode.org/worg/worg-git.html
> 
> After checking out the worg-new-exporter branch you will find a file
> 
> worgmap.org
> 
> in the root of the repository.  This file has headlines for every
> single file/directory on Worg current as of last night some
> time. Worgmap.org has TODO entries so we can keep track of what is
> DONE, what is TODO, what is INPROGRESS, etc. We can also add AUTHOR
> properties, etc, to help the update proceed smoothly.
> 
> 
> CALL TO WORG AUTHORS:
> 
> - 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.
> 
> 
> If you know of ways to streamline this update process, please feel
> free to speak up and/or move forward with it immediately.  There are
> ~700 files on Worg to be checked, so we have a nontrivial job ahead
> of us.
> 
> Thanks to John Hendy for some offlist brainstorming and advice - I
> think worgmap.org is much better as a result.
> 
> 
> -- 
> Jay
> 
> P.S. I did a once-over to mark obvious things like *.png, *.pdf,
> etc. as DONE.  I tried to be sparing to avoid false positives, though
> I could have made some mistakes. Please fix any errors you find.
> 
> P.P.S. I inadvertently deleted a few directory names from the list when
> I first started work.  This should be harmless, but if you notice
> something missing feel free to add it back for completeness.
> 

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 20:57 Jay Kerns
2013-04-24  7:25 ` Suvayu Ali
2013-04-24  7:44   ` Bastien
2013-04-24  7:52     ` Suvayu Ali
2013-04-24  7:53 ` Carsten Dominik [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=1F6A18AD-B971-42CE-A06E-373402CD137C@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=gjkernsysu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).