Skip to content

Commit

Permalink
Updated README and the CODE_OF_CONDUCT
Browse files Browse the repository at this point in the history
  • Loading branch information
ForeverZer0 committed Aug 27, 2023
1 parent bcd41b3 commit f22ae23
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 78 deletions.
79 changes: 10 additions & 69 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -1,75 +1,16 @@
# Contributor Covenant Code of Conduct
# This is Just a Code Repo Code of Conduct

## Our Pledge
This is:

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.
* A public repository to share code and track issues

## Our Standards
This is NOT:

Examples of behavior that contributes to creating a positive environment
include:
* Your priest
* Your parent
* Your moral guide
* Anything that has any authority over you whatsoever

* Use commonsense, which by definition does not need explanation
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Not feeling compelled to try and use a "group" you choose to identify with to elevate your position
As such, it pure silliness to issue a "code of conduct", but alas, GitHub really wants us to put them here. Conduct yourself however you see fit to conduct yourself, the same as you do in every other interaction in life.


Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or
advances
* Pushing your political ideologies onto others
* Trolling, insulting/derogatory comments, and personal 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 efreed09@gmail.com. All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and 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/
If the very idea that a code repository can be considered "unsafe", then I strongly suggest you not interact with it. I don't even know what that means, nor do I wish to adopt the modern-era madness of pretending I do. I can assure you of one thing: in all of history, a code repository has never hurt anyone. I don't believe that this one will be an exception.
10 changes: 1 addition & 9 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,15 +16,7 @@ A CLS-compliant implementation of the Named Binary Tag (NBT) specifications (Jav
* **Ease-of-use:** An intuitive API design, following the style and conventions of the .NET runtime, with full Intellisense for every member: Spend more time being productive and less time digging through documentation.
* **Performance:** Leverages the power of modern C# language features, including `Span` with `stackalloc`, `MemoryMarshal`, etc. This allows for a type-safe way to reinterpret raw buffers without pointers or making unnecessary copies of buffers, a common pitfall with serialization in type-safe languages.
* **Concurrency:** Includes standard async/await concurrency patterns for reading and writing.
* **Cross-platform and cross-language support:** Fully CLR compliant and build against .NET Standard 2.1, allowing support for any CLR language (i.e. C#, Visual Basic, F#, etc.) for the following runtime versions or greater:
* .NET Standard 2.1
* .NET 5.0
* .NET Core 3.0
* Mono 6.4
* Xamarin.iOS 12.16
* Xamarin.Mac 5.16
* Xamarin.Android 10.0
* Unity 2021.2.0b6
* **Cross-language support:** Fully CLR compliant and build against .NET 7.0, allowing support for any CLR language (i.e. C#, Visual Basic, F#, etc.) with the supported runtime version.
* **Callbacks:** Can subscribe to events that get a callback as the parser steps through a stream to get immediate feedback without waiting for document completion. This allows subscribers to even parse the payload themselves and handle the event entirely.
* **String NBT**: Supports both generating and parsing arbitrary SNBT strings.

Expand Down

0 comments on commit f22ae23

Please sign in to comment.