Move to FormidableLabs org

Author: kitten

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# 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, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, 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 [email protected]. 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,96 @@
+# Development
+
+Thanks for contributing! We love seeing continuous improvements
+and enhancements, no matter how small or big they might be.
+
+## How to contribute?
+
+We follow fairly standard but lenient rules around pull requests and issues.
+Please pick a title that describes your change briefly, optionally in the imperative
+mood if possible.
+
+If you have an idea for a feature or want to fix a bug, consider opening an issue
+first. We're also happy to discuss and help you open a PR and get your changes
+in!
+
+## How do I set up the project?
+
+Luckily it's not hard to get started. You can install dependencies using yarn.
+Please don't use `npm` to respect the lockfile.
+
+```sh
+yarn
+```
+
+You can then run the build using:
+
+```sh
+yarn build
+```
+
+And you can run Flow to check for any type errors:
+
+```sh
+yarn flow check
+```
+
+## How do I test my changes?
+
+It's always good practice to run the tests when making changes.
+It might also make sense to add more tests when you're adding features
+or fixing a bug, but we'll help you in the pull request, if necessary.
+
+```sh
+yarn test            # Single pass
+yarn test --watch    # Watched
+yarn test --coverage # Single pass coverage report
+```
+
+Sometimes it's a good idea to run the Jest in `production` mode,
+since some data structures and behaviour changes in React in
+`production`:
+
+```sh
+NODE_ENV=production yarn test
+```
+
+## How do I lint my code?
+
+We ensure consistency in this codebase using `prettier`.
+It's run on a `precommit` hook, so if something's off it'll try
+to automatically fix up your code, or display an error.
+
+If you have them set up in your editor, even better!
+
+## How do I publish a new version?
+
+If you're a core contributor or maintainer this will certainly come
+up once in a while.
+
+Make sure you first create a new version. The following commands
+bump the version in the `package.json`, create a commit,
+and tag the commit on git:
+
+```sh
+yarn version --new-version X
+# or
+npm version patch # accepts patch|minor|major
+```
+
+Then run `npm publish` (npm is recommended here, not yarn)
+And maybe run `npm publish --dry-run` first to check the output.
+
+```sh
+npm publish
+```
+
+There's a `prepublishOnly` hook in place that'll clean and build
+the package automatically.
+
+Don't forget to push afterwards:
+
+```sh
+git push && git push --tags
+```
+
+[This process can be simplified and streamlined by using `np`.](https://github.com/sindresorhus/np)

package.json

@@ -4,10 +4,11 @@
   "description": "A custom partial React SSR renderer for prefetching and suspense",
   "main": "index.js",
   "source": "src/index.js",
-  "author": "Phil Plückthun <phil@kitten.sh>",
+  "author": "Phil Plückthun <phil[email protected]>",
   "license": "MIT",
+  "repository": "[email protected]:FormidableLabs/react-ssr-prepass.git",
   "bugs": {
-    "url": "https://github.com/kitten/react-ssr-prepass/issues"
+    "url": "https://github.com/FormidableLabs/react-ssr-prepass/issues"
   },
   "files": [
     "index.js",