- 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.
- 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)
- Collaborative Lesson Development
- Why Teachers Don't Collaborate on Lesson Development
- OER Beyond Voluntarism
- Why Can’t OER Enjoy the Same Success as Open Source Software?
- On the Sustainability of OER Initiatives in Higher Education
- The Four R’s of Openness and ALMS Analysis: Frameworks for OER
- Producing Open Source Software
- Applying Software Development Paradigms to OER
- Good Enough Practices in Scientific Computing
- 80 resources for Open Education Developers
- Sphinx - ReadTheDocs
- OERPUB
- Static Site Generators
- Jupyter Notebooks
- gitbook
- pandoc
- rhinotype
- pollen
- ShareLaTeX
- Authorea
- Texmaker
- Reveal.js
- impress.js
- deck.js
- Scrollama
- Google Web Designer
- GitHub
- BitBucket
- Accessibility Project
- Translate
- L20N
- Docker
- Ansible
- Travis-CI
- Discourse
- gitter
- eXeLearning
- H5P
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent