emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: org-annotate/collaboration?
Date: Sat, 11 Feb 2017 18:07:33 +0000	[thread overview]
Message-ID: <87mvds1tzu.fsf@mat.ucm.es> (raw)
In-Reply-To: 87wpd02b3s.fsf@ericabrahamsen.net

>>> "Eric" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:

   > Matt Price <moptop99@gmail.com> writes:
   >> Does anyone use org-annotate actively? I'm wondering what your
   >> workflow is, how you incorporate comments, etc.  

   > I wrote it, and I don't use it that much. I do use it for quick
   > notes-to-self when writing, but footnotes do the job just as well.

   >> I'm hoping to embark on a book project with a colleague. I would like
   >> to use org-mode if I can, but I need to get a sense of the
   >> collaboration workflow. When you work on projects together, do you use
   >> annotations? Or git pull requests? If the latter, od you use any
   >> filters, or any magit tricks, to approve or modify suggested changes
   >> chunk by chunk?  

   > It's a huge problem, and one that org-annotate isn't going to solve. I
   > do a lot of manuscript editing, and passing files around, and have only
   > barely gotten some people to accept my "weird" workflow, which is to
   > send them a clean version of an edited file, and along with that an HTML
   > file containing htmlized word-diff output, where the insertions and
   > deletions are colorized. They make further edits on the clean copy, and
   > I do another go-around. It's a huge pain.

I did (and still do) the same, using latex and latexdiff, but found out
that a better solution is to use mercurial and bitbucket (I presume git
should be fine as well), since one of my collaborators agree to use it
as well. This is quite a relief to the former method relying on external
tools and email.  

    -  Usually instead of comments I use issuesin bitbucket.
    -  hg diff is not perfect but a good first approximation.

  parent reply	other threads:[~2017-02-11 18:07 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   ` Uwe Brauer [this message]
2017-02-14  1:55     ` org-annotate/collaboration? Eric Abrahamsen
2017-02-14 21:44       ` org-annotate/collaboration? Uwe Brauer
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

  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=87mvds1tzu.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 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).