diff options
Diffstat (limited to 'deps/sol2/.github')
-rw-r--r-- | deps/sol2/.github/FUNDING.yml | 28 | ||||
-rw-r--r-- | deps/sol2/.github/ISSUE_TEMPLATE.md | 14 |
2 files changed, 42 insertions, 0 deletions
diff --git a/deps/sol2/.github/FUNDING.yml b/deps/sol2/.github/FUNDING.yml new file mode 100644 index 0000000..13a387d --- /dev/null +++ b/deps/sol2/.github/FUNDING.yml @@ -0,0 +1,28 @@ +# sol3
+
+# The MIT License (MIT)
+
+# Copyright (c) 2013-2019 Rapptz, ThePhD and contributors
+
+# Permission is hereby granted, free of charge, to any person obtaining a copy of
+# this software and associated documentation files (the "Software"), to deal in
+# the Software without restriction, including without limitation the rights to
+# use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+# the Software, and to permit persons to whom the Software is furnished to do so,
+# subject to the following conditions:
+
+# The above copyright notice and this permission notice shall be included in all
+# copies or substantial portions of the Software.
+
+# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+# FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+# COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+# IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+# CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+github: ThePhD
+patreon: ThePhD
+ko_fi: ThePhD
+liberapay: ThePhD
+custom: https://thephd.github.io/support/
diff --git a/deps/sol2/.github/ISSUE_TEMPLATE.md b/deps/sol2/.github/ISSUE_TEMPLATE.md new file mode 100644 index 0000000..4322ab0 --- /dev/null +++ b/deps/sol2/.github/ISSUE_TEMPLATE.md @@ -0,0 +1,14 @@ +Read these guidelines. They are relatively simple and will allow me to help you better: + +1. Produce a simple, short, compilable test case that reproduces your problem. +2. Make a descriptive title that summarises the bug as a whole. +3. Explain the bug in as much detail as you can in the body of the issue. +4. Include Compiler/IDE (Visual Studio, XCode...), Build and Deployment System, Language (C++, Objective-C++), and any special defines you have set. + +If you want to request a feature: + +1. Produce any relevant imaginary code that illustrates what you would like or desired behavior. +2. Include a description and title of what you would like. +3. Annotate and describe the behavior through comments, asserts or just a small write up. + +Thanks for helping sol grow! |