WebFund 2013W: Proposal - Revision history

Soma at 17:34, 25 January 2013

2013-01-25T17:34:20Z

← Older revision		Revision as of 17:34, 25 January 2013
Line 1:		Line 1:
	* Final project proposals for your group are due by February 1st, 2013, at 1 PM. You should submit well before this date, however, so you may discuss your proposal with your TA before grades are determined. With your TA's assistance you all should be able to get full marks for this milestone; if you just submit without consulting with your TA, however, you may not get full marks.		* Final project proposals for your group are due by '''February 1st, 2013, at 1 PM'''. You should submit well before this date, however, so you may discuss your proposal with your TA before grades are determined. With your TA's assistance you all should be able to get full marks for this milestone; if you just submit without consulting with your TA, however, you may not get full marks.

	* Your proposal should be submitted by entering it into the README.md of your team's primary repository on github. Your proposal should be in text with optional markdown formatting. You may remove any content that was previously there in the file (such as the TA: line some of your repositories have).		* Your proposal should be submitted by entering it into the README.md of your team's primary repository on github. Your proposal should be in text with optional markdown formatting. You may remove any content that was previously there in the file (such as the TA: line some of your repositories have).

Soma at 17:34, 25 January 2013

2013-01-25T17:34:01Z

← Older revision		Revision as of 17:34, 25 January 2013
Line 12:		Line 12:
	*Your description should be concise but should give your TA a relatively detailed understanding of what web application your team is attempting to create. It should also give a rough description of the relative duties of the web client, web server, and backend store.		*Your description should be concise but should give your TA a relatively detailed understanding of what web application your team is attempting to create. It should also give a rough description of the relative duties of the web client, web server, and backend store.

	*You should have weekly milestones starting the week of February 4th and going through the last week of the term but excluding winter break. That gives you 9 milestones, of which you should include those below. You need to add four milestones to this list and specify the due week for each. ~~Which day of the week it~~ will ~~be due will be negotiated with your individual TA~~.		*You should have weekly milestones starting the week of February 4th and going through the last week of the term but excluding winter break. (Which day of the week it will be due will be negotiated with your individual TA.) That gives you 9 milestones, of which you should include those below. You need to add four milestones to this list and specify the due week for each. As best as you can, give more details for what you will do for each milestone.

	# Architecture diagram & external library/program use		# Architecture diagram & external library/program use

Soma at 17:33, 25 January 2013

2013-01-25T17:33:03Z

← Older revision		Revision as of 17:33, 25 January 2013
Line 12:		Line 12:
	*Your description should be concise but should give your TA a relatively detailed understanding of what web application your team is attempting to create. It should also give a rough description of the relative duties of the web client, web server, and backend store.		*Your description should be concise but should give your TA a relatively detailed understanding of what web application your team is attempting to create. It should also give a rough description of the relative duties of the web client, web server, and backend store.

	*You should have weekly milestones starting the week of February 4th and going through the last week of the term but excluding winter break. That gives you 9 milestones, of which you should include the ~~following:~~		*You should have weekly milestones starting the week of February 4th and going through the last week of the term but excluding winter break. That gives you 9 milestones, of which you should include those below. You need to add four milestones to this list and specify the due week for each. Which day of the week it will be due will be negotiated with your individual TA.

	# Architecture diagram & external library/program use		# Architecture diagram & external library/program use
Line 19:		Line 19:
	# Draft documentation		# Draft documentation
	# Final code and documentation (April 10th)		# Final code and documentation (April 10th)

	~~You need to add four milestones to this list and specify the due week for each. Which day of the week it will be due will be negotiated with your individual TA.~~

Soma at 17:32, 25 January 2013

2013-01-25T17:32:24Z

← Older revision		Revision as of 17:32, 25 January 2013
Line 3:		Line 3:
	* Your proposal should be submitted by entering it into the README.md of your team's primary repository on github. Your proposal should be in text with optional markdown formatting. You may remove any content that was previously there in the file (such as the TA: line some of your repositories have).		* Your proposal should be submitted by entering it into the README.md of your team's primary repository on github. Your proposal should be in text with optional markdown formatting. You may remove any content that was previously there in the file (such as the TA: line some of your repositories have).

	Your proposal should have:		*Your proposal should have:
	* The name of your project.		** The name of your project.
	* A paragraph-long description of your project		** A paragraph-long description of your project
	* Your proposed milestones		** Your proposed milestones

	You may include your names, but that is optional. Please don't enter your student numbers into this file. Email or github message your TA with the name of all students in your team and their corresponding github usernames '''as soon as possible''' (i.e., before the proposal is submitted and ideally during the tutorial on Jan 25/28).		*You may include your names, but that is optional. Please don't enter your student numbers into this file. Email or github message your TA with the name of all students in your team and their corresponding github usernames '''as soon as possible''' (i.e., before the proposal is submitted and ideally during the tutorial on Jan 25/28).

	Your description should be concise but should give your TA a relatively detailed understanding of what web application your team is attempting to create. It should also give a rough description of the relative duties of the web client, web server, and backend store.		*Your description should be concise but should give your TA a relatively detailed understanding of what web application your team is attempting to create. It should also give a rough description of the relative duties of the web client, web server, and backend store.

	You should have weekly milestones starting the week of February 4th and going through the last week of the term but excluding winter break. That gives you 9 milestones, of which you should include the following:		*You should have weekly milestones starting the week of February 4th and going through the last week of the term but excluding winter break. That gives you 9 milestones, of which you should include the following:

	# Architecture diagram & external library/program use		# Architecture diagram & external library/program use

Soma at 17:31, 25 January 2013

2013-01-25T17:31:48Z

← Older revision		Revision as of 17:31, 25 January 2013
Line 1:		Line 1:
	Final project proposals for your group are due by February 1st, 2013, at 1 PM. You should submit well before this date, however, so you may discuss your proposal with your TA before grades are determined. With your TA's assistance you all should be able to get full marks for this milestone; if you just submit without consulting with your TA, however, you may not get full marks.		* Final project proposals for your group are due by February 1st, 2013, at 1 PM. You should submit well before this date, however, so you may discuss your proposal with your TA before grades are determined. With your TA's assistance you all should be able to get full marks for this milestone; if you just submit without consulting with your TA, however, you may not get full marks.

	Your proposal should be submitted by entering it into the README.md of your team's primary repository on github. Your proposal should be in text with optional markdown formatting. You may remove any content that was previously there in the file (such as the TA: line some of your repositories have).		* Your proposal should be submitted by entering it into the README.md of your team's primary repository on github. Your proposal should be in text with optional markdown formatting. You may remove any content that was previously there in the file (such as the TA: line some of your repositories have).

	Your proposal should have:		Your proposal should have:

Soma at 17:31, 25 January 2013

2013-01-25T17:31:27Z

← Older revision		Revision as of 17:31, 25 January 2013
Line 1:		Line 1:
	~~Project~~ proposals for your group are due by February 1st, 2013, at 1 PM.		Final project proposals for your group are due by February 1st, 2013, at 1 PM. You should submit well before this date, however, so you may discuss your proposal with your TA before grades are determined. With your TA's assistance you all should be able to get full marks for this milestone; if you just submit without consulting with your TA, however, you may not get full marks.

	Your proposal should be submitted by entering it into the README.md of your team's primary repository on github. Your proposal should be in text with optional markdown formatting. You may remove any content that was previously there in the file (such as the TA: line some of your repositories have).		Your proposal should be submitted by entering it into the README.md of your team's primary repository on github. Your proposal should be in text with optional markdown formatting. You may remove any content that was previously there in the file (such as the TA: line some of your repositories have).

Soma: Created page with "Project proposals for your group are due by February 1st, 2013, at 1 PM. Your proposal should be submitted by entering it into the README.md of your team's primary repository..."

2013-01-25T17:29:01Z

Created page with "Project proposals for your group are due by February 1st, 2013, at 1 PM. Your proposal should be submitted by entering it into the README.md of your team's primary repository..."

New page

Project proposals for your group are due by February 1st, 2013, at 1 PM.

Your proposal should be submitted by entering it into the README.md of your team's primary repository on github. Your proposal should be in text with optional markdown formatting. You may remove any content that was previously there in the file (such as the TA: line some of your repositories have).

Your proposal should have:
* The name of your project.
* A paragraph-long description of your project
* Your proposed milestones

You may include your names, but that is optional. Please don't enter your student numbers into this file. Email or github message your TA with the name of all students in your team and their corresponding github usernames '''as soon as possible''' (i.e., before the proposal is submitted and ideally during the tutorial on Jan 25/28).

Your description should be concise but should give your TA a relatively detailed understanding of what web application your team is attempting to create. It should also give a rough description of the relative duties of the web client, web server, and backend store.

You should have weekly milestones starting the week of February 4th and going through the last week of the term but excluding winter break. That gives you 9 milestones, of which you should include the following:

# Architecture diagram & external library/program use
# Framework demo (running application skeleton)
# Working prototype/demo
# Draft documentation
# Final code and documentation (April 10th)

You need to add four milestones to this list and specify the due week for each. Which day of the week it will be due will be negotiated with your individual TA.