What is the ultimate goal of your proposal?
- The ultimate goal of my proposal is to make Anjuta faster to operate if a developer is using the keyboard.
What components/modules will it touch/change or create?
- During the working period, I will fix some of the reported bugs that are connected with keyboard shortcuts, also some similar, although not so relevant ( I included the links in the timeline). I will also focus on making the general usability of Anjuta more accessible and operable by keyboard, so may modules concerning it's most used features will be changed.
What benefits does it have for GNOME and its community?
- As many developers use the keyboard more than the mouse, it will make Anjuta more appealing to them, and easier to use.
Why you'd like to complete this particular project?
- I am interested in the the Anjuta project, because I got familiar with the code while doing the initial contribution, and I think it is quite challenging and interesting. I have already some things in mind that I can, and I want to improve and help solve, so I would love to continue in that direction.
How do you plan to achieve completion of your project?
- As I mentioned above, my project of interest is Anjuta, as coding is done is GTK+/C that is very challenging and interesting for me. The problem described is just one of the tasks I am going to focus on. After talking with my mentor, we came to a conclusion that I can use my "newbie eye" to contribute to some general usability improvements, for example, improving some unclear dialogs and doubtful work-flows. He also mentioned that there would be a lot more new tasks that I could work on during the program.
Problem description After the discussion with my mentor, I chose to work on making Anjuta faster to operate using the keyboard. As for now, many of the main menu items have keyboard shortcuts and many things are doable only by mouse.
Problem solution Researching and analysing the most used features and check if the default keyboard shortcuts are convenient for them, or if they have a keyboard shortcut at all, and then assigning better or new shortcuts to them.
Before 25th of April:
- Researching GNOME development further; - Getting more familiar with the Anjuta code;
From 25th of April to 23 of May (before official coding starts):
- Research about the subject (faster keyboard operating); - Communicating and consultations with the community and mentor about the best way to solve this issue. - Creating final goals before the coding starts; - Focusing on other proposed tasks by the mentor.
From 23rd May to 11th June (official coding starts):
- Continuous communication with mentor about planned task; - Working on bugs: https://bugzilla.gnome.org/show_bug.cgi?id=346574 and https://bugzilla.gnome.org/show_bug.cgi?id=591688; - Defining clear goals and tasks to fix concerning the keyboard shortcuts problem. Final preparations before coding.
From 12th June to 23 June:
- Working on bug: https://bugzilla.gnome.org/show_bug.cgi?id=591782; - Coding the changes to be made; - Testing and improving the code; - Constant communication and collaboration with mentor and community.
From 23 June to 6th July:
- The feature/fix involving the most used features of Anjuta, (which now will have more convenient keyboard shortcuts,and the ones who didn't have before will have new assigned), will land here. - Implementing suggested improvements suggested by mentor, community and by various tests;
From 7th July to 23rd July:
- Working on bugs: https://bugzilla.gnome.org/show_bug.cgi?id=615084 and https://bugzilla.gnome.org/show_bug.cgi?id=564269; - Evaluation period for the changes; - Focusing on additional tasks by mentor.
From 23rd of July to 31 July:
- Making documentation about the changes and improvements made in the code; - Running additional tests if needed.
From 1th of August to 22nd of August:
- Improving user documentation to reflect best practices and fast keyboard navigation. - Working on bug: https://bugzilla.gnome.org/show_bug.cgi?id=610387.
What will showable at mid-term [1]?
- Yes, as the timeline says, it will be showable at the midterm.
Why do you think you are be the best person to work on this project?
- Although I am new to GNOME development, making my initial contribution I got found of coding for GNOME. It is challenging and yet interesting. I also can contribute specifically to this task, because I already posted one patch for Anjuta and I am familiar with the code. I also already did some research аnd many Anjuta and GNOME users overall would love to see some improvements in operating with the keyboard, so I would love to help users get what they need.
What are your past experiences (if any) with the open source world?
- I've been using Ubuntu for a while, and I've just started attending the local FOSS community meetings. I haven't contributed to any free software projects before I made this patch as a contribution, but I would love to get more involved in the GNOME community and contribute as much as I can.
Why are you interested in improving GNOME?
- I would love to contribute to a free software. I like idea anyone contribute to make it better and more useful, and I would love to be a part of that. I also think that GNOME has a lot of potential, and I would love to be a part of it's future.
Please attach a link to a bug (bugzilla.gnome.org or other Free Software tracker) containing a patch you've written.
[1] All students are invited to attend GUADEC and present their project there, which is right after the midterm evaluation deadline.