/hackoer

HackOER - Applying FLOSS best practices to OER

HackOER - Applying FLOSS best practices to OER

  • treating content as source code (in plain text)
  • keeping it under version control
  • using build tools to generate multiple OER
  • leveraging i18n methods
  • packaging in several formats
  • releasing under free and open license models
  • nurturing a community around OERs
  • applying agile methodologies
  • etc.

The 5R permissions of OER

  • Retain: Make, own, and control copies of the content
  • Reuse: Use the content in a variety of ways
  • Revise: Adapt, adjust, modify, improve, or alter the content (e.g., translate the content into another language)
  • Remix: Combine the original or revised content with other OER to create something new (e.g., incorporate the content into a mashup)
  • Redistribute: Share copies of the original content, your revisions, or your remixes with others (e.g., post a copy of the content online for others to download)

The ALMS analysis (more detail at http://opencontent.org/definition/)

  • Access to editing tools?
  • Level of expertise required to revise or remix?
  • Meaningfully editable?
  • Source file access

You can see a rubric in a presentation (from p. 10 on)

reference (about OER and FLOSS)

articles

OER

Standards

Software Development

Tools