emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Spiers <orgmode@adamspiers.org>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: using org for meeting agendas and minutes?
Date: Sat, 9 Feb 2008 12:56:07 +0000	[thread overview]
Message-ID: <20080209125607.GC20023@atlantic.linksys.moosehall> (raw)

I "accidentally" became secretary of my resident's association
committee recently, so I'm now producing meeting agendas and minutes
more often than before (sometimes it happens at work too).  So I
thought I'd poll the enormous collective wisdom of this group and see
if we could establish some kind of best practice around using org for
this task.  It could even become a Worg article ;-)

These are the goals as I see them:

  (1) Allow *fast* production of meeting agendas and minutes,
      exportable in a good-looking legible format which non-org
      readers can digest.

  (2) Allow minutes to be taken as the meeting progresses, minimising
      the amount of work required after the meeting.

  (3) Allow actions to be captured and then automatically extracted
      into a simple tabulated report which clearly shows actions
      grouped by owner.

  (4) Track progress of actions *after* the minutes have been issued.

  (5) (Up for debate) Allow minutes to be embedded within a previous
      agenda, easily demarcating between agenda items and minute
      items.  This encourages the meeting to follow its intended
      structure, and clearly documents unplanned deviations from the
      agenda (for better or worse), e.g. via colour coding.

I think it's pretty obvious that org already enables (1) and (2)
admirably, and of course I'm already beginning to use it in this
manner.  But I'm slightly struggling with the others.

For (3) and (4), my current thinking is to have workflow defined by
TODO keywords, e.g. 

  #+SEQ_TODO: ACTION WAITING | DONE

and to have action ownership defined via tags, e.g.

  #+TAGS: { Alice(a) Bob(b) Carys(c) }

Then a dynamic columnview block at the end of the file could easily
extract all actions and summarise them so that each owner of action(s)
can easily see them.  This is where sorting of rows in column view
would be really useful!

For (5) I'm really not sure how to achieve the demarcation.  Maybe
it's best when beginning to take minutes simply to copy the agenda to
a new file and start embedding minutes within that.  Then a diff of
agenda.org and minutes.org shows any deviations etc.?  This would also
preserve the original agenda by protecting it against accidental
editing.

Any thoughts on this or other ideas very welcome!

Thanks,
Adam

             reply	other threads:[~2008-02-09 12:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09 12:56 Adam Spiers [this message]
2008-02-11 13:34 ` using org for meeting agendas and minutes? Adam Spiers
2008-02-11 16:55   ` Eric Schulte
     [not found] ` <15369.1203180295@localhost>
2008-02-17 17:24   ` Adam Spiers
2008-02-18 11:19     ` Carsten Dominik
2008-02-18 11:47       ` Adam Spiers
2008-02-19  4:23         ` Bastien
2008-02-19  9:46           ` Carsten Dominik
2008-02-22 14:39     ` Carsten Dominik

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=20080209125607.GC20023@atlantic.linksys.moosehall \
    --to=orgmode@adamspiers.org \
    --cc=emacs-orgmode@gnu.org \
    /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).