# NTP Source Code

**URL:** <https://community.nwtime.org/t/ntp-source-code/90>\
**Category:** Source Code\
**Created:** [January 28, 2026, 5:00pm UTC](https://community.nwtime.org/t/ntp-source-code/90 "2026-01-28T17:00:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dru](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nwtime.org/dru/32/337_2.png) [@Dru](https://community.nwtime.org/u/Dru)\
**Post date:** [January 28, 2026, 5:00pm UTC](https://community.nwtime.org/t/ntp-source-code/90/1 "2026-01-28T17:00:08Z")

</div>

The NTP source code is available on GitHub.

> **[GitHub - ntp-project/ntp: The full and complete NTP Reference Implementation...](https://github.com/ntp-project/ntp/)**
>
> The full and complete NTP Reference Implementation from the Network Time Protocol Project at Network Time Foundation.

---

<div class="post-metadata">

**Author:** ![msommer](https://avatars.discourse-cdn.com/v4/letter/m/dbc845/32.png) [@msommer](https://community.nwtime.org/u/msommer)\
**Post date:** [March 17, 2026, 5:48am UTC](https://community.nwtime.org/t/ntp-source-code/90/2 "2026-03-17T05:48:30Z")

</div>

Thank you for the GitHub mirror.  
How often do you plan to update the mirror with the bk source code?

Thanks in advise.

Kind regards Michael

---

<div class="post-metadata">

**Author:** ![harlan](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nwtime.org/harlan/32/8_2.png) [@harlan](https://community.nwtime.org/u/harlan)\
**Post date:** [June 3, 2026, 10:17pm UTC](https://community.nwtime.org/t/ntp-source-code/90/3 "2026-06-03T22:17:01Z")

</div>

Hi Michael,

I’m working on getting -stable and -dev code publication automated again.

Right now, it’s a manual process to take internal master repo commits and get them pushed out to the public repositories. The goal is to get the automated publication process working again.

What I’d like to see is that any commit to the internal BK repo causes:

- an automatic push to the public BK repo
- an automatic push to the “BK to git” internal repo
- Commits to the internal git repos auto-push to the public git repos

and a daily check that any new work on -dev will cause the generation of a point release that is also offered as a tarball.

OK?

H