[05:42] 'lo all [06:04] bodhizazen: hello [06:56] doctormo, https://wiki.ubuntu.com/Learning/Structure [07:01] *reading* [07:08] Looks like a good draft bodhizazen [07:10] thank you for looking at it doctormo [07:10] I would have teachers and students as "users" and have both groups as open launchpad groups with launchpad based mailing lists. I'd then have contributors (translators, artists, video producers etc) in a moderated group like devs with commit access, these would have a mailing list. Finally I'd have an administrators group of admins (no mailing list) who publish the work in revisions as required and then the council who are here for [07:11] dispute resolution. [07:11] well, admins need a mailing list, IMO, it they do dispute resolution [07:12] admins don't do dispute resolution, that's the council. admins manage to content, they're like the technical commity. [07:12] users (teachers, students) >> contributors >> admins >> council [07:12] i see [07:13] I would tend to have admins and council be the same people [07:13] All members of the council will be admins, all admins are contributors and everyone may or may not be teachers and students. [07:13] I am not familiar enough with moodle roles to know for sure [07:14] We can fold them into the same group while the project is small < 100 people total, but if we get bigger, I'd suggest having it there as an optional expansion to the structure. [07:14] and I am hoping for some additional input =) [07:15] Also, all admins/council members must be contributors and all contributors have to have pasted the moodle moodle class. [07:16] This forces me to have to do the class and pushes us to organise internal training of members. === pleia2 changed the topic of #ubuntu-learning to: Ubuntu Community Learning Project | https://wiki.ubuntu.com/Learning | Next Meeting: Tuesday July 20th @ 9pm EDT (01:00 UTC July 21th) | Support in #ubuntu [23:10] hello peoples [23:12] hey Vantrax [23:20] i didnt get much time to work on this site over the weekend >.<