From 94d2be934bd62488b4d4a4d1b2bc21b27f746765 Mon Sep 17 00:00:00 2001
From: SkyFi Geek <45924209+mobileskyfi@users.noreply.github.com>
Date: Thu, 20 Mar 2025 08:13:37 -0700
Subject: [PATCH] update readme with current status; fix minor typos

---
 README.md | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index 6e0d99368..deb824924 100644
--- a/README.md
+++ b/README.md
@@ -2,24 +2,23 @@
 
 > This project is a work in progress, with goal to help ensure GPL complaince for MikroTik RouterOS.  
 
-MikroTik does not currently publish GPL source code, specifically the Linux kernel, on its website or other publicly downloadable place.  Instead, it requires a email request to obtain the source code.  So this repo was created to automate the process and provide it for direct download from GitHub when source is provided by Mikrotik.
-
-TIKOCI will continue to advocate for MikroTik providing regular, on-going, per-build disclosure of GPL/other sources, as required under various open source licenses.    
+MikroTik does not currently publish GPL source code, specifically the Linux kernel, on its website or other publicly downloadable place.  Instead, it requires a email request to obtain the source code.  So this repo was created to automate the process and provide it for direct download from GitHub when source is provided by MikroTik.
 
 > [!WARNING]
-> At time of writing, the only GPL sources received are dated from 2022, and as response to a request for "RouterOS 7.18.2" GPL source.  No other response has been received to date.  
-> While perhaps possible there have not been changes in GPL source code since 2022, the current disclosure leaves more questions on MikroTik GPL compliance. 
+> At time of writing, the only GPL sources received are dated from 2022, and as response to a request for "RouterOS 7.18.2" GPL source.  Upon inquiry, MikroTik support suggested on March 20, 2025, "[w]e are working on a newer patch".
+
+TIKOCI will continue to advocate for MikroTik providing regular, on-going, per-build disclosure of GPL/other sources, as required under various open source licenses.
 
 > [!TIP]
-> Source code from RouterOS 6.41rc38 was found on this unrelated GitHub project, from 8 years ago:
+> This project is focused on current and new versions of RouterOS, although older versions contained GPL code.  Use other resources for older MikroTik GPL disclosures.  For example RouterOS 6.41rc38 was found on this unrelated GitHub project, from 8 years ago:
 > https://github.com/robimarko/routeros-GPL
 
 
 ### Implementation Details
 
-When the GPL/open source code is obtained from MikroTik, it will be manually checked into repo.    This project is mainly _store_ those GPL disclosure publicly.  So the only "code" here is a GitHub Action, `gpl-nag-email.yaml`.  The build script checks MikroTik website for the current "stable" and "latest" versions of RouterOS.  If a version is NOT found in GitHub [Releases](https://github.com/tikoci/mikrotik-gpl/releases), the build will email MikroTik to obtain the GPL source.  The build is schedule to check for new releases daily, and will not send emails if a version has already been requested.
+When the GPL/open source code is obtained from MikroTik, it will be manually checked into this repo.    So this project mainly _stores_ MikroTik's GPL disclosure publicly.  So the only "code" here is a GitHub Action, `gpl-nag-email.yaml`.  The build script checks MikroTik website for the current "stable" and "testing" versions of RouterOS.  If a version is NOT found in GitHub [Releases](https://github.com/tikoci/mikrotik-gpl/releases), the build will email MikroTik to obtain the GPL source.  The build is schedule to check for new releases daily, and will not send emails if a version has already been requested.
 
-When MikroTik response with source, it provided disclosure will be in Releases.  Additional, the expanded contents will be stored in repo by RouterOS version, or date received if version is unclear.  
+When MikroTik response with source, the provided disclosure will be in Releases.  Additional, the expanded contents will be stored in repo by RouterOS version, or date received if version is unclear.  
 
 ### Potential Uses