From f8971ac3a13639d1bb1d2a3f150b0ec961ed967c Mon Sep 17 00:00:00 2001
From: alanef <alan@fullworks.net>
Date: Sun, 12 Nov 2023 16:24:47 +0000
Subject: [PATCH 1/3] Proposed change to guideline 4 to clarify use of build
 tools

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

diff --git a/guideline-04.md b/guideline-04.md
index 6cbe22e..3b42435 100644
--- a/guideline-04.md
+++ b/guideline-04.md
@@ -1,12 +1,13 @@
-<h4>4. Code must be (mostly) human readable.</h4>
+<h4>4. Original source code and  build tools must be publicly available.</h4>
 
-Obscuring code by hiding it with techniques or systems similar to <code>p,a,c,k,e,r</code>'s obfuscate feature, uglify's mangle, or unclear naming conventions such as <code>$z12sdf813d</code>, is not permitted in the directory. Making code non-human readable forces future developers to face an unnecessary hurdle, as well as being a common vector for hidden, malicious code.
-
-We require developers to provide public, maintained access to their source code and any build tools in one of the following ways:
+We require developers to provide public, maintained access to their original source code and any build tool configuration files and custom build tools in one of the following ways:
 
 <ul>
-    <li>Include the source code in the deployed plugin</li>
-    <li>A link in the readme to the development location</li>
+<li>Include the source code any build tool configuration files and custom build tools in the deployed plugin</li>
+<li>A link in the readme to the development location<li></li>
 </ul>
 
-We strongly recommend you document how any development tools are to be used.
+We strongly recommend you document how any build tools are to be used.
+
+Original source code must be human readable and not be deliberately obscured.
+

From 52a11af1d3ee39993e6af5fc7c07c998b0a6e691 Mon Sep 17 00:00:00 2001
From: alanef <alan@fullworks.net>
Date: Sun, 12 Nov 2023 18:39:39 +0000
Subject: [PATCH 2/3] Adjust to review comments

---
 guideline-04.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/guideline-04.md b/guideline-04.md
index 3b42435..86a6195 100644
--- a/guideline-04.md
+++ b/guideline-04.md
@@ -3,8 +3,8 @@
 We require developers to provide public, maintained access to their original source code and any build tool configuration files and custom build tools in one of the following ways:
 
 <ul>
-<li>Include the source code any build tool configuration files and custom build tools in the deployed plugin</li>
-<li>A link in the readme to the development location<li></li>
+<li>Include the source code, any build tool configuration files and custom build tools (if any) in the deployed plugin</li>
+<li>A link in the readme to the development location</li>
 </ul>
 
 We strongly recommend you document how any build tools are to be used.

From 2e25a9533d5d341b5a3f80998a42d580fe78330e Mon Sep 17 00:00:00 2001
From: alanef <alan@fullworks.net>
Date: Sun, 12 Nov 2023 18:51:32 +0000
Subject: [PATCH 3/3] Adjust to add more about what original source is

---
 guideline-04.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/guideline-04.md b/guideline-04.md
index 86a6195..d752d4c 100644
--- a/guideline-04.md
+++ b/guideline-04.md
@@ -9,5 +9,8 @@ We require developers to provide public, maintained access to their original sou
 
 We strongly recommend you document how any build tools are to be used.
 
-Original source code must be human readable and not be deliberately obscured.
+Original source code must be the original edit of the code and not minified or otherwise altered after editing. 
+Original source code should be written so it is clearly understandable using sensible naming conventions and comments where appropriate
+and not deliberately obscured or obfuscated.
+