Skip to content
This repository was archived by the owner on Oct 1, 2024. It is now read-only.

Commit 88af59e

Browse files
committed
Documentation dump.
1 parent 35f8341 commit 88af59e

21 files changed

+504
-205
lines changed

.gitignore

+90-2
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,92 @@
1+
# Byte-compiled / optimized / DLL files
2+
__pycache__
3+
*.py[cod]
4+
*$py.class
5+
6+
# C extensions
7+
*.so
8+
9+
# Distribution / packaging
10+
.Python
11+
env/
12+
.env/
13+
build/
14+
develop-eggs/
15+
dist/
16+
downloads/
17+
eggs/
18+
.eggs/
19+
lib/
20+
lib64/
21+
parts/
22+
sdist/
23+
var/
24+
*.egg-info/
25+
.installed.cfg
26+
*.egg
27+
28+
# Bluemix vendored packages
29+
vendor/
30+
31+
# PyInstaller
32+
# Usually these files are written by a python script from a template
33+
# before PyInstaller builds the exe, so as to inject date/other infos into it.
34+
*.manifest
35+
#*.spec
36+
pyinstaller/
37+
38+
# Installer logs
39+
pip-log.txt
40+
pip-delete-this-directory.txt
41+
42+
# Unit test / coverage reports
43+
htmlcov/
44+
.tox/
45+
.coverage
46+
.coverage.*
47+
.cache
48+
nosetests.xml
49+
coverage.xml
50+
*,cover
51+
.pytest_cache/*
52+
53+
# Translations
54+
*.pot
55+
56+
# Sphinx documentation
57+
docs/_build/
58+
59+
# PyBuilder
60+
target/
61+
62+
# WingIDE (we do want .wpr but not .wpu)
63+
*.wpu
64+
65+
# Vim
166
*.swp
67+
68+
# Pycharm
69+
.idea/
70+
71+
# Visual Studio Code
72+
.vscode
73+
74+
# OSX
75+
.DS_Store
76+
/.vs/slnx.sqlite
77+
78+
# Movie
79+
*.mp4
80+
81+
# Virtual Environment
82+
.venv/
83+
84+
# MyPy
85+
.mypy_cache/
86+
87+
# Django
88+
*.sqlite3
89+
.envrc
90+
91+
# JavaScript
292
*.min.js
3-
.coverage
4-
__pycache__

AUTHORS.md

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# Authors
2+
3+
Nicholas H.Tollervey [[email protected]](mailto:[email protected])

CHANGELOG.md

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# Changelog
2+
3+
## 0.0.1
4+
5+
* Initial release.

CODE_OF_CONDUCT.md

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# Code of Conduct
2+
3+
The Code of Conduct is [available in the PyScript Governance repo](https://github.com/pyscript/governance/blob/main/CODE-OF-CONDUCT.md).

CONTRIBUTING.md

+58
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
# Contributing
2+
3+
Thank you for wanting to contribute to the PolyPlug project!
4+
5+
## Working together
6+
7+
The [PolyPlug Code of Conduct](https://github.com/pyscript/governance/blob/main/CODE-OF-CONDUCT.md) governs the project and everyone participating in it. By participating, you are expected to uphold this code. Please report unacceptable behavior to the maintainers or administrators as described in that document.
8+
9+
## Activities
10+
11+
### Reporting bugs
12+
13+
Bugs are tracked on the [project issues page](https://github.com/pyscript/polyplug/issues). Please check if your issue has already been filed by someone else by searching the existing issues before filing a new one. Once your issue is filed, it will be triaged by another contributor or maintainer. If there are questions raised about your issue, please respond promptly.
14+
15+
### Creating useful issues
16+
17+
* Use a clear and descriptive title.
18+
* Describe the specific steps that reproduce the problem with as many details as possible so that someone can verify the issue.
19+
* Describe the behavior you observed, and the behavior you had expected.
20+
* Include screenshots if they help make the issue clear.
21+
22+
### Reporting security issues
23+
24+
If you aren't confident that it is appropriate to submit a security issue using the above process, you can e-mail it to [email protected]
25+
26+
### Asking questions
27+
28+
If you have questions about the project, using PolyPlug, or anything else, please ask in the [PolyPlug forum](https://community.anaconda.cloud/c/tech-topics/pyscript).
29+
30+
### Places to start
31+
32+
If you would like to contribute to PolyPlug, but you aren't sure where to begin, here are some suggestions.
33+
34+
* **Read over the existing documentation.** Are there things missing, or could they be clearer? Make some changes/additions to those documents.
35+
* **Review the open issues.** Are they clear? Can you reproduce them? You can add comments, clarifications, or additions to those issues. If you think you have an idea of how to address the issue, submit a fix!
36+
* **Look over the open pull requests.** Do you have comments or suggestions for the proposed changes? Add them.
37+
* **Check out the examples.** Is there a use case that would be good to have sample code for? Create an example for it.
38+
39+
### Setting up your local environment and developing
40+
41+
If you would like to contribute to PolyPlug, you will need to set up a local development environment. The instructions are in the README.
42+
43+
### License terms for contributions
44+
45+
This Project welcomes contributions, suggestions, and feedback. All contributions, suggestions, and feedback you submitted are accepted under the [Apache 2.0](license.md) license. You represent that if you do not own copyright in the code that you have the authority to submit it under the [Apache 2.0](license.md) license. All feedback, suggestions, or contributions are not confidential.
46+
47+
### Becoming a maintainer
48+
49+
Contributors are invited to be maintainers of the project by demonstrating good decision making in their contributions, a commitment to the goals of the project, and consistent adherence to the [code of conduct](https://github.com/pyscript/governance/blob/main/CODE-OF-CONDUCT.md). New maintainers are invited by a 3/4 vote of the existing maintainers.
50+
51+
### Trademarks
52+
53+
The Project abides by the Organization's [trademark policy](https://github.com/pyscript/governance/blob/main/TRADEMARKS.md).
54+
55+
---
56+
Part of MVG-0.1-beta.
57+
Made with love by GitHub. Licensed under the [CC-BY 4.0 License](https://creativecommons.org/licenses/by-sa/4.0/).
58+

LICENSE

-201
This file was deleted.

0 commit comments

Comments
 (0)