Hi!<br><br><div><span class="gmail_quote">2007/8/29, martin f krafft <<a href="mailto:madduck@debian.org">madduck@debian.org</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
also sprach Luca Brivio <<a href="mailto:lucab83@infinito.it">lucab83@infinito.it</a>> [2007.08.29.0159 +0200]:<br>> Since she aims to provide a truly complete and thorough<br>> introduction to all aspects of developing Debian packages,
<br><br>I don't want to discourage Miriam, but such a course is, IMHO,<br>impossible, unless she has several weeks. So instead, I suggest that<br>she should formulate a realistic goal and plan for much time to let<br>
people play around with the concepts taught.</blockquote><div><br>Yup, I know. I count on having some weeks, and my plan is to start from the very beginning and go ahead wherever we reach. If I find that the girls in LinuxChix are not interested anymore,then I'll stop there, but otherwise I plan on going slowly forward. I don't want to do the course in a hurry, I want them to be able to go their speed and develop their interest. My real goal with this is that some of them might decide to try to go NM and become DDs.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Miri, once you have an outline, I'd be happy to glance over it. I've<br>
been teaching professional Linux courses for 6 years, and I've<br>learnt a lot about volume of topics and to keep that low. It never<br>hurts to prepare more, but you should set the bar at the lower end.<br>Then, if you find to be progressing faster than expected, you can
<br>keep adding topics.</blockquote><div><br>I already have an outline, but it's really really really a pre-pre-alpha.<br><br><a href="http://women.debian.org/wiki/English/Courses/MaintainingPackages/">http://women.debian.org/wiki/English/Courses/MaintainingPackages/
</a><br><br>My plan is to develop a short part of theory for each step, then some small exercises so they can practice a bit, and then questions, as I cannot know in advance which doubts might have. There are lots of things I need to add there anyway, and probably reestructure some parts of it. I wanted to have it more advanced by now, but Kenta Cho got in the way, and Cultivation, then Fenix, and Pingus, ... Once all of Kenta Cho's games are finished, and they almost are, that should be my 1st priority :)
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I usually prepare a list of topics to cover and estimate the time it<br>would take for me to present it. Then, I multiply it by two, write
<br>the time down next to the topic, and select those topics that<br>I think *need* to be taught. I fill up, e.g. 3 days of a 5 days<br>course. At the end of the third day, depending on how far we got,<br>I might present the students with the list of topics and ask them
<br>which they want to go over for the remaining time. If it's been slow<br>up to now, I might wait until the end of the forth day. And so on.</blockquote><div><br>I don't really have a time limit here, so I plan to use that in my favour.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> this look like an outstanding chance for cooperating. While both<br>> contents and shape of her course and our handbook will in many
<br>> ways differ, I think there's nevertheless enough interesting room<br>> to make things together. I do mean writing, merging, editing and<br>> adapt text for our different purposes.<br><br>It would be good to find out the areas people were most interested
<br>in, topics that confused people, errors, and so on.</blockquote><div><br>Yup, I agree that should be the best. It'll make it easier to plan for future courses. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> (License-wise, Davide and I would at this moment adopt GPL2+<br>> - this won't forbid us to re-license some parts or put them in the<br>> public domain, but might clearly have some disadvantages -, but<br>> please tell me if you don't agree with us.)
<br><br>What's the + in GPL2+?</blockquote><div><br>I guess it means Version 2 or, at your option, any later version.<br><br>Miry<br><br></div></div><br>