Planet
navi homePPSaboutscreenshotsdownloaddevelopmentforum

Changes between Version 11 and Version 12 of pps/HowTo


Ignore:
Timestamp:
Jan 28, 2010, 10:39:19 AM (14 years ago)
Author:
bknecht
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • pps/HowTo

    v11 v12  
    11= PPS !HowTo =
    22
    3 You want to know what it takes to make a PPS for a whole semester?
     3You want to know what it takes to organize the Orxonox PPS for a whole semester?
    44
    5 Well, you will have to be able to answer many questions by the PPS students. You should either know the Blender by heart or know a lot of details about the code, the framework of Orxonox.
     5Well, you will have to be able to answer many questions from the PPS students. You should either know Blender by heart or know a lot of details about the code, the framework of Orxonox.
    66
    7 == Preparation ==
     7This !HowTo is full of (insider) jokes and puns, so you shouldn't take it too seriously. Please don't be offended, if there is a comment about how lazy the PPS students are. We know that we exaggerate.
     8
     9== Preparation (a month before semester start) ==
    810 * Define a general style for the content, otherwise the results will differ too much.
    911 * Offer certain projects with very clear tasks and some with a lot of freedom.
     12 * Already define a provisional date for the fondue/grill.
     13 * Book the computer room and the room for the tutorial phase early.
    1014
    11 == Tutorial Phase ==
    12  * Don't make long presentations... they won't listen anyway.
    13  * You will NEVER have enough time. No way.
     15== Tutorial Phase (first three weeks) ==
     16 * Don't make long presentations... the students won't listen anyway.
     17 * You will NEVER have enough time to finish everything. No way.
    1418 * Students which lose their handouts won't get any points.
    1519 * Make sure, that the students know where to get information, so they don't always have to ask you.
    1620 * Always tell them, that when they get stuck, they should ask you and not just try lots of ways to find a way out. Sometimes you solve their problems with three clicks and they have been working on it for three hours.
    1721 * Everybody has to commit a piece of code or a first model in the early weeks to learn about the revision control system SVN.
     22 * Inform students about the rough timetable. Tell them about the presentation, the pizza nights and the fondue/grill.
    1823
    1924== Coding/Modeling Phase ==
    20  * Force the students to commit more and more often!
    21  * Students which don't know SVN after 2 months won't get any points.
    22  * Send more mails to tell them what's going on, whats next and that they are already behind the schedule. (Be sure they read them)
    23  * Students are never finished... invent more tasks ;)
     25 * Motivate/Force the students to commit more and more often!
     26 * Students who don't know SVN after 2 months won't get any points.
     27 * Send more mails to tell them what's going on behind the scenes, whats next and that they are already behind the schedule. (Be sure they read them. It helps when it's written in German.)
     28 * Students are never finished... find more tasks if they want to go home early ;-).
     29 * Do never prepare something for the students during the lessons. Just work before and after the lessons.
    2430
    25 == End Phase ==
    26  * Most important: Specify location of presentation EARLY! Write to Reto Kreuzer to ask for a room. Write him a mail about 3 weeks before the presentation.
    27  * Make the poster early. Start the design 3 weeks before the presentation. Print it at the [mailto:repro-zentrum@ethz.ch Reprozentrale] about 10 days before the presentation. Print approximately 15 posters à A3-size. Just write an email with the link to the poster on our server.
     31== End Phase (three weeks before presentation) ==
     32 * Most importantly: Specify location of presentation EARLY! Write to a BIWI secretary to ask for a room. Write her a mail about 3 weeks before the presentation.
     33 * Make the poster early. Start the design 3 weeks before the presentation. You should write to Pascal Graf early enough so he can come up with a design and make some free time to implement it.
     34 * Print the poster at the [mailto:repro-zentrum@ethz.ch Reprozentrale] about 10 days before the presentation. Print approximately 15 posters à A3-size. Just write an email with the link to the poster on our server.
    2835 * Alternatively you can print at ETZSPEZ via VPP2: Find more information [http://computing.ee.ethz.ch/ETZSPEZ here]. Also: I figured out, that PDF does not seem to work, so send the job with PS. Also you will have to cut away white edges if you don't want them. Pricing can be found on the aforementioned website.
    2936 * Write an ad for the Blitz. Remember that the last Blitz is published two weeks before semester end (two weeks before the presentation). The deadline for articles will be one week before (so three weeks before presentation). So be quick enough.
    30  * Involve the students with general project tasks (printing the poster, making ads, organizing a room...)
    31  * Do never prepare something for the students during the lessons. Just work before and after the lessons.
    32  * Be sure to reserve some evening and nights to work on Orxonox. You should also drag as many students to those evenings so they work more and you don't have to do all the work.
     37 * Involve the students in general project tasks (printing the poster, making ads, organizing a room...)
     38 * Be sure to plan in some evening and nights to work on Orxonox. You should also drag as many students to those evenings so they work more and you don't have to do all the work for them.
    3339 * On these evenings you should buy pizzas for everyone. Be sure to order them early because the pizza guy is normally quite slow and they don't know where Physikstrasse 3 is (the address of the ETL building) or how to get there. The zip code is 8092! There are several places in Zürich to order a pizza.[[BR]]We recommend Domino's Pizza. Buy 1/2 - 2/3 Dominator Pizzas for each Student (and yourself, of course). Call them (0844 12 12 12) and choose 2, 1, 1 to get connected to the new branch at Universitätsstrasse 11! Since it's so close, you can collect your 'zza at the Universitätsstrasse to get reduction!
    3440 * Also do not buy too much beer. You and the students need to be fit to code. We rather suggest a coke as perfect beverage to the pizza.
     
    3945 * You should probably have a presentation branch right two or one week(s) before the presentation, because then the hacks are implemented and we do not want them in our trunk, do we?
    4046 * The presentation itself should be a great show. Of course everything is going to be hacked, but relax as long as it looks good at the presentation. ;)
    41 
     47 * Go drink a beer with the students after the presentation.