Minor update. Updated GLua MIDI parser script and readme...

Moved "midi-parser.lua" file to "lua/includes/modules" folder.

"midiParser" function has been renamed into "midi.Parse".

Added verification for function arguments (fileName and path).

Fixed a nil concat error when path were passed as nil.

Added Contributor Guidelines and Code of Conduct.

Author: CaptainPRICE

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## 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 identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior 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
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized 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
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+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 behaviors 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 project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [support@github.com](mailto:support@github.com). All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and 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
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

.github/CONTRIBUTING.md

@@ -0,0 +1,82 @@
+# How to Contribute
+
+Contributions take many forms from submitting issues, writing docs, to making
+code changes - we welcome it all!
+
+## Getting Started
+
+If you don't have a GitHub account, you can [sign up](https://github.com/signup/free)
+as it will help you to participate with the project.
+
+If you are running GitHub Desktop, you can clone this repository locally from
+GitHub using the "Clone in Desktop" button from the GLua-midi-parser project page,
+or run this command in your Git-enabled Shell/Bash:
+
+`git clone https://github.com/garrysmodlua/GLua-midi-parser.git midi-parser`
+
+If you want to make contributions to the project,
+[forking the project](https://help.github.com/articles/fork-a-repo) is the
+easiest way to do this. You can then clone down your fork instead:
+
+`git clone https://github.com/MY-USERNAME-HERE/GLua-midi-parser.git midi-parser`
+
+## How can I get involved?
+
+We have an [`up-for-grabs`](https://github.com/garrysmodlua/GLua-midi-parser/labels/up-for-grabs)
+tag on our issue tracker to indicate tasks which contributors can pick up.
+
+If you've found something you'd like to contribute to, leave a comment in the issue
+so everyone is aware.
+
+## Making Changes
+
+When you're ready to make a change, create a branch off the `master` branch:
+
+```
+git checkout master
+git pull origin master
+git checkout -b SOME-BRANCH-NAME
+```
+
+We use `master` as the default branch for the repository, and it holds the most
+recent contributions. By working in a branch away from `master` you can handle
+potential conflicts that may occur in the future.
+
+If you make focused commits (instead of one monolithic commit) and have descriptive
+commit messages, this will help speed up the review process.
+
+### Submitting Changes
+
+You can publish your branch from GitHub for Windows, or run this command from
+the Git Shell/Bash:
+
+`git push origin MY-BRANCH-NAME`
+
+Once your changes are ready to be reviewed, publish the branch to GitHub and
+[open a pull request](https://help.github.com/articles/using-pull-requests)
+against it.
+
+A few suggestions when opening a pull request:
+
+ - If you are addressing a particular issue, reference it like this:
+
+>   Fixes #1234
+
+ - Prefix the title with `[WIP]` to indicate this is a work-in-progress. It's
+   always good to get feedback early, so don't be afraid to open the PR before
+   it's "done".
+ - Use [checklists](https://github.com/blog/1375-task-lists-in-gfm-issues-pulls-comments)
+   to indicate the tasks which need to be done, so everyone knows how close you
+   are to done.
+ - Add comments to the PR about things that are unclear or you would like
+   suggestions on.
+
+Some things that will increase the chance that your pull request is accepted:
+
+* Follow existing code conventions.
+* Update the documentation, the surrounding one, examples elsewhere, guides,
+  whatever is affected by your contribution.
+
+# Additional Resources
+
+* [General GitHub documentation](http://help.github.com/)

README.md

@@ -1,22 +1,53 @@
 # MIDI Parser for Garry's Mod Lua
 
-**It is not perfect**! Use it for just experiment.  
+**It is not perfect**! Use it for experimental purposes.  
 This is a GLua fork of [Lua_midiParser](https://github.com/FMS-Cat/Lua_midiParser).
 
-## Usage
+## Installation
+
+### Download
+
+You must download the source code first, there are 4 ways to do it, use any way you like:  
+* Download the latest release from [here](https://github.com/garrysmodlua/GLua-midi-parser/releases/latest).  
+* Download ZIP of this repository [here](https://github.com/garrysmodlua/GLua-midi-parser/archive/master.zip).
+* Clone this repository using [git](https://git-scm.com/downloads): `git clone https://github.com/garrysmodlua/GLua-midi-parser.git midi-parser`.
+* Save the <code><a href="lua/includes/modules/midi-parser.lua">midi-parser.lua</a></code> file (Press <kbd>Ctrl</kbd>+<kbd>S</kbd>; Or, <kbd>Cmd</kbd>+<kbd>S</kbd> on Mac).
+
+### GMod Setup
+
+1. Navigate to your `./Steam/steamapps/common/GarrysMod/garrysmod` folder.
+2. Depending on which download method you have used, make sure you have the following directory structure (create any neccessary folder yourself if it doesn't exist):
+
+![Expected directory structure](https://user-images.githubusercontent.com/9789070/27001572-ba3c1c16-4dcd-11e7-9348-a2954c8bd033.png)
+
+3. You are done. Have fun!
+
+## Usage / Code Example
+
+1. Must require our `midi-parser` module:
+	```lua
+	require( "midi-parser" )
+	```
+
+2. Call either of these 2 functions:
+	* `[table] = midi.Parse(string midiData)` - To parse MIDI data as string.
+	* `[table] = midi.ParseFile(string fileName[, string path="DATA"])` - To parse a given `.mid` file.
 
 ```lua
--- Will attempt to parse "garrysmod/data/abcdef.mid" file
-myMidi = midiParser( "abcdef.mid" ) -- if path is omitted, it defaults to "DATA"
+-- Notes/Information:
+-- ParseFile function: A fileName argument, if you are dealing with multiple directories, remember to use forward-slash (/) character as directory separator; do NOT use backslash (\) character.
+-- ParseFile function: A path argument is optional, it defaults to "DATA" when omitted; by default it will search relative to "GarrysMod/garrysmod/data" folder.
+-- Both of the Parse functions will throw an error if something goes wrong (e.g. if a given file does not exist, or could not be read, etc).
+-- Moreover, if MIDI file/data is succesfully parsed, a function will return a table as a result.
 
--- Will attempt to parse "garrysmod/lua/test.mid" file
-testingMidi = midiParser( "test.mid", "LUA" )
+local firstMidi = midi.ParseFile( "midis/first.mid" ) -- Will attempt to parse "GarrysMod/garrysmod/data/midis/first.mid" file
 
--- Prints the contents of testingMidi table:
-PrintTable( testingMidi )
+local testingMidi = midi.ParseFile( "test.mid", "LUA" ) -- Will attempt to parse "GarrysMod/garrysmod/lua/test.mid" file
+
+PrintTable( testingMidi ) -- Prints the contents of testingMidi table
 ```
 
-## Return sample
+### Return Sample
 
 ```lua
 {
@@ -87,6 +118,37 @@ PrintTable( testingMidi )
 }
 ```
 
+## Documentation
+
+Sorry, there is no wiki nor docs...
+
+## Contribution
+
+Visit the [Contributor Guidelines](https://github.com/garrysmodlua/GLua-midi-parser/blob/master/.github/CONTRIBUTING.md) for more details. All contributors are expected to follow our [Code of Conduct](https://github.com/garrysmodlua/GLua-midi-parser/master/.github/CODE_OF_CONDUCT.md).
+
+## Support
+
+If you think you have found a bug or have a feature/enhancement request for GLua MIDI parser, use our [issue tracker](https://github.com/garrysmodlua/GLua-midi-parser/issues/new).  
+
+Before opening a new issue, please be kind and search to see if your problem has already been reported. Try to be as detailed as possible in your issue reports.  
+When creating an issue, clearly explain  
+
+* What you were trying to do?
+* What you expected to happen?
+* What actually happened?
+* Steps to reproduce the problem.
+
+Also include any other information you think is relevant to reproduce the problem.
+
 ## License
 
-This repository is licensed with the [MIT](LICENSE) license.
+[GLua MIDI parser](https://github.com/garrysmodlua/GLua-midi-parser) repository/code is freely distributed under the [MIT](LICENSE) license. See [LICENSE](LICENSE) for more details.
+
+## Credits
+
+[FMS-Cat](https://github.com/FMS-Cat) for the original Lua code.  
+[CaptainPRICE](https://github.com/CaptainPRICE) for making it compatible with [Garry's Mod](http://gmod.facepunch.com/) (GLua).
+
+## Related Projects
+
+[GMod-Expression2-midi-parser](https://github.com/garrysmodlua/GMod-Expression2-midi-parser): MIDI Parser (Wire Expression 2 extension).