Recent changes to Absent Directives

Absent Directives modified by Stephen

Stephen — Thu, 20 Aug 2015 12:43:11 -0000

--- v5
+++ v6
@@ -11,10 +11,10 @@
 Achieved in part from simplicity and correctness. There is no reason great enough to compromise on security.

 ###### Correctness
-Do what is right regardless of performance or usability impact. This more often than not leads to security and by association carries the same weight.
+Do what is right regardless of performance or usability impact. This often leads to security and by association carries the same weight.

 ###### Stability
-Stability is a noticeable indicator of security, simplicity, and correctness.
+Stability is an observable indicator of security, simplicity, and correctness.

 #### Goals

Absent Directives modified by Stephen

Stephen — Thu, 20 Aug 2015 12:12:18 -0000

--- v4
+++ v5
@@ -1,6 +1,6 @@
 #### Goals and Directives ####

-All projects should have a set of goals or directives to govern its development to keep it focused. This linux is being developed within a set of Directives while striving to achieve additional goals.
+All projects should have a set of goals or directives to govern its development to keep it focused. This OS is being developed within a set of Directives while striving to achieve additional goals.

 #### Directives ####

Absent Directives modified by Stephen

Stephen — Wed, 11 Feb 2015 17:48:00 -0000

--- v3
+++ v4
@@ -1,18 +1,34 @@
-Goals and Directives
---------------------
-All projects should have a set of goals or directives to govern its development to keep it focused. This linux is being developed within a set of Directives while trying to achieve additional goals.
+#### Goals and Directives ####

-Directives
+All projects should have a set of goals or directives to govern its development to keep it focused. This linux is being developed within a set of Directives while striving to achieve additional goals.

-1. Simplicity, do not over complicate the code or system functionality. Simplicity does not mean user friendly.
-2. Security, achieved in part from simplicity and correctness.
-3. Correctness, do what is right regardless of performance or usability impact.
-4. Stability, if the system is not stable it is not correct.
-5. Automation, if there is no need to do a function manually then it should be automated within the reach of simplicity, security, and correctness.
-6. Portability, seek to make all parts interchangeable with minimal difficulty or changes to system.
-7. Be posix and standards compliant where sane to do so.
-8. Be true to the unix philosophy.
-9. Adapt new techniques or technologies where able to do so without conflict to directives.
+#### Directives ####
+
+###### Simplicity
+Do not over complicate the code or system functionality. Simplicity does not mean user friendly. One key to Simplicity is the Unix Philosophy.
+
+###### Security
+Achieved in part from simplicity and correctness. There is no reason great enough to compromise on security.
+
+###### Correctness
+Do what is right regardless of performance or usability impact. This more often than not leads to security and by association carries the same weight.
+
+###### Stability
+Stability is a noticeable indicator of security, simplicity, and correctness.
+
+#### Goals
+
+###### Automation
+Time is important and computers are present to facilitate automation. Anything that can be automated without taking away from Directives or user control should be.
+
+###### Portability
+Seek to make all parts interchangeable with minimal difficulty or changes to system.
+
+###### Compliance 
+Be Posix and standards compliant where sane to do so. This is crucial for retaining cross system compatibility increasing ease of project migrations.
+
+###### Innovate
+Adapt new techniques or technologies where able to do so without conflict to Directives.

 [Home]

Absent Directives modified by Stephen

Stephen — Wed, 11 Feb 2015 17:16:52 -0000

--- v2
+++ v3
@@ -1,7 +1,8 @@
-Absent OS 
-A unix based system
+Goals and Directives
+--------------------
+All projects should have a set of goals or directives to govern its development to keep it focused. This linux is being developed within a set of Directives while trying to achieve additional goals.

-All projects should have a set of goals or directives to govern its development less it be overwhelmed with useless features and bloat. These are the reasons I have not been satisfied with various linux and bsd distributions and so these are the directives to which Absent OS will adhere. 
+Directives

 1. Simplicity, do not over complicate the code or system functionality. Simplicity does not mean user friendly.
 2. Security, achieved in part from simplicity and correctness.

Absent Directives modified by Stephen

Stephen — Sun, 25 Jan 2015 07:25:26 -0000

--- v1
+++ v2
@@ -12,3 +12,6 @@
 7. Be posix and standards compliant where sane to do so.
 8. Be true to the unix philosophy.
 9. Adapt new techniques or technologies where able to do so without conflict to directives.
+
+
+[Home]

Absent Directives modified by Stephen

Stephen — Sun, 25 Jan 2015 07:25:11 -0000

Absent OS
A unix based system

All projects should have a set of goals or directives to govern its development less it be overwhelmed with useless features and bloat. These are the reasons I have not been satisfied with various linux and bsd distributions and so these are the directives to which Absent OS will adhere.

Simplicity, do not over complicate the code or system functionality. Simplicity does not mean user friendly.
Security, achieved in part from simplicity and correctness.
Correctness, do what is right regardless of performance or usability impact.
Stability, if the system is not stable it is not correct.
Automation, if there is no need to do a function manually then it should be automated within the reach of simplicity, security, and correctness.
Portability, seek to make all parts interchangeable with minimal difficulty or changes to system.
Be posix and standards compliant where sane to do so.
Be true to the unix philosophy.
Adapt new techniques or technologies where able to do so without conflict to directives.