Summer of Code/2014/Prasoon2211/Social Help - Revision history

FGrose at 14:41, 28 May 2014

2014-05-28T14:41:20Z

← Older revision		Revision as of 10:41, 28 May 2014
Line 1:		Line 1:
			{{Box\|'''Project blog:''' http://sugargsoc.wordpress.com/}}
	==About Me==		==About Me==

Prasoon2211: /* Miscellaneous */

2014-04-11T05:32:18Z

Miscellaneous

← Older revision		Revision as of 01:32, 11 April 2014
Line 192:		Line 192:
	* [https://github.com/sugarlabs/sugar/commit/dc104f5768867b9ff18b5ac0749420104327d780 #244, Merged.]		* [https://github.com/sugarlabs/sugar/commit/dc104f5768867b9ff18b5ac0749420104327d780 #244, Merged.]

	* Set of two PRs for ticket 4686. This one required quite a few reiterations: [https://github.com/sugarlabs/sugar/pull/326 #326, sugar], [https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/132 #132, sugar-toolkit-gtk3].		* Set of two PRs for ticket 4686, both merged. This one required quite a few reiterations: [https://github.com/sugarlabs/sugar/pull/326 #326, sugar], [https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/132 #132, sugar-toolkit-gtk3].

Prasoon2211 at 07:48, 4 April 2014

2014-04-04T07:48:58Z

← Older revision		Revision as of 03:48, 4 April 2014
Line 192:		Line 192:
	* [https://github.com/sugarlabs/sugar/commit/dc104f5768867b9ff18b5ac0749420104327d780 #244, Merged.]		* [https://github.com/sugarlabs/sugar/commit/dc104f5768867b9ff18b5ac0749420104327d780 #244, Merged.]

	* [https://github.com/sugarlabs/sugar/pull/~~314~~ #~~314~~, ~~Made PR after incoporating changes~~. ~~Awaiting response~~.]		* Set of two PRs for ticket 4686. This one required quite a few reiterations: [https://github.com/sugarlabs/sugar/pull/326 #326, sugar], [https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/132 #132, sugar-toolkit-gtk3].

Prasoon2211: /* Miscellaneous */

2014-03-27T15:32:44Z

Miscellaneous

← Older revision		Revision as of 11:32, 27 March 2014
Line 192:		Line 192:
	* [https://github.com/sugarlabs/sugar/commit/dc104f5768867b9ff18b5ac0749420104327d780 #244, Merged.]		* [https://github.com/sugarlabs/sugar/commit/dc104f5768867b9ff18b5ac0749420104327d780 #244, Merged.]

	* [https://github.com/sugarlabs/sugar/pull/~~259~~ #~~259~~, ~~Changes suggested~~.]		* [https://github.com/sugarlabs/sugar/pull/314 #314, Made PR after incoporating changes. Awaiting response.]

Prasoon2211: /* Timeline */

2014-03-27T14:56:18Z

Timeline

← Older revision		Revision as of 10:56, 27 March 2014
Line 119:		Line 119:
	! Week !! Work to be done		! Week !! Work to be done
	\|-		\|-
	\| 21st April - 19th May (Community Bonding Period) \|\| Discuss which authentication bridge to use with Discourse.		\| 21st April - 19th May (Community Bonding Period) \|\| Discuss which authentication bridge to use with Discourse. Get to know the community. Make a standalone WebKitGTK+ activity that can be later ported to sugar.
	\|-		\|-
	\| 19th May - 26th May \|\| Begin coding. Add the social help button to sugar menus. Start working on the social-help activity.		\| 19th May - 26th May \|\| Begin coding. Add the social help button to sugar menus. Start working on the social-help activity.

Prasoon2211 at 05:59, 22 March 2014

2014-03-22T05:59:27Z

← Older revision		Revision as of 01:59, 22 March 2014
Line 1:		Line 1:
	~~'''''Note''': This is the first draft. Please report any mistakes in the discussions page''~~

	==About Me==		==About Me==

Prasoon2211: /* About my project */

2014-03-21T15:42:46Z

About my project

← Older revision		Revision as of 11:42, 21 March 2014
Line 116:		Line 116:
	'''''> What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; 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 (27 June); 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 from May 19 - August 22; 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 (27 June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''''

			===Timeline===
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 158:		Line 159:
	Unfortunately however, I cannot share the code of these applications since the code officially belongs to the institute. All of this work is a part of work I've done as part of a campus students' group - the Information Management Group. We are the guys who've made the [https://speakerdeck.com/imgiitroorkee/content-management-system CMS] for managing the large amount of content on the [http://www.iitr.ac.in college website] and developed a great intranet portal for the institute; [https://www.facebook.com/IMGIITRoorkee/photos_albums?ref=hl Photos]. [https://www.facebook.com/media/set/?set=a.10152183260016988.512292.353701311987&type=3 Some More].		Unfortunately however, I cannot share the code of these applications since the code officially belongs to the institute. All of this work is a part of work I've done as part of a campus students' group - the Information Management Group. We are the guys who've made the [https://speakerdeck.com/imgiitroorkee/content-management-system CMS] for managing the large amount of content on the [http://www.iitr.ac.in college website] and developed a great intranet portal for the institute; [https://www.facebook.com/IMGIITRoorkee/photos_albums?ref=hl Photos]. [https://www.facebook.com/media/set/?set=a.10152183260016988.512292.353701311987&type=3 Some More].

	I've also done ~~other minor~~ work in PHP and NodeJS. You can find it at my [https://github.com/prasoon2211 github ~~repository~~].		I've also done some work in PHP and NodeJS. You can find it at my [https://github.com/prasoon2211 github profile].

	==Me and the community==		==Me and the community==

Prasoon2211: /* About my project */

2014-03-21T15:39:38Z

About my project

← Older revision		Revision as of 11:39, 21 March 2014
Line 111:		Line 111:
	## A fourth way, and this was [https://meta.discourse.org/t/signing-a-user-in-through-a-desktop-application/13700 told to me by the Discourse devs], is to use Discourse SSO (Single Sign On). But this would require an existing service on which we can ''hang'' the Discourse auth onto.		## A fourth way, and this was [https://meta.discourse.org/t/signing-a-user-in-through-a-desktop-application/13700 told to me by the Discourse devs], is to use Discourse SSO (Single Sign On). But this would require an existing service on which we can ''hang'' the Discourse auth onto.

	Any one of these methods can work. ~~We'll need to decide on a single one~~.		Any one of these methods can work. At the moment, I am leaning towards the first approach.

Prasoon2211: /* About my project */

2014-03-21T15:35:45Z

About my project

← Older revision		Revision as of 11:35, 21 March 2014
Line 69:		Line 69:

	===Abstract===		===Abstract===

	To create an easily accessible, highly usable platform that sugar users can use to discuss, debate and share ideas about everything related to sugar.		To create an easily accessible, highly usable platform that sugar users can use to discuss, debate and share ideas about everything related to sugar.


	===Deliverables===		===Deliverables===
Line 88:		Line 86:
	This project is aimed at all sugar users. The ability to start a discussion on any help-related topic with a single mouse click will be extremely helpful for the users. The ''real aim'' of this project is to develop a repository of all information regarding sugar - much like StackOverflow - that will be the go-to place for sugar users. For these reasons, it is imperative that this project be undertaken.		This project is aimed at all sugar users. The ability to start a discussion on any help-related topic with a single mouse click will be extremely helpful for the users. The ''real aim'' of this project is to develop a repository of all information regarding sugar - much like StackOverflow - that will be the go-to place for sugar users. For these reasons, it is imperative that this project be undertaken.

	====Technical Details=====		====Technical Details====
	Work will be in Python for the most part. Some taks like tweaking Discourse might require some me to deal with Ruby. For cutomizing the frontend, I shall need to work with HTML5/CSS3/JS as well. I've worked extensively with all these technologies except Ruby which I'll need to brush up.		Work will be in Python for the most part. Some taks like tweaking Discourse might require some me to deal with Ruby. For cutomizing the frontend, I shall need to work with HTML5/CSS3/JS as well. I've worked extensively with all these technologies except Ruby which I'll need to brush up.

Prasoon2211 at 15:34, 21 March 2014

2014-03-21T15:34:23Z

Show changes