Skip to content

Latest commit

 

History

History
121 lines (74 loc) · 4.3 KB

final.md

File metadata and controls

121 lines (74 loc) · 4.3 KB
Raw

HFOSS final project

Goal

Your final goal is to write an Activity that targets US 4th grade math curriculum.

Resources

You can try to pick something to address from this curriculum chart on the Sugarlabs Wiki. You are not restricted to using this, but it is an option.

Speaking of, have at least one team member request an account for that wiki. This is a manual process so please begin right away.

You may find the NY State math standards helpful. Pay special note to the 4th grade curriculum (p55-66 in the PDF from circa 2019).

A previous version of the standards has been archived and may be useful for comparison.

Though out-of-date in several respects, this guide to developing a desktop activity for the XO by IBM is a good general overview to using a separate development environment

The Sugarlabs Github organization holds more recent documentation for contributing to Sugar This provides pointers for desktop and web activities.

You may wish to start by building some easy first project examples, Hello World and Sugar quickstart

Steps

Brainstorm project ideas individually

We'll use these ideas for team formation.

Form a team.

Seek a diverse set of skills in your team.

Form around one or two project ideas.

Propose a project.

Be sure to note what curricular components are included. Assign roles to team members.

Track work-in-progress

Create issues. Make commits. Document your work in your journals.

Demonstrate some proof-of-concept

Demonstrate a prototype

Present and demonstrate final game

Team Assessments

  • 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 instructor They will remain private.

Final Presentation

Your presentations should last 10 minutes with another 5 minutes for discussion.

Your team will need to present from the front of the room.

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?)

Finished Project

  • 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:

  • 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 Sugar?
  • Code quality and git commit history.
  • Quality of the wiki entry at sugarlabs.org