100
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + Line 37:
Line 37: − + + + + + + + + + + + + + + + + Line 45:
Line 60: + + + + + + Line 99:
Line 120: − + − + + − + − + + − <br> − <br>+ − - Create a mini-journal instance that will be shared.+ − <br> − - Design a single mini-journal instance that will handle instances of other shared activities. − <br> − <br>+ − - Make this system sync the files when the user does not have the activity running. − <br>+ − |<nowiki>- Test the working of mini-journal system that is in sync with the File-Syncer system.</nowiki>+ − <br>+ − - Write test cases that can be further used for developing and testing. − + − - Send patches of the feature completed for review. − − + Line 147:
Line 162: − + − <br>+ − - On completion, send patch for review.+ − <br> − + − + − - Design the File-Chooser Dialog View for Home View.+ − <br>+ − − <br>+ − |<nowiki>- UI improvements.</nowiki>+ − + − - Improve code efficiency.+ − + − - Test again all the tools and features. − − - Send patches for more reviews. − + − <br>+ − - Documentation and Update the wiki page of Journal, describe the new features that are added.+ − <br>+ − - Add comments that will help further development. − + − + + + + + + + + + + + − <b>Prototype:</b><br>+ − + − *Implemented the Icon View for Journal+ − − https://github.com/AbrahmAB/sugar-prototype/tree/prototype<br> − + Line 204:
Line 221: − + − + + + + + + + + − + + Line 216:
Line 241: + + Line 222:
Line 249: − + − + − + − + − + − + − + − + − + − + − There was an incident past two years ago, when my teacher showed us the poetry algorithm. An computer algorithm that generates poetry! I was surprised to see that the poem generated by that algorithm was as equivalent as a real human composing a poetry. This incident arose the programmer in me.+ + +
Summer of Code/2016/Journal Rethink (view source)
Revision as of 06:37, 28 March 2016
, 06:37, 28 March 2016→Miscellaneous
== About Me: ==
== About Me ==
<b>What is your name?</b><br>
<b>What is your name?</b><br>
Journal Rethink is to enhance Journal such that students could use it as a platform to do their project-work.
Journal Rethink is to enhance Journal such that students could use it as a platform to do their project-work.
The listed features can be used for making Journal as a platform for working on projects.
The listed features can be used for making Journal as a platform for working on projects.<br>
This project will benefit students as well as teachers in many ways.<br>
'''For Students :''' <br>
Positive group experiences will contribute to student learning, retention and overall school success.Properly structured, group projects can reinforce skills that are relevant to both group and individual work, including the ability to:
* Break complex tasks into parts and steps
* Plan and manage time
* Refine understanding through discussion and explanation
* Give and receive feedback on performance
* Develop stronger communication skills.
* Tackle more complex problems than they could on their own.
* Pool knowledge and skills.
* Develop their own voice and perspectives in relation to peers.
'''For teachers :''' <br>
Teachers can often assign more complex, authentic problems to groups of students than they could to individuals. Group work also introduces more unpredictability in teaching, since groups may approach tasks and solve problems in novel, interesting ways. This can be refreshing for instructors. Additionally, group assignments can be useful when there are a limited number of viable project topics to distribute among students. And they can reduce the number of final products instructors have to grade.
*'''Shared mini-journal:'''
*'''Shared mini-journal:'''
In short, When users opens the Journal they can see list of projects (mini-journals) in Projects List View. When they click on the particular project, they see a list of activities that are shared with the same participants under the same project in the mini-journal (same layout as journal today).
In short, When users opens the Journal they can see list of projects (mini-journals) in Projects List View. When they click on the particular project, they see a list of activities that are shared with the same participants under the same project in the mini-journal (same layout as journal today).
-> '''Flow chart:''' <br>
A flow chat demonstrating the functioning of “Shared Mini-Journal” feature.
[[File:Flow_chart_journal.png|border|center|960x500px]]
*'''File Syncer System for mini-journal:'''
*'''File Syncer System for mini-journal:'''
'''
'''
{| class="wikitable"
{| class="wikitable"
! style="width: 150px;" | Week
! style="width: 150px;" | Days
!Task
!Task
|-
|-
|31 April to 9 May
|31 April to 9 May
|* Get thorough with Journal code. Analyze its working. I have basic understanding of the code because of my previous contributions to sugar.
|
* Get thorough with Journal code. Analyze its working. I have basic understanding of the code because of my previous contributions to sugar.
* Get a better grip over telepathy salut and gabble.
* Get a better grip over telepathy salut and gabble.
|-
|-
|10May to 18 May
|10 May to 18 May
|* Analyze more on how collaboration works in sugar.
|
* Analyze more on how collaboration works in sugar.
* Develop an outline of the project and more discussion with my mentor Sam and other community members regarding the features that are to be implemented.
* Develop an outline of the project and more discussion with my mentor Sam and other community members regarding the features that are to be implemented.
|-
|-
|19 May to 31 May
|19 May to 31 May
|Start developing the “Shared-project” tool.
|Start developing the “Shared-project” tool.
* Create a mini-journal instance that will be shared.
* Design a single mini-journal instance that will handle instances of other shared activities.
|-
|-
|1 June to 13 June
|1 June to 13 June
|Implement the File-Syncer System.
|Implement the File-Syncer System.
* Make this system sync the files when the user does not have the activity running.
|-
|-
|14 June to 24 June
|14 June to 24 June
|
* Test the working of mini-journal system that is in sync with the File-Syncer system.
* Write test cases that can be further used for developing and testing.
|-
|-
|25 June to 26 June
|25 June to 26 June
|Prepare for mid-term evaluation.
|Prepare for mid-term evaluation.
* Send patches of the feature completed for review.<br>
The main Shared mini-journal would be implemented till midterm.
The main Shared mini-journal would be implemented till midterm.
|-
|-
|27 June to 28 June
|27 June to 28 June
|Midterm Evaluation
|'''Midterm Evaluation'''
|-
|-
|29 June to 5 July
|29 June to 5 July
|-
|-
|10 July to 26 July
|10 July to 26 July
|<nowiki>- Add alerts to the file-syncer system that would alert the user for changes in state of shared activity.</nowiki>
|
* Add alerts to the file-syncer system that would alert the user for changes in state of shared activity.
* On completion, send patch for review.
|-
|-
|27 July to 2 August
|27 July to 2 August
|Integrate the Chat Activity in mini-journal.
|Integrate the Chat Activity in mini-journal.
|-
|-
|3 August to 6 August
|3 August to 6 August
|Implement the “Add new Item” tool.
|
* Implement the “Add new Item” tool.
* Design the File-Chooser Dialog View for Home View.
|-
|-
|7 August to 10 August
|7 August to 10 August
|Implement the Icon View for Journal.
|<nowiki>- Implement the Icon View for Journal.</nowiki>
|-
|-
|11 August to 17 August
|11 August to 17 August
|
* UI improvements.
* Improve code efficiency.
* Test again all the tools and features.
* Send patches for more reviews.
|-
|-
|18 August to 22 August
|18 August to 22 August
|<nowiki>- Fix bugs.</nowiki>
|
* Fix bugs.
* Documentation and Update the wiki page of Journal, describe the new features that are added.
* Add comments that will help further development.
|-
|-
|23 August
|23 August
|Final Evaluation
|'''Final Evaluation'''
|}
|}
'''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.'''<br>
'''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.'''<br>
I am familiar with Journal codebase. I have no other commitments apart from GSoC. My university will also be going through vacations this summer and I have no other short/long vacations planning during the summer. So, there will be no obstacles regarding my availability and my weekly dedicated time. The only fun trip I wish to have this summer is to fulfill my dream of completing GSoC 2016.<br>
I am familiar with Journal codebase, have been contributing from more than a month now and have exactly understood the developments needed.
I have no other commitments apart from GSoC. My university will also be going through vacations this summer and I have no other short/long vacations planning during the summer. So, there will be no obstacles regarding my availability and my weekly dedicated time. The only fun trip I wish to have this summer is to fulfill my dream of completing GSoC 2016.
Prototype:
I have also developed a prototype.
* Implemented the Icon View for Journal.
* Designed the File Chooser View of Home View.
Link for the same:
https://github.com/AbrahmAB/sugar-prototype/tree/prototype
I have also developed a prototype for sugar-toolkit-gtk3 for supporting the changes made in my sugar-prototype
I have also developed a prototype.
Link for this sugar-toolkit-gtk3-proto is:
https://github.com/AbrahmAB/sugar-toolkit-gtk3-proto/tree/prototype
Link for the same ->
'''My college project work as well as other games that I have developed are as bfollows:'''
'''My college project work as well as other games that I have developed are as follows:'''
*'''[https://github.com/AbrahmAB/my_tiny_shell Tiny-Shell]''' : The project included to write a simple Unix shell program that supports job control. The language used was C.
*'''[https://github.com/AbrahmAB/my_tiny_shell Tiny-Shell]''' : The project included to write a simple Unix shell program that supports job control. The language used was C.
*'''[https://github.com/AbrahmAB/my_Dynamic_memory_allocator Dynamic Memory Allocator]''' : This is an ongoing project, in which I am writing a dynamic storage allocator for C programs, i.e., my own version of the malloc , free , and realloc routines.
*'''[https://github.com/AbrahmAB/my_Dynamic_memory_allocator Dynamic Memory Allocator]''' : This is an ongoing project, in which I am writing a dynamic storage allocator for C programs, i.e., my own version of the malloc , free , and realloc routines.
*'''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.'''
'''My answer :''' The project Journal Rethink is all making Journal support the project-based school activities. This will promote project-activities in school and improve students team-work qualities.
'''My answer :''' The project Journal Rethink is all making Journal support the project-based school activities. This will promote project-activities in school and improve students’ team-work qualities.
Sugar focuses on sharing and collaboration. And this project would probably bring a great extension in collaboration and sharing system. A whole new experience for the students and teachers.
Sugar focuses on sharing and collaboration. And this project would probably bring a great extension in collaboration and sharing system.
The file syncer system is pretty new for sugar. This will sync files whose activities are not running and alert the inattentive student. Each and every member of project group must be informed about the changes made in the project. Without any notification or alert system the changes may go unnoticed. For this file syncer system comes handy.
The Shared mini-journal alongwith the file syncer system will make Journal a platform for project based activities in school. A whole new and better experience for the students and teachers.
'''Sam : '''
It will strategically use Sugar's journal system to make the user experience much better. Instead of having separated systems, making a project based journal will tie the journal and collab together in a way that users will intuitively understand. It will also allow for better reflection and group work, which are Sugar's key advantaged over a LMS+desktop approach.<br>
'''Sam :'''
'''Walter : '''
The Journal has always been at the heart of Sugar, but its potential has never been fully realized. This project will bring many underdeveloped and underutilized features to the forefront, furthering our pedagogical goals.<br>
'''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?'''
I am planning to write a blog on Wordpress where I will post updates of the progress as well as obstacles being faced by me.
I am planning to write a blog on Wordpress where I will post updates of the progress as well as obstacles being faced by me.
If allowed I will also create a wiki page with details as per the layout of Features page for all the features that would be implemented and update the current status for each feature regularly.
I will also announce milestones on the mailing list or IRC channel to inform the community of my progress.
I will also announce milestones on the mailing list or IRC channel to inform the community of my progress.
== Miscellaneous ==
== Miscellaneous ==
[[File:Sugar ss.png|border|center|900x600px]]
[[File:Sugar ss.png|border|center|900x600px]]
'''Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.'''
'''Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.'''<br>
**[Journal] Implemented toggled sorting order (merged) : https://github.com/sugarlabs/sugar/pull/653
**['''Journal'''] Implemented toggled sorting order : https://github.com/sugarlabs/sugar/pull/653 ('''merged''')
**[Journal] Typo in sugar (merged) : https://github.com/sugarlabs/sugar/pull/654
**['''Journal'''] Typo in sugar : https://github.com/sugarlabs/sugar/pull/654 ('''merged''')
**[Journal] Journal entries name can be renamed to blank (merged) : https://github.com/sugarlabs/sugar/pull/655
**['''Journal'''] Journal entries name can be renamed to blank : https://github.com/sugarlabs/sugar/pull/655 ('''merged''')
**[Journal] Dragging a Journal entry drags the whole white entry bar instead of icon (merged) : https://github.com/sugarlabs/sugar/pull/656
**['''Journal'''] Dragging a Journal entry drags the whole white entry bar instead of icon : https://github.com/sugarlabs/sugar/pull/656 ('''merged''')
**[Sugar-toolkit-gtk3] Ellipsis in title and msg of alert (unreviewed): https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/310
**['''Sugar-toolkit-gtk3'''] Ellipsis in title and msg of alert : https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/310 ('''merged''')
**[Turtle-extras] Fixed spellchecks in taextras.py (merged) : https://github.com/walterbender/turtleextras/pull/1
**['''Turtle-extras'''] Fixed spellchecks in taextras.py : https://github.com/walterbender/turtleextras/pull/1 ('''merged''')
**[Journal] Buddy palette appears in wrong position (merged) : https://github.com/sugarlabs/sugar/pull/662
**['''Journal'''] Buddy palette appears in wrong position : https://github.com/sugarlabs/sugar/pull/662 ('''merged''')
**[Journal] Fixed issue: Journal Entries can be renamed to blank via Detail View (open): https://github.com/sugarlabs/sugar/pull/663
**['''Journal'''] Fixed issue: Journal Entries can be renamed to blank via Detail View : https://github.com/sugarlabs/sugar/pull/663 ('''open''')
**[Reflect Activity] Fixed #5: Solved sorting of list (unreviewed): https://github.com/walterbender/reflect/pull/6
**['''Reflect Activity'''] Fixed #5: Solved sorting of list : https://github.com/walterbender/reflect/pull/6 ('''merged''')
'''Describe a great learning experience you had as a child.'''<br>
'''Describe a great learning experience you had as a child.'''<br>
Once my teacher showed us the poetry algorithm. A computer algorithm that generates poetry! I was surprised to see that the poem generated by that algorithm was as equivalent as a real human composing a poetry. As an experiment, 10 of us were handed paper which contained two poems, one composed by human and other by computer. Surprisingly 8 out of us failed to tell which one was composed by computer! This incident arose the programmer in me.
[[Category:2016 GSoC applications]]