From: Stefan Kamphausen <skampi@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: org mode vs basecamp
Date: Wed, 24 Oct 2007 09:27:13 +0200 [thread overview]
Message-ID: <854pghdlbi.fsf@usenet.my.skamphausen.de> (raw)
In-Reply-To: <877ild4v1s.fsf@bzg.ath.cx> (Bastien's message of "Tue, 23 Oct 2007 18:09:35 +0100")
Hi,
Bastien <bzg@altern.org> writes:
> But I guess the important side of your question is: can I use Org as a
> *collaboration* tool?
>
> Well -- please do :)
>
> 1. One idea is to put an Org file on a CVS server, letting people check
> it in and out, so that everybody knows what he has to-do and what is
> the state of the project.
>
> 2. Another idea is to give someone the responsability to maintain an Org
> file dispatching to-do list items through the team, displaying clear
> deadlines, tasks status, etc.
>
> 3. The third idea is to let a web interface directly operate changes on
> underlying Org files. I think this is achievable: Org files are text,
> but with a reasonable set of conventions to format them we could edit
> them through another tool.
>
in my mind lives another idea which is close to your #3: use a wiki as
a backend (currently I'm thinking about oddmuse).
- Write an extension to oddmuse which displays org-syntax as HTML.
Has to be written in Perl, probably could reuse lots of regexps from
org.el. A really fancy extension would render checkboxes and the
like, but I don't know whether this is achievable.
- Instead of find-file and save-buffer one could use oddmuse-edit and
oddmuse-post from [1].
- Setup auto-mode-alist to set org-mode when opening such a wikipage,
or put a -*-modeline into the wikipages
One of the benefits is that the other collaborateurs would not have to
use emacs (which they don't in my case), they would "just" have to
write the correct wiki-syntax. Publishing, history, user-tracking,
remote-access, etc. all comes for free.
I'll try to find some time during the next weeks to start with the
oddmuse-extension, but I can't see when that will happen. It has to
fill the time-slots when they come up ;-)
Kind Regards
Stefan
Footnotes:
[1] http://www.emacswiki.org/cgi-bin/wiki/OddmuseMode
--
Stefan Kamphausen --- http://www.skamphausen.de
a blessed +42 regexp of confusion (weapon in hand)
You hit. The format string crumbles and turns to dust.
next prev parent reply other threads:[~2007-10-24 7:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 9:17 org mode vs basecamp cezar
2007-10-23 17:09 ` Bastien
2007-10-23 18:43 ` cezar
2007-10-23 20:21 ` Bastien
2007-10-24 9:06 ` cezar
2007-10-24 10:26 ` Bastien
2007-10-24 10:52 ` cezar
2007-10-24 12:05 ` Bastien
2007-10-24 7:27 ` Stefan Kamphausen [this message]
2007-10-24 9:43 ` Bastien
2007-10-24 8:58 ` Stefan Kamphausen
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=854pghdlbi.fsf@usenet.my.skamphausen.de \
--to=skampi@gmx.net \
--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).