All,
TL;DR:
- I agree, initial course should be pedagogically neutral.
- I want to re-emphasize the "course pack" model.
- Who wants a login to the Modole site?
- If we're not using Moodle, where is the content repository?
- How do we start?
As Ken mentioned here, Moving Forward with Some Questions/Discussion
(http://groups.oeru.org/groups/oss-production-course-team/messages/topic/6p9kBiCUMlM80h3nTVIMhE)
Clark Shah-Nelson and I began developing a course based on my current offering
at the State University of New York at Albany (UAlbany).
I think I messed up...
I think Wayne has it right, this should be a very basic course that adopters
can use as they like (format, content, activities, etc.). The only "hard-coded"
aspect would be the use of Karl Fogel's text, Producing Open Source Software.
The online resources should replicate the current "standards" for a course pack
(ugh, I just threw up a little bit in my mouth).
My course at UAlbany uses Team Based Learning (TBL), which I really like and
which I think compliments the open ethos of open source software. But I
realize, most faculty probably want to "teach the book" and are looking for
straight forward materials that do not require them to adopt a new pedagogy.
This opinion was recently reinforced, twice. By a co-worker who also teaches an
open source course, and wanted to use my materials, but was scared off by the
TBL approach.
Secondly, as part of my OSI role, I recently joined the "Professor's Open
Source Software Experience" (http://foss2serve.org/index.php/POSSE) and after
several meetings, it is clear attaching a pedagogical style is a bad idea.
So, I defer to the experts. I think Karl as the author, and I, as one who has
taught the course for four years, can provide the content "expertise" but will
defer to the course and instructional designers to lead the development effort.
Considering the above, I still think we should use Moodle as a foundation
(although I also understand having a content repository, which does eliminates
a pedagogical bias and would be happy to shift to that).
OK, how do we start?
Patrick
TL;DR:
- I agree, initial course should be pedagogically neutral.
- I want to re-emphasize the "course pack" model.
- Who wants a login to the Modole site?
- If we're not using Moodle, where is the content repository?
- How do we start?
As Ken mentioned here, Moving Forward with Some Questions/Discussion
(http://groups.oeru.org/groups/oss-production-course-team/messages/topic/6p9kBiCUMlM80h3nTVIMhE)
Clark Shah-Nelson and I began developing a course based on my current offering
at the State University of New York at Albany (UAlbany).
I think I messed up...
I think Wayne has it right, this should be a very basic course that adopters
can use as they like (format, content, activities, etc.). The only "hard-coded"
aspect would be the use of Karl Fogel's text, Producing Open Source Software.
The online resources should replicate the current "standards" for a course pack
(ugh, I just threw up a little bit in my mouth).
My course at UAlbany uses Team Based Learning (TBL), which I really like and
which I think compliments the open ethos of open source software. But I
realize, most faculty probably want to "teach the book" and are looking for
straight forward materials that do not require them to adopt a new pedagogy.
This opinion was recently reinforced, twice. By a co-worker who also teaches an
open source course, and wanted to use my materials, but was scared off by the
TBL approach.
Secondly, as part of my OSI role, I recently joined the "Professor's Open
Source Software Experience" (http://foss2serve.org/index.php/POSSE) and after
several meetings, it is clear attaching a pedagogical style is a bad idea.
So, I defer to the experts. I think Karl as the author, and I, as one who has
taught the course for four years, can provide the content "expertise" but will
defer to the course and instructional designers to lead the development effort.
Considering the above, I still think we should use Moodle as a foundation
(although I also understand having a content repository, which does eliminates
a pedagogical bias and would be happy to shift to that).
OK, how do we start?
Patrick