OERu/Planning/OERu Management Committee/15.06 Meeting of the OERu Management Committee

When: NZST (Click on link for local time.) Where: Google Hangouts on Air (Broadcast live) Backchannel #OERu feed. Post using WENotes or Twitter

Meeting documents

 * 1) OERu Strategic Plan 2015 - 2017 (pdf)
 * 2) OERu mid-year progress report
 * 3) Minutes and decisions of the 3rd meeting of the Strategic Planning Working Group.

Suggested agenda items

 * Suggested items have been transferred into the main agenda.
 * Any late suggestions should be added here

Agenda

 * 1) Welcome and introductions
 * 2) Dave Lane, Open Source Technologist joins the OERu
 * 3) Review allocation of 2015 KPIs to relevant working groups.
 * 4) Summary of suggested key output targets for 2015 working group activities (derived from Strategic Plan, 2014 OERu meetings and Strategic Planning working group meeting of 28 May 2015.)
 * 5) * Strategic planning
 * 6) ** OERu open business models
 * 7) ** Collating the OERu annual report
 * 8) * Curriculum and programme of study
 * 9) ** 1st year of study
 * 10) ** Post-graduate professional development qualification
 * 11) ** 2015 call for course nominations
 * 12) * Partner engagement
 * 13) ** Implement recommendations for course design and development partners manual / task force for new OERu partners/ OERu induction mOOC? (See: Draft outline for "Getting started with OERu").
 * 14) ** OERu certified educators
 * 15) ** Achieving working group participation targets
 * 16) ** Implementation of recommendations of the Singer and Porter OERu research project using activity theory framework
 * 17) ** How do we progress the concept of OERu focal points at each partner institution / regional OERu hubs.
 * 18) * Standing committee for credit transfer
 * 19) ** Registrar review of OERu credit transfer and course articulation guidelines
 * 20) ** Draft the OERu Handbook for Requesting Articulation
 * 21) ** Draft the OERu Handbook for Subject Discipline Articulation Sub-Committees
 * 22) * Course approval and quality
 * 23) ** Publish OERu quality guidelines (Design blueprinting and quality standards)
 * 24) * Technology
 * 25) ** Regular operational meetings
 * 26) ** Oversee coordination of activities for the shared Open Source Technologist position
 * 27) ** Recruit members from marketing departments at partner institutions - to assist with integration of partners guide and other support materials in the OERu corporate site
 * 28) Current Course Development and Delivery Schedule
 * 29) * Maintaining a central page in the wiki for active developments
 * 30) * Keeping the OERu site up to date on anticipated dates of completion.
 * 31) Maintain 2015 OERu Action Calendar including associated key milestones
 * 32) New groups.oeru.org site - Action items for conveners to be completed in the next fortnight
 * 33) Register on the site
 * 34) Complete your profile page on the site (model community leadership)
 * 35) Join the OERuMC group and join the the working group you are convening
 * 36) Appoint co-moderators for your group (preferably in different time zones) and award moderation rights.
 * 37) Review the members of your own working group. Check to see if members from 2014 have registered. If not please email the 2014 members of your group and request that they re-register on the list.
 * 38) Invite members of your working group to join using the invite someone new to join link (don't force subscription using the add a member link).
 * 39) Regularly review the manage the members link to check if participants have registered and resend the invitation if required.
 * 40) Moderators should approve posts of new members  and remove the moderation flag by visiting the mange the members link (moderation flag is set for new members until it's removed by the group moderators.)
 * 41) Trialling Discourse.org open source discussion platform for built for the "next decade of the Internet"
 * 42) * Possible replacement for main OERu community list on Google groups.
 * 43) * Potentially useful as peer community support for OERu learners.
 * 44) Regional meetings for design and development of open business models for tabling at the next council of CEOs meeting.
 * 45) * Australia / New Zealand meeting
 * 46) * Vancouver meeting
 * 47) Proposed schedule of OERuMC meetings
 * 48) Week of 27 July 2015 (Group site established, meeting convened to determine target outputs of working groups for the October OERu meetings in South Africa)
 * 49) Week of 14 September 2015 (Draft progress report of working groups outputs and discussion on agenda for OERu annual partners meeting)
 * 50) Week of 16 November 2015 (Post OERu partners meeting and wrap-up for the year.)

Minutes and decisions

 * 1) Attendance Jim Taylor, Irwin DeVries, Brian Lamb, Dave Lane, David Bull (viewer), Sarah Lambert, Marc Singer, Wayne Mackintosh. Apology: David Porter.
 * [1:25] Introduction and welcome.
 * 1) * Summarised the working group structure, composition and purpose of the OERuMC, namely to coordinate the activities of the working groups in implementing the 2015 operational priorities of the OERu strategic plan (pdf).
 * 2) * [2:12] Introduced and welcomed Dave Lane, the new Open Source Technologist at the OERF and acknowledged the platinum-level OERu partners who are contributing to this shared position, specifically: OER Foundation, Otago Polytechnic, Kwantlen Polytechnic University, University of Highlands and Islands and University of Southern Queensland.
 * 3) * [4:33]] Members of the OERuMC introduced themselves: Irwin DeVries, Jim Taylor, Marc Singer, [17:53] Sarah Lambert,
 * [9:27] Review allocation of 2015 KPIs
 * 1) * Resolved that each convenor will review the 2015 KPIs from the strategic plan and list those which are relevant to their respective working groups on the 2015 KPI allocations page to inform current working group objectives and activities.
 * 2) [11.20] Update and discussion of output targets for individual working groups.
 * 3) Strategic planning: Received the report from the May 2015 meeting
 * 4) * Noted the approval of the refined aims and objectives for the working group.
 * 5) * Incorporated the suggestion for an "action calendar" with key milestones for this OERuMC meeting
 * 6) * Emphasised the importance of product development for OERu and supporting strategies, including for example the introduction of a course development and delivery schedule (discussed as a separate agenda item in this meeting)
 * 7) * Noted the updates to the Quicklinks page and utility of the page as an access point for new members.
 * 8) * Recommended two regional meetings to design and develop open business models to be tabled at the 2015 meeting of the OERu Council of CEOs meeting in October.
 * 9) * Noted the role of the strategic planning group to act as facilitator for the co-ordination of working group activities through the OERuMC and liaison with the Council of CEOs and OERF Board of Directors.
 * 10) [18:55] Curriculum and programme of study
 * 11) * Reiterated the aim of the group to develop a coherent OERu programme of study with multiple exit points.
 * 12) * Noted the 2015 priority of the working group is to focus on developing a programme document for the OERu 1st year of study in conjunction with the potential streams arising from the OERu partner nominations to date.
 * 13) [20.06] Partner engagement
 * 14) * Noted that the two co-conveners of this working group will be meeting face-to-face on Friday 3 July 2015.
 * 15) * Observed the growth and popularity of the partner engagement working group within the OERu community.
 * 16) [21:16] Standing committee for credit transfer
 * 17) * Referenced the Credit transfer and course articulation guidelines tabled at the 3rd meeting of OERu partners.
 * 18) * Agreed to review the guidelines highlighting areas where more detailed feedback is needed with due recognition to the challenges of virtual mobility across international boundaries.
 * 19) * Suggested targeted technical feedback from sample of Registrars in the network.
 * 20) [23:30] Course approval and quality
 * 21) * Noted that the working group is negotiating dates for 1st 2015 meeting.
 * 22) * Recommended that new members joining the course approval and quality group review the draft quality guidelines published in the wiki.
 * 23) * Highlighted value of course blueprints in promoting quality elements at the design stage of OERu courses, and need to foster and support wider adoption by current and emerging OERu course designers.
 * 24) * Emphasised the need for improved access to information about current and active course developments to enable effective communication between OERu partner institutions, which is required for effective open peer review of the subject plans.
 * 25) [27:28] Technology
 * 26) * Noted continuation of regular monthly meetings of the technology working group
 * 27) * Noted that the working group will revisit aims and objectives in the light of progress in expanding capacity for the OERu community source model with the appointment of the new Open Source Technologist
 * 28) * Advised that Dave Lane will be joining the technology working group to support Brian Lamb as co-convener and to engender liaison with the new IT contact representatives from the platinum partners, who are contributing financially to the shared position, and who will be joining the technology working group.
 * 29) * Confirmed that the technology working group will work with representatives from the marketing group regarding integration of key support resources on the public OERu.org website.
 * 30) * Expressed appreciation for the developments and progress of the WordPress theme for course snapshots prototyped with the recent DS4OER course.
 * 31) [30:44] Course development and delivery schedule
 * 32) * Discussed the shortcomings of the historical practice of listing course nominations on separate wiki pages for each nomination year noting difficulties in monitoring the status of current developments and how this relates to the OERu programme of study.
 * 33) * Agreed that the OERu should create and maintain a single page in the wiki for the current course development and delivery schedule, which clearly identifies projected completion dates as well as the anticipated delivery schedule for the courses listed per quarter.
 * 34) * Agreed that the Quicklinks page should incorporate a link to the new course development and delivery schedule page.
 * 35) * Discussed the current practice where each partner assigns a Content Management System administrator who has password access to maintaining the respective course pages of partner institutions.
 * 36) * Noted that some partners who are not familiar with CMS technology have difficulties in maintaining and updating their pages.
 * 37) * Agreed to:
 * 38) ** Post a call to the OERu partner network for a dedicated Administrative volunteer to provide CMS support to work in parallel with the current system of partner autonomy to update pages.
 * 39) ** Work with representative from Thomas Edison State College who have a number of courses to list on the Website and use this experience to develop a self-help resource for maintaining and updating pages on the OERu CMS.
 * 40) ** Establish a CMS administrators group on groups.oeru.org to improve communication and support for this group.
 * 41) [40:10] Collaboration potential of the OERu network (rich discussion arising from experiences of OERu partners)
 * 42) * Discussed examples of collaborative development potential arising from shared interest in the network and complementary expertise and strengths of individual partners
 * 43) ** Noted discussions between Unisa and TESC around shared interests and collaboration potential arising through the OERu.
 * 44) ** Noted the collaboration in developing a research methods course between University of Wollongong and North-West University
 * 45) ** Noted the emerging project in Culinary Arts to develop a shared mOOC including Thompson Rivers University, Otago Polytechnic, Portage Collage and the BCcampus open textbook project in Culinary Arts.
 * 46) ** Noted the current development of an online Master of Education Degree at Thompson Rivers University, which includes a stream in Open and Connected Learning with the potential to incorporate OERu open courses in this area.
 * 47) ** Confirmed the principle of "paying learning forward" where more experienced partners can assist new partner institutions in designing open courses based on their experiences from OERu course developments. In turn, the new partners can pay their learning forward as new partners join the network thus scaling the benefits of cooperation in the OERu network.
 * 48) [50:41] 2015 Action Calendar
 * 49) * Reviewed the draft action calendar
 * 50) * Agreed to shift the proposed SCoPE seminar for inputs into the agenda for the 4th meeting of OERu partners to the 2nd week in September 2015.
 * 51) * Agreed to administer a short survey to determine the optimal time for running the next DS4OER course (to support partners with course development needs) taking into account academic workload, northern hemisphere summer holidays and the southern hemisphere academic calendar.
 * 52) * Agreed to have separate calendars for OERuMC related milestones and "Academic / Professional" development scheduling.
 * 53) * Agreed that OERuMC members will populate the action calendar with relevant dates, activities and milestones relating to working group outputs in preparation for the October partners' meeting.
 * [1:02:40] Discussed the new group software at groups.oeru.org powered by onlinegroups.net using the open source Groupserver software.
 * 1) * Summarised existing group lists maintained by OERu and challenges associated with the administration interface of Mailman for non-technical users as well as inappropriate use of non-free software for the open OERu community list.
 * 2) * Demonstrated the new groups.oeru.org site which runs on open source software and combines the functionality of an email list with a groups website that automatically archives emails, which are searchable via the web interface.
 * 3) * Noted that attachments are stored on the site avoiding the challenge of list recipients having to download attachments with the email.
 * 4) * Noted the ability to migrate archives from Mailman which would enable searching in the new site. Will investigate options for migrating the archives of the OERu Google groups site.
 * 5) * Noted that the interface and structure with links back to the active planning pages in the wiki is a valuable feature of the technology.
 * 6) * Noted (via simultaneous Chat discussion) that dudle.com will be explored as possible meeting planning tool.
 * 7) * Agreed that the OERu partners list on Mailman and the OERu list on Google groups will be migrated. A combined announcement list will be hosted on groups.oeru.org plus individual group lists to support communications for each working group rather than the use of personal emails. Working group conveners will be allocated administration rights for moderating their own working groups to simplify administration and the automatic generation of a public record of communications, which will be searchable.
 * 8) * Agreed that a planned and phased migration should be implemented with advanced notifications, support and opportunities to use this migration as a catalyst for dormant members to re-engage.
 * 9) * Agreed that conveners will serve as moderators of their respective working groups and will take responsibility for inviting the members of their working groups to join the list thus establishing personal rapport with new members of the list.
 * [1:31:24] Introducing discourse.org as community platform for OERu.
 * 1) * Discussed intentions to implement discourse.org as the new community.org.oeru site to support community building.
 * 2) * Noted the community building features of the technology as a discussion platform built for the "next decade of the Internet".
 * 3) * Shared the rationale that rather than using a third-party hosted service, the OERF will host the platform to gain first-hand experience of the technology, which will inform possible decisions about using discourse.org to support OERu learners in the future.
 * 4) * Agreed that we will use OERuMC members as an early prototype community to explore the technology.
 * 5) * Agreed that the OERu will adopt an incremental approach to introducing new technologies to avoid the risks of overloading individuals with having to learn how to use new technologies.
 * [1:34:50] Proposal to develop an induction mOOC for new participants: Getting started with OERu
 * 1) * Discussed ideas to develop an online induction course for new OERu partners and participants on how to get engaged with the OERu.
 * 2) * Noted the advantages of a coherent cohort working together in engaging with the OERu rather than just reading static pages in the wiki.
 * 3) * Agreed to share the development pages with members of the OERuMC and invite them to review and contribute to the development.
 * 4) Meeting adjourned at 12:39 NZST.

Action items completed

 * 1) Wayne to initiate the 2015 KPI allocations page and invite conveners to allocate the respective KPIs for their groups. Done --Mackiwg (talk) 05:34, 29 July 2015 (UTC)
 * 2) Working group conveners to schedule meetings of their OERu working groups before the next OERuMC meeting at the end of July 2015 to: 1) Determine or refine aims and objectives of their working group 2) Determine output targets of their working groups for the OERu partners' meeting in October 2015. Groups have convened. Due to summer vacation - partner engagement group have discussed outputs virtually on groups.oeru.org. --Mackiwg (talk) 05:44, 29 July 2015 (UTC)
 * 3) Create and maintain a single page in the wiki for the current course development and delivery schedule which clearly identifies projected completion dates as well as the anticipated delivery schedule for the courses listed per quarter. Consolidated course [OERu/Planning/Course_development_schedule|Course development schedule]] created. Invitations to update and review to be sent to OERu contact people. --Mackiwg (talk) 05:48, 29 July 2015 (UTC)
 * 4) Shift the proposed 2015 SCoPE seminar for inputs into the agenda for the 4th meeting of OERu partners to the 2nd week in September 2015. Done --Mackiwg (talk) 06:27, 29 July 2015 (UTC)
 * 5) Administer a short survey to determine the optimal time for running the next DS4OER course (to support partners with course development needs) taking into account academic workload, northern hemisphere summer holidays and the southern hemisphere academic calendar. Removed action item - OERF does not have capacity to facilitate another DS4OER before the partner meetings. --Mackiwg (talk) 06:37, 3 August 2015 (UTC)
 * 6) Plan and implement the phased migration of the current OERu lists to new platforms. In progress. --Mackiwg (talk) 06:27, 29 July 2015 (UTC)
 * 7) Conveners to serve as moderators of their respective working groups lists and carry out the steps listed under item 7 of the agenda above. Mostly achieved --Mackiwg (talk) 06:27, 29 July 2015 (UTC)
 * 8) Share the development pages of the "Getting started with OERu" induction mOOC with members of the OERuMC and invite them to review and contribute to the development. Posted on Getting started with OERu on Planning portal page --Mackiwg (talk) 06:32, 29 July 2015 (UTC)

Action items outstanding
(To be transferred to action items for the next meeting)


 * 1) Wayne to update the Quicklink to 2015 operational priorities once the July round of working group meetings has been completed.
 * 2) Post a call to the OERu partner network for a dedicated Administrative volunteer to provide CMS support to work in parallel with the current system of partner autonomy to update pages.
 * 3) Work with representative from Thomas Edison State College, who have a number of courses to list on the Website, and use this experience to develop a self-help resource for maintaining and updating pages on the OERu CMS.
 * 4) Establish a CMS administrators group on groups.oeru.org to improve communication and support for this group.
 * 5) OERuMC members to populate the action calendar with relevant dates, activities and milestones relating to working group outputs in preparation for the October partners' meeting.
 * 6) Plan and adopt an incremental approach for introducing discourse.org using OERuMC members as early prototype users.