Agenda
1982
Comment:
|
2068
|
Deletions are marked like this. | Additions are marked like this. |
Line 20: | Line 20: |
||[[Cprofitt]]||Course Structure - Conversation (should I take lead in this area?)|| |
General Agenda Items and Proposals
PLEASE COME TO THE MEETINGS PREPARED.
This means:
- If there is an issue for the project add it to the agenda.
- Agenda items then should be discussed "informally" on #ubuntu-learning or using the mailing list.
- Ideally, meetings then are for decision making, project votes.
- Agenda items that require more then 5 minutes of discussion may need to be deferred.
Who |
What |
Licensing, restricting the use of CC-NC works to avoid contamination, using CC-BY-SA for all works, rules for re-licensing, how to contact creators (re-licensing isn't allowed to happen automatically without copyright assignment) |
|
Themeing / Naming of site |
|
Content - How do these various teams contribute ? Each team gets a course ? |
|
Next steps? What still needs to be done before we can tell teams they can start using Moodle |
|
We need to develop team governance. |
|
Opinions on the Moodle Course - Good, Bad or Other. |
|
Need for Moodle Instructors to guide other teams. |
|
Approval process of courses? |
|
Course Structure - Conversation (should I take lead in this area?) |
Discussion
- Governance - How does someone join the team ? How does one resolve grievances / complaints ?
- Should we identify team members with the use of voice ? Another way ?
- Interactions with other teams - To reduce confusion , at least initially, I suggest we establish "official" liaisons -
- Who shall contact what member of which teams and who shall those teams contact with questions ?
- Listing of liaisons on wiki page ?
Meeting Archives
June 2nd 2009: Community Council Discussion (see 22:00 timestamp)
Learning/Agenda (last edited 2010-03-14 01:27:44 by ptr)