Changes

Line 57: Line 57:     
''> 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?''
 +
 +
''This is a bit larger than 20 sentences.''
    
I will be integrating the Discourse open-source discussion platform into sugar. This will be done in such a way that the users can launch themselves into discussion on any topic regarding sugar right from the sugar shell. This will be much like sugar help where users can click on the help icon to access context based help.
 
I will be integrating the Discourse open-source discussion platform into sugar. This will be done in such a way that the users can launch themselves into discussion on any topic regarding sugar right from the sugar shell. This will be much like sugar help where users can click on the help icon to access context based help.
Line 83: Line 85:  
Anyway, any one of these methods can work. We'll need to decide though. The mailing list thread that I tried discussing this on hasn't really seen much activity yet. So, we shouldn't decide on a approach just yet.
 
Anyway, any one of these methods can work. We'll need to decide though. The mailing list thread that I tried discussing this on hasn't really seen much activity yet. So, we shouldn't decide on a approach just yet.
   −
'''''<Timeline forthcoming soon>'''''
+
''> 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.''
 +
 
 +
{| class="wikitable"
 +
|-
 +
! Week !! Work to be done
 +
|-
 +
| 21st April - 19th May (Community Bonding Period) || Discuss which authentication bridge to use with Discourse.
 +
|-
 +
| 19th May - 26th May || Begin coding. Add the social help button to sugar menus.
 +
|-
 +
| 26th May - 2nd June || Set up a local Discourse environment that can be launched from within sugar.
 +
|-
 +
| 2nd June- 9th June || Work on tweaking the Discourse styling to suit sugar.
 +
|-
 +
| 9th June - 23rd June || Build the auth bridge. The way this would be done would depend on the approach chosen for this.
 +
|-
 +
| 23rd June - 27th June || Iron out the kinks in the code developed till now for the midterm evaluation deadline.
 +
|-
 +
| '''Midterm Evaluation''' || '''''Milestone:''''' Show a working sugar shell that can launch into Discourse and get the user logged in.
 +
|-
 +
| 27th June - 4th July || Make a data migration script that can be used to set up Discourse locally with the data from a central DB.
 +
|-
 +
| 4th July - 11th July || Manually add all major possible topics to Discourse and populate it with data from the wiki and any other relevant sources.
 +
|-
 +
| 11th July - 18th July || Open the data-populated Discourse for testing on Heroku. I’ll personally test of course, but, it will be great if the community helps - it usually helps catch a large number of bugs.
 +
|-
 +
| 18th July - 1st August || Fix bugs, test and file more bugs, repeat. By the end of these two weeks, we should be pretty bug-free.
 +
|-
 +
| 1st August - 11th August (Pencils down date) || Polish out the code and add documentation to ready them for release.
 +
|-
 +
| '''End Term Evaluation''' || '''''Milestone:''''' Show the final, working social help platform via Google Hangout, that can be tested on Heroku.
 +
|}
    
''> 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.''
 
''> 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.''
25

edits