Copyright © 2014 - MIT 6.470 - All rights reserved
There are certain milestones due by certain dates that we require you to turn in on Stellar. This is both so you will have a development schedule you can follow as well as so we can track your progress
This year in 6.470, we will be using Git/Github for milestone submissions and to make it easier for you to turn in your source code. Every team is expected to have a Git repository hosted somewhere accessible on the Internet. If you’re not familiar with Git, check out the lecture given on Tuesday, ask on Piazza, or come to office hours.
In order for the staff to access your repositories without making them public, we will create repositories for you in the mit6470 organization. These repositories will automatically be private to your team and the 6.470 staff. The repositories will be on github.mit.edu, so you will need MIT certificates to access them. Cross-registered students should be able to get an MIT certificate after getting an Athena account.
To clone the repo from github.mit.edu, you must generate and add an ssh key to your github.mit.edu account and clone through via SSH not via HTTPS:
git clone email@example.com:mit6470/<repo-name-here>.git
If you have already created a Git repository and started developing out of it, that's ok! We're only requiring you to update the repo we give to once for each milestone. Please email us at firstname.lastname@example.org if you have any questions, or post on Piazza
We will email you when we’ve created your repository. You can use this repository as you develop your site since all of you will have access to it.
Please make sure all of your teammates have logged onto github.mit.edu at least once, else we will not be able to add them all to the repo.
We will email you when we’ve created your repository. You may need to use another repository to develop your site (such as another repository on the non-MIT Github) since the team members without certificates will not be able to access the MIT Github repository. However, we would still like you to turn in your milestones (along with source code) to the MIT repository created for you.
Please make sure all of your teammates who can log onto github.mit.edu have done so at least once, else we will not be able to add them all to the repo.
In order to do this, at least one of you will need to add a second remote, using one of these commands:
git remote add mit email@example.com:mit6470/<repo-name-here>.git
git remote add mit https://github.mit.edu/mit6470/<repo-name-here>.git
Then, to push to this repository when turning in a milestone, simply do:
git push mit
Email the staff. You will still have to use a regular Github account, but we will give you instructions for allowing the staff to access your repository.
Before beginning work on any website, you should first take some time to think about your users. Who do you envision using your site, what needs will your site fulfill for your target users, and how should you best design your site to fulfill these needs?
For this milestone, please complete the following:
Think hard about your most complicated page. What are the important features of this page? What usability problems may come up? For your most important page:
In agile software design, a minimal viable product (MVP), or "simplest thing that works" is a product that encapsulates the essence of your application. This is an opportunity for you to think hard about what features are essential to your application and make sure that it is implementable. By implementing your MVP, you may learn more about your users' preferences or discover unexpected pitfalls.
Remember, an MVP is not just a skeleton. You should make sure that you have made significant progress on your most important features. For example, a site that just implements login is not a valid MVP.
The MVP will be due on 1/22/14, five days before the final product is due. Teams that do not pass the MVP milestone will not be eligible to compete in the main division.
Please answer the following questions about your plan for your MVP:
Please answer the following questions. Please be succinct as possible.
To submit Milestone 1, fill out the form here by the submission deadline
When submitting the form, you will need to provide a link to an MIT Github repo that we created for you during Milestone 0.
Please put your answers to Milestone 1 questions in a single Markdown file milestone1.md within a milestone1 directory in your repository. You may also place images into this directory and include them into the Markdown file.
For this milestone, we would like to see that you've made significant progress towards your final product by looking at your MVP. You may wish to review the technical requirements to ensure that your site meets these requirements.
Remember, your MVP should capture the essence of your application and include your most important or compelling features. As such, your app should go beyond a simple skeleton or scaffold. Users should be able to get the essence of your application via a fully-functional important feature.
Specifically, by this milestone, you should have, at minimum:
Answer the following questions:
Also, while some of you were notified that you do not qualify for the rookie division in Milestone 1, your team has the responsibility to make sure that you qualify even in case you were not notified. Teams that do not qualify for the rookie division must change to the main division by Milestone 2.
To submit Milestone 2, fill out this google form
When submitting the form, you will need to provide a link to an MIT Github repo that we created for you during Milestone 0. You will also need to host your site in a way so that it can be accessed over the Internet. Hosting platforms like Heroku or MIT Scripts are preferred. You can also host on your local computer, but beware of changing IP addresses and turning off your computer.
Please put your answers to Milestone 2 questions in a single Markdown file milestone2.md within a milestone2 directory in your repository. Please do NOT use PDF or Word documents, or any other document format that cannot be viewed on Github.
This only applies to competitors.
Your final submission will be a form found on this site, to be posted closer to the deadline. Note: this form will close at exactly 5:00PM; submissions will not be accepted after the form has closed.
Additionally, please be aware of the following if you are chosen for a semifinalist: