[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[O] FW: How to deal with small projects which are often changing their s
From: |
M |
Subject: |
[O] FW: How to deal with small projects which are often changing their status/ person |
Date: |
Tue, 22 Jan 2013 23:27:56 +0100 |
User-agent: |
Microsoft-Entourage/11.4.0.080122 |
> Von: M <address@hidden>
> Datum: Tue, 22 Jan 2013 23:22:59 +0100
> An: Thorsten Jolitz <address@hidden>
> 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 <address@hidden>
>> Datum: Tue, 22 Jan 2013 22:55:15 +0100
>> An: <address@hidden>
>> Betreff: Re: [O] How to deal with small projects which are often changing
>> their status/ person
>>
>> M <address@hidden> 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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [O] FW: How to deal with small projects which are often changing their status/ person,
M <=