CweUser/CweGuidedExploration

Notes to a Guided Exploration of the CWE (GS)

Groupware vs Transaction systems (CWE is "Groupware") (GU)
from "conversation" to "speech acts" to work flow (ref. John Austin, John Searle, Fernando Flores & Terry Winograd; also see: http://www.swif.uniba.it/lei/foldop/foldoc.cgi?speech+act) (GV)

for more serious reading, try reading: Winograd, T. & Flores, F. "Understanding Computers and Cognition : A New Foundation for Design" (GW)
Doug Engelbart's Bootstrap, Networked Improvement Community and Collective Intelligence. Ref: [The Bootstrap Vision and Mission http://web.archive.org/web/20000623003026/http://www.bootstrap.org/vision_mission.htm] (GX)

and, in particular, Doug's concepts on A-B-C work, OHS (Open Hyperdocument System) and DKR (Dynamic Knowledge Repository). (HX)

an archived email forum - to hold our converstions and discussions (H0)
a wiki - to help us collaboratively compose our work (H1)
a file repository - to hold documents, work and resources that we can share, and (H2)
a portal - to provide a convenient single point of entry to the environment and the work of the community (H3)

it's all about getting work done effectively, especially when we are not in the same place (H4)
it takes People, Process and Tools to achieve that (emphasis: People heads the list; and this is definitely not just about technology) (H5)
it's about: (H6)

sharing (H7)
distributing the work (H8)
getting things done without being in the same place, at the same time (H9)
being able to capture the entire life cycle and all the interactions of the collaboration, and be able to re-use that knowledge to improve on the effectiveness of the collaboration (HY)
working within an expressive environment - where communication is not hampered by the rigidity of the setting; minimal structure; spurring innovation and emergent behavior (HA)

some suggestions and best practices in the cwe discussion forum (ref: http://community.cim3.net/cgi-bin/wiki.pl?CweUser/BestPractice#nidA7) (HD)

It is recommended that you save this posting address e.g. <community-forum@mp.cim3.net> to your address book; set it to receive mail in plain text only, and to wrap the text with line length of 65 characters. (HE)
always think of the “recipient” of the information. Consider how one can get the message (and its “meaning”) across unambiguously, effectively and efficiently. Provide context (succinctly), by citing links to relevant supporting information, where necessary. (HF)
use the SUBJECT line wisely. That's almost the first thing that will be presented in a human "explore and search" effort (HG)
Threaded Conversations / Discussions : one issue at a time; separate the threads properly; open and close conversations properly; continue the thread (don’t start a new one) until it is closed (HH)
don't quote the entire "previous discussion", just capture the point you are making a remark on (HI)
organize the message into paragraphs and/or lists (numbered or bulleted) (HJ)

leave a blank line between each paragraph or bullet point (so that purple numbers can be properly inserted) (HK)

proper use of "attn" within the message -- highlight and draw the attention of particular targeted audience (HL)

be very specific about action items, expected deliverables, due dates, deadlines, ... etc. (HM)
link your audience to your cited reference "in context" through the use of granular linking (with "purple numbers") (HN)
save documents into the repository, and refer to them in the thread-discussion (e-mail message) with a hyperlink. (HO)

testing our "screen sharing" (synchronous collaboration) service (ref: http://community.cim3.net/cgi-bin/wiki.pl?CweUser/FAQ#nidAN) (HR)

use as appropriate: opening new windows (with right-mouse-click when mouse-over link) (HW)