it sounds like you're talking about having the event online, bob. when i'm talking about using blogs, the notes that would usually be posted into a word document end up as so many blog postings. then, yes, any after-conversations, followup actions, new information, would hang off the individual posts.... but that mirrors for me, because all of that is stuff that proceeds from the initial conversation. and any sort of media can be linked to in those comments. <br>
<br>as for structuring, whenever there is something really new taht comes up following the meeting, like one breakout conversation proceeds to the point where everyone says "we need another meeting, another round of conversation, a specific action of some kind..." then that can be posted in the comments as the culmination, or maybe just a milestone, hanging off of the blog post with the notes from teh original conversation -- AND -- it can be posted as a new item, it's own blog post, a new invitation to that next round of conversation/action. <br>
<br>the only catch in all of this is that while everyone generally can post comments in a blog structure, everyone might or might not have access level required to post new items. there is a learning curve that is possible, where more people learn to post new blog entries, new invitations. <br>
<br>there is also a debate possible: is it enough for people to write their own new postings, or must they be able to post them directly for themselves (not wait for somebody else in a stewards group to do it). do we make participants bring their own tape in os meetings, for instance... no... but we make them tape them up themselves. i think it's best when they can post directly, but *i think* with things like buddypress and ning, we are getting to the place where the tech easily supports anyone adding a post directly to a blog stream, so this debate starts to go away.<br>
<br>m<br clear="all"> <br>--<br><br>Michael Herman<br>Michael Herman Associates<br><br><a href="http://MichaelHerman.com">http://MichaelHerman.com</a><br><a href="http://RonanParkTrail.com">http://RonanParkTrail.com</a><br>
<a href="http://ManorNeighbors.com">http://ManorNeighbors.com</a><br><a href="http://ChicagoConservationCorps.org">http://ChicagoConservationCorps.org</a><br><a href="http://OpenSpaceWorld.org">http://OpenSpaceWorld.org</a><br>
<br>312-280-7838 (mobile)<br>
<br><br><div class="gmail_quote">On Sat, Jun 12, 2010 at 9:38 AM, Robert Fabian <span dir="ltr"><<a href="mailto:robert@fabian.ca">robert@fabian.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Some background on my Drupal comment ...<br>
<br>
In my experience, the best information systems "mirror" the socio-tech<br>
systems they are intended to serve. When the architectures are in conflict<br>
the information system is a constant source of frustration (and error) for<br>
the people forced to use it. It is possible to pull back from a full<br>
"mirror" to provide a minimal architecture that people can deploy as they<br>
see fit. The information system doesn't encourage any specific kind of<br>
deployment.<br>
<br>
Against this consider three OST support/extensions system tools: Blog; Wiki;<br>
and Drupal Organic Groups. Blogs are easy to understand, but everything<br>
hangs off the initial post; the system provides no direct support for any<br>
structuring of the information. Wikis do support structuring, but are<br>
significantly less easy (familiar) for many. Further, the crowd approach to<br>
structuring depends on a relatively high level of activity. I would be<br>
concerned that a lightly used Wiki might imply a structure that the crowd<br>
would not, in fact, support, but became the default through limited use.<br>
<br>
Drupal and Organic Groups pose a different challenge. Within an Organic<br>
Group participants can be free to add any kind of content, from simple web<br>
pages to faqs to "books" (a Drupal "book" is really a wiki, but with a table<br>
of contents). The Group has available to it a full range of web based<br>
information container tools. The boundaries can be made as open or closed as<br>
one might want. But this is going to be a universe that many will find<br>
strange and not all that natural. However, with experience, it can become a<br>
natural home for Group discussions and contributions.<br>
<br>
The Drupal answer has the virtue that it can provide a good "mirror" to the<br>
emergent social organization of an Open Space. The cost is a somewhat higher<br>
learning curve. Depending on the tech-comfort of the participants it could<br>
be an effective support/extension environment. It's an opportunity that<br>
appeals to me. I would be happy to explore it further if there is interest.<br>
<br>
Bob Fabian<br>
<br>
*<br>
*<br>
==========================================================<br>
<div><div></div><div class="h5"><a href="mailto:OSLIST@LISTSERV.BOISESTATE.EDU">OSLIST@LISTSERV.BOISESTATE.EDU</a><br>
------------------------------<br>
To subscribe, unsubscribe, change your options,<br>
view the archives of <a href="mailto:oslist@listserv.boisestate.edu">oslist@listserv.boisestate.edu</a>:<br>
<a href="http://listserv.boisestate.edu/archives/oslist.html" target="_blank">http://listserv.boisestate.edu/archives/oslist.html</a><br>
<br>
To learn about OpenSpaceEmailLists and OSLIST FAQs:<br>
<a href="http://www.openspaceworld.org/oslist" target="_blank">http://www.openspaceworld.org/oslist</a><br>
</div></div></blockquote></div><br>
*
*
==========================================================
OSLIST@LISTSERV.BOISESTATE.EDU
------------------------------
To subscribe, unsubscribe, change your options,
view the archives of oslist@listserv.boisestate.edu:
http://listserv.boisestate.edu/archives/oslist.html
To learn about OpenSpaceEmailLists and OSLIST FAQs:
http://www.openspaceworld.org/oslist