Project Guidelines & Timeline

📄️ Part 1: Project Idea Brainstorming

Overview

📄️ Part 3: Informal Pitch to Club Leadership

Why create an informal pitch?

📄️ Part 4: Technical Design Doc/Product Spec + Learning Phase

NOTE: These two sections of Part 4 are especially important because it dictates your team’s project design and determines whether you are capable of contributing code once your team starts developing. Specifically for the learning phase, if you want to code, you must ensure you learn enough about the language you plan on coding in before you dive into it. See Learning Phase for more info.

📄️ Part 5: Club-wide Spec Presentation

Now that you’ve finished planning your project and completed your spec, it’s time to present your product specification to the club! The purpose of a club-wide spec presentation is to inform your fellow club members about what your team is hoping to accomplish with your project and to receive feedback on what your team may have overlooked and what they can improve upon.

📄️ Part 6: Github Development Setup

Now that you’ve fleshed out the design of your project, it’s time to set up your GitHub repository so you can begin coding.

📄️ Part 7: Github Issue Brainstorm

NOTE: Going forward, we are assuming that after your spec is done, your repo is created, and your team has begun development and set up the initial file structure/skeleton of your project. Since every project is different, if your team is struggling with codebase setup, contact the Tech Team.

📄️ Part 8: Development Phase

Here’s our workflow guide on how to properly contribute code to your project

📄️ Part 0: Logistics