As discussed in our planning sessions, a preliminary form of our documentation should be prepared and present on this repository's wiki no later than Friday, April 22nd, 2016. I am responsible for writing and creating the documentation.

As discussed in our planning meetings, the project would need to have a presence on the Sugar Labs wiki, along with other past RIT projects for the Sugar / XO projects. I now have an account on the Sugar Labs wiki, so I am able to log in and make changes to the wiki.

As the documentation lead, I am responsible for getting our project's presence on the wiki by April 26th, 2016.

I think it would be a good thing to refactor the code to meet the PEP 8 guidelines.

There should be some kind of static, fixed high score number saved to disk that is displayed to the user somewhere. It's updated every time the user beats their previous best score of pizzas made.

Going to create blank pizzas, five toppings and 1 & 2 cut overlays

@wilfriedE has been documenting some of the project with Python docstrings. None of us in the project are extremely familiar with them or if you can generate a "pretty page" for them, like you might with JavaDocs HTML pages. Part of this task is for me to research if it's possible to generate some kind of page like this from the docstrings that are in the code.

If this is possible, we can use GitHub pages to host the docstring pages for reference later. This can be considered a "stretch goal". It may not be possible to do this, but if so, it would be nice to have.

Nothing happens when you click buttons. It works properly on a regular machine, however when running on an XO nothings happens.

This logo will be used for the Sugar images in the Sugar environment as well as on the wiki for our project.

When we try building and deploying the game on the XO, the game will present a black screen without any usable interface. This is not the case when the game is run on normal hardware, like Linux desktop environment (on my system, at least). It seems like there are unknown factors contributing to running the game on the XO / Sugar that are preventing us from running the game.

Hey, I see you're using Sugargame 1.1, there's a new 1.2 available which has a few fixes.

The last milestone for the project is to optimize the game so that it runs efficiently (WYSIWYG) on an XO laptop. As of now, the game is sluggish on one of the XO laptops. With further optimizations applied, the game should be able to run at a decent speed on one of the XO laptops.

One item to complete for the game is to add levels that increase by difficulty or some other way as you "rank up" by making the right pizzas.

I'll work on making up the art assets we need for 4/26

As an end goal for the project, we want to deploy this app on the SugarLabs download portal, activities.sugarlabs.org. I am responsible for following up on this task.

This can only be completed once the game is in a "finished" state.

Summary

The HFOSS Fall 2016 class is resuming development on PyCut to expand the idea and develop it further – we'd like to coordinate with the downstream project to merge their changes and improvements back here to the upstream.

Analysis

The team working on PyCut for the HFOSS class are @tcreeds, @PatrickGormley, and @adf5051. The downstream repo is forked by tcreeds here. The scope of their changes is not yet clear, but some of the more abstract goals are to close out existing issues in this repo (#10 and #33), a more strict adherence to some of the NYS curriculum goals (detailed here), and some of the "to-do" list of tasks we determined towards the end of our project semester. This is not an exhaustive list or limiting factor to what can or cannot happen. 😄

If needed, @wilfriedE and myself can provide commentary to questions about design or implementation of the existing code (and maybe @spg1502 too if he's still hanging around and interested).

Whether the new team would like to submit pull requests back upstream in small changes (and benefit from any feedback by past team members) or submit everything in a big PR at the end of the semester is up to the current team to decide. In either case, upstream is receptive to supporting the work happening downstream whichever way they choose!

This issue can be a place for any current team members to get feedback or ask questions too.

A final presentation is needed for the HFOSS course. Our presentation slot is tentatively scheduled for May 11th, 2016.