From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: sharing Org-mode files for collaboration
Date: Sun, 25 Jul 2010 08:38:54 -0600 [thread overview]
Message-ID: <87vd831v9d.fsf@gmail.com> (raw)
In-Reply-To: <87wrskczlb.fsf@mundaneum.com> ("Sébastien Vauban"'s message of "Sat, 24 Jul 2010 23:57:36 +0200")
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
> Hello Carles,
>
>> There have been some threads here about sharing and collaboratively
>> editing Org-mode files. I have a LAN with a central server and Samba
>> shares, all clients have Emacs and Org-mode installed.
>>
>> Sharing of calendars and tasks could be done through Org agenda. Right
>> now I am implementing a very simple setup:
>>
>> - a shared folder with one org file per user
>>
>> - each user has writing permissions for his own file and reading
>> permissions for all other org files
>>
>> - org-agenda-files of each user includes the names of the shared files
>> of the other users
>>
>> Do you see any problems arising from this setup. Any other suggestions
>> how it could be improved or extended?
>
> I have launched such a discussion, about extending the CLOCK times with a
> suffix identifying the user. I have not had that much amount of reaction.
> Maybe, this is not (yet) a main theme, currently.
>
> I find your setup interesting. The only drawback, for me, is that the next
> thing we want is to work on common tasks, meaning we want to clock on common
> tasks. Hence, my topic http://osdir.com/ml/emacs-orgmode-gnu/2010-06/msg00277.html.
>
> Best regards,
> Seb
Hi Carles,
I've also been following the previous collaboration discussions, but
haven't recently had a personal collaboration need.
I would second Sébastien's suggestions of maintaining a single Org-mode
file to be shared by all users, that way each task need only appear
once, and users can share notes, task information etc... in that one
file.
From one previous thread, the following can be used to associate each
user's username with clock in-out information.
--8<---------------cut here---------------start------------->8---
(defun org-clock-out-mark-clock ()
(unless remove (insert (format " (%s)" user-full-name))))
(add-hook 'org-clock-out-hook 'org-clock-out-mark-clock)
--8<---------------cut here---------------end--------------->8---
Also, take a look at the `org-log-note-headings' variable (documentation
included below [1]), which consists of an easily customized format
string, and can be used to associate information (most notably username)
with task state changes.
Summary information (e.g. who's been working on what) could then be
collected using the username tags above in combination with something
like org-collector [2].
I certainly find this area interesting, and I'd be interested to hear
how your collaboration experience plays out.
Best -- Eric
Footnotes:
[1]
,----[org-log-note-headings]
| org-log-note-headings is a variable defined in `org.el'.
| Its value is shown below.
|
| Documentation:
| Headings for notes added to entries.
| The value is an alist, with the car being a symbol indicating the note
| context, and the cdr is the heading to be used. The heading may also be the
| empty string.
| %t in the heading will be replaced by a time stamp.
| %T will be an active time stamp instead the default inactive one
| %s will be replaced by the new TODO state, in double quotes.
| %S will be replaced by the old TODO state, in double quotes.
| %u will be replaced by the user name.
| %U will be replaced by the full user name.
|
| In fact, it is not a good idea to change the `state' entry, because
| agenda log mode depends on the format of these entries.
|
| You can customize this variable.
|
| Value:
| ((done . "CLOSING NOTE %t")
| (state . "State %-12s from %-12S %t")
| (note . "Note taken on %t")
| (reschedule . "Rescheduled from %S on %t")
| (delschedule . "Not scheduled, was %S on %t")
| (redeadline . "New deadline from %S on %t")
| (deldeadline . "Removed deadline, was %S on %t")
| (refile . "Refiled on %t")
| (clock-out . ""))
|
| [back]
`----
[2] http://orgmode.org/worg/org-contrib/org-collector.php
prev parent reply other threads:[~2010-07-25 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 13:32 sharing Org-mode files for collaboration Carles
2010-07-24 21:57 ` Sébastien Vauban
2010-07-25 14:33 ` Carles
2010-07-25 14:38 ` Eric Schulte [this message]
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=87vd831v9d.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).