(18:00:58) billycina: we all ready to rock and roll?
(18:01:09) billycina: :)
(18:01:10) billycina: ok
(18:01:28) billycina: so, i had 2 things to cover on the agenda item today:
(18:02:04) billycina: 1. tetet will provide us with a tutorial of how to use the LP bluprint in order to make revisions of the desktop course for hardy
(18:02:37) billycina: this will enable us to ensure that changes made tot he course are made following the same guidelines as ubuntu releases
(18:02:56) billycina: 2. An update regarding the Connexions toolchain from Belinda Lopez
(18:03:15) billycina: unfortunately Belinda could not make it this week - so this will be done int he next session
(18:03:32) billycina: does anybody have anything else they wish to cover before i hand over to Tetet?
(18:03:43) billycina: ok
(18:03:48) billycina: tetet: floor is yours
(18:04:02) TeTeT: On the Launchpad Blueprints or specifications:
(18:04:14) billycina: blueprints
(18:05:05) TeTeT: they do have people assigned to them and can be of different priority and status
(18:05:31) TeTeT: the blueprints are handy to monitor progress and see where work needs to be done
(18:05:52) TeTeT: I've started writing a few blueprints for the hardy update, please have a look at https://blueprints.edge.launchpad.net/ubuntu-desktop-course/
(18:06:20) TeTeT: the 'hardy-update' is the core blueprint for getting the course material updated for 8.04
(18:06:39) sidelil [n=davide@extern-halls-wl-4.soton.ac.uk] entered the room.
(18:06:44) TeTeT: when you take a look at the hardy-update spec in detail at https://blueprints.edge.launchpad.net/ubuntu-desktop-course/+spec/hardy-updatehttps://blueprints.edge.launchpad.net/ubuntu-desktop-course/+spec/hardy-update
(18:06:46) TeTeT: sorry
(18:06:48) TeTeT: https://blueprints.edge.launchpad.net/ubuntu-desktop-course/+spec/hardy-update
(18:07:11) TeTeT: you see in the central column a brief description of what the blueprint is about
(18:07:22) TeTeT: followed by the dependency tree
(18:07:44) TeTeT: I would like to setup a separate blueprint for each chapter
(18:08:01) TeTeT: make that, chapter update
(18:08:24) billycina: makes sense
(18:08:32) TeTeT: I've assigned the hardy-update blueprint to UDS intrepid
(18:09:03) TeTeT: this would reflect roughly when I think we should have finished the blueprint's implementation: end of May, one month after Hardy release
(18:09:16) billycina: what does that mean?
(18:09:21) billycina: that's the deadline
(18:09:28) billycina: ?
(18:09:34) TeTeT: that the course is updated for 8.04 by that time, yes
(18:09:38) billycina: ok
(18:10:28) TeTeT: a neat feature of the blueprints is that you can assign bugs to them as well
(18:10:56) TeTeT: for example, the update-introduction blueprint is now set to not implemented
(18:11:33) TeTeT: when we move forward and the intro is updated, it will become implemented. Any information that is in the introduction and is not valid for 8.04 would then be filed as a bug vs the blueprint
(18:11:47) billycina: i am trying to see if within each bluprint, we can set up sub-requests?
(18:11:50) TeTeT: the blueprint's assignee than has the chance to see all the problems reported
(18:12:01) TeTeT: billycina: yes, blueprints can be hierarchical
(18:12:08) billycina: so in lesson 1
(18:12:09) volksman left the room (quit: "ChatZilla 0.9.81 [Firefox 2.0.0.12/2008020121]").
(18:12:17) billycina: we could have 10 blueprints?
(18:12:19) TeTeT: I thought about hardy-update -> (intro, lesson1, lesson2,....)
(18:12:25) billycina: yep
(18:12:53) TeTeT: any chapter specific blueprint can also have more, if we want to split the tasks even more, for example intro -> (text.images) or some such
(18:13:02) TeTeT: though I feel that this is overkill
(18:13:07) ***billycina nods
(18:13:18) TeTeT: any thoughts or questions on the overall idea of using blueprints that way?
(18:13:26) billycina: sounds good to me
(18:13:40) TeTeT: I believe blueprints should also be used for doing translations
(18:13:45) billycina: ?
(18:14:00) TeTeT: so start a translation by writing a blueprint, e.g. 'Translate Desktop Course to Klingon'
(18:14:07) TeTeT: then assign your branch to the blueprint
(18:14:16) TeTeT: just an idea
(18:14:42) billycina: no view on how this makes it better than current branching system
(18:15:00) TeTeT: it's not a replacement, it's just another piece of Launchpad being used
(18:15:31) billycina: ok
(18:15:49) billycina: so how do we assign people to issue and review blueprints
(18:15:58) billycina: specifically for the desktop course now?
(18:16:08) TeTeT: on the blueprint page, actions -> change people
(18:16:36) billycina: ooooh so i can pick anyone :)
(18:16:42) TeTeT: the approver for example needs to move the definition forward
(18:16:52) TeTeT: well, would be great if people volunteer ;)
(18:16:58) billycina: sure :)
(18:17:08) MagicFab left the room (quit: Remote closed the connection).
(18:17:29) TeTeT: any questions?
(18:17:44) MagicFab [n=magicfab@ubuntu/member/magicfab] entered the room.
(18:18:03) TeTeT: guess we can move on then
(18:18:25) billycina: ok - thanks torsten :)
(18:18:45) billycina: i will send an email to the training lists asking people to start witht his process for hardy
(18:18:53) billycina: I will attach this log
(18:19:21) TeTeT: ACTION: billycina to send blueprint information for hardy update to mailing list
(18:19:22) billycina: then people will understand what needs to be done
(18:19:38) TeTeT: ACTION: TeTeT sets up blueprints for all chapters
(18:19:40) billycina: anybody want to discuss anything else?
(18:20:05) billycina: ok - so we will close the meeting
(18:20:12) billycina: bye all
(18:20:19) Syntux: bye.
(18:20:35) TeTeT: bye