From: M <Elwood151@web.de>
To: Thorsten Jolitz <tjolitz@googlemail.com>, 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:40:29 +0100 [thread overview]
Message-ID: <CD24C5DD.13D11%Elwood151@web.de> (raw)
In-Reply-To: <87a9s0apj1.fsf@googlemail.com>
Thanks Thorsten for your reply!
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?
Kind regards
Martin
> Von: Thorsten Jolitz <tjolitz@googlemail.com>
> Datum: Tue, 22 Jan 2013 22:14:42 +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:
>
> Hi,
>
>> At the moment there are many little projects where I
>>
>> * get a text from someone (or write it myself)
>> * have to read and edit it
>> * send it oer email to 1 or 2 other colleagues which have to read / edit it
>> * get it back and check the changes
>> * maybe send the text again to the original author
>> * then finally release the text for publication
>>
>> ... and you imagine, there is not only 1 such text at once but several of
>> them.
>>
>> I wonder what is an approriate way to keep track of such workflows with
>> org-mode..
>
> this doesn't sound so different from several programmers working on the
> same source code file, so I suspect that GIT is the best and the most
> popular solution for collaborative work on plain text files.
>
> If you/your fellow workers don't use GIT or another VCS, there is still
> dropbox - put your project text files in your dropbox folder and share
> them with other, there are automatic backups of older versions by
> Dropbox.
>
> Or you wait for colorg to be released, that would probably fit your
> needs exactly
>
> --
> cheers,
> Thorsten
>
>
next prev parent reply other threads:[~2013-01-22 21:40 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 [this message]
2013-01-22 21:55 ` Thorsten Jolitz
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=CD24C5DD.13D11%Elwood151@web.de \
--to=elwood151@web.de \
--cc=emacs-orgmode@gnu.org \
--cc=tjolitz@googlemail.com \
/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).