To make time line I usually do the following:
1- Define from where I will start  and what the end result I want to achieve.
2- See what tools and technologies I will have to learn in order to achieve my goal.
3- Define the project architecture. It’s good practice that my project architecture follow a well known design pattern like Model-View-Controller (MVC) or whatever is suitable for my project. But if I can’t make my project follow a well known pattern it’s OK design pattterns are not for all type of project. But always try to make your architecture into layers and modules.
4- Divide my big goals into millstones. Each millstone  means I have something that can work and can be tested. For example, if I’m following Model-View-Controller (MVC) design Pattern then finishing the model is a millstone and finishing the view is a millstone, also finishing the controller is a millstone, testing is millstone, packaging is a millstone, etc..
5- On each millstone I try to divide it to a smaller tasks like I want to implement class A on day1 and class B on day2, I want to test module X on day 3, etc.
6- Always put some time for catchup in case I didn’t follow the timetable. GSoC is very short programm so I guss you can’t put more than week for catch up.
7- Always Revise the time line you put on the proposal during the Community Bonding period because once I know more about my project I will be able define more accurate time line.
8- Always do weekly progress reports even I don’t made any progress. By this way I always put the time table on mind and do my dest to follow it.

What's open source

MySQL GSoC 2008 Logo

Free Ubuntu CD

The seconad was sunny! and I did better than the first day. On the second day I talk specificlly on GSoC and how to join this program. But I notice that some of the students have some fears from participating such big program some of them might think “Oh, this is Google and the most prestigious FOSS organizations what I’m going to do! “. I belive GSoC is a challenging program in which I pushed my self to the limit. GSoC is designed for students and they know that you’re a student and you’re here to have fun and learn.

GSoC Statistics

Google Summer of Code™ 2009 Logo

1. Look at the previous GSoC mentoring organizations, most of them has already published this year ideas list. You might try using Google search engine to search for ‘Google Summer of Code 2009 Ideas’.
2. Try thinking of those ideas, see what might interest you. I would remind you that GSoC is about three to four months you don’t have much time for big projects. Also, being ambitious is good but remember you have to be realistic about your project don’t over take projects that are over your capabilities. In GSoC you’re going to learn a lot of things and you mostly you will not have all the knowledge and experience to do the project. But you should got the basics and you have all the summer to learn and work. So, the best thing is to try to balance between what you already have and between what you’re going to learn.
3. Make short list about 5 to 7 projects from different organizations. You free to select more, but big list will distract you. Also, try to select projects that have similarities on your advantage, like all the project on your list use PHP and you have PHP experience.
4. Start walking around on the mailing lists and IRC channels for these projects.
5. It will rise your chance to be accepted if you send patches for those projects, but if you don’t it’s OK.
6. If you feel that those projects on the short list is hard and over your capabilities don’t panic. Try thinking again on that project sometimes project look very hard at the first time but when you think of it or discuss it with your friends you will see how easy it is. If you think of the project one time after another and you still find it very hard it’s OK, try looking for other projects.
7. Note: not all organizations that apply for GSoC will be accepted. It’s also competitive for the mentoring organizations, so be sure that your short list contain projects from at least three diffrent mentoring organizations.

The First day I will introduce the Open Source and the philosophy behind it. On the second day, I will talk about Google Summer of Code. And on the third day I will talk about Open Source developments and the things that will be useful for students to learn before  joining Google Summer of Code.

Google Summer of Code™ Your Way to a Global Mission Workshop Invitation

Note: Each attandant student will get a free copy of Ubuntu Linux from PNINA and will get GSoC sticker from Google