Homework turn in - Revision history

FGrose at 01:24, 20 December 2016

2016-12-20T01:24:02Z

← Older revision		Revision as of 21:24, 19 December 2016
Line 1:		Line 1:
	{{~~Obsolete \| Blank page not linked from anywhere~~}}		{{Stub}}

KachachanC at 05:02, 19 December 2016

2016-12-19T05:02:55Z

← Older revision	Revision as of 01:02, 19 December 2016
Line 1:	Line 1:
		{{Obsolete \| Blank page not linked from anywhere}}

Ajuonline: Removing all content from page

2009-04-08T10:50:26Z

Removing all content from page

Show changes

Ajuonline at 23:24, 3 April 2009

2009-04-03T23:24:26Z

← Older revision		Revision as of 19:24, 3 April 2009
Line 166:		Line 166:

	----		----

	~~<noinclude>[[Category:2009 GSoC applications]]</noinclude>~~

	~~[[Category:GSoC]]~~

Ajuonline: /* About your project */

2009-04-03T23:23:34Z

About your project

← Older revision		Revision as of 19:23, 3 April 2009
Line 75:		Line 75:

	'''Community Bonding Period :: 21st April - 22nd May''':		'''Community Bonding Period :: 21st April - 22nd May''':
			# To read up on Moodle docs
			# To add "sugar metadata to the downloads" -- look at the recent code in
			the custom moodle-xs by Martin,
			# local/lib.php has a function that creates Journal Entry Bundles wrapping the content file with metadata.
			#

Ajuonline: /* About your project */

2009-04-03T21:22:31Z

About your project

← Older revision		Revision as of 17:22, 3 April 2009
Line 46:		Line 46:
	Q1 :'''What is the name of your project?'''		Q1 :'''What is the name of your project?'''

	Ans : Homework Turn in - Moodle Integration		Ans : Homework Turn in - Moodle Integration [possible]

	----		----
Line 55:		Line 55:

	b): '''For whom?''':		b): '''For whom?''':
			# Deployments which use a schoolserver mostly
			# Typical classroom environment, school kids.

	c): '''Why?''':		c): '''Why?''':
			# Right now, the only possible (or at least, the easiest) way for kids to send back assignments to teachers is to use email.
			# This does not scale, and causes a disaster if kids/teachers mess up things.
			# If this is built: it will streamline the entire process,
			# ... get rid of the dependency on the external Internet.
			# ... reduce Bandwidth usage.

	d): '''Technologies''':		d): '''Technologies''':
			PHP, mySQL, Python.

	----		----
Line 76:		Line 81:


	~~It would be distributed in the following manner:~~

	Week 1:		Week 1:

Ajuonline: /* You and the community */

2009-04-03T21:10:59Z

You and the community

← Older revision		Revision as of 17:10, 3 April 2009
Line 120:		Line 120:
	Q2 :'''Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?'''		Q2 :'''Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?'''

	Ans :		Ans : I would contact the bunch from India that I know and help out. Happy to work on this, close to Kolkata, probably. Anywhere in India is still fine.

	----		----
Line 127:		Line 127:

	Ans :I will resort to the following means:		Ans :I will resort to the following means:
	#		# Contact the community. Both Moodle and Sugar have a significantly active community.
			# Contact the GSoC admin for Sugar for a backup mentor in case
			# Lookup on the internet.
			# Contact fellow Sugar students.

	----		----

Line 133:		Line 137:

	Ans :		Ans :
	#		# Mailing lists.
			# Wiki updates.
			# Blog posts.

	----		----

Ajuonline at 18:59, 3 April 2009

2009-04-03T18:59:38Z

Show changes

Ajuonline at 18:29, 3 April 2009

2009-04-03T18:29:03Z

← Older revision		Revision as of 14:29, 3 April 2009
Line 13:		Line 13:
	# What is the name of your project? Homework turn in		# What is the name of your project? Homework turn in
	# Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?		# Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
	# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
	# ~~Convince us, in 5-15 sentences~~, ~~that you~~ will be able to ~~successfully complete your~~ project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.		What:
			Who:
			Why:
			Technologies:

			# What is the timeline for development of your project?
			Week1:
			Week2:
			Week3:
			Week4:
			Week5:
			Week6:
			Week7:

			# Why I think, I will be able to finish the project within deadline?

	====You and the community====		====You and the community====
Line 20:		Line 34:
	# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.		# If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
	# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?		# Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?

	# What will you do if you get stuck on your project and your mentor isn't around?		# What will you do if you get stuck on your project and your mentor isn't around?
			First seek help from community.

	# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?		# How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?

Line 28:		Line 45:
	# Describe a great learning experience you had as a child.		# Describe a great learning experience you had as a child.

			<noinclude>[[Category:2009 GSoC applications]]</noinclude>

	[[:Category:~~2009~~ GSoC ~~applications~~]]		[[Category:GSoC]]

Ajuonline at 17:22, 3 April 2009

2009-04-03T17:22:40Z

← Older revision		Revision as of 13:22, 3 April 2009
Line 1:		Line 1:
	====About you====		====About you====

	# What is your name?		# What is your name? Ajay Kumar
	# What is your email address?		# What is your email address? ajuonline at gmail dot com
	# What is your Sugar Labs wiki username?		# What is your Sugar Labs wiki username? Ajuonline
	# What is your IRC nickname?		# What is your IRC nickname? ajuonline
	# What is your primary language? ~~(We have mentors who speak multiple languages and can match you with one of them if you'd prefer~~.)		# What is your primary language? Hindi. Secondary: English.
	# Where are you located, and what hours do you tend to work? ~~(We also try to match mentors by general time zone if possible~~.)		# Where are you located, and what hours do you tend to work? India. UTC +0530 hours.
	# ~~Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source~~. ~~If not, why do you want to work on an open-source project this summer?~~		# More info: www.ajuonline.net

	====About your project====		====About your project====

	# What is the name of your project?		# What is the name of your project? Homework turn in
	# Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?		# Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
	# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.		# What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
Line 25:		Line 25:
	====Miscellaneous====		====Miscellaneous====
	[[Image:New-developer-challenge.png\|thumb\|right\|An example of the kind of screenshot of your first modification to your development environment which you should include in your application. Note that the drop-down menu text has Mel's email address in place of the word "Restart" - your screenshot should contain your email instead.]]		[[Image:New-developer-challenge.png\|thumb\|right\|An example of the kind of screenshot of your first modification to your development environment which you should include in your application. Note that the drop-down menu text has Mel's email address in place of the word "Restart" - your screenshot should contain your email instead.]]
	# We want to make sure that you can set up a [[DevelopmentTeam#Development_systems\|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.		# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.) Large
	# What is your t-shirt size? (Yes, we know Google asks for this already; humor us.)
	# Describe a great learning experience you had as a child.		# Describe a great learning experience you had as a child.
	~~# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?~~

	<!-- Delete this paragraph and the following one when preparing your application. -->Note: you will post this application on the wiki in the category [[:Category:2009 GSoC applications]]. We encourage you to browse this category and comment on the talk page of other applications. Also, others' comments and your responses on the talk page of your own application are viewed favorably, and, while we don't like repetitive spam, we welcome honest questions and discussion of your project idea on the mailing list(s) (primarily [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel] for technical issues and [http://lists.sugarlabs.org/listinfo/iaep It's An Education Project] for educational issues) and/or [[IRC]].

	~~The NeL project has some good general recommendations for~~ [~~http~~://dev.ryzom.com/projects/nel/wiki/GSoC2009WritingProposals writing proposals]. We endorse them all; although Sugar is (regrettably) not test driven development (yet - your project could change that!), we encourage GSoC code to include tests.		[[:Category:2009 GSoC applications]]

	~~<noinclude>[[~~Category:2009 GSoC applications~~]]</noinclude>~~

	~~[[Category:GSoC~~]]