caretaker-core 0.0.1

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA256:
3
+ metadata.gz: 2763a93725479b1827314d27495d0f1774fbef102908f0c490af332a58ade638
4
+ data.tar.gz: 467e1bf159db4b0571cf62295443e6a6bed166050e80679539f476c4f2be22ec
5
+ SHA512:
6
+ metadata.gz: 839780e40a91f1a4322d7f880aa5fc5f4bc4835e7bb7ce9e4cb50dfdcaf6c2d17280cb8508e988f0e357eca8c80c2868b604c474fd05e5ea5c31dfb23435fd2f
7
+ data.tar.gz: 262c5341208356017b32a0c4936f83c3f91e6013eec3b4ba89acb9679a80d3462e9b875837d78d3c00f7dcd616a46fd518f22e219e35e9072423137b2a024a78
@@ -0,0 +1,5 @@
1
+ #
2
+ # These owners will be the default owners for everything in the repo.
3
+ #
4
+ * @TGWolf
5
+
@@ -0,0 +1,76 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as
6
+ contributors and maintainers pledge to making participation in our project and
7
+ our community a harassment-free experience for everyone, regardless of age, body
8
+ size, disability, ethnicity, sex characteristics, gender identity and expression,
9
+ level of experience, education, socio-economic status, nationality, personal
10
+ appearance, race, religion, or sexual identity and orientation.
11
+
12
+ ## Our Standards
13
+
14
+ Examples of behavior that contributes to creating a positive environment
15
+ include:
16
+
17
+ * Using welcoming and inclusive language
18
+ * Being respectful of differing viewpoints and experiences
19
+ * Gracefully accepting constructive criticism
20
+ * Focusing on what is best for the community
21
+ * Showing empathy towards other community members
22
+
23
+ Examples of unacceptable behavior by participants include:
24
+
25
+ * The use of sexualized language or imagery and unwelcome sexual attention or
26
+ advances
27
+ * Trolling, insulting/derogatory comments, and personal or political attacks
28
+ * Public or private harassment
29
+ * Publishing others' private information, such as a physical or electronic
30
+ address, without explicit permission
31
+ * Other conduct which could reasonably be considered inappropriate in a
32
+ professional setting
33
+
34
+ ## Our Responsibilities
35
+
36
+ Project maintainers are responsible for clarifying the standards of acceptable
37
+ behavior and are expected to take appropriate and fair corrective action in
38
+ response to any instances of unacceptable behavior.
39
+
40
+ Project maintainers have the right and responsibility to remove, edit, or
41
+ reject comments, commits, code, wiki edits, issues, and other contributions
42
+ that are not aligned to this Code of Conduct, or to ban temporarily or
43
+ permanently any contributor for other behaviors that they deem inappropriate,
44
+ threatening, offensive, or harmful.
45
+
46
+ ## Scope
47
+
48
+ This Code of Conduct applies both within project spaces and in public spaces
49
+ when an individual is representing the project or its community. Examples of
50
+ representing a project or community include using an official project e-mail
51
+ address, posting via an official social media account, or acting as an appointed
52
+ representative at an online or offline event. Representation of a project may be
53
+ further defined and clarified by project maintainers.
54
+
55
+ ## Enforcement
56
+
57
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
+ reported by contacting the project team at . All
59
+ complaints will be reviewed and investigated and will result in a response that
60
+ is deemed necessary and appropriate to the circumstances. The project team is
61
+ obligated to maintain confidentiality with regard to the reporter of an incident.
62
+ Further details of specific enforcement policies may be posted separately.
63
+
64
+ Project maintainers who do not follow or enforce the Code of Conduct in good
65
+ faith may face temporary or permanent repercussions as determined by other
66
+ members of the project's leadership.
67
+
68
+ ## Attribution
69
+
70
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
+ available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72
+
73
+ [homepage]: https://www.contributor-covenant.org
74
+
75
+ For answers to common questions about this code of conduct, see
76
+ https://www.contributor-covenant.org/faq
@@ -0,0 +1,9 @@
1
+ # Contributing
2
+
3
+ Please refer to the [contributing](https://github.com/WolfSoftware/contributing) documentation.
4
+
5
+ ## Important
6
+
7
+ ALL commits must be signed to ensure the identity of the developer, any pull requests that are made with unsigned commits will be rejected as a matter of course.
8
+
9
+ > This project has a [code of conduct](CODE_OF_CONDUCT.md). By interacting with this repository, organization, or community you agree to abide by its terms.
@@ -0,0 +1,4 @@
1
+ # Funding
2
+ # https://help.github.com/en/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository
3
+
4
+ ko_fi: wolfsoftware
@@ -0,0 +1,10 @@
1
+ ---
2
+ name: Ask a question
3
+ about: Feel free to ask us a question
4
+ title: ''
5
+ labels: 'question'
6
+ assignees: 'TGWolf'
7
+
8
+ ---
9
+
10
+ **What would you like to know?**
@@ -0,0 +1,30 @@
1
+ ---
2
+ name: Bug report
3
+ about: Create a report to help us improve
4
+ title: ''
5
+ labels: 'bug'
6
+ assignees: 'TGWolf'
7
+
8
+ ---
9
+
10
+ **Describe the bug**
11
+ A clear and concise description of what the bug is.
12
+
13
+ **To Reproduce**
14
+ Steps to reproduce the behavior:
15
+ 1.
16
+ 2.
17
+ 3.
18
+ 4.
19
+
20
+ **Expected behavior**
21
+ A clear and concise description of what you expected to happen.
22
+
23
+ **Screenshots**
24
+ If applicable, add screenshots to help explain your problem.
25
+
26
+ **Environment**
27
+ Any relevant information about your environment, OS version, virtualised or not.
28
+
29
+ **Additional context**
30
+ Add any other context about the problem here.
@@ -0,0 +1 @@
1
+ blank_issues_enabled: false
@@ -0,0 +1,20 @@
1
+ ---
2
+ name: Feature request
3
+ about: Suggest an idea for this project
4
+ title: ''
5
+ labels: 'enhancement'
6
+ assignees: 'TGWolf'
7
+
8
+ ---
9
+
10
+ **Is your feature request related to a problem? Please describe.**
11
+ A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12
+
13
+ **Describe the solution you'd like**
14
+ A clear and concise description of what you want to happen.
15
+
16
+ **Describe alternatives you've considered**
17
+ A clear and concise description of any alternative solutions or features you've considered.
18
+
19
+ **Additional context**
20
+ Add any other context or screenshots about the feature request here.
@@ -0,0 +1,28 @@
1
+ Thanks for submitting a pull request! Please provide enough information so that others can review your pull request:
2
+
3
+ **Summary**
4
+
5
+ <!-- Summary of the PR -->
6
+
7
+ This PR fixes/implements the following **bugs/features**
8
+
9
+ * [ ] Bug 1
10
+ * [ ] Feature 1
11
+ * [ ] Breaking changes
12
+
13
+ <!-- You can skip this if you're fixing a typo or adding an app to the Showcase. -->
14
+
15
+ Explain the **motivation** for making this change. What existing problem does the pull request solve?
16
+
17
+ <!-- Example: When "Adding a function to do X", explain why it is necessary to have a way to do X. -->
18
+
19
+ **Test plan (required)**
20
+
21
+ Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots help greatly.
22
+
23
+ <!-- Make sure tests pass on both Travis. -->
24
+
25
+ **Closing issues**
26
+
27
+ <!-- Put `fixes #XXXX` in your comment to auto-close the issue that your PR fixes (if such). -->
28
+ Fixes #
@@ -0,0 +1,39 @@
1
+ # Security Policies and Procedures
2
+
3
+ This document outlines security procedures and general policies for this project.
4
+
5
+ * [Reporting a Bug](#reporting-a-bug)
6
+ * [Disclosure Policy](#disclosure-policy)
7
+ * [Comments on this Policy](#comments-on-this-policy)
8
+
9
+ ## Reporting a Bug
10
+
11
+ We take **ALL** security related bugs and issues very seriously.
12
+
13
+ If you think you have identified a security related issue, please [report it immediately](mailto:disclose@wolfsoftware.com)
14
+ and include the word "SECURITY" in the subject line. If you are not sure, don’t worry.
15
+ Better safe than sorry – just send an email.
16
+
17
+ * Please provide as much information as you can.
18
+ * Please do not open issues related to any security concerns publicly.
19
+ * Please do not include anyone else on the disclosure email.
20
+
21
+ Report security bugs in third-party modules to the person or team maintaining
22
+ the module.
23
+
24
+ ## Disclosure Policy
25
+
26
+ When a security report is received, we will carry out the following steps:
27
+
28
+ * Confirm the problem and determine the affected versions.
29
+ * Audit code to find any potential similar problems.
30
+ * Prepare fixes for all releases still under maintenance. These fixes will be
31
+ released as fast as possible.
32
+
33
+ We will endeavor to keep you informed of the progress towards a fix
34
+ and full announcement, and may ask for additional information or guidance.
35
+
36
+ ## Comments on this Policy
37
+
38
+ If you have suggestions on how this process could be improved please submit a
39
+ pull request.
@@ -0,0 +1,8 @@
1
+ # Support
2
+
3
+ If the documentation is not providing the information that you require then you have a couple of options:
4
+
5
+ 1. [Start a discussion](https://github.com/DevelopersToolbox/positronic-core/discussions).
6
+ 1. [Open an issue](https://github.com/DevelopersToolbox/positronic-core/issues), using the `Ask a question` option.
7
+
8
+ > This project has a [code of conduct](CODE_OF_CONDUCT.md). By interacting with this repository, organization, or community you agree to abide by its terms.
data/.gitignore ADDED
@@ -0,0 +1,17 @@
1
+ **/ab-results*
2
+
3
+ /.bundle/
4
+ /.yardoc
5
+ /_yardoc/
6
+ /coverage/
7
+ /doc/
8
+ /pkg/
9
+ /spec/reports/
10
+ /tmp/
11
+
12
+ # rspec failure tracking
13
+ .rspec_status
14
+
15
+ /Gemfile.lock
16
+
17
+ *.gem
data/.reek.yml ADDED
@@ -0,0 +1,6 @@
1
+ ---
2
+ detectors:
3
+ TooManyStatements:
4
+ max_statements: 10
5
+ UtilityFunction:
6
+ public_methods_only: true
data/.rspec ADDED
@@ -0,0 +1,3 @@
1
+ --format documentation
2
+ --color
3
+ --require spec_helper
data/.rubocop.yml ADDED
@@ -0,0 +1,30 @@
1
+ AllCops:
2
+ NewCops: enable
3
+
4
+ Layout/FirstHashElementIndentation:
5
+ Enabled: false
6
+
7
+ Layout/HashAlignment:
8
+ Enabled: false
9
+
10
+ Layout/IndentationWidth:
11
+ Width: 4
12
+
13
+ Layout/LineLength:
14
+ Enabled: false
15
+
16
+ Layout/SpaceInsideArrayLiteralBrackets:
17
+ Enabled: false
18
+
19
+ Naming/FileName:
20
+ Enabled: false
21
+
22
+ Style/FrozenStringLiteralComment:
23
+ Enabled: false
24
+
25
+ Style/HashSyntax:
26
+ EnforcedStyle: hash_rockets
27
+
28
+ Style/RaiseArgs:
29
+ EnforcedStyle: compact
30
+
data/.travis.yml ADDED
@@ -0,0 +1,129 @@
1
+ matrix:
2
+ include:
3
+ - language: ruby
4
+ name: Bundler (rvm 2.5)
5
+ rvm: 2.5
6
+ before_install:
7
+ - gem install bundler
8
+ - language: ruby
9
+ name: Bundler (rvm 2.6)
10
+ rvm: 2.6
11
+ before_install:
12
+ - gem install bundler
13
+ - language: ruby
14
+ name: Bundler (rvm 2.7)
15
+ rvm: 2.7
16
+ before_install:
17
+ - gem install bundler
18
+ - language: ruby
19
+ name: Bundler (rvm 3.0)
20
+ rvm: 3.0
21
+ before_install:
22
+ - gem install bundler
23
+ - language: ruby
24
+ name: Rubocop (rvm 2.5)
25
+ rvm: 2.5
26
+ before_install:
27
+ - git clone https://github.com/TravisToolbox/rubocop.git
28
+ install:
29
+ - "./rubocop/install.sh"
30
+ script:
31
+ - "./rubocop/scan.sh"
32
+ - language: ruby
33
+ name: Rubocop (rvm 2.6)
34
+ rvm: 2.6
35
+ before_install:
36
+ - git clone https://github.com/TravisToolbox/rubocop.git
37
+ install:
38
+ - "./rubocop/install.sh"
39
+ script:
40
+ - "./rubocop/scan.sh"
41
+ - language: ruby
42
+ name: Rubocop (rvm 2.7)
43
+ rvm: 2.7
44
+ before_install:
45
+ - git clone https://github.com/TravisToolbox/rubocop.git
46
+ install:
47
+ - "./rubocop/install.sh"
48
+ script:
49
+ - "./rubocop/scan.sh"
50
+ - language: ruby
51
+ name: Rubocop (rvm 3.0)
52
+ rvm: 3.0
53
+ before_install:
54
+ - git clone https://github.com/TravisToolbox/rubocop.git
55
+ install:
56
+ - "./rubocop/install.sh"
57
+ script:
58
+ - "./rubocop/scan.sh"
59
+ - language: ruby
60
+ name: Reek (rvm 2.5)
61
+ rvm: 2.5
62
+ before_install:
63
+ - git clone https://github.com/TravisToolbox/reek.git
64
+ install:
65
+ - "./reek/install.sh"
66
+ script:
67
+ - "./reek/scan.sh"
68
+ - language: ruby
69
+ name: Reek (rvm 2.6)
70
+ rvm: 2.6
71
+ before_install:
72
+ - git clone https://github.com/TravisToolbox/reek.git
73
+ install:
74
+ - "./reek/install.sh"
75
+ script:
76
+ - "./reek/scan.sh"
77
+ - language: ruby
78
+ name: Reek (rvm 2.7)
79
+ rvm: 2.7
80
+ before_install:
81
+ - git clone https://github.com/TravisToolbox/reek.git
82
+ install:
83
+ - "./reek/install.sh"
84
+ script:
85
+ - "./reek/scan.sh"
86
+ - language: ruby
87
+ name: Reek (rvm 3.0)
88
+ rvm: 3.0
89
+ before_install:
90
+ - git clone https://github.com/TravisToolbox/reek.git
91
+ install:
92
+ - "./reek/install.sh"
93
+ script:
94
+ - "./reek/scan.sh"
95
+ - language: ruby
96
+ name: YAML Linting (rvm 2.7)
97
+ rvm: 2.7
98
+ before_install:
99
+ - git clone https://github.com/TravisToolbox/yaml-lint
100
+ install:
101
+ - "./yaml-lint/install.sh"
102
+ script:
103
+ - "./yaml-lint/scan.sh"
104
+ - language: bash
105
+ name: Shellcheck (Bash)
106
+ os: linux
107
+ arch: arm64-graviton2
108
+ before_install:
109
+ - git clone https://github.com/TravisToolbox/shellcheck
110
+ install:
111
+ - "./shellcheck/install.sh"
112
+ script:
113
+ - "./shellcheck/scan.sh"
114
+ - language: ruby
115
+ name: Link Checking (rvm 2.7)
116
+ rvm: 2.7
117
+ env:
118
+ - WHITELIST="https://img.shields.io,https://github.com/DevelopersToolbox/sonny"
119
+ - EXCLUDE_FILES="CHANGELOG.md"
120
+ before_install:
121
+ - git clone https://github.com/TravisToolbox/awesomebot
122
+ install:
123
+ - "./awesomebot/install.sh"
124
+ script:
125
+ - "./awesomebot/scan.sh"
126
+ notifications:
127
+ email: false
128
+ slack:
129
+ secure: G60Aax/kzMqAVBY35tZmhGRFbnHjuk5Zrzl77+2A3EwgXQtn/1v/+QLHR1wJ4FuScPXNxla680+vGljld7xLMwIzTcVUPF5qhM/NFpkjDbY+H9Wm5OxOntXcXsineYPVWC0qWBtlp1p4JtpSyT1Tej3+/BUsTSMCto0OD9ubZupBgFYgQna3052hmdyqkJTxJk51I7B0S41tqscXjW9RxCQSbpsP3VVUsiFgHfhwT0czGrAOA0Bf3ksqdtnLwbF+/rEoWTsuHgn3ZXZ4fyD3CZWEEpz9Ljlag4iS9XCMDHw/AVU966+JHELjPYd8q08tTD3svwi0Q3p/xMr4vNb5cFzE5VrWQTmFdNAovSPm4u9f8LiqxJMXriN7ffCu4PHgLV/BV/MkuQKOsyzE+6bWDCkkq3tbEvBPAgPxBKerG5mlg0SqqkJIrqlfJYoqptesn8RrqA9ddHPDS4arWCU9pCar/RTIotca4s9WBU0M9rDcXWIsw1uOzMuEVWmkuzLbHm9K90zqd/GcRs7vubx4hQVZatKOPEUA+FGNDUPxJLilU0N1oi2L++yhlJInKNQht6DDBZ8iYVO3t1LIuJ+f4ppK+exGYJLr0mQWEJRqY6cMI5Z3CGxqSrfAIrDiK+1gdkVIYv0/J0KMHf4RhS1MT5HBeny+4HuagiZ9XV6z0U0=