Add contribution guide and code of conduct

Author: dondonz

CODE_OF_CONDUCT.md

@@ -0,0 +1,49 @@
+# Contributor Code of Conduct
+
+As contributors and maintainers of this project, and in the interest of
+fostering an open and welcoming community, we pledge to respect all people who
+contribute through reporting issues, posting feature requests, updating
+documentation, submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free
+experience for everyone, regardless of level of experience, gender, gender
+identity and expression, sexual orientation, disability, personal appearance,
+body size, race, ethnicity, age, religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery
+- Personal attacks
+- Trolling or insulting/derogatory comments
+- Public or private harassment
+- Publishing other's private information, such as physical or electronic
+ addresses, without explicit permission
+- Other unethical or unprofessional conduct
+
+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.
+
+By adopting this Code of Conduct, project maintainers commit themselves to
+fairly and consistently applying these principles to every aspect of managing
+this project. Project maintainers who do not follow or enforce the Code of
+Conduct may be permanently removed from the project team.
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting a project maintainer at andimarek@fastmail.fm. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. Maintainers are
+obligated to maintain confidentiality with regard to the reporter of an
+incident.
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.3.0, available at
+[http://contributor-covenant.org/version/1/3/0/][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/3/0/

CONTRIBUTING.md

@@ -1,3 +1,43 @@
 # GraphQL Custom Scalars Specification Contribution Guide
 
-TODO
+Thanks for contributing to GraphQL Scalars.
+
+The goal of the GraphQL Scalars project is to provide a directory of GraphQL
+Custom Scalar specifications, contributed by the community. Contributed
+specifications will be hosted on a GraphQL Foundation owned domain, which can be
+referenced with the built-in `@specifiedBy` GraphQL directive.
+
+GraphQL Custom Scalar specifications are language agnostic and thus can be used
+to document and standardize behavior across different languages.
+
+We will confirm the domain details soon. We are currently setting this up.
+
+Please ensure that you read the [Code of Conduct](CODE_OF_CONDUCT.md) before
+contributing to this project.
+
+## How to contribute
+
+1. Copy the `template-string.md`
+ [template](https://github.com/graphql/graphql-scalars/blob/main/scalars/template-string.md)
+ for Custom Scalars based on the built-in String Scalar, or otherwise use the
+ `template.md`
+ [template](https://github.com/graphql/graphql-scalars/blob/main/scalars/template.md)
+ for all other Custom Scalars. Templates are located in the
+ [graphql-scalars GitHub repository](https://github.com/graphql/graphql-scalars/tree/main/scalars).
+
+2. [Open a new pull request](https://github.com/graphql/graphql-scalars/pulls)
+ for each Custom Scalar specification you would like to add.
+
+3. Modify your selected template, and save it in the correct place
+ `scalars/contributed/<github-user-name>/<scalar-name>.md` in the
+ [graphql-scalars GitHub repository](https://github.com/graphql/graphql-scalars/tree/main/scalars/contributed).
+ The directory location is important, as this will form part of the reference
+ URL for your specification.
+
+## Review process
+
+Your specification will then be reviewed by a maintainer of the
+[graphql-scalars repository](https://github.com/graphql/graphql-scalars). The
+maintainers will verify that the template has been completed, but note that the
+correctness of the specification is the responsibility of the original
+contributor.

scalars/new-scalar.md

@@ -1,14 +1,44 @@
-# Guide to contribute a new Custom Scalar specification
+# Custom Scalar specification contribution guide
 
-In order to contribute a new Custom Scalar specification, please open a new PR
-for each new Custom Scalar.
+Thanks for contributing to GraphQL Scalars.
 
-Use the "template-string.md" template for Custom Scalars based on the built-in
-String Scalar.
+The goal of the GraphQL Scalars project is to provide a directory of GraphQL
+Custom Scalar specifications, contributed by the community. Contributed
+specifications will be hosted on a GraphQL Foundation owned domain, which can be
+referenced with the built-in `@specifiedBy` GraphQL directive.
 
-Use the "template.md" template for all other Custom Scalars.
+GraphQL Custom Scalar specifications are language agnostic and thus can be used
+to document and standardize behavior across different languages.
 
-Modify your selected template, and save it in the correct place
-"scalars/contributed/<github-user-name>/<scalar-name>.md". The directory
-location is important, as this will form part of the reference URL for your
-specification.
+We will confirm the domain details soon. We are currently setting this up.
+
+Please ensure that you read the
+[Code of Conduct](https://github.com/graphql/graphql-scalars/blob/main/CODE_OF_CONDUCT.md)
+before contributing to this project.
+
+## How to contribute
+
+1. Copy the `template-string.md`
+ [template](https://github.com/graphql/graphql-scalars/blob/main/scalars/template-string.md)
+ for Custom Scalars based on the built-in String Scalar, or otherwise use the
+ `template.md`
+ [template](https://github.com/graphql/graphql-scalars/blob/main/scalars/template.md)
+ for all other Custom Scalars. Templates are located in the
+ [graphql-scalars GitHub repository](https://github.com/graphql/graphql-scalars/tree/main/scalars).
+
+2. [Open a new pull request](https://github.com/graphql/graphql-scalars/pulls)
+ for each Custom Scalar specification you would like to add.
+
+3. Modify your selected template, and save it in the correct place
+ `scalars/contributed/<github-user-name>/<scalar-name>.md` in the
+ [graphql-scalars GitHub repository](https://github.com/graphql/graphql-scalars/tree/main/scalars/contributed).
+ The directory location is important, as this will form part of the reference
+ URL for your specification.
+
+## Review process
+
+Your specification will then be reviewed by a maintainer of the
+[graphql-scalars repository](https://github.com/graphql/graphql-scalars). The
+maintainers will verify that the template has been completed, but note that the
+correctness of the specification is the responsibility of the original
+contributor.

scalars/template-string.md

@@ -1,6 +1,4 @@
-# This template is meant to be copied and modified
-
-# This template is meant for Scalars which are based on the built-in String Scalar
+# This template is meant to be copied and modified. This template is meant for Scalars which are based on the built-in String Scalar
 
 # Custom Scalar spec \<name\>