Thorsten Jolitz writes:
> A kind of team agende would indeed be useful, accessible form Org-mode
> _and_ other calendar/planning tools (I can't imagine a pure
> Emacs/Org-mode team).
Why not?
> I remember an attempt to make Org-mode a collaborative software (ColOrg
> or so) - whats the state of
Sebastien Vauban writes:
> Samuel Loury wrote:
>> Sebastien Vauban writes:
> For example, IIUC, different users will share one file with tasks, where they
> will clock in/out. Then, what about the SCHEDULED and DEADLINE properties?
> Will the tasks be in all the user agendas? Not acceptable. The
"Sebastien Vauban"
writes:
> Don't misunderstand me. I'm not trying to convince you or anybody to stop and
> cry. On the contrary, I feel that some such possibilities are _needed_ to
> transform Org from a "personal organizer" to a "team organizer".
A kind of team agende would indeed be useful,
Samuel Loury wrote:
> Sebastien Vauban writes:
>
>> Having thought about that in the past, I had thought of adding "tags" after
>> clock lines, such as:
>>
>> --8<---cut here---start->8---
>> CLOCK: [2013-09-05 Thu 07:55]--[2013-09-05 Thu 08:46] => 0:51 :u
Sebastien Vauban writes:
> Having thought about that in the past, I had thought of adding "tags" after
> clock lines, such as:
>
> --8<---cut here---start->8---
> CLOCK: [2013-09-05 Thu 07:55]--[2013-09-05 Thu 08:46] => 0:51 :userA:
> CLOCK: [2013-09-
Samuel Loury wrote:
> I recently encountered the issues of having to collaborate with other
> persons on the same task (all of us would need at some point to clock
> into this task).
>
> I thought that changing the value of the variable org-clock-string could
> help, but I have not tried it yet. Le
Hi,
Richard Lawrence writes:
> Hi Gareth,
>
> Gareth Smith writes:
>
>> I hadn't thought of using :tags on a clock table. I still worry if we'll
>> find ourselves in a situation where more than one of us has clocked in
>> some time on the same task.
>
> Yes, I agree this might not be optimal, fo
Hi Richard,
Thanks for those suggestions - they're definitely helpful. I'll have a
bit more of a think, and if I come up with a "more optimal" idea, I'll
post again.
Cheers,
Gareth.
Richard Lawrence writes:
> Hi Gareth,
>
> Gareth Smith writes:
>
>> I hadn't thought of using :tags on a clock
Hi Gareth,
Gareth Smith writes:
> I hadn't thought of using :tags on a clock table. I still worry if we'll
> find ourselves in a situation where more than one of us has clocked in
> some time on the same task.
Yes, I agree this might not be optimal, for that case in particular.
One nice thing a
Thanks for the reply Richard!
Richard Lawrence writes:
> Is there a reason you don't want any clock data to end up in the shared
> tasks.org?
>
> If not, one thing you could do is:
>
> 1) When claiming a task, each person uses a tag for their name (in
> addition to, or instead of, just changing
Hi Gareth,
Gareth Smith writes:
> Does anyone use org to collaborate on task lists? It seems to me that it
> would be very natural to put a tasks.org file into a VCS repo, claim a
> task by changing its status from TODO to IN_PROGRESS (and committing
> that change), work, then mark as DONE at th
Hi all,
Does anyone use org to collaborate on task lists? It seems to me that it
would be very natural to put a tasks.org file into a VCS repo, claim a
task by changing its status from TODO to IN_PROGRESS (and committing
that change), work, then mark as DONE at the end.
That's all awesome - but
12 matches
Mail list logo
