Comments on Web 2.0 Overview Document

I've posted an overview of the Web 2.0 document at http://docs.google.com/Doc?id=df2dswdk_115c6d7vn which is intended to explain the project to the general Wesleyan community. Please use the space below to record any comments or suggestions you have that will make this a better document.

-- mike

Allegheny's Blogging Help Pages

Allegheny College has done a nice job of creating documentation and a request form for their blogging service. It is at http://help.allegheny.edu/tutorials/mtype/weblog.php . They don't keep a directory of blogs on campus, which I found odd, but whatever.

--mike

Assignments and Agenda for March 21 Meeting

At our last meeting (March 7) we divided into 4 teams of 2 to evaluate the 4 packages.

drupal: Pat and Jen
moveable type: Jane and Adrian
wordpress: Beth and David
journal lx (blackboard): Mike & Mike

I also did a bit of searching around to see if there were other applications that we ought to be looking at but none turned up.

The agenda can be pretty simple:

1. updates and first impressions from each group.
2. reminder to give everyone access to each of the four tools
3. plan for amherst visit to demo drupal
4. plan for formal evaluation/report/demo by ?
5. develop list of pilot projects for summer/fall
6. develop plan for involving more users in testing/evaluation


-- mike

Agenda for March 7, 2007 Meeting

1. Review of overall charge to group (on dokuwiki)
1. Mike will draft a human-readable overview of the various pieces of this project
2. develop use cases and scenarios
3. recruit end users in the evaluation process
4. work with TSS to get test installations of candidate software
5. where appropriate, schedule vendor visits, or visits by/to schools that are using system(s)
6. identify technical lead for the project
7. identify functioal lead for the project
8. develop plans for training trainers
9. develop plans for writing documentation
10. identify pilot projects that will use new applications
11. if needed, develop policy


2. Assemble teams of two for:
a. drupal
b. moveable type
c. wordpress multiuser
d. journal lx (blackboard building block)

Teams should:
1. evaluate according to requirements
2. talk with other schools
3. prepare report to group (to be scheduled in the next month)

3. Sanity check:Other candidates?
what other tools are we ignoring? should we do survey to make sure we aren't forgetting something important?