Project import

.gitignore

@@ -0,0 +1,7 @@
+*.b#*
+*.bak
+*.s#*
+*.swp
+*~
+.DS_Store
+Thumbs.db

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# 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 github@brazio.org. The project team will review and investigate all complaints, and will respond in a way that it deems 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/

CONTRIBUTING.md

@@ -0,0 +1,34 @@
+# Contributing
+## Contributing guidelines
+We’d love you to help us improve this project. To help us keep this collection high quality, we
+request that contributions adhere to the following guidelines.
+
+- **Provide links to documentation** supporting the change you’re making.
+  If documentation isn’t available to support your change, do the best you can to explain what
+  you're aiming for.
+
+- **Explain why you’re making a change**. Even if it seems self-evident, please take a sentence or
+  two to tell us why your change or addition should happen. It’s especially helpful to articulate
+  why this change applies to *everyone* who works with the applicable technology, rather than just
+  you or your team.
+
+- **One change/feature per pull request**. This helps keep pull requests and feedback focused on a
+  specific topic or improvement.
+
+In general, the more you can do to help us understand the change you’re making, the more likely
+we’ll be to accept your contribution quickly.
+
+## Contributing workflow
+Here’s how we suggest you go about proposing a change to this project:
+
+1. [Fork this project][fork] to your account.
+2. [Create a branch][branch] for the change you intend to make.
+3. Make your changes to your fork.
+4. [Send a pull request][pr] from your fork’s branch to our `master` branch.
+
+Using the web-based interface to make changes is fine too, and will help you by automatically
+forking the project and prompting to send a pull request too.
+
+[fork]: https://github.com/jbrazio/ardufocus-schematics#fork-destination-box
+[branch]: https://github.com/jbrazio/ardufocus-schematics/branches
+[pr]: https://github.com/jbrazio/ardufocus-schematics/pulls