Re: org-mode as an accountability system?

[Jude DaShiell <jdashiel@shellworld.net>]

Rather than "did not do" perhaps "pending" might be a little shorter. On 
Sat, 3 Mar 2012, John Hendy wrote:

> On Sat, Mar 3, 2012 at 1:18 PM, Peter Salazar <cycleofsong@gmail.com> wrote:
> > Hi Thorsten,
> >
> > Thanks for the thoughts.
> >
> > Clarification: I send my accountability partner a summary of MY committed
> > actions for the day for him to review. We dont' collaborate, and he does not
> > touch or change my tasks. (Although he does send me a list of his own tasks,
> > and how well he did each day.)
> >
> 
> He doesn't have to change them, just be able to view the up to date
> state of your todos. I think that was the point. =git pull= is not
> significantly more work than opening an email.
> 
> > It's important to send the tasks by e-mail so I know he'll see them right
> > away (and that will keep me accountable). If I send him a link, I know he
> > may or may not view the file if and when he has time.
> >
> 
> Whether he opens his browser/email client and reads the email or opens
> a terminal and does =git pull=, again, does not seem horridly
> different. Then again, for a non git user, you are correct that one
> more step might make the difference between reading and not.
> 
> > As for using Agenda and hitting > to move a task to the next day, there are
> > two problems with this:
> >
> > 1. this does not change the state of a @didnotdo task to @todo
> 
> Have a look at: http://orgmode.org/manual/Agenda-commands.html
> 
> I, too, am not a power user, however it seems like you could do the following:
> -- `C-a t` (show all todos)
> -- `m` on each one you did not complete
> -- `B` (shift+b, conduct bulk action on all marked entries)
> -- `t` to change todo state for each marked item
> -- Type in 'didnotdo' to change the state
> -- `C-a T` (agenda search based on todo state)
> -- Type in 'didnotdo' (gives you all the items you just marked since
> you didn't do them)
> -- Copy the current agenda view into an email and send it
> ---- Alternative do `C-x C-w` and write it to a file you can push to a git repo
> -- `m` on all the shown entries (all are state `didnotdo` at this point)
> -- `B` (conduct a bulk action)
> -- `s` (schedule new date for all actions)
> -- Use the minibuffer calendar to schedule them to a new day
> 
> Looks like a lot, but this should go pretty fast once you get the hang of it.
> 
> Also, Bernt Hanson has a diddy on his website for creating a timestamp
> for every new headline. Perhaps you could use it to create a timestamp
> with today's date for every new todo headline? See his elisp code
> here:
> -- http://doc.norang.ca/org-mode.html#sec-15-21
> 
> > 2. for habits (using the format SCHEDULED: <2012-03-03 Sat  +1d>), if I miss
> > a day and then try to mark a habit DONE today, it stamps the habit done for
> > the day I missed, rather than stamping it done today and recording that I
> > did not do it on the day I was supposed to do it.
> >
> 
> I don't use habit, but I know there's a graph that's supposed to show
> color coded bars based on whether you did or did not do the task
> according to how you scheduled the habit.
> -- http://orgmode.org/manual/Tracking-your-habits.html
> 
> Hope this gives you some ideas or even helps you directly!
> 
> 
> John
> 
> >
> > On Sat, Mar 3, 2012 at 1:56 PM, Thorsten <quintfall@googlemail.com> wrote:
> >>
> >> Peter Salazar <cycleofsong@gmail.com> writes:
> >>
> >> Hi Peter,
> >> without claiming being an expert org-mode user, I had the following
> >> thoughts when reading your post:
> >>
> >> > I have an accountability partner with whom I exchange daily "committed
> >> > actions." Every morning, I e-mail him a list of the tasks I commit to
> >> > completing that day.
> >>
> >> Why sending per email? Why not getting a free private(!) git repo (1GB)
> >> at assembla.com and cooperatively work on one or several org file(s) in
> >> that repo?
> >>
> >> > When I complete a task, I mark it DONE. If I don't complete a task
> >> > that day, I mark it @didnotdo and manually cut and paste it to the
> >> > next day.
> >> >
> >> > Every night, I send him a report of which actions I did and which ones
> >> > I did not do. (I find I get so much more done since I started making
> >> > daily commitments to someone other than myself.)
> >>
> >> If you both work on the same file using git, the current state of
> >> affairs will always be clear, as well as who did what at what time (and
> >> pushed it to the repo).
> >>
> >> > 1. Given that I'm creating my daily task list manually, is there an
> >> > easy way, when I mark a task @didnotdo, to automatically move it to
> >> > the next day's list and change its state to @todo?
> >>
> >> When I have a TODO task in the agenda that I did not complete today, I
> >> just change the date to tomorrow in the agenda using '>'.
> >> If you don't do that, it will appear anyway in the agenda as overdue
> >> task.
> >>
> >>
> >> --
> >> cheers,
> >> Thorsten
> >>
> >>
> >
> 
> 

----------------------------------------------------------------
Jude <jdashiel-at-shellworld-dot-net>
<http://www.shellworld.net/~jdashiel/nj.html>