Wiki source code of OSI-EDU-WG-notes-25feb2014
Last modified by Administrator on 2023/02/17 01:53
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
6.1 | 1 | __**Participating**__ |
| |
1.1 | 2 | |
| |
6.1 | 3 | Joseph Potvin |
| |
7.1 | 4 | Patrick Masson |
| |
6.1 | 5 | Wayne Mackintosh |
| |
3.1 | 6 | |
| |
6.1 | 7 | = Discussion Notes = |
| 8 | |||
| 9 | == 1: Text of Short Announcement & Invitation to Participate == | ||
| 10 | |||
| |
5.2 | 11 | * Please add your suggested text to this box: |
| |
3.1 | 12 | |
| |
4.5 | 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.// | ||
| |
4.1 | 15 | |
| |
4.5 | 16 | __Points discussed:__ |
| |
4.2 | 17 | |
 |
7.2 | 18 | * The announcement/invitation should be promotional and perhaps even somewhat provocative |
| |
4.5 | 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 | ||
| |
4.2 | 28 | |
| |
6.1 | 29 | __Action__: Patrick will draft somethinga and circulate for input |
| |
4.2 | 30 | |
| |
6.1 | 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 | |||
| |
5.1 | 35 | * https://togetherjs.com/ |
| |
2.1 | 36 | * http://openmeetings.apache.org/ |
| |
5.1 | 37 | * http://bigbluebutton.org/ |
| |
2.1 | 38 | * http://www.ekiga.org/ |
| 39 | * others? | ||
| |
5.1 | 40 | ...Let's continue to assess, but make the decision next week about the primary venue for OSI-EDU-WG weekly meetings. |
| |
2.1 | 41 | |
| |
5.1 | 42 | Some criteria are: |
| |
5.2 | 43 | |
| |
5.1 | 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 ) | ||
| |
6.1 | 47 | * the venue we choose for OSI-EDU-WG will thus be getting an implicit thumbs-up |
| |
4.2 | 48 | |
| |
6.1 | 49 | == 3: Management of Open Access; Open Learning, as a Topic == |
| |
5.2 | 50 | |
| |
6.1 | 51 | Thoughts on a sub-section to the syllabus about the effective management of open learning intiatives, open access journals |
| 52 | |||
| |
5.1 | 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/ | ||
| |
4.2 | 56 | |
| |
5.1 | 57 | Possibly a sub-section of "Methodologies Inspiring Our Approach" |
| |
1.1 | 58 | http://osi.xwiki.com/bin/Projects/draft-flow-syllabus#HMethodologiesInspiringOurApproach |
| |
4.2 | 59 | |
| |
5.1 | 60 | Yes this would be useful, BUT |
| |
5.2 | 61 | |
| |
5.1 | 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 | ||
| |
4.2 | 67 | |
| |
6.1 | 68 | == 4: Resource-Based Learning == |
| |
5.2 | 69 | |
| |
6.1 | 70 | Thoughts on: "Resource-based learning" [[http:~~/~~/www.reusability.org/read/chapters/hannafin.doc>>url:http://www.reusability.org/read/chapters/hannafin.doc]] |
| 71 | |||
| |
5.1 | 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. | ||
| |
7.5 | 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. |
| |
7.6 | 76 | * Reminder to provide points for each section on "learning outcomes" |