Semantic Versioning

The Semantic Versioning specification is authored by Tom Preston-Werner, inventor of Gravatars and cofounder of GitHub.

Disclaimer

This is a human-readable summary of (and not a substitute for) the license.

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Creative Commons is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

You are free to:

• Share — copy and redistribute the material in any medium or format
• Adapt — remix, transform, and build upon the material for any purpose, even commercially.

The licensor cannot revoke these freedoms as long as you follow the license terms.

Under the following terms:

• Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
• No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.

Notices:

• You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation.
• No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.

Contributions are welcome and will be fully credited.

Before getting started, please take a minute to read the Contributor Code of Conduct. By participating in this project, you are expected to comply with it and treat everyone respectfully.

Proposing Changes

• Fork the repo on Github
• Clone the project to your own machine
• Create a topic branch from the master branch
• Commit changes to your own branch
• Push your work to your fork
• Make a Pull request so that your changes can be reviewed

Contribution Review Process

This repository is currently maintained by @guillermocalvo, who will review your contribution as soon as possible. If you haven’t heard from him in 10 days, feel free to bump the thread or @-mention him to review your contribution.

Community

Discussions about the PragVer specification take place on this repository’s Issues and Pull Requests sections. Anybody is welcome to join these conversations.

Wherever possible, do not take these conversations to private channels, including contacting the maintainer directly. Keeping communication public means everybody can benefit and learn from the conversation.

Text Files

• The file encoding must be UTF-8.
• Line endings must be Unix-style (LF), as opposed to Windows-style (CRLF) or Macintosh-style (CR). Git should handle this automatically for you via the project .gitattributes file.
• Trailing white space should be removed from the end of lines.
• Lines should word-wrap at a non-strict 120 character length limit. Exceptions can be made for things like readability.

Documentation Format

• All documentation must be written in Markdown format adhering to CommonMark specification.
• Kramdown extensions may be used.
• Specification files must contain a YAML front matter block.

Content Principles

• Approachability: Don’t assume reader has prior knowledge.
• Brevity: Keep it simple, link to outside content for deeper dives.
• Curation: Amplify community best practices vs. any individual’s point of view.

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 pragver@guillermo.dev. 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, version 1.4, available at http://contributor-covenant.org/version/1/4.