Virginia Faculty Collaborative cMOOC Countdown

Teaching Open Source Practices version 4.0
Teaching Open Source Practices version 4.0

I’ve been working with a great group of higher ed folks affiliated with the AAC&U Faculty Collaboratives project for the last several months. The collaboratives are state-level efforts to enlist faculty in the far-reaching and essential challenges of re-imagining role of liberal education at this time of transformation across the higher education landscape.

In January we will be facilitating a cMOOC addressing all aspects of “Open Education,” a category that includes open educational resources (OER), open pedagogical practices, open access, participatory cultures and literacies, networked learning, etc. These topics will structure weekly readings, viewings, etc., as well as the reflections and networked learning that the course participants will offer each other.

For an overview of goals and planned activities, see A week-by-week listing of topics, readings, etc., is developing at

More information about the course and reflections on what we hope to accomplish will be coming in the new year. In the meantime, if you are interested or implicated in liberal learning — especially in Virginia — and would like to take part in a meaningful exploration of the potential for open education to contour the landscape of learning in the twenty-first century, it’s never to early to join the cMOOC here:

5 Replies to “Virginia Faculty Collaborative cMOOC Countdown”

  1. Okay, I’m going to ask a dumb question. You seem like a pretty typical faculty member: You teach classes; you conduct scholarly research; you’ve been in academia for a number of years. As a colleague once said (actually more than once) if it ain’t broke, why fix it? So here’s the question: Why should a faculty member get involved in open education? If you’re like me, you have more than enough to do with your time. So why this?

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: