Hi everyone,
Following a meeting with Ken, and then the USQ team, I wanted to consolidate
the discussion on outcomes so that we had consensus on exactly what it was that
we were working toward. This clarity will assist all involved in terms of the
expectations for all parties involved (and meeting them), as well as
highlighting opportunities for people to take the lead at various stages. What
follows is the rough understanding the USQ team has; please do provide
corrections are needed - the aim here is understanding and a way forward. I
have presented each as a statement of purpose and then resulting questions for
that purpose.
**Overall aim:
to produce a course on Open Source Software Projects in conjunction with the
OSI and OERu. USQ aims to offer the course as part of our degree program too.
Questions on Overall Aim:
- Will this be a full course for USQ, or is the aim to have this as content
that is drawn into other existing courses? The flexibility could allow both,
of course, but if it is going to be a full course for USQ we have some internal
and external considerations to meet. Once I know the answer to this, I can
pose a few additional questions (such as AQF, Accrediting bodies, how this fits
into existing degrees, Course Specification documents, etc).
- what timeframe do we currently have for this project? When is it expected to
launch?
**Modes of study:
Currently offered face-to-face using a team-based curriculum.
Questions about Modes of Study:
- Can we confirm the types of enrollment sought by this course. In my
discussions with Ken, he mentioned: face-to-face on-campus with teams, online
with teams, online individual, and 'blended' online offerings. IS this still
the case?
**Content:
Using Karl Fogel's book 'Producing Open Source Software'
(http://producingoss.com/en/index.html) as well as the other content in the
Syllabus.
Questions about content:
- To what extent is the Fogel text to be integrated with the course?
- Angela mentioned that many of the examples in the course are North American
in focus. The design team does need to consider how to remix/repurpose some
examples so that they are more widely appropriate.
- We'll need to consider the assessment (Criterion-Referenced)
- Is there a level of 'assumed knowledge' for the course? If so, can we develop
a 'pre-test' tool so that we make this assumed knowledge explicit to students?
If we can get to the answers to these questions, I feel that it will contribute
greatly to the pre-blueprinting phase.
Regards,
Adrian
Following a meeting with Ken, and then the USQ team, I wanted to consolidate
the discussion on outcomes so that we had consensus on exactly what it was that
we were working toward. This clarity will assist all involved in terms of the
expectations for all parties involved (and meeting them), as well as
highlighting opportunities for people to take the lead at various stages. What
follows is the rough understanding the USQ team has; please do provide
corrections are needed - the aim here is understanding and a way forward. I
have presented each as a statement of purpose and then resulting questions for
that purpose.
**Overall aim:
to produce a course on Open Source Software Projects in conjunction with the
OSI and OERu. USQ aims to offer the course as part of our degree program too.
Questions on Overall Aim:
- Will this be a full course for USQ, or is the aim to have this as content
that is drawn into other existing courses? The flexibility could allow both,
of course, but if it is going to be a full course for USQ we have some internal
and external considerations to meet. Once I know the answer to this, I can
pose a few additional questions (such as AQF, Accrediting bodies, how this fits
into existing degrees, Course Specification documents, etc).
- what timeframe do we currently have for this project? When is it expected to
launch?
**Modes of study:
Currently offered face-to-face using a team-based curriculum.
Questions about Modes of Study:
- Can we confirm the types of enrollment sought by this course. In my
discussions with Ken, he mentioned: face-to-face on-campus with teams, online
with teams, online individual, and 'blended' online offerings. IS this still
the case?
**Content:
Using Karl Fogel's book 'Producing Open Source Software'
(http://producingoss.com/en/index.html) as well as the other content in the
Syllabus.
Questions about content:
- To what extent is the Fogel text to be integrated with the course?
- Angela mentioned that many of the examples in the course are North American
in focus. The design team does need to consider how to remix/repurpose some
examples so that they are more widely appropriate.
- We'll need to consider the assessment (Criterion-Referenced)
- Is there a level of 'assumed knowledge' for the course? If so, can we develop
a 'pre-test' tool so that we make this assumed knowledge explicit to students?
If we can get to the answers to these questions, I feel that it will contribute
greatly to the pre-blueprinting phase.
Regards,
Adrian