From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Release 8.0
Date: Mon, 22 Apr 2013 22:17:56 +0200 [thread overview]
Message-ID: <87sj2ijp57.fsf@gmail.com> (raw)
In-Reply-To: CA+M2ft_ODyupxB+c4tgnHKjMReGLA1Szt9ZcnvkvDCvD3XB0sA@mail.gmail.com
John Hendy <jw.hendy@gmail.com> writes:
>>> 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.
>> 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:
[...]
>> 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.
>
> Not sure we totally need to organize this. I'm wondering about
> something like an "editor" property in the file from #2. Contributors
> could self-assign by adding their name to that property in the tracker
> file and then push. Perhaps an agenda view or simply column view could
> quickly show who is assigned to what file?
>> Any takers?
I don't know if this would put a huge work load on somebody who
contributed *much* content to Worg, but otherwise I would propose for
this step that all authors of Worg articles/pages take care of their own
pages. In my case that would be e.g. half a dozen of pages, not that
much of a problem.
Once most Worg authors have fixed their own pages, another round of
fixing the (few?) remaining pages by some volunteers could be started.
Just my 2cents
--
cheers,
Thorsten
prev parent reply other threads:[~2013-04-22 20:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 16:41 Release 8.0 Bastien
2013-04-18 16:58 ` Jambunathan K
2013-04-18 17:37 ` Bastien
2013-04-18 18:06 ` Jambunathan K
2013-04-18 17:15 ` Anthony Lander
2013-04-18 17:28 ` Appeal to donors (Re: Release 8.0) Jambunathan K
2013-04-19 15:42 ` OAppeal " Wes Hardaker
2013-04-19 16:38 ` Russell Adams
2013-04-18 17:41 ` Release 8.0 Neuwirth Erich
2013-04-18 18:01 ` Achim Gratz
2013-05-09 7:55 ` Neuwirth Erich
2013-04-18 17:43 ` François Pinard
2013-04-18 17:57 ` Glyn Millington
2013-04-18 18:24 ` Jambunathan K
2013-04-18 18:00 ` John Hendy
2013-04-18 18:10 ` Aaron Ecay
2013-04-18 18:18 ` Jambunathan K
2013-04-18 18:22 ` Bastien
2013-04-18 19:09 ` Jambunathan K
2013-04-18 19:16 ` Jambunathan K
2013-04-18 19:28 ` Billy O'Connor
2013-04-18 19:50 ` Jambunathan K
2013-04-18 20:15 ` Bastien
2013-04-18 20:20 ` Glyn Millington
2013-04-18 18:17 ` Rasmus
2013-04-18 19:28 ` Samuel Wales
2013-04-18 22:05 ` Carsten Dominik
2013-04-19 4:53 ` Brian van den Broek
2013-04-20 8:15 ` Xiao-Yong Jin
2013-04-19 0:20 ` Bernt Hansen
2013-04-19 6:58 ` Christian Moe
2013-04-19 8:02 ` Stefan Vollmar
2013-04-21 12:07 ` Memnon Anon
2013-04-21 13:25 ` Bastien
2013-04-22 16:56 ` Jay Kerns
2013-04-22 17:17 ` Bastien
2013-04-22 18:32 ` Carsten Dominik
2013-04-22 19:46 ` John Hendy
2013-04-22 20:06 ` Carsten Dominik
2013-04-22 20:17 ` Thorsten Jolitz [this message]
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=87sj2ijp57.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).