1. Logistics

Tuesday will probably work out better for the weekly conference call.

Here's a suggested initial target:
Wed 08:00 am in AUCKLAND
Wed 05:00 am in BRISBANE  
Tue 19:00 pm in LONDON  
Tue 14:00 pm in NYC  
Tue 11:00 am in SFRAN

• Joseph will test this out via Doodle 
• We could potentially alternate call times to accommodate time zone differences

2. Notes from Previous Meeting

• http://osi.xwiki.com/bin/Projects/EDU-WG-notes-31jan2014
• No revisions suggested.

3. "Form Follows Function"

(a) Venue for Syllabus

• http://osi.xwiki.com/bin/Projects/draft-flow-syllabus
• The OSI Board wants to use osi.xwiki.com as its platform for collaborative content and discussion of issues;
• Refined content is then pushed to opensource.org website
• The "current version" can be occasionally updated. The dev environment remains the wiki.

(b) What's the best structure and environment for us to maintain the master?

Maybe breaking up the current long page and use of a multi-page table of contents extension would be useful but first...
This needs to be asked as: "What is the most useful structure and environment to instructional designers?"
If it's to be a guide to "best-of-breed" resources, it should not expand too much.
We need to refine "what the resource needs to be".

• Need to write specific learning objectives for each module;
• Each section should follow a template, with guidance from instructional designers 
• This syllabus provides a quality-control and structuring service that educators can use in preparing their online learning, online campuses, open educational resources, open textbooks. That's to say the educational specialists should be able to rely on this OSI-coordinated syllabus output, as input to creating their courses;
• The WG thus needs the participation of educators to advise on the most useful generic structure and process to supply this content as learning objects, for their use in creating their delivery
• The focus is practical implementation of free/libre/open, and how to introduce it in organizations

Meanwhile:

• Tagging items of course would be useful
• Should change to CC-by license, to be consistent with majority of free/libre/open educational content

Note that Github is popular for the technically inclined, but:

• Github is limiting for diverse users. We need to ensure accessibility for the less technical.
• We want to advance this as a genuine OSI-hosted effort, so OSI would visibility if this was located on Github
• It is also important to retain the OSI visibility avoid open-washing. 
• It's valuable to ensure the primary presence of OSI as "the trusted aggregator" of the legitimate free/libre/open educational material (i.e. not "open-washed" material that would confuse)

(c) Working Group Participation

• The OSI-EDU-WG can be comprised of several "Theme-Based" Subject Matter Experts and Content Contributors
• Example 1: "License Compliance Theme" with a community of lawyers;
• Example 2: "Project Management Theme" with a community from the PM discipline;
• Follow-up thought by Joseph (after the meeting): I think it might be strategic to NOT segregate the WG into discipline ghettos (lawyers, economists, project management methodologists). The risk is that they end up taking past each other. The WG themes are currently topic-based and inter-disciplinary. Before we break the WG into separate working communities by professional field, let's assemble the initial interdiscplinary working group.  Granted that interdisciplinary discussions are inherently harder to do, but they force us to address the very issues that make them difficult.
• We need an initial draft an email explaining the FLOW Syllabus resource << Joseph will provide an initial description for the introductory emails
• We should say where the initial funding is from (Joseph will check on permission)
• The intro email invite participation via the weekly teleconf call
• Seek content contributions, sharing of training materials, build a working consensus on an approach to documentation and dissemination