Summer of Code/2014/AnaBalica/Social Help: Difference between revisions

Line 87:

*''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:

:* 19-25 May - Decide on and ~~create a~~ final design ~~and GUI~~ of the Social Help window ~~(general activity view and context-dependent view)~~

:* 19-25 May - Decide on and code the final UI design of the Social Help window

:* 26-1 June - Bring on a context-dependent window ~~(within an activity)~~ on ~~<Shift><Alt><c>~~ keypress to show all available communication channels for the following context

:* 26-1 June - Bring on a context-dependent window on a specific keypress to show all available communication channels for the following context and attach callbacks to UI widgets

:* 2-8 June - Create a toolbar button for social help with a ~~dropdown menu~~ listing all available channels for the current context

:* 2-8 June - Create a toolbar button for social help with a palette listing all available channels for the current context, integrate the toolbar button to main activities

:* 9-15 June - On IRC channel button press event open IRC activity and join the channel

:* 9-15 June - On IRC channel button press event open IRC activity, set the nickname based on system user and join the help channel

:* 16-22 June - Set up a forum platform ~~(Discourse for example)~~, ~~configure it (~~create ~~general topics, assign admins, rules, write descriptions)~~

:* 16-29 June - Set up a forum platform or familiarize with the existing one, create a seamless registration and authentication process for Sugar users

:* 23-~~29 June~~ - On Forum(s) button press event open Browse activity and ~~open~~ the ~~page~~ to the ~~specific topic on the sugar forum~~

:* 30-6 July - On Forum(s) button press event open the respective activity or the Browse activity and point to the context-dependent category to post the question

:* 30-6 July - ~~Localization, review, refactor if necessary some parts of code~~

:* 7-13 July - Create error message popup windows and offer to download missing components (i.e. IRC activity)

:* 7-13 July - Write unit and integration tests for the ~~activity and the~~ functionality ~~integrated into sugar~~

:* 14-20 July - Write unit and integration tests for the available functionality

:* 14-20 July - Extensive manual testing

:* 21-27 July - Extensive manual testing, bugfixing, localization

~~:* 21-27 July - Fix bugs~~, ~~solve unexpected issues~~

:* 28-3 August - Write documentation (docstrings, a wiki page with description, help page to Help activity maybe)

:* 4-10 August - Extra polishing (small enhancements)

@@ Line 87: / Line 87: @@
 *''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:
-:* 19-25 May - Decide on and create a final design and GUI of the Social Help window (general activity view and context-dependent view)
+:* 19-25 May - Decide on and code the final UI design of the Social Help window
-:* 26-1 June - Bring on a context-dependent window (within an activity) on <Shift><Alt><c> keypress to show all available communication channels for the following context
+:* 26-1 June - Bring on a context-dependent window on a specific keypress to show all available communication channels for the following context and attach callbacks to UI widgets
-:* 2-8 June - Create a toolbar button for social help with a dropdown menu listing all available channels for the current context
+:* 2-8 June - Create a toolbar button for social help with a palette listing all available channels for the current context, integrate the toolbar button to main activities
-:* 9-15 June - On IRC channel button press event open IRC activity and join the channel
+:* 9-15 June - On IRC channel button press event open IRC activity, set the nickname based on system user and join the help channel
-:* 16-22 June - Set up a forum platform (Discourse for example), configure it (create general topics, assign admins, rules, write descriptions)
+:* 16-29 June - Set up a forum platform or familiarize with the existing one, create a seamless registration and authentication process for Sugar users
-:* 23-29 June - On Forum(s) button press event open Browse activity and open the page to the specific topic on the sugar forum
+:* 30-6 July  - On Forum(s) button press event open the respective activity or the Browse activity and point to the context-dependent category to post the question
-:* 30-6 July - Localization, review, refactor if necessary some parts of code
+:* 7-13 July - Create error message popup windows and offer to download missing components (i.e. IRC activity)
-:* 7-13 July - Write unit and integration tests for the activity and the functionality integrated into sugar
+:* 14-20 July - Write unit and integration tests for the available functionality
-:* 14-20 July - Extensive manual testing
+:* 21-27 July - Extensive manual testing, bugfixing, localization
-:* 21-27 July - Fix bugs, solve unexpected issues
 :* 28-3 August -  Write documentation (docstrings, a wiki page with description, help page to Help activity maybe)
 :* 4-10 August - Extra polishing (small enhancements)