emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: M <Elwood151@web.de>
To: emacs orgmode-mailinglist <emacs-orgmode@gnu.org>
Subject: FW: How to deal with small projects which are often changing their status/ person
Date: Tue, 22 Jan 2013 23:27:56 +0100	[thread overview]
Message-ID: <CD24D0FC.13D26%Elwood151@web.de> (raw)
In-Reply-To: <CD24CFD3.13D23%Elwood151@web.de>

> Von: M <Elwood151@web.de>
> Datum: Tue, 22 Jan 2013 23:22:59 +0100
> An: Thorsten Jolitz <tjolitz@googlemail.com>
> Unterhaltung: [O] How to deal with small projects which are often changing
> their status/ person
> Betreff: Re: [O] How to deal with small projects which are often changing
> their status/ person
> 
> I agree, that sending edited documents by e-mail is not the best available
> approach.
> 
> Using Google Docs for partly confidential information concerning products of a
> company is a no-go in my opinion (same for dropbox etc.)
> 
> Maybe you misunderstood my initial question:
> it is not about a tool to keep track of changes to the documents, but a way to
> keep track of the project in MY todo-lists managed by org-mode.
> 
> Some ideas I had in the meantime:
> - creating templates for such projects which already contain the "standard"
> sub-tasks.
> 
> 
> 
> 
>> Von: Thorsten Jolitz <tjolitz@googlemail.com>
>> Datum: Tue, 22 Jan 2013 22:55:15 +0100
>> An: <emacs-orgmode@gnu.org>
>> Betreff: Re: [O] How to deal with small projects which are often changing
>> their status/ person
>> 
>> 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
>> 
>> 

------ Ende der weitergeleiteten Nachricht

           reply	other threads:[~2013-01-22 22:28 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CD24CFD3.13D23%Elwood151@web.de>]

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=CD24D0FC.13D26%Elwood151@web.de \
    --to=elwood151@web.de \
    --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).