r52 - 2013-06-13 - 08:05:53 - HarlanStennYou are here: NTP >  Dev Web > GoogleSummerOfCode
NTP users are strongly urged to take immediate action to ensure that their NTP daemon is not susceptible to use in a reflected denial-of-service (DRDoS) attack. Please see the NTP Security Notice for vulnerability and mitigation details, and the Network Time Foundation Blog for more information. (January 2014)

Google Summer Of Code

Related Topics: NTF:Main/GoogleSummerOfCode PTPd:Main/GoogleSummerOfCode

Student Application Template

Please see NTF:Main/GoogleSummerOfCodeStudentApplicationTemplate for the Student Application Template.

Project Ideas

Please see GSoCProjectIdeas for some NTP-related GSoC project ideas.

Feel free to add more ideas!

If you are a student who would like to work on a project (either one you see here or one you think of), please speak up! It would help if we could see what sort of work you can do. An easy way to show us is to find an open bug report, fix it, and submit the patch. There are project developers who are happy to work with you and help you to do this.


NTP is participating in the 2013 Google Summer Of Code effort, under the Network Time Foundation (GSoC Organization ID "networktime"). Here's the timeline for GSoC 2013.

The following projects were accepted:

GSoC 2013 Accepted Projects


NTP is participating in the 2012 Google Summer Of Code effort, under the Network Time Foundation (GSoC Organization ID "networktime"). Here's the timeline for GSoC 2012.

The following projects were accepted for NTP:

GSoC 2012 Accepted Projects


NTP is very happy to be a mentoring organization for the 2011 Google Summer Of Code effort.

Please see the timeline for GSoC 2011.

The following projects were accepted:

GSoC 2011 Accepted Projects


The NTP Forum is very happy to be a mentoring organization for the 2010 Google Summer Of Code effort.

Please see the timeline for GSoC 2010.

The following projects were accepted:

GSoC 2010 Accepted Projects

2010 Applications

Please include the following information in your application (which should be done at the Google site, not here):

  • Abstract of your project
  • Times that you will busy/unavailable during the 2010 GSoC period.
  • Are you applying to any other GSoC groups? If so, which one(s)?
  • Do you have any examples of your work we could see?
  • Contact information
    • Name
    • e-mail
    • phone number
    • physical address
  • Backup contact (in case you go "missing")

Please meet and talk to us on IRC or on our mailing lists.


The NTP Forum is again very pleased to have been accepted for inclusion in the Google Summer Of Code effort.

GSoC 2009 Accepted Projects

GSoC 2009 comments

hi all,

this is Kapila , from Sri Lanka, regrading the Gnu AutoGen project proposal. this is about what came in to my mind when i studying the project. we want to generate different document formats for same code base. so can we do it in this way. we let programmer who write source code to decide out put format and we can have interpreter which read the source code and analyze the source using it's key words and other language specific features and using these as a parameters we can produce unique documents in different format . simple example is job of a translator , he know many languages so he convert one language in to many , i like to here form you what you think about this.

-- KapilaBogahapitiya - 20 Mar 2009

Kapila, there is more information at GSoC2008doc. AutoGen currently supports .texi tags, and we want to eventually support .man, .mandoc, .pod, and perhaps some others. If properly designed, once we support .texi and .man we'll have enough done that we can implement our documentation, and adding the other target formats should be much easier.

-- HarlanStenn - 20 Mar 2009

Last year i worked on this project and this project is not as simple as it seems. AutoGen is made in such way that it needs a major changes to to add the functionality,as writing some code in perl instead of used sed script. The manual pages generated by AutoGen are not so flexible.

-- RahulKumar - 21 Mar 2009

Hi Rahul,

You are absolutely correct, and you and I learned a lot about the very many ways that this project is made up of many pieces. This project seems simple, but the implementation stages need to be documented and planned, and we need to choose carefully what steps need to be implemented, and the different ways they could be implemented, in order to get a "usable core" out of it. This project is one that will eventually take a fair amount of work to get fully completed.

-- HarlanStenn - 21 Mar 2009

Thanks Rahul and Harlan for the views. According to these information , first thing we don't want to reinvent the wheel . Out come won't be a good user friendly package if it differs from existing design since users has to change or learn. To achieve this we should have clear understanding of existing code base to integrate new feature. so this should be new plug-in for existing package and it should make it more worth wile with out making it hazard to users. am i correct?

-- KapilaBogahapitiya - 21 Mar 2009

I have a brownie point available to the first person to identify the timekeeping error on the timeline for GSoC2009 page. :) Thanks for your interest in the NTP Forum's Google Summer of Code 2009.

-- DaveHart - 23 Mar 2009

Is it that "March 9: ~12 noon PST / 19:00 UTC" mentions a "PST" time instead of a "PDT" time even though daylight savings time in the U.S. started on March 8 this year?

-- BreckBeatie - 23 Mar 2009

Yes, in fact I had it wrong when I asked the question. I did not realize they got the date of transition wrong (good eye), what I caught was the consistent offset from UTC across (apparently) the transition. Good job.

-- DaveHart - 24 Mar 2009


I am an interested candidate for GSoC . I was going through the list of ideas, and came across the problem of updating NTPQ, as one of the ideas. Can you please provide more information on this? All I can gather is that it is related to IPv6 packets and their display. So, I assume the time synch messages sent as IP packets, and the problem is to display the 128-bit source and destination IPv6 addresses? Also, where does the authentication information come from?

Thanks, Smita

-- SmitaVijayakumar - 30 Mar 2009

Hi Everyone,

My name is Anthony, and I've proposed a hardware/firmware/software project.. I would like to get the NTP community helping me and involved with the development of a high-throughput (Gig-E linerate), low jitter (only 8ns max) stratum-1 NTP server. This is similar to a project described here: http://www2.nict.go.jp/w/w114/tsp/publication/PDF/f-poster1-ptb-bipm.pdf , however my implementation doesn't require a host PC and is designed to be low-cost and low-power. I've already verified some firmware (timestamping and ARP+NTP datapath) on a prototyping board, and have fabricated an initial prototype PCB. So the project would consist of porting existing work to opensource languages and tools, fixing problems in the first prototype, and implementing a management interface so changes don't require re-synthesis of firmware. I would very much like to hear of any questions or comments..

Thanks, Anthony

-- AnthonyBlake - 02 Apr 2009


The NTP Forum was successful in getting several proposals needed by the NTP Project accepted by the 2008 Google Summer Of Code project.

Here are links to the projects. If you have any ideas for projects for next year, please let us know!

Related Topics:

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r52 < r51 < r50 < r49 < r48 | More topic actions
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2014 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding the site? Send feedback