🚀 Release 1.0.3.

Author: justinhartman

.gitignore

@@ -1,2 +1,52 @@
+# Copyright (C) 2018 Justin Hartman (https://justin.hartman.me).
+#
+# This program is free software: you can redistribute it and/or modify
+# it under the terms of the GNU Affero General Public License as
+# published by the Free Software Foundation, either version 3 of the
+# License, or (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU Affero General Public License for more details.
+#
+# You should have received a copy of the GNU Affero General Public License
+# along with this program. If not, see <https://www.gnu.org/licenses/>.
+#
+# -----------------------------------------------------------------------------
+#
+
+######################
+### Additions      ###
+######################
 other/
-.DS_Store
+.vscode
+
+######################
+### macOS Specific ###
+######################
+*.DS_Store
+.AppleDouble
+.LSOverride
+
+# Icon must end with two \r #
+Icon
+
+# Thumbnails #
+._*
+
+# Files that might appear in the root of a volume #
+.DocumentRevisions-V100
+.fseventsd
+.Spotlight-V100
+.TemporaryItems
+.Trashes
+.VolumeIcon.icns
+.com.apple.timemachine.donotpresent
+
+# Directories potentially created on remote AFP share #
+.AppleDB
+.AppleDesktop
+Network Trash Folder
+Temporary Items
+.apdisk

CHANGELOG.md

@@ -1,20 +1,35 @@
+# Project Change-Log
 
-Version 1.0.2 / 2018-05-20
-==================
-ba20f1ff3b483d36a9b5e238249f8ba53da62b0c
+Below is a detailed change-log, along with specific tasks completed, for each
+version released to date.
 
-  * Simplified the `CHANGELOG.md` file.
-  * Added VS Code workspace file.
-  * Added link to LICENSE file.
+## Version 1.0.3 (31/05/2018)
+
+- [#enhancement](#enhancement)
+  - Renamed the `_basic/` template folder to a more appropriate name; `_core/`.
+  - Updated the `.gitignore` template.
+  - Enhanced the `PULL_REQUEST_TEMPLATE.md` by becoming more human.
+- [#bugfix](#bugfix)
+  - Fixed up the trailing whitespace before linebreaks in:
+    - `CODE_OF_CONDUCT.md`
+    - `CONTRIBUTING.md`
+    - `README.md`
+    - `PULL_REQUEST_TEMPLATE.md`
+  - Set the correct file permissions on the licenses contained in the
+    `_licenses` folder.
+
+## Version 1.0.2 / 2018-05-20
+
+- Simplified the `CHANGELOG.md` file.
+- Added VS Code workspace file.
+- Added link to LICENSE file.
 
 ## Version 1.0.1 (11/05/2018)
 
 - [#bugfix](#bugfix)
-    + Fixed a minor issue in the README, relating to copying all the files.
+  - Fixed a minor issue in the README, relating to copying all the files.
 
 ## Version 1.0.0 (10/05/2018)
 
 - [#new](#new)
-    + Initial Release
-- [#enhancement](#enhancement)
-- [#bugfix](#bugfix)
+  - Initial Release

CODE_OF_CONDUCT.md

@@ -1,6 +1,7 @@
 # Contributor Covenant Code of Conduct
 
-## Table of Contents
+### Table of Contents
+
 <!-- MarkdownTOC -->
 
 - [Our Pledge](#our-pledge)
@@ -14,73 +15,73 @@
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as 
-contributors and maintainers pledge to making participation in our project and 
-our community a harassment-free experience for everyone, regardless of age, 
-body size, disability, ethnicity, gender identity and expression, level of 
-experience, nationality, personal appearance, race, religion, or sexual 
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age,
+body size, disability, ethnicity, gender identity and expression, level of
+experience, nationality, personal appearance, race, religion, or sexual
 identity and orientation.
 
 ## Our Standards
 
-Examples of behaviour that contributes to creating a positive environment 
+Examples of behaviour that contributes to creating a positive environment
 include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
 
 Examples of unacceptable behaviour by participants include:
 
-* The use of sexualised language or imagery and unwelcome sexual attention or 
+- The use of sexualised language or imagery and unwelcome sexual attention or
   advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic 
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
   address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a 
+- Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable 
-behaviour and are expected to take appropriate and fair corrective action in 
+Project maintainers are responsible for clarifying the standards of acceptable
+behaviour and are expected to take appropriate and fair corrective action in
 response to any instances of unacceptable behaviour.
 
-Project maintainers have the right and responsibility to remove, edit, or 
-reject comments, commits, code, wiki edits, issues, and other contributions 
-that are not aligned to this Code of Conduct, or to ban temporarily or 
-permanently any contributor for other behaviours that they deem inappropriate, 
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviours that they deem inappropriate,
 threatening, offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces 
-when an individual is representing the project or its community. Examples of 
-representing a project or community include using an official project e-mail 
-address, posting via an official social media account, or acting as an 
-appointed representative at an online or offline event. Representation of a 
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an
+appointed representative at an online or offline event. Representation of a
 project may be further defined and clarified by project maintainers.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behaviour may be 
-reported by contacting the project team [by clicking here][email]. The project 
-team will review and investigate all complaints, and will respond in a way 
-that it deems appropriate to the circumstances. The project team is obligated 
-to maintain confidentiality with regard to the reporter of an incident. 
+Instances of abusive, harassing, or otherwise unacceptable behaviour may be
+reported by contacting the project team [by clicking here][email]. The project
+team will review and investigate all complaints, and will respond in a way
+that it deems appropriate to the circumstances. The project team is obligated
+to maintain confidentiality with regard to the reporter of an incident.
 Further details of specific enforcement policies may be posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good 
-faith may face temporary or permanent repercussions as determined by other 
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
 members of the project's leadership.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], 
-version 1.4, available at 
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at
 [http://contributor-covenant.org/version/1/4][version].
 
 [//]: # (Make sure to change the email address below to your)

CONTRIBUTING.md

@@ -2,33 +2,32 @@
 
 ## Did You Find a Bug?
 
-- **Ensure the bug was not already reported** by searching on GitHub under 
+- **Ensure the bug was not already reported** by searching on GitHub under
   [Issues][issues].
-- If you're unable to find an open issue addressing the problem, 
-  [open a new one][new-issue]. Be sure to include a **title and clear 
-  description**, as much relevant information as possible, and a **code 
-  sample** or an **executable test case** demonstrating the expected 
+- If you're unable to find an open issue addressing the problem,
+  [open a new one][new-issue]. Be sure to include a **title and clear
+  description**, as much relevant information as possible, and a **code
+  sample** or an **executable test case** demonstrating the expected
   behaviour that is not occurring.
 
 ## Did You Write a Patch That Fixes a Bug?
 
 - Open a new GitHub pull request with the patch.
-    + Fork this project
-    + Create your feature branch: `git checkout -b my-new-feature`
-    + Commit your changes: `git commit -am 'Add some feature'`
-    + Push to the branch: `git push origin my-new-feature`
-    + Submit a pull request :tada:
-- Ensure the PR description clearly describes the problem and solution. 
+  - Fork this project
+  - Create your feature branch: `git checkout -b my-new-feature`
+  - Commit your changes: `git commit -am 'Add some feature'`
+  - Push to the branch: `git push origin my-new-feature`
+  - Submit a pull request :tada:
+- Ensure the PR description clearly describes the problem and solution.
   Include the relevant issue number if applicable.
 
 ## Do You Intend to Add a New Feature or Change an Existing One?
 
-- Suggest your change as a [new issue][new-issue] using the label 
+- Suggest your change as a [new issue][new-issue] using the label
   `enhancement`, **BEFORE** you start writing code.
 
 Thanks for contributing! :heart:
 
-
 [//]: # (Simply change the URL's below to your own project information)
 
 [issues]: https://github.com/justinhartman/.github/issues