Difference between revisions of "Summer of Code/2014/AnaBalica/Social Help"
< Summer of Code | 2014
Jump to navigation
Jump to search
(about the project section updates) |
(timeline and other updates) |
||
| Line 8: | Line 8: | ||
:AnaBalica | :AnaBalica | ||
*''What is your IRC nickname on irc.freenode.net?'' | *''What is your IRC nickname on irc.freenode.net?'' | ||
| − | : | + | :ananasova |
*''What is your first language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'' | *''What is your first language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)'' | ||
:I know 3 languages: Romanian, Russian and English. | :I know 3 languages: Romanian, Russian and English. | ||
| Line 29: | Line 29: | ||
:* propose enhancements | :* propose enhancements | ||
:* debug possible problems | :* debug possible problems | ||
| − | :To think about it, today's society is overwhelmed with social networks, forums and chats. Social Help is an easy way to access social channels | + | :To think about it, today's society is overwhelmed with social networks, forums and chats. Social Help is an easy way to access social channels and get children involved into helping each other. The interaction can give them a headstart in understanding how to use the tools they are offered and even contribute to the project. |
| − | * 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: | ||
| + | :* 19-25 May - Decide on and create a final design and GUI of the Social Help window (general activity view and context-dependent view) | ||
| + | :* 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 | ||
| + | :* 2-8 June - Create a toolbar button for social help with a dropdown menu listing all available channels for the current context | ||
| + | :* 9-15 June - On IRC channel button press event open Chat activity and join the channel | ||
| + | :* 16-22 June - Set up a forum platform (Discourse for example), configure it (create general topics, assign admins, rules, write descriptions) | ||
| + | :* 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 - Review, refactor if necessary parts of code | ||
| + | :* 7-13 July - Write unit and integration tests for the activity and the functionality integrated into sugar | ||
| + | :* 14-20 July - Extensive manual testing | ||
| + | :* 21-27 July - Fix bugs, solve unexpected issues | ||
| + | :* 28-3 August - Write documentation (docstrings, a wiki page with description, help page to Help activity) | ||
| + | :* 4-10 August - Extra polishing (small enhancements) | ||
| + | :* 11-17 August - Merging to main repos, submitting code to melange | ||
* 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. | ||
Revision as of 09:32, 11 March 2014
About me
- What is your name?
- Ana Balica
- What is your email address?
- ana.balica@gmail.com
- What is your Sugar Labs wiki username?
- AnaBalica
- What is your IRC nickname on irc.freenode.net?
- ananasova
- What is your first language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
- I know 3 languages: Romanian, Russian and English.
- Where are you located, and what hours (UTC) do you tend to work? (We also try to match mentors by general time zone if possible.)
- Originally I am from Republic of Moldova. My current location (also during the summer) is Prague, Czech Republic (UTC +1). Normal working day starts at 8AM UTC and ends at 7PM UTC.
- 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?
- Open-source contributions:
- moin2.0 - change subscription mechanism and other small enhancements
- sugar bugfix - 1 and 2
About the project
- What is the name of your project?
- Social Help
- 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?
- Social Help is going to be a system wide mechanism to access a range of social channels like IRC and forums. In order to access a context-dependent window with available communication channels, the user should press <Shift><Alt><c> (c stands for chat or connect). The user can choose between being connected to IRC (via Chat activity) or post a question to a forum (Discourse, Moot or some other reasonable modern forum software).
- The feature is oriented towards users of Sugar (kids) that for various reasons are in need of social interaction:
- ask a question on how to achieve something within Sugar or an activity
- share knowledge and experience
- propose enhancements
- debug possible problems
- To think about it, today's society is overwhelmed with social networks, forums and chats. Social Help is an easy way to access social channels and get children involved into helping each other. The interaction can give them a headstart in understanding how to use the tools they are offered and even contribute to the project.
- 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)
- 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
- 2-8 June - Create a toolbar button for social help with a dropdown menu listing all available channels for the current context
- 9-15 June - On IRC channel button press event open Chat activity and join the channel
- 16-22 June - Set up a forum platform (Discourse for example), configure it (create general topics, assign admins, rules, write descriptions)
- 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 - Review, refactor if necessary parts of code
- 7-13 July - Write unit and integration tests for the activity and the functionality integrated into sugar
- 14-20 July - Extensive manual testing
- 21-27 July - Fix bugs, solve unexpected issues
- 28-3 August - Write documentation (docstrings, a wiki page with description, help page to Help activity)
- 4-10 August - Extra polishing (small enhancements)
- 11-17 August - Merging to main repos, submitting code to melange
- 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.