From: Jean Louis <bugs@gnu.support>
To: daniela-spit@gmx.it
Cc: Tim Cross <theophilusx@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Adding Org Files to org-agenda-files
Date: Sun, 29 Nov 2020 09:50:34 +0300 [thread overview]
Message-ID: <X8NEup1FaWEpA9ag@protected.rcdrun.com> (raw)
In-Reply-To: <trinity-c91003a6-41e0-4f09-9e5f-5832bb9c3d5e-1606622703908@3c-app-mailcom-bs11>
* daniela-spit@gmx.it <daniela-spit@gmx.it> [2020-11-29 07:06]:
> That looks adequate at first, but what if you want the history for a project
> and gaant charts on how time was spent. I mainly want it to figure out
> if jobs are worth stopping or changing.
Here are some references:
https://orgmode.org/worg/org-tutorials/org-taskjuggler.html
https://github.com/swillner/org-gantt/blob/master/org-gantt-manual.org
https://github.com/swillner/org-gantt
For me, tracking of how time was spent is out of use. I am tracking
products or services delivered, something valuable produced and
real. As value is what I need. Time is environment where values are
produced and does not necessarily speak of values.
** TODO Project has several tasks which I keep rather in lists [0/3] [0%]
:PROPERTIES:
:ASSIGNED: James
:END:
1) [ ] Purchase X equipment at ABC store.
2) [ ] bring X equipment to location XYZ and introduce yourself to technician
3) [ ] give the technical drawing to technician
Now if person assigned to do those tasks does not purchase equipment,
I would not like spending my time analyzing where the time went
because neither there is no value from not doing it, neither from me
analyzing. If tasks are in logical order then I know where the person
is stuck and we have both agreement as we know what is NEXT to be done
as tasks are numbered and even if not numbered they can be in
chronological order.
Count values, not time.
Jean
next prev parent reply other threads:[~2020-11-29 6:52 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 15:39 Adding Org Files to org-agenda-files daniela-spit
2020-11-28 16:51 ` Jeremie Juste
2020-11-28 16:54 ` daniela-spit
2020-11-28 17:01 ` daniela-spit
2020-11-28 17:41 ` Jeremie Juste
2020-11-28 18:12 ` daniela-spit
2020-11-28 18:30 ` daniela-spit
2020-11-28 18:43 ` daniela-spit
2020-11-28 19:01 ` Jeremie Juste
2020-11-28 19:16 ` daniela-spit
2020-11-28 19:26 ` Detlef Steuer
2020-11-28 19:44 ` daniela-spit
2020-11-28 19:55 ` Jeremie Juste
2020-11-28 20:06 ` daniela-spit
2020-11-28 20:11 ` daniela-spit
2020-11-28 20:27 ` Jeremie Juste
2020-11-28 20:40 ` daniela-spit
2020-11-28 21:32 ` Jeremie Juste
2020-11-28 21:45 ` daniela-spit
2020-11-28 23:18 ` Jeremie Juste
2020-11-28 23:29 ` daniela-spit
2020-11-29 1:36 ` Tim Cross
2020-11-29 2:54 ` daniela-spit
2020-11-29 3:51 ` Tim Cross
2020-11-29 4:05 ` daniela-spit
2020-11-29 5:23 ` Tim Cross
2020-11-29 9:30 ` Jean Louis
2020-11-29 6:50 ` Jean Louis [this message]
2020-11-29 6:41 ` Jean Louis
2020-11-29 12:28 ` Ihor Radchenko
2020-11-29 13:00 ` Tim Cross
2020-11-29 17:11 ` Jean Louis
2020-11-29 17:05 ` Jean Louis
2020-12-01 2:24 ` Ihor Radchenko
2020-12-01 8:59 ` Jean Louis
2020-12-13 15:36 ` Ihor Radchenko
2020-12-13 16:27 ` steve-humphreys
2020-12-25 2:17 ` Ihor Radchenko
2020-12-13 20:21 ` Jean Louis
2020-12-13 20:59 ` Tim Cross
2020-12-13 21:59 ` pietru
2020-12-13 23:28 ` Jean Louis
2020-11-29 4:46 ` Jean Louis
2020-11-29 14:46 ` daniela-spit
2020-11-29 17:01 ` Tim Cross
2020-11-29 17:38 ` daniela-spit
2020-11-29 20:55 ` Jeremie Juste
2020-11-30 0:21 ` Tim Cross
2020-11-28 23:36 ` daniela-spit
2020-11-29 5:51 ` Jean Louis
2020-11-28 20:28 ` daniela-spit
2020-11-28 18:50 ` daniela-spit
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=X8NEup1FaWEpA9ag@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=daniela-spit@gmx.it \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@gmail.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).