provide ways for others to participate in the design

i want it clear that i'm willing for others to contribute to and, depending on compatability of vision, steer the design. i'd like for this wiki to embody that dialogue, though it may take some doing to keep clear who said what.

some exist measures already keep that clear. comment-form comments are distinct. (for clearly identified comments, use the "contact" link to ask me for an account, including some clue information about your interest.) likewise, creating new pages (from a comment or an edit) indicates ownership.

for annotations and edits within a page's body text that are not by the page owner, include a personal wiki badge (like Ken Manheimer) with each edit.

continue to develop Risks And Countermeasures

some objections to commercializing something like contactimprov.net makes it apparent that i need to be more clear that i don't want to do that - that neither the local (eg, dc-ci) nor regional (eg, eastcoastjam.com) nor collective (eg, contactimprov.net) presentation of events and resources need cost anything beyond what the resources for that locality incurs. it would just be the infrastructure for distributing notifications that would cost proportional to the scope of distribution - and teasing that out of the relevant Risks And Countermeasures will help resolve the design.

i need to finish synopsizing the risks in the Project Proposal section, as the risks themselves are being ironed out.

incorporate a list of my personal aims

... to illuminate what's important from my perspective (and encourage others to reveal the same), eg:

• local community coordination - eg dc jam

• regional event coordination - eg eastcoast jam

• encompassing community coordination - eg contactimprov.net

  • ongoing events - local jams, classes
  • occasional events - regional jams, workshops
  • contacts
  • resources

• discussion medium for progressive collaborative document development

  not just:

  • blurting out bits about subjects, eg weblogs, email
  • presenting frontier revisions of progressively edited documents, eg wikis

  but rather, something in between. (this is the goal of Turning Answers Into Stories, but that's a ways off.)

  in addition to guidance (positive and negative) to be harvested from precedents like weblogs, email, wikis, etc, chris mcdonough (with contributions from Bruce Eckel and Bill Venners) developed backtalk for similar purposes, and there may be ideas to steal and/or lessons to learn from that.

  in part i'm looking for low-hanging fruit, here. eg:

  • fix kupu so, eg, selecting linking in neighboring pages is so easy and effective that it (kupu) is viable instead of structured text (reSt). (i still may stick with reSt, because i like to remotely edit plain text in emacs.)
  • make outline collapsing built in so it can be trivially employed on bulleted lists like these. i wonder whether some css and javascript could be used to create a style that instruments bulleted lists for collapsability?? that'd be ever so handy. and then, in reSt have the '+' bullet designate a collapsable list entry, whee!
  • make page-update notifications more controllable, so, eg, people can get cumulative digests rather than being pinged with every revision.

start adding use cases

from some late-night notes, these need to be resolved, but may have some useful info:

• personal info
  • maintain personal info
  • maintain ongoing info:
    • gatherings: local jam (activity), regional jam, workshop, party
    • discussions
• manage event info
  • request/relinquish authorization to maintain info
    • last person with authority may be unable to relinquish
  • grant/rescind authorization to maintain info
  • post notification about upcoming event
• seek event info
  • subscribe to notification about upcoming event
  • subscribe to notification about event series (reminders)
  • subscribe to notification about exceptions to event series (cancellations, changes)
  • visitor seeks occurrence of ongoing event (jam, square dance, game)
    • location
    • date/time
    • focus / genre
    • teacher
    • level
  • visitor seeks to participate in event
  • visitor seeks to join event as ongoing member