Buy Periactin without prescription - allergy symptoms, Buy Singulair without prescription,Buy Nasonex without prescription , Buy Ventolin inhaler,Buy Pulmicort inhaler without prescription, Buy Symbicort online



  handbook Roadmap

If you want to build a ship, don’t drum up people to collect wood and don’t assign them tasks and work, but rather teach them to long for the endless immensity of the sea.


This project seeks to empower the worldwide population of self-motivated learners who use digital media to connect with each other, to co-construct knowledge, to co-learn.

Process note

For anything complicated that might have to be repeated, please add “How To” instructions in the “Done” section at the end.

Upcoming (Major milestones)

  1. Filter content from our unfunded Knight Foundation Proposal about the Peeragogy.EDU course into this Roadmap, breaking it into concrete, do-able tasks.
  2. Develop a Peeragogy Linux-on-a-Stick USB to distribute with the book, and add some brief quickstart technical notes for key tools.
  3. Etc (add ideas here)

Upcoming (Editing notes/suggestions)

  1. Finish and import a draft “FAQ” and create guidelines for getting new questions onto the FAQ.
  2. Etc (add ideas here)

Upcoming (Tech notes/suggestions)

  1. Fix the “Technologies” template so that the things that people write about technologies actually show up on the site; either that or officially abandon the “Technologies” template and just start writing about technologies as Pages.
  2. Etc (add ideas here)

Upcoming (Research notes/suggestions)

  1. Joint paper for WikiSym 2013.
  2. Technology Accessibility – low bandwidth, “Slow TV”, closed circuit – can we learn from history and increase involvement?
  3. Integration of project streams:, CAN,, Google+, Facebook, Twitter, and contributors’ various other site locations (, etc.)
  4. Etc (add ideas here)

Upcoming (Content notes/suggestions)

  1. Write a short article that compares & contrasts “peer learning” and “self-regulated” or “self-directed” learning.  Some relevant notes are here; Alison Seaman has volunteered to work on this in early March.
  2. Sum up the references in the “Tips from an Open Source Perspective” recommended readings (in the Peer Learning article) and add an article about open source software to the technology section of the book.
  3. “Rewrite from scratch” the article on self-organization (current version draws on Wikipedia CC-By-SA content and so isn’t suitable for the book).
  4. Etc (add ideas here)

Upcoming (Translation notes/suggestions)

  1. Translation into Italian (Fabrizio coordinating with Permondo)
  2. Translation into Spanish (Paola coordinating)
  3. Translation into Mandarin and Cantonese (Charlie coordinating)
  4. Translation into Brazilian Portuguese (Fabrizio coordinating with Maria Ione Silva)
  5. Etc (add ideas here)

Upcoming (but generally low priority)

  1. Configure the backup system to make backups fully automatic.  The plugin that does backups will send a notification email to a designated address.  Either that could be scripted client-side, or the code that sends the email could be hacked to do more, e.g. run a system call to scp.  The relevant code is here:
  2. Is there a way to make “justified text” the default?  Maybe not.
  3. Polycentric leadership research
  4. Etc. (add ideas here)

Case Studies and Components

  1. Finish the re-boot of (Joe)
  2. Implement the system as a way to inject money into the project (Joe)
  4. Etc. (add ideas here)

Roles available

  1. Volunteer Coordinator needed.  Build a page that will accompany this Roadmap, describing the skills, expertise, and interests of specific persons/roles that are needed in the peeragogy project.
  2. Seminar Coordinator needed. Someone should coordinate our live meetings.  Charlie has been doing this with informal work meetings, but it may become a larger job when we start doing more public events.  Anyone want to step up to the role of “Seminar Coordinator”?
  3. Usability Guru needed.  The first step will be to generate some “usability targets” for the handbook. For example: let’s check, is the book really useful for someone who is running a course?  Is the book really useful for someone who is building or running a “learning space”?  Is it easy for readers to understand how they can contribute to improving the book?  (Etc., those are just samples.)  Note that some related things have been worked out in a procedural way in our Peeragogy in Action syllabus, but the book itself will still need a good once-over from the point of view of “usability” and “usefulness”.  That may progress along with the Peeragogy in Action course, which itself will be developing on Google+ and in various seminars and discussions.  But we probably need someone to own this.  Could it be you?
  4. Activities Master needed. Someone should take ownership of the Activities section, and do something with it on a level comparable to what we’ve done with Use Cases.  It makes sense to start collecting Activities now that we’re entering Peeragogy in Action!  One approach is just to ask people “what are your peeragogical activities?” and then just write down what they say.  In the process of working in this role you will also improve the handbook’s content to make it more useful for an “active reader”.
  5. Tech lead needed. Right now we’re using a “borrowed” hosted space, but it would probably be good to have our own server with a bit more control.  Someone will have to set that up and take ownership of polishing it.  Could it be you?
  6. Etc (add ideas here)


  1. Site created
  2. Headway theme installed
  3. Some content ported over
  4. Add some useful ways to comment on the status of pages (separate from “comments”) — we’re using “Notes” which can be added right above the Publish/Update button when editing a page; a feed of all notes, with links to the pages where they originate, is also available on the Dashboard.
  5. Clickable SVG Cmaps (e.g. on the Patterns and Heuristics page) (How-to)
  6. Installed the Post Revision Display plugin and Style Tweaker plugin to make it work well.
  7. Installed the BackupWordPress plugin.
  8. Added <p style="text-align: justify;"> and </p> tags to text that we want to be aligned.
  9. Launched “alpha testing” from May 11 18th (How-to), now energy-centered by Ted
  10. Turned on comments for reviewers
  11. Removed the sitewide password, so that anyone can view content
  12. Implemented most of Anna’s Visualization team’s design elements
  13. “Meet the authors” info collected via web form, and published on
  14. Added a “Recent Changes” feed to the sidebar (How-to)
  15. Fix the Footer to take up less space, and so the links work, and change the text so this isn’t a “Howard Rheingold University” project.  We can thank HRU on a separate page. (How-to)
  16. Revise the Literature Review and use it to seed a new “Peer Learning” page on Wikipedia
  17. Fine tune elements to match Visualization team’s design and/or decide what isn’t easy/practical and call it a wrap.  (This seems stable now.)
  18. Finish importing content (for version 1.0)
  19. Tweak CSS (How-to)
  20. Fix the right sidebar for “final” author and editor content (won’t fix)
  21. Improvements to the quickstart guide and contributor instructions (may need some continued attention as the project continues to grow!)
  22. “final” editorial pass (relevant to building “Version 1.0″ of the handbook, obviously it could continue to grow and improve forever!)
  23. Finish writing any last sections that are still stubs, if we want to include them in “Version 1.0″
  24. Revise content so that links and references point (where relevant) to pages and workflow on rather than (How-to)
  25. ebook preparation and publication (“free download here”).  Let’s call the first public downloadable version “Version 1.0″ of the handbook.  Approximate date for staging of content: August 15.  Editorial work to take place after that.  Updated deadline: January 1 for downloadable book. You can also download and recompile the sources, and generally use them without limitationUpdated directions: LaTeX sources now available from
  26. Multilingual versions of the handbook and WP pages – this is reasonably well started on using the open source version of the WPML plugin.  The plugin needed some tweaking to actually make it workable.  Also, the wp_posts table in the database had to be converted to UTF8 (and why not UTF8MB4 while we’re at it!)  Note: We still need translation teams to finish the job.
  27. Edited David Preston’s Assessment case study and used it to seed the Case Studies / Motivation collection.
  28. Added captions to the menu on the left. (HOWTO)

Post Revisions:

Doctors often prescribe a safe and powerful drug called clomid to infertile women

Loading Facebook Comments ...