Team Proposal

List your other team members below:

Nicholas Gallagher - npg3253@rit.edu - Handle: MrNex
Josh Davis - jad2828@gmail.com - Handle: Dtendr

Which Project did your team choose?

My team chose to work on a project called "Duality" (https://github.com/AdamsLair/duality) .

2-liner description of the project?

"Duality" is a "2d Game Development Framework" which appears to be very similar to a game engine.  Specifically, it reminds me of "Unity" (http://unity3d.com/) .

"Duality" is programmed in C# and implements OPENTK (http://www.opentk.com/) which wraps OpenGL, OpenCL, and OpenAL.

What will each team member's role be?

Team roles will be determined.

Source Code Repository URL?

https://github.com/AdamsLair/duality

List your upstream Mentor's below:

Adam from "AdamsLair" - adam@adamslair.net

Other mentor's from Github include: fireDude90 - fireDude90@gmail.com

and BraveSirAndrew - andrew@batcatgames.com

How will you communicate with them?

Adam prefers to be contacted via his forums here: http://forum.adamslair.net/

The others we will contact via Email and IRC if possible.

The Easy Parts

• Judging by his contribution, the main developer Adam seems extremely invested in this project, and he has done a good job organizing everything, especially information about current issues.
• My teammate and I already know each other and live together, so communication between us should be very easy.
• Being that my teammate and I have both programmed extensively in C#, we should be pretty familiar with the programming used in this project.

The Hard Parts

• We will have to juggle a lot of other work on top of this project.
• The fact that this is a game engine implies that it is very complex.
• We don't know how picky or trusting the main developer is about his project, so he may be reluctant to how we want to change things.

How will you overcome both?

Overcoming obstacles will involve communication within our team, but also with the contributors.  It will also require a lot of diving into the code.  Lastly, I think we will need a positive attitude and some good structure and organization.

Milestones:

1. Familiarize ourselves with the code, contact Adam or contributors with specific questions
2. Address exactly what we want to work on to narrow down and be more specific
3. Make sure that what we want to work on is worth the time and effort
4. Actually start working on the issues - this will likely be a different process entirely
5. Get some commits up
6. Continue conversation to make sure everything is coordinated
7. Eventually finalize what we have done
8. Testing changes
9. Reflect? Maybe?
10. Profit.