From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: org-annotate/collaboration?
Date: Tue, 14 Feb 2017 21:44:16 +0000 [thread overview]
Message-ID: <87fujgcurz.fsf@mat.ucm.es> (raw)
In-Reply-To: 87tw7xbkot.fsf@ericabrahamsen.net
> Uwe Brauer <oub@mat.ucm.es> writes:
> I think collaborators who have even a tiny familiarity with
> technological tools make the whole process much, much easier.
> Unfortunately I'm working with technophobes, the sort of people who
> call the browser "the internet", so I have almost no wiggle room at
> all...
One of the annoying thing in collaboration is to use email that is why a
server client model is more convenient.
Hm, my collaborator is neither technical skilled but willing to use the
command line, and he writes in latex anyway which requires some
understanding your folks seem not to have.
Another option you could use is LyX (and therefore latex of some sort).
LyX has a tracker of changes similar to the one provided by OpenOffice
and friends. It also supports some version control system (forgot the
details).
But then again that might all be too technical, shrug
next prev parent reply other threads:[~2017-02-14 21:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 1:10 org-annotate/collaboration? Matt Price
2017-02-09 5:21 ` org-annotate/collaboration? Eric Abrahamsen
2017-02-09 7:09 ` org-annotate/collaboration? Alan E. Davis
2017-02-09 22:07 ` org-annotate/collaboration? Eric Abrahamsen
2017-02-10 4:43 ` org-annotate/collaboration? Alan E. Davis
2017-02-10 21:19 ` org-annotate/collaboration? Cook, Malcolm
2017-02-10 22:59 ` org-annotate/collaboration? Alan E. Davis
2017-02-11 18:07 ` org-annotate/collaboration? Uwe Brauer
2017-02-14 1:55 ` org-annotate/collaboration? Eric Abrahamsen
2017-02-14 21:44 ` Uwe Brauer [this message]
2017-02-16 1:45 ` org-annotate/collaboration? Eric Abrahamsen
2017-02-16 18:53 ` org-annotate/collaboration? Uwe Brauer
2017-02-11 22:20 ` org-annotate/collaboration? Eduardo Mercovich
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fujgcurz.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.