From Fedora Project Wiki

No edit summary
 
(23 intermediate revisions by 2 users not shown)
Line 1: Line 1:
For information how to complete this form, refer to [[Summer Coding 2010 step-by-step for students]].
{{admon/important|Proposal deadline is passed. This page is locked.|Do not change any details on this page.  If must change something, talk with the project mentor first.}}
 
== Random list of application requirements ==
 
# Must include a schedule that was worked out with mentor
# Keep on eye on the ''Talk:'' page that is associated with the proposal page you create.  Click on the ''discussion'' link on the top of your proposal page. The Talk: page is where mentors comment on your proposal.
# Make sure you have clicked on the ''watch'' link on the top of your proposal page(s) and Talk: page(s).  Use the link to ''my preferences'' at the top of the page to set your ''Watchlist'' preferences to email you when changes are made.


== About me ==
== About me ==
Line 13: Line 7:
{{:Summer_Coding_2010_student_application_-_Michal_Luscon}}
{{:Summer_Coding_2010_student_application_-_Michal_Luscon}}


== About your project ==
== About my project ==
 
# Project name: KUI
# Project comes from [[Summer_Coding_2010_ideas_-_KDE_Usablity_tool]].
# 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?
# What is the timeline for development of your project? The Fedora Summer Coding work period is 11 weeks long, May 24 - August 9; 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 (July 5-12); the last steps always take longer than you think, and we will consider canceling projects that are not mostly working by then.
#* If your project development progresses differently so there is not 90% functionality by the mid-term, you '''must''' be in regular contact with your mentor about this.  Your mentor must not be surprised about the state of your project when the mid-term comes.
#* If you are not progressed this far in mid-term, you must have a plan with your mentor to fix the situation.
# 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.


== You and the community ==
<li>Project name: KUI</li>
<li>Kui will be practical part of bachelors thesis about application usability.
<li>Project comes from [[Summer_Coding_2010_ideas_-_KDE_Usablity_tool]].</li>
<li>The main idea of KUI project is recording and storing all relevant informations about users behaviour in third Qt applications. Mouse trajectories, usage of buttons and menus would be very helpful for designing users interfaces in Fedora. Next part of project consists of stored data visualization mainly creating videos, graphs and bitmaps.</li>
<li>In FSOC program I will realize simple console tool for recording desktop or single application and QtGUI for this tool.</li>
<li>KUI also will be used by "System Config Tools cleanup" project.</li>


# If your project is successfully completed, what will its impact be on the Fedora 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 Fedora community, at least one of whom should be a Fedora Summer Coding mentor. Provide email contact information for non-Summer Coding mentors.
== Timeline ==
# What will you do if you get stuck on your project and your mentor isn't around?
<ul>
# In addition to the required blogging minimum of twice per week, how do you propose to keep the community informed of your progress and any problems or questions you might have over the course of the project?
<li>4.6-18.6: School examinations</li>
<li>19.6-22.6: Studying of recording libraries</li>
<li>23.6 - Start coding console part</li>
<li>14.7 - Console part is complite</li>
<li>15.7 - Start coding Gui part</li>
<li>29.7 - Gui part is complite</li>
<li>30.7-9.8 - Bughunting</li>
</ul>


== Miscellaneous ==
== Miscellaneous ==
# We want to make sure that you are prepared before the project starts
<ul>
#* Can you set up an appropriate development environment?
<li>Can you set up an appropriate development environment?</li>
#* Have you met your proposed mentor and members of the associated community?
Of course I can.
# What is your t-shirt size?
# Describe a great learning experience you had as a child.
# Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
 
<!-- Delete this paragraph and the following one when preparing your application. -->Note: you will post this application on the wiki in the category [[:Category:Summer Coding 2010 applications]]. We encourage you to browse this category and comment on the talk page of other applications. Also, others' comments and your responses on the talk page of your own application are viewed favorably, and, while we don't like repetitive spam, we welcome honest questions and discussion of your project idea on the mailing list and/or IRC.


The NeL project has some good general recommendations for [http://dev.ryzom.com/projects/nel/wiki/GSoC2009WritingProposals writing proposals]. We encourage Summer Coding code to include tests.
<li>Have you met your proposed mentor and members of the associated community?</li>
Yes, I had meeting with [[JaroslavReznik]].
<li>What is your t-shirt size?</li>
M
</ul>


== Comments ==
== Comments ==

Latest revision as of 16:02, 4 June 2010

Important.png
Proposal deadline is passed. This page is locked.
Do not change any details on this page. If must change something, talk with the project mentor first.

About me

  • name: Michal Luscon
  • email: dizieg(at)gmail.com
  • username: dizie
  • IRC nickname: dizie
  • primary language: Slovak/Czech
  • location: Czech Republic

    • About my project

  • Project name: KUI
  • Kui will be practical part of bachelors thesis about application usability.
  • Project comes from Summer_Coding_2010_ideas_-_KDE_Usablity_tool.
  • The main idea of KUI project is recording and storing all relevant informations about users behaviour in third Qt applications. Mouse trajectories, usage of buttons and menus would be very helpful for designing users interfaces in Fedora. Next part of project consists of stored data visualization mainly creating videos, graphs and bitmaps.
  • In FSOC program I will realize simple console tool for recording desktop or single application and QtGUI for this tool.
  • KUI also will be used by "System Config Tools cleanup" project.

    • Timeline

    • 4.6-18.6: School examinations
    • 19.6-22.6: Studying of recording libraries
    • 23.6 - Start coding console part
    • 14.7 - Console part is complite
    • 15.7 - Start coding Gui part
    • 29.7 - Gui part is complite
    • 30.7-9.8 - Bughunting

    Miscellaneous

    • Can you set up an appropriate development environment?
      • Of course I can.
    • Have you met your proposed mentor and members of the associated community?
      • Yes, I had meeting with JaroslavReznik.
    • What is your t-shirt size?
      • M

    Comments

    Use the Talk:Summer Coding 2010 student proposal application to actually make comment, which then appear here on the main proposal page. You can use this link to make a new comment].

    plus talk

Retrieved from "https://fedoraproject.org/w/index.php?title=Summer_Coding_2010_proposal_-_Kde_usability_inspector&oldid=178043"