Wiki source code of OSI-EDU-WG-notes-25feb2014
Last modified by Administrator on 2023/02/17 01:53
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | __**Participating**__ | ||
| 2 | |||
| 3 | Joseph Potvin | ||
| 4 | Patrick Masson | ||
| 5 | Wayne Mackintosh | ||
| 6 | |||
| 7 | = Discussion Notes = | ||
| 8 | |||
| 9 | == 1: Text of Short Announcement & Invitation to Participate == | ||
| 10 | |||
| 11 | * Please add your suggested text to this box: | ||
| 12 | |||
| 13 | >**Call for Participation in OSI's Working Group on Management Education**: //Let's work together to strengthen the quality of management amongst free/libre/open projects and portfolios, and amongst their governing organizations.// | ||
| 14 | > //We invite your collaboration towards improving the FLOW Syllabus. This is a peer-curated guide to the domains of knowledge that anyone involved in creating or maintaining Free/Libre/Open Works (FLOW). It is designed to help stakeholders to optimize value, to control costs, and to manage risk.// | ||
| 15 | |||
| 16 | __Points discussed:__ | ||
| 17 | |||
| 18 | * The announcement/invitation should be promotional and perhaps even somewhat provocative | ||
| 19 | * OSI has several conferences coming soon, and this can be highlighted | ||
| 20 | * Useful to have a twitter link, wiki link, presentation link | ||
| 21 | * Touch on different perspectives of Syllabus use (by educators; self-directed learners; specialist advisors whether software architects, lawyers, business strategists, etc.) | ||
| 22 | * For the educators, emphasize that the resources are optimised for re-use in, say: | ||
| 23 | ** http://www.merlot.org | ||
| 24 | ** http://www.ocwconsortium.org/courses/ | ||
| 25 | * That's to say, the FLOW Syllabus is not a course or a curriculum in and of itself, rather it is a venue for the community to identify the salient topics to be successful in the coordination of free/libre/open works; | ||
| 26 | * Keep the intro/invite short, link to a more complete statement | ||
| 27 | * Situate the FLOW Syllabus as one of the results of the direction that the OSI Board has decided to go | ||
| 28 | |||
| 29 | __Action__: Patrick will draft somethinga and circulate for input | ||
| 30 | |||
| 31 | == 2: OSI-EDU-WG Meeting Venu == | ||
| 32 | |||
| 33 | Discussion about the media of participation, and the Useful Coordination Links section http://osi.xwiki.com/bin/Projects/draft-flow-syllabus#HUsefulCoordinationLinks Some options for the primary meeting venue currently being looked at: | ||
| 34 | |||
| 35 | * https://togetherjs.com/ | ||
| 36 | * http://openmeetings.apache.org/ | ||
| 37 | * http://bigbluebutton.org/ | ||
| 38 | * http://www.ekiga.org/ | ||
| 39 | * others? | ||
| 40 | ...Let's continue to assess, but make the decision next week about the primary venue for OSI-EDU-WG weekly meetings. | ||
| 41 | |||
| 42 | Some criteria are: | ||
| 43 | |||
| 44 | * respect freedom of choice of users | ||
| 45 | * people in other fields will want other tools they are familiar with | ||
| 46 | * best if the solution does not requre yet another registration to something (nice example: http://www.openetherpad.org ) | ||
| 47 | * the venue we choose for OSI-EDU-WG will thus be getting an implicit thumbs-up | ||
| 48 | |||
| 49 | == 3: Management of Open Access; Open Learning, as a Topic == | ||
| 50 | |||
| 51 | Thoughts on a sub-section to the syllabus about the effective management of open learning intiatives, open access journals | ||
| 52 | |||
| 53 | * http://wikieducator.org/OERF:About | ||
| 54 | * http://oeruniversitas.org/terms-of-service | ||
| 55 | * Governance tagged items at http://www.evolllution.com/category/institutional_governance/ | ||
| 56 | |||
| 57 | Possibly a sub-section of "Methodologies Inspiring Our Approach" | ||
| 58 | http://osi.xwiki.com/bin/Projects/draft-flow-syllabus#HMethodologiesInspiringOurApproach | ||
| 59 | |||
| 60 | Yes this would be useful, BUT | ||
| 61 | |||
| 62 | * stick to FLOW Syllabus scope | ||
| 63 | * not more than a sub-section | ||
| 64 | * point to some best sources | ||
| 65 | * keep in mind that the audience is different than the main FLOW audience | ||
| 66 | * highlight similarities with free/libre/open, but realize that the starting point for most educators is different | ||
| 67 | |||
| 68 | == 4: Resource-Based Learning == | ||
| 69 | |||
| 70 | Thoughts on: "Resource-based learning" [[http:~~/~~/www.reusability.org/read/chapters/hannafin.doc>>url:http://www.reusability.org/read/chapters/hannafin.doc]] | ||
| 71 | |||
| 72 | * Generally there's an inverse relation between reusability and substantive focus | ||
| 73 | * FLOW Syllabus should point learners to resources, let learners and educators structure "their courses" | ||
| 74 | * This implies emphasis on primary sources, not on "learning activities". Let users of the syllabus design learning activities. | ||
| 75 | * Probably best to remove the "education philosophy" content (andragogy, case method, problem method) since this is out of scope for the FLOW Syllabus per se, and yet would attract a lot of debate amongst educators. It's interesting, but provides no specific net benefit for the FLOW Syllabus' explicit objectives. | ||
| 76 | * Reminder to provide points for each section on "learning outcomes" |