User:Sj/Log

Editor's Log

Monday June 26

Step 3 : Communicating dreams

Grand dreams gain luster as they are shared; inspire enthusiasm from a distance as well as up close. Communicating and promoting dreams, asking for detailed advice and help (and not simply approval or shallow support) makes them real. Particularly when changes occur rapidly, leaving the path of change and its every step open helps disparate groups who feel associated to a great Work feel involved, drawn up in the hunt even if at the rear of the pack. Those of you who remember The Beast may recall how much energy was put into keeping an audience of new and old hands alike entranced by and in step with the rapidly changing texture of a complex project with many fronts. Three people devoted a fair chunk of their time to maintaining those centers for community cooperation, planning, and storytelling; without foregoing participation in the production of new ideas and material. There isn't much in the way of detailed visions on this wiki at present; in part because this space is still finding its voice, not because visions for this project have not been articulated. Some of this will change in the months to come, some may even come from readers of this log. But beyond initial vision, sharing dreams over time means conveying progress, successes and failures, needs and desires. I aim to do what I can along these lines; if you are interested in the same, let me know (or just start doing it!).

Step 2 : Chain of tools

It's really too early to start talking about tools and toolchains; when there are regular schedules and connections to be made. But a few can be mentioned from the start: a place to ask questions and find answers; a place to throw out new ideas (Hardware, Software, Pedagogy); a place to suggest useful content.

Step 1 : Applying wiki culture

There is a world of difference between having a tool and knowing how to use it, and between knowing how to use it and making it an extension of oneself -- knowing how that tool sees the world, being able to reinterpret any situation in that context. The expression "when all you have is a hammer, everything looks like a nail" has both positive and negative aspects. There is utility in being able to see the nail-like aspect of any problem, whether or not there is a hammer handy (in particular, one should regularly be considering how important it is to find a hammer, if one is not). When it comes to wikis - there is much more to effectively implementing an open collaborative content aggregator than having and using one. Content workflows with detailed roles (protection, privacy segmentation, &c), continuing use of other information channels for public sharable knowledge (email, blogs, whiteboards, phone calls, ticket systems) that don't pass through the wiki -- all of these limit the scalability and efficacy of a wiki's openness. For the purposes of OLPC : if we want the public to take an active part in guiding and advising on the project progress, news and photos and updates should come through the wiki first or second, not as an afterthought when someone remembers. Wiki watchlists should be a key part of tracking new ideas. Educators, officials, students, other community members should all be directed to the wiki for sharing their thoughts and discovering what is going on -- withthe caveat that if they can't find what they're looking for, they should ping someone to update the information here. And internally, using a wiki to organize text and project ideas will help accustom project members to that style of formatting and interlinking thoughts. Please leave me comments and tell me what you think.

Day 0, Step 0 : Logging backwards

A day of preparation; setting up the log. Tomorrow will be the first proper day of logging.