From: Kevin Day Date: Mon, 2 May 2022 01:24:30 +0000 (-0500) Subject: Update: Add licenses to text files and clarify OSL text. X-Git-Tag: 0.5.10~176 X-Git-Url: https://git.kevux.org/?a=commitdiff_plain;h=313c7f9e3bfdd570d24413475ae3a6e0819b21cb;p=fll Update: Add licenses to text files and clarify OSL text. Minor modifications to the text in the open-standard-license-1.0. One notable change is changing "application" to "applying" because "application" can be mis-interpreted as a program (which are also called applications or app for short). In this context the word "application" is meant to mean "applying". Just change the word to "applying" to avoid this potential confusion. Add more text to the protocol terminology to declare the context is in regards to computers and source code. Add the cc-by-sa-4.0 license file. They do not provide a downloadable copy of the license, so for now just add links. I need to come back and fix this once I get a downloadable text file that I can legally store in the source code and transfer to others. --- diff --git a/documents/cygwin.txt b/documents/cygwin.txt index c2ebf5c..85c58b8 100644 --- a/documents/cygwin.txt +++ b/documents/cygwin.txt @@ -1,4 +1,7 @@ # fss-0002 +# +# license: cc-by-sa-4.0 +# Cygwin: The following are a collection of informal notes on getting this to compile and run under Windows using Cygwin. diff --git a/documents/debugging.txt b/documents/debugging.txt index 182c985..4d05896 100644 --- a/documents/debugging.txt +++ b/documents/debugging.txt @@ -1,4 +1,7 @@ # fss-0002 +# +# license: cc-by-sa-4.0 +# Debugging: There are various tools out there to assist in investigating for problems and debugging the compiled code. diff --git a/documents/private_functions.txt b/documents/private_functions.txt index dfc5603..b15a6a3 100644 --- a/documents/private_functions.txt +++ b/documents/private_functions.txt @@ -1,4 +1,7 @@ # fss-0002 +# +# license: cc-by-sa-4.0 +# Private Functions: One of the objectives of this project is to make as much, if not all, of the functions available for use. diff --git a/documents/readme.txt b/documents/readme.txt index eb5a374..64442d3 100644 --- a/documents/readme.txt +++ b/documents/readme.txt @@ -1,5 +1,7 @@ # fss-0002 # +# license: cc-by-sa-4.0 +# # This readme file is inteded to provide a basic introduction to the Featureless Linux Library (FLL). # diff --git a/documents/return_codes.txt b/documents/return_codes.txt index 71a2a70..5c1131d 100644 --- a/documents/return_codes.txt +++ b/documents/return_codes.txt @@ -1,4 +1,7 @@ # fss-0002 +# +# license: cc-by-sa-4.0 +# Implicit Return Types for f_status_t: When f_status_t is used as the return type, there are a common set of status codes that should always be expected as a possible return value. diff --git a/documents/style_guide.txt b/documents/style_guide.txt index 3987025..b38285c 100644 --- a/documents/style_guide.txt +++ b/documents/style_guide.txt @@ -1,4 +1,7 @@ # fss-0002 +# +# license: cc-by-sa-4.0 +# Style Guide: The Featureless Linux Library uses a set of styles and practices designed in hopes to communicate both explicitly and implicitly multiple meanings and contexts. diff --git a/documents/threads.txt b/documents/threads.txt index b6c94e2..7734b92 100644 --- a/documents/threads.txt +++ b/documents/threads.txt @@ -1,4 +1,7 @@ # fss-0002 +# +# license: cc-by-sa-4.0 +# Threads Documentation: With the inclusion of the f_thread project, the Featureless Linux Library supports and uses threads by default. diff --git a/level_3/control/documents/packet_request.txt b/level_3/control/documents/packet_request.txt index e3b98b1..8bf8179 100644 --- a/level_3/control/documents/packet_request.txt +++ b/level_3/control/documents/packet_request.txt @@ -1,4 +1,7 @@ # fss-0002 +# +# license: open-standard-license-1.0 +# Packet Request: The control program sends packets and receives packet responses from the controller program over the controller program's control socket. diff --git a/level_3/control/documents/packet_response.txt b/level_3/control/documents/packet_response.txt index 3c7dafb..f5dc346 100644 --- a/level_3/control/documents/packet_response.txt +++ b/level_3/control/documents/packet_response.txt @@ -1,4 +1,7 @@ # fss-0002 +# +# license: open-standard-license-1.0 +# Packet Response: The control program sends packets and receives packet responses from the controller program over the controller program's control socket. diff --git a/level_3/utf8/documents/about.txt b/level_3/utf8/documents/about.txt index aa1f774..51b5eec 100644 --- a/level_3/utf8/documents/about.txt +++ b/level_3/utf8/documents/about.txt @@ -1,4 +1,7 @@ # fss-0002 +# +# license: cc-by-sa-4.0 +# About utf8 Documentation: The utf8 program is intended to provide simple support for identifying UTF-8 character sequences with regard to its Unicode codepoint designation. diff --git a/level_3/utf8/documents/output.txt b/level_3/utf8/documents/output.txt index ab55ef2..2b4b27f 100644 --- a/level_3/utf8/documents/output.txt +++ b/level_3/utf8/documents/output.txt @@ -1,4 +1,7 @@ # fss-0002 +# +# license: cc-by-sa-4.0 +# Output Documentation: This program either outputs a binary string representing UTF-8 character sequences or a string representing Unicode codepoints. diff --git a/licenses/cc-by-sa-4.0 b/licenses/cc-by-sa-4.0 new file mode 100644 index 0000000..e672f4e --- /dev/null +++ b/licenses/cc-by-sa-4.0 @@ -0,0 +1,4 @@ +Creative Commons Attribution Share Alike 4.0 International + +see: https://creativecommons.org/licenses/by-sa/4.0/ +see: https://creativecommons.org/licenses/by-sa/4.0/legalcode diff --git a/licenses/open-standard-license-1.0 b/licenses/open-standard-license-1.0 index fabcda4..f96b9f1 100644 --- a/licenses/open-standard-license-1.0 +++ b/licenses/open-standard-license-1.0 @@ -7,11 +7,11 @@ This license applies to the Standards and their Specifications and designates le Terminology: - Standard: A set of rules and guidelines. - Specification: A specific interpretation or clarification of a Standard, such as the documentation that describes how to use or follow a Standard. -- Implementation: The application of some Standard or Specification. +- Implementation: The applying of some Standard or Specification. - API: Application Programming Interface*. - ABI: Application Binary Interface**. - Service: Any action or labor performed by one party for another party (such as one person helping another person). -- Protocol: A Standard focused on communication between two parties (often referring to Internet communication). +- Protocol: In the context of computers and software, this is a Standard focused on communication between two parties (often referring to Internet communication). * The API term is commonly mis-represented as Services or Protocols (such as "Web API"). An API instructs a programmer how to use a dependency when programming some software that utilizes said dependency.