Skip to content

Commit c9fed4f

Browse files
bgrantbgrant
committed
Initial commit
0 parents  commit c9fed4f

File tree

16 files changed

+715
-0
lines changed

16 files changed

+715
-0
lines changed

‎.gitignore‎

Lines changed: 215 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,215 @@
1+
2+
# Created by https://www.toptal.com/developers/gitignore/api/python,jetbrains+all
3+
# Edit at https://www.toptal.com/developers/gitignore?templates=python,jetbrains+all
4+
5+
### JetBrains+all ###
6+
# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio and WebStorm
7+
# Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839
8+
9+
# User-specific stuff
10+
.idea/**/workspace.xml
11+
.idea/**/tasks.xml
12+
.idea/**/usage.statistics.xml
13+
.idea/**/dictionaries
14+
.idea/**/shelf
15+
16+
# Generated files
17+
.idea/**/contentModel.xml
18+
19+
# Sensitive or high-churn files
20+
.idea/**/dataSources/
21+
.idea/**/dataSources.ids
22+
.idea/**/dataSources.local.xml
23+
.idea/**/sqlDataSources.xml
24+
.idea/**/dynamic.xml
25+
.idea/**/uiDesigner.xml
26+
.idea/**/dbnavigator.xml
27+
28+
# Gradle
29+
.idea/**/gradle.xml
30+
.idea/**/libraries
31+
32+
# Gradle and Maven with auto-import
33+
# When using Gradle or Maven with auto-import, you should exclude module files,
34+
# since they will be recreated, and may cause churn. Uncomment if using
35+
# auto-import.
36+
# .idea/modules.xml
37+
# .idea/*.iml
38+
# .idea/modules
39+
40+
# CMake
41+
cmake-build-*/
42+
43+
# Mongo Explorer plugin
44+
.idea/**/mongoSettings.xml
45+
46+
# File-based project format
47+
*.iws
48+
49+
# IntelliJ
50+
out/
51+
52+
# mpeltonen/sbt-idea plugin
53+
.idea_modules/
54+
55+
# JIRA plugin
56+
atlassian-ide-plugin.xml
57+
58+
# Cursive Clojure plugin
59+
.idea/replstate.xml
60+
61+
# Crashlytics plugin (for Android Studio and IntelliJ)
62+
com_crashlytics_export_strings.xml
63+
crashlytics.properties
64+
crashlytics-build.properties
65+
fabric.properties
66+
67+
# Editor-based Rest Client
68+
.idea/httpRequests
69+
70+
# Android studio 3.1+ serialized cache file
71+
.idea/caches/build_file_checksums.ser
72+
73+
### JetBrains+all Patch ###
74+
# Ignores the whole .idea folder and all .iml files
75+
# See https://github.com/joeblau/gitignore.io/issues/186 and https://github.com/joeblau/gitignore.io/issues/360
76+
77+
.idea/
78+
79+
# Reason: https://github.com/joeblau/gitignore.io/issues/186#issuecomment-249601023
80+
81+
*.iml
82+
modules.xml
83+
.idea/misc.xml
84+
*.ipr
85+
86+
# Sonarlint plugin
87+
.idea/sonarlint
88+
89+
### Python ###
90+
# Byte-compiled / optimized / DLL files
91+
__pycache__/
92+
*.py[cod]
93+
*$py.class
94+
95+
# C extensions
96+
*.so
97+
98+
# Distribution / packaging
99+
.Python
100+
build/
101+
develop-eggs/
102+
dist/
103+
downloads/
104+
eggs/
105+
.eggs/
106+
lib/
107+
lib64/
108+
parts/
109+
sdist/
110+
var/
111+
wheels/
112+
pip-wheel-metadata/
113+
share/python-wheels/
114+
*.egg-info/
115+
.installed.cfg
116+
*.egg
117+
MANIFEST
118+
119+
# PyInstaller
120+
# Usually these files are written by a python script from a template
121+
# before PyInstaller builds the exe, so as to inject date/other infos into it.
122+
*.manifest
123+
*.spec
124+
125+
# Installer logs
126+
pip-log.txt
127+
pip-delete-this-directory.txt
128+
129+
# Unit test / coverage reports
130+
htmlcov/
131+
.tox/
132+
.nox/
133+
.coverage
134+
.coverage.*
135+
.cache
136+
nosetests.xml
137+
coverage.xml
138+
*.cover
139+
.hypothesis/
140+
.pytest_cache/
141+
142+
# Translations
143+
*.mo
144+
*.pot
145+
146+
# Django stuff:
147+
*.log
148+
local_settings.py
149+
db.sqlite3
150+
151+
# Flask stuff:
152+
instance/
153+
.webassets-cache
154+
155+
# Scrapy stuff:
156+
.scrapy
157+
158+
# Sphinx documentation
159+
docs/_build/
160+
161+
# PyBuilder
162+
target/
163+
164+
# Jupyter Notebook
165+
.ipynb_checkpoints
166+
167+
# IPython
168+
profile_default/
169+
ipython_config.py
170+
171+
# pyenv
172+
.python-version
173+
174+
# pipenv
175+
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
176+
# However, in case of collaboration, if having platform-specific dependencies or dependencies
177+
# having no cross-platform support, pipenv may install dependencies that don’t work, or not
178+
# install all needed dependencies.
179+
#Pipfile.lock
180+
181+
# celery beat schedule file
182+
celerybeat-schedule
183+
184+
# SageMath parsed files
185+
*.sage.py
186+
187+
# Environments
188+
.env
189+
.venv
190+
env/
191+
venv/
192+
ENV/
193+
env.bak/
194+
venv.bak/
195+
196+
# Spyder project settings
197+
.spyderproject
198+
.spyproject
199+
200+
# Rope project settings
201+
.ropeproject
202+
203+
# mkdocs documentation
204+
/site
205+
206+
# mypy
207+
.mypy_cache/
208+
.dmypy.json
209+
dmypy.json
210+
211+
# Pyre type checker
212+
.pyre/
213+
214+
# End of https://www.toptal.com/developers/gitignore/api/python,jetbrains+all
215+
.tool-versions

‎CODEOWNERS‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# Comment line immediately above ownership line is reserved for related gus information. Please be careful while editing.
2+
#ECCN:Open Source 5D002

‎CODE_OF_CONDUCT.md‎

Lines changed: 105 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,105 @@
1+
# Salesforce Open Source Community Code of Conduct
2+
3+
## About the Code of Conduct
4+
5+
Equality is a core value at Salesforce. We believe a diverse and inclusive
6+
community fosters innovation and creativity, and are committed to building a
7+
culture where everyone feels included.
8+
9+
Salesforce open-source projects are committed to providing a friendly, safe, and
10+
welcoming environment for all, regardless of gender identity and expression,
11+
sexual orientation, disability, physical appearance, body size, ethnicity, nationality,
12+
race, age, religion, level of experience, education, socioeconomic status, or
13+
other similar personal characteristics.
14+
15+
The goal of this code of conduct is to specify a baseline standard of behavior so
16+
that people with different social values and communication styles can work
17+
together effectively, productively, and respectfully in our open source community.
18+
It also establishes a mechanism for reporting issues and resolving conflicts.
19+
20+
All questions and reports of abusive, harassing, or otherwise unacceptable behavior
21+
in a Salesforce open-source project may be reported by contacting the Salesforce
22+
Open Source Conduct Committee at [email protected].
23+
24+
## Our Pledge
25+
26+
In the interest of fostering an open and welcoming environment, we as
27+
contributors and maintainers pledge to making participation in our project and
28+
our community a harassment-free experience for everyone, regardless of gender
29+
identity and expression, sexual orientation, disability, physical appearance,
30+
body size, ethnicity, nationality, race, age, religion, level of experience, education,
31+
socioeconomic status, or other similar personal characteristics.
32+
33+
## Our Standards
34+
35+
Examples of behavior that contributes to creating a positive environment
36+
include:
37+
38+
* Using welcoming and inclusive language
39+
* Being respectful of differing viewpoints and experiences
40+
* Gracefully accepting constructive criticism
41+
* Focusing on what is best for the community
42+
* Showing empathy toward other community members
43+
44+
Examples of unacceptable behavior by participants include:
45+
46+
* The use of sexualized language or imagery and unwelcome sexual attention or
47+
advances
48+
* Personal attacks, insulting/derogatory comments, or trolling
49+
* Public or private harassment
50+
* Publishing, or threatening to publish, others' private information—such as
51+
a physical or electronic address—without explicit permission
52+
* Other conduct which could reasonably be considered inappropriate in a
53+
professional setting
54+
* Advocating for or encouraging any of the above behaviors
55+
56+
## Our Responsibilities
57+
58+
Project maintainers are responsible for clarifying the standards of acceptable
59+
behavior and are expected to take appropriate and fair corrective action in
60+
response to any instances of unacceptable behavior.
61+
62+
Project maintainers have the right and responsibility to remove, edit, or
63+
reject comments, commits, code, wiki edits, issues, and other contributions
64+
that are not aligned with this Code of Conduct, or to ban temporarily or
65+
permanently any contributor for other behaviors that they deem inappropriate,
66+
threatening, offensive, or harmful.
67+
68+
## Scope
69+
70+
This Code of Conduct applies both within project spaces and in public spaces
71+
when an individual is representing the project or its community. Examples of
72+
representing a project or community include using an official project email
73+
address, posting via an official social media account, or acting as an appointed
74+
representative at an online or offline event. Representation of a project may be
75+
further defined and clarified by project maintainers.
76+
77+
## Enforcement
78+
79+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
80+
reported by contacting the Salesforce Open Source Conduct Committee
81+
at [email protected]. All complaints will be reviewed and investigated
82+
and will result in a response that is deemed necessary and appropriate to the
83+
circumstances. The committee is obligated to maintain confidentiality with
84+
regard to the reporter of an incident. Further details of specific enforcement
85+
policies may be posted separately.
86+
87+
Project maintainers who do not follow or enforce the Code of Conduct in good
88+
faith may face temporary or permanent repercussions as determined by other
89+
members of the project's leadership and the Salesforce Open Source Conduct
90+
Committee.
91+
92+
## Attribution
93+
94+
This Code of Conduct is adapted from the [Contributor Covenant][contributor-covenant-home],
95+
version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html.
96+
It includes adaptions and additions from [Go Community Code of Conduct][golang-coc],
97+
[CNCF Code of Conduct][cncf-coc], and [Microsoft Open Source Code of Conduct][microsoft-coc].
98+
99+
This Code of Conduct is licensed under the [Creative Commons Attribution 3.0 License][cc-by-3-us].
100+
101+
[contributor-covenant-home]: https://www.contributor-covenant.org (https://www.contributor-covenant.org/)
102+
[golang-coc]: https://golang.org/conduct
103+
[cncf-coc]: https://github.com/cncf/foundation/blob/master/code-of-conduct.md
104+
[microsoft-coc]: https://opensource.microsoft.com/codeofconduct/
105+
[cc-by-3-us]: https://creativecommons.org/licenses/by/3.0/us/

‎CONTRIBUTING.md‎

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
This project is owned by the Verification as a Service team. To contribute to
2+
this project, you'll need to follow the
3+
[fork-and-PR](https://help.github.com/articles/creating-a-pull-request-from-a-fork/)
4+
workflow.
5+
6+
* We follow [PEP 8](https://www.python.org/dev/peps/pep-0008/) for coding standards.
7+
* Any PRs must pass all automated checks to be approved.
8+
9+
This library powers production services. New features must be approved by the
10+
maintainer. PRs for bug fixes are welcome, but new features or breaking changes
11+
should be associated with a discussion. Please use the Github issue tracker to
12+
kick off the discussion. Rough ideas to fully fleshed out designs are welcome!
13+
14+
PRs can be submitted at any time, however if it's not ready to be merged,
15+
please add the "work in progress" label.
16+
17+
18+
## Pull Request Process
19+
20+
1. You must create your own fork, and a feature branch on that fork.
21+
2. Try not to introduce system wide breakages.
22+
3. Your feature must not cause any failure of current tests.
23+
4. You need to show testing compliance for your added code.
24+
5. Please write copious PR comments, so you remember what you did.
25+
6. If appropriate, update the README.md with any relevant details of changes
26+
you made which affect the project. This may include changes to the
27+
interface, new environment variables, new ports, useful new file locations,
28+
added or removed dependencies, and anything else that will affect other
29+
contributors.
30+
7. We will contact you when you create your PR. In some cases, we may just
31+
approve it for merge.

‎LICENSE.txt‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
MIT License
2+
3+
Copyright (c) 2020 Evan Grim
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy
6+
of this software and associated documentation files (the "Software"), to deal
7+
in the Software without restriction, including without limitation the rights
8+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9+
copies of the Software, and to permit persons to whom the Software is
10+
furnished to do so, subject to the following conditions:
11+
12+
The above copyright notice and this permission notice shall be included in all
13+
copies or substantial portions of the Software.
14+
15+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21+
SOFTWARE.

0 commit comments

Comments
 (0)