OERu/Planning/Community source

Now is the time for partner institutions (and others in the Open Source community) to help build the tools to make the OERu successful and scalable.

There have been years of discussion on the WikiEducator Tech mailing list around ways WikiEducator could be augmented and resources stored in WikiEducator could be easily reused. We have also published a list of smaller projects that provide incremental improvements.

Additional ideas include:
 * 1) accelerate the transition to Mediawiki 1.23+
 * 2) * reverse engineer LiquidThreads (LQT) version 1 and provide a migration path to LQT2 and/or Flow
 * 3) * update extensions, including:
 * 4) ** WEnotes
 * 5) ** WEvotes
 * 6) ** WEPoll
 * 7) ** WEoptions (or decommission, replace with Education project?)
 * 8) ** LicenseByCategory
 * 9) ** WikiArticleFeeds
 * 10) ** RSS feed
 * 11) ** update from mp3 and OggHandler extensions to MediawikiPlayer or Timed Media Handler extensions (see Multimedia)
 * 12) ** lower priority extensions
 * 13) *** OERFDonation
 * 14) *** Oppia
 * 15) *** Collection (user interface changes)
 * 16) *** HTML5video (decommission in favor of some new solution?)
 * 17) *** update or decommission SAMLAuth
 * 18) *** WEtheme (or decomission?)
 * 19) * find a replacement video solution for Kaltura
 * 20) * update system Javascript (both wikibits and MediaWiki:Common.js)
 * 21) * update system CSS (both skins and especially MediaWiki:Common.css)
 * 22) * update WikiEducator tutorials
 * 23) * build transition path from WE upload form to standard MW form (and/or UploadWizard)
 * 24) a scalable, robust discussion forum
 * 25) * or (adapt and) reuse Flow
 * 26) (partially) automating importing content from other formats
 * 27) * open text books
 * 28) * LMS backups
 * 29) * Markdown
 * 30) * document Microsoft Word extension
 * 31) * enhance OpenOffice extension
 * 32) additional ways of snapshotting open resources for use on the web, CMS or LMS
 * 33) improve pedagogical templates
 * 34) * consistent CSS (MediaWiki:Common.css updates)
 * 35) * consistent layout and classes
 * 36) (HTML5) video upload and storage in a robust, cost-effective manner
 * 37) federating systems
 * 38) * within WikiEducator infrastructure
 * 39) * across partner institutions
 * 40) * allow use of widgets across instances
 * 41) building robust versions of the prototype Widgets that have been used in early courses
 * 42) * build versions that work in snapshot deployments
 * 43) building additional assessment options
 * 44) additional data collection and plotting tools
 * 45) make offline (PDF and ePub) options more robust
 * 46) integrate badges or digital certifications for course completion
 * 47) improve WikiEducator authoring tutorials
 * 48) implement OAuth logins
 * 49) implement IFrame skin
 * 50) build a robust method of mailing all participants in a course, with one-click unsubscribe and automated bounce handling