From: Thorsten Jolitz <tjolitz@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: How to deal with small projects which are often changing their status/ person
Date: Tue, 22 Jan 2013 22:55:15 +0100 [thread overview]
Message-ID: <87622oanng.fsf@googlemail.com> (raw)
In-Reply-To: CD24C5DD.13D11%Elwood151@web.de
M <Elwood151@web.de> writes:
> it is not about programming and it is not about plain text files, but MS
> Office (Word) files..
>
> Dropbox is not an option, maybe a document management system (DMS) with
> versioning, but it is not in place yet.
> And even if there is, how could I then track my workflow with Emacs?
Maybe I shouldn't say this on this list, but this actually sounds to me
like a perfect use case for Google Docs, which is very similar to Word,
can import and export to Word (or simply replace it if the Docs are not
too complex), and is very well suited for collaborative work on the same
documents with automatic backup in the clouds and versioning.
I think its all about avoiding to work locally on different copies of a
document and then send it back and forth by email. Thats just too
old-school in my eyes.
--
cheers,
Thorsten
next prev parent reply other threads:[~2013-01-22 21:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 20:19 How to deal with small projects which are often changing their status/ person M
2013-01-22 21:14 ` Thorsten Jolitz
2013-01-22 21:39 ` Nicolas Richard
2013-01-22 21:56 ` Thorsten Jolitz
2013-01-22 21:40 ` M
2013-01-22 21:55 ` Thorsten Jolitz [this message]
2013-01-23 8:59 ` Tomas Hlavaty
2013-01-23 10:20 ` OT: using ZIP based files with git (was: How to deal with small projects which are often changing their status/ person) Karl Voit
2013-01-22 21:39 ` How to deal with small projects which are often changing their status/ person Thomas S. Dye
2013-01-22 22:27 ` M
2013-01-22 22:49 ` Thomas S. Dye
2013-01-23 1:59 ` Eric Abrahamsen
2013-01-23 9:15 ` Julian Burgos
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=87622oanng.fsf@googlemail.com \
--to=tjolitz@googlemail.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).