github-starred/awesome-sysadmin
2
0
Fork 0
mirror of https://github.com/awesome-foss/awesome-sysadmin.git synced 2026-05-06 02:18:54 -05:00
Code Issues 452 Packages Projects Releases Wiki Activity

[PR #728] [MERGED] Rename the section to time servers and add PTP/Roughtime tools #5855

New Issue
Closed
opened 2026-05-02 17:15:51 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-02 17:15:51 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/awesome-foss/awesome-sysadmin/pull/728
Author: @Ashith04
Created: 3/30/2026
Status: ✅ Merged
Merged: 4/2/2026
Merged by: @Technetium1

Base: master ← Head: patch-1

📝 Commits (3)

  • 993b543 Rename the section to time servers and add PTP/Roughtime tools
  • 4f6e98e Update time synchronization tools list with licenses
  • d59e0e6 Formatting the document (Leave a space after time server )

📊 Changes

1 file changed (+14 additions, -0 deletions)

View changed files

📝 README.md (+14 -0)

📄 Description

Thank you for taking the time to work on a PR for Awesome-Sysadmin!

To ensure your PR is dealt with swiftly please check the following:
Resolving issue #423. Based on maintainer feedback, I have broadened the requested category to "Time Servers" to accommodate PTP and Roughtime protocols alongside NTP.

  • Your additions are Free software
  • Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
  • Submit one item per pull request. (Note: Adding a new section of 5 items to resolve Issue #423 as discussed)
  • Format your submission as follows...
  • Additions are inserted preserving alphabetical order.
  • Additions are not already listed at awesome-selfhosted
  • The Language tag is the main server-side requirement...
  • You have searched the repository for any relevant issues or PRs...
  • Any category you are creating has the minimum requirement of 3 items.
  • Any software project you are adding to the list is actively maintained.
  • The pull request title is informative...

  • Why is it awesome?
    It fulfills an open community request (Issue #423) and creates a robust, future-proof "Time Servers" category that tracks standard implementations across NTP, PTP, and Roughtime protocols.

  • Have you used it? For how long?
    Yes, tools like Chrony are foundational infrastructure I rely on for network monitoring and system tracking projects.

  • Is this in a personal or professional setup?
    Both.

  • How many devices/users/services/... do you manage with it?
    N/A - This is a baseline requirement for all networked servers.

  • Biggest pros/cons compared to other solutions?
    By including NTPsec, Statime (PTP), and Roughenough (Roughtime), this section now covers the spectrum from legacy precision to modern cryptographic time security.

  • Any other comments about your use case, things you've found excellent, limitations you've encountered... ?
    Thank you to the reviewers for the excellent feedback on broadening the category name!

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/awesome-foss/awesome-sysadmin/pull/728 **Author:** [@Ashith04](https://github.com/Ashith04) **Created:** 3/30/2026 **Status:** ✅ Merged **Merged:** 4/2/2026 **Merged by:** [@Technetium1](https://github.com/Technetium1) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (3) - [`993b543`](https://github.com/awesome-foss/awesome-sysadmin/commit/993b543eb48756fad06e14b0619869e87fe3a72c) Rename the section to time servers and add PTP/Roughtime tools - [`4f6e98e`](https://github.com/awesome-foss/awesome-sysadmin/commit/4f6e98ec88702d3b263ab9cbed782793e1517528) Update time synchronization tools list with licenses - [`d59e0e6`](https://github.com/awesome-foss/awesome-sysadmin/commit/d59e0e657e19e36074690cfa7fc44ed04ffa92e4) Formatting the document (Leave a space after time server ) ### 📊 Changes **1 file changed** (+14 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+14 -0) </details> ### 📄 Description <!-- IF YOUR PULL REQUEST ADDS NEW SOFTWARE TO THE LIST, DO NOT DELETE THE TEXT BELOW. --> <!-- Please make sure relevant boxes are checked [x] --> Thank you for taking the time to work on a PR for Awesome-Sysadmin! To ensure your PR is dealt with swiftly please check the following: Resolving issue #423. Based on maintainer feedback, I have broadened the requested category to "Time Servers" to accommodate PTP and Roughtime protocols alongside NTP. - [x] Your additions are Free software - [x] Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts). - [x] Submit one item per pull request. *(Note: Adding a new section of 5 items to resolve Issue #423 as discussed)* - [x] Format your submission as follows... - [x] Additions are inserted preserving alphabetical order. - [x] Additions are not already listed at awesome-selfhosted - [x] The `Language` tag is the main **server-side** requirement... - [x] You have searched the repository for any relevant issues or PRs... - [x] Any category you are creating has the minimum requirement of 3 items. - [x] Any software project you are adding to the list is actively maintained. - [x] The pull request title is informative... -------------- - **Why is it awesome?** It fulfills an open community request (Issue #423) and creates a robust, future-proof "Time Servers" category that tracks standard implementations across NTP, PTP, and Roughtime protocols. - **Have you used it? For how long?** Yes, tools like Chrony are foundational infrastructure I rely on for network monitoring and system tracking projects. - **Is this in a personal or professional setup?** Both. - **How many devices/users/services/... do you manage with it?** N/A - This is a baseline requirement for all networked servers. - **Biggest pros/cons compared to other solutions?** By including NTPsec, Statime (PTP), and Roughenough (Roughtime), this section now covers the spectrum from legacy precision to modern cryptographic time security. - **Any other comments about your use case, things you've found excellent, limitations you've encountered... ?** Thank you to the reviewers for the excellent feedback on broadening the category name! --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-02 17:15:51 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
addition
curation
discussion
duplicate
enhancement
feedback needed
fix
help wanted
invalid
non-free
not awesome enough
pull-request
Mirrored from GitHub Pull Request
 question / discussion
reviewers wanted
tools
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-sysadmin#5855
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?