Differences between revisions 2 and 3
Revision 2 as of 2014-03-17 15:12:33
Size: 3174
Editor: ?NicolaeAlexandru
Comment:
Revision 3 as of 2014-03-20 21:15:12
Size: 4428
Editor: ?NicolaeAlexandru
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
* I understand what the project wants and an idea about how to do it  * I understand what the project wants and an idea about how to do it
Line 15: Line 15:
* I have experience as a programmer  * I have experience as a programmer
Line 17: Line 17:
* I want to develop new abilities regarding programming, working with Linux architecture and working with a compiler  * I want to develop new abilities regarding programming, working with Linux architecture and working with a compiler
Line 19: Line 19:
* I think an important step in becoming a good programmer is understanding how the compiler works and I want to improve my programming skills  * I think an important step in becoming a good programmer is understanding how the compiler works and I want to improve my programming skills
Line 21: Line 21:
* I spent the last couple of weeks collecting information about the project from the mentor and the official site of the project  * I spent the last couple of weeks collecting information about the project from the mentor and the official site of the project
Line 23: Line 23:
* I am good at working in a team  * I am good at working in a team
Line 25: Line 25:
* I am a big fan of the open source idea because I think paying for a software is like paying for a theorem or an algorithm  * I am a big fan of the open source idea because I think paying for a software is like paying for a theorem or an algorithm
Line 27: Line 27:
* I want to work hard and help the community  * I want to work hard and help the community
Line 33: Line 34:
 * '''Project schedule''': I believe that the schedule and the goal should be fixed by the mentor. I can start anytime the mentor will decide.  * '''Project schedule''':

 * From now - April 20

         * Learn and understand better how to build with clang instead of the classic GNU compiler

         * Work on the easy bugs in coordination with the mentor and the community to solve as many as possible and leave only the medium, hard and uncategorized bugs for the summer

 * April 20 - May 24

        * Work on the medium bugs and try to categorize the ones that are not categorized yet
                    
        * Fix the easy and medium bugs that appear from the uncategorized bugs list

        * Review the list of bugs and verify if the bugs that are already fixed did not relapsed or have created another ones

 * May 24 - June 13

        * The work will get a little slower in this period because of the exams

        * Start working on hard bugs

 * June 13 - August 1

        * Fix all the hard bugs

        * Bring the bug count down to zero

 * August 1 - August 18

        * Couple of days off

        * Make sure that are no other bugs left

        * Make a documentation with all the fails,their fixes and how to avoid them in the future

        * Review the documentation and submit my work

 **** I can work 8-10 hours a day, 5-6 days a week and the time I will have lost with the exams and the vacation in August I will recover by working Sundays
Line 35: Line 75:
 * '''Other summer plans''': I plan a short vacation in the early August but I will have internet connection and i can continue working on the project.  * '''Other summer plans''': I plan a short vacation in the early August but I will have Internet connection and i can continue working on the project.

Student Application Template

To fill this in, copy the source text. Please don't rename the template.

This is a suggestion for the kind of information we'll find useful from students in their submissions. Remember -- you're going to be committing to several months' work. The more information and planning you can provide up-front, the more we (and Google!) will have to go on when we're ranking your application. Do not forget adding your submission at SummerOfCode2013/StudentApplications

  • Name: Nicolae Alexandru

  • Contact/Email: nicolae.alexandru1406@gmail.com

  • Background: I am an automation and computer science student at Politehnica University of Bucharest. I started to learn C/C++ 5 years ago in high school and in the last year I started to learn Java, Python, CSS, SQL by myself in order to improve my abilities as a programmer.

Why do I think I am the right person for this project? Mostly because:

  • I understand what the project wants and an idea about how to do it
  • I have experience as a programmer
  • I want to develop new abilities regarding programming, working with Linux architecture and working with a compiler
  • I think an important step in becoming a good programmer is understanding how the compiler works and I want to improve my programming skills
  • I spent the last couple of weeks collecting information about the project from the mentor and the official site of the project
  • I am good at working in a team
  • I am a big fan of the open source idea because I think paying for a software is like paying for a theorem or an algorithm
  • I want to work hard and help the community
  • Project title: Debian built with clang

  • Project details: For the last couple of years improvements have been made regarding building Debian with clang instead of gcc. In present, clang is almost complete and compile most of the libraries,but there are still some packages that clang do not compile because it is more strict than gcc.

  • Synopsis: The project goal is to find a way to patch all the packages that clang rejects.

  • Benefits to Debian: It will improve the quality of source's packages and also time spent on compiling and debugging.

  • Deliverables: An archive with all the Debian packages built with clang.

  • Project schedule:

  • From now - April 20
    • Learn and understand better how to build with clang instead of the classic GNU compiler
    • Work on the easy bugs in coordination with the mentor and the community to solve as many as possible and leave only the medium, hard and uncategorized bugs for the summer
  • April 20 - May 24
    • Work on the medium bugs and try to categorize the ones that are not categorized yet
    • Fix the easy and medium bugs that appear from the uncategorized bugs list
    • Review the list of bugs and verify if the bugs that are already fixed did not relapsed or have created another ones
  • May 24 - June 13
    • The work will get a little slower in this period because of the exams
    • Start working on hard bugs
  • June 13 - August 1
    • Fix all the hard bugs
    • Bring the bug count down to zero
  • August 1 - August 18
    • Couple of days off
    • Make sure that are no other bugs left
    • Make a documentation with all the fails,their fixes and how to avoid them in the future
    • Review the documentation and submit my work
  • *** I can work 8-10 hours a day, 5-6 days a week and the time I will have lost with the exams and the vacation in August I will recover by working Sundays
  • Exams and other commitments: I will have exams in the May 24 - June 13 period,but that will not interfere with my work for the project.

  • Other summer plans: I plan a short vacation in the early August but I will have Internet connection and i can continue working on the project.

  • Why Debian?: I have chosen Debian because it is one of the most user friendly Linux distribution, I have Debian installed on my computer and I will love the opportunity to work to improve the architecture and to understand more how a compiler works.

  • Are you applying for other projects in SoC?: No,I want to focus my work on this project only.