Tools & Assumptions for KnowledgeSpace

Goal:

Improve entry level experience, show what technologies can do - what it is, why do I need it, DSpace vs. Fedora - why chose one over the other, use cases examples, how to set up a repo and get started.

1. develop on-line materials (similar to Ruby's RailGuides: http://guides.rubyonrails.org/)
   1. each topic has: (a) Screencast, (b) Text-based Guide, (c) Powerpoint based, and, if available (d) link to relevant video/wedinar
2. Next steps
   1. de-coupled RSP educational proposals vs. our larger educational curriculum 
      1. Jonathan mtg w/RSPs later this month, would like to show them what we have
   2. create table of content page and a team for each project 
      1. DSpace curriculum: Tim to confirm the table of contents is complete and ready for feedback
      2. Fedora curriculum: Chris to confirm the table of contents is complete and ready for feedback
   3. tools to be used
      1. to start -- just a set of wiki pages or something else - Val to research theme/format on Confluence (checklist box at top),
      2. vimeo account for video - link to w/in the guide, people will have to submit the videos to us so we can put it in our vimeo acct
      3. need to approve, make sure no writes violation, ensure that it is permanently stored in a repository (and backup) somewhere
      4. slideshare account for powerpoint
   4. Create examples of each: (a) Screencast, (b) Text-based Guide, (c) Powerpoint based
      1. DSpace:Tim to let Val know of any relevant resources to help get started
         1. Basic intro on XMLUI - w/screencast, text guide and Powerpoint
         2. install/set up process (paragraph descriptor only w/references and future plans)
         3. What is DSpace?/Why use DSpace? Jonathan working on already
      2. Fedora:  Chris to let Val know of any relevant resources to help get started
         1. installation
         2. conceptual Fedora (what is an object? what is a Fedora repository?)
         3. What is Fedora? Why use Fedora? Jonathan working on already
   5. contributors/editors - once examples are done, reach out to others for help - editor, mtnr, organizer: Bram (consulting partner), Jeff Trimble, Claudia (reviewer, organzier, knows what people are asking, what should be encourage to get written, are we mtg the need on this topic), Stuart Lewis/Leonie
      1. contributor license agreements - contributors/editors - need to sign a CLA
      2. suggest Apache 2 both ICLA (individual) and CCLA (corporate) licences, and then Creative Commons on the content - use one of the some rights reserved - future opp to pkg up and profit from it $
      3. develop committer process
   6. build wiki structure for delivery - special module/component to mimic Confluence - Brad, Tim, Chris, Andrew, Bill?

Tools

Screencast.com Widget Connector Extension
(https://plugins.atlassian.com/plugin/details/33430)
Jing, Camtasia, Screencast.com videos can now be embedded in Confluence using the Widget Connector.

ScreenSnipe for Confluence
(https://plugins.atlassian.com/plugin/details/28446)
Create easy and powerful screenshots at hand - directly from your Confluence (with no client-side installation). Creating beautiful and informative release notes, technical documentation or clear, visual comments was never simpler.

TaskDock for Confluence
(https://plugins.atlassian.com/plugin/details/13744)
Communication and workflow for your content. Project tracking, tasks, and messaging for your wiki. Includes JIRA integration.