Skip to content

Milestones

List view

  • Playable prototype (for the children)

    Get game to a playable state for play-testing with actual 1st/4th graders for Wens 5/14 2014

    Due by May 14, 2014
    •2/2 issues closed
    100% complete0 open2 closed

  • Finished Product

    (The following is only relevent to contributors in Remy DeCausemaker's HFOSS class at RIT) Finished Project 20% Add a fully-fleshed out entry and link to your project information to this wiki page (Use the examples already there as a standard for the quality of your addition): http://wiki.sugarlabs.org/go/Math4Team/RIT/Projects Your grade here will be derived from the following factors (adjusted for progress over the quarter): Is the code clearly licensed under an OSI-compatible license? Does your source repository contain clear written instructions for future developers? (i.e. How to setup their environment to work on your project) What TODO items are left to do? Does it work on python on a normal machine? Does it work on the OLPC? Code quality and git commit history. Quality of the wiki entry at sugarlabs.org

    Due by May 21, 2014
    0% complete0 open0 closed

  • Final Presentation

    (The following is only relevent to contributors in Remy DeCausemaker's HFOSS class at RIT) Final Presentation 20% Your presentations should last 10 minutes with another 5 minutes for discussion. Your team will need to present from the front of the room. You can either: 1) Make your slides web-accessible, or 2) Email slides as a .pdf to your instructor. Every member of your team needs to speak for a roughly equal amount of the presentation. Be prepared. Give a demonstration of your project. How does the code work? What are some of the best pieces of software you wrote? Why? What are some of the worst pieces? Why? What stumbling blocks were there? What successes? What would you have done differently? What would you have worked on if you'd had more time? Your Presentation will be graded on aspects such as: Presentation Skills (Projection, Posture, Body Language) Grammar/Spelling Design (colorschemes, graphics, look/feel) Timing (significantly over/under time limit) Content (quality/quantity of information) Adherence to Guidelines (Did you hit all the bullet points in this list?)

    Due by May 21, 2014
    0% complete0 open0 closed

  • Final Evaluation

    (The following is only relevant to contributors in Remy Decausemaker's HFOSS class at RIT) Team Evaluations 15% -200-1000 words per teammate. -Indicate what they did to contribute to the project. -What skills did they pick up this semester? -What skills should they develop further? -Give a numeric score (1-10) for them and justify it. -These must be emailed to the professor They will remain private.

    Due by May 21, 2014
    0% complete0 open0 closed

  • Starting up design

    We want to start building levels, nailing down mechanics, etc... I'm not going to fill this out until we get something running on the exo though

    No due date
    •1/1 issues closed
    100% complete0 open1 closed

  • Base Engine

    Our hope is to get an engine set up as quickly as possible so that we can focus mostly on design, art, adding levels, etc... With that in mind, we want to keep things as simple as possible. - A starting menu + level select - A way to import levels from files - Levels themselves (tile-based) Keeping the engine very very light and modular will allow us to expand on these things as needed.

    Due by April 30, 2014
    •9/9 issues closed
    100% complete0 open9 closed