Browse files

docs: update community guidelines

  • Loading branch information...
Burak Tasci
Burak Tasci committed Aug 18, 2017
1 parent ebbcc54 commit 358c4fc4841306fa7cbee3620fca79583fc33440
Showing with 338 additions and 32 deletions.
  1. +30 −19 .github/
  2. +38 −0 .github/
  3. +46 −0
  4. +202 −0
  5. +21 −12
  6. +1 −1 package.json
@@ -1,39 +1,50 @@

**I'm submitting a ...** (check one with "x")
[ ] bug report => check the README and search github for a similar issue or PR before submitting
[ ] support request => check the README and search github for a similar issue or PR before submitting
[ ] feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request

**Current behavior**
<!-- Describe how the bug manifests. -->
<!-- Describe how the issue manifests. -->

**Expected/desired behavior**
<!-- Describe what the behavior would be without the bug. -->
<!-- Describe what the desired behavior would be. -->

**Minimal reproduction of the problem with instructions**
If the current behavior is a bug or you can illustrate your feature request better with an example,
please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via
For bug reports please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via or similar (you can use this template as a starting point:

**What is the motivation / use case for changing the behavior?**
<!-- Describe the motivation or the concrete use case -->

**Please tell us about your environment:**
<!-- Operating system, IDE, package manager, HTTP server, ... -->
<!-- Describe the motivation or the concrete use case. -->

* **Angular version:** 2.0.X
* **Angular version:** X.Y.Z
<!-- Check whether this is still an issue in the most recent Angular version -->

* **Browser:** [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
<!-- All browsers where this could be reproduced -->

* **Language:** [all | TypeScript X.X | ES6/7 | ES5]

* **Node (for AoT issues):** `node --version` =
* **Browser:**
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX

* **For Tooling issues:**
- Node version: XX <!-- run `node --version` -->
- Platform: <!-- Mac, Linux, Windows -->

* Others:
<!-- Anything else relevant? Operating system version, IDE, package manager, HTTP server, ... -->
@@ -0,0 +1,38 @@
** PR Checklist
Please check if your PR fulfills the following requirements:

- [ ] The commit message follows our guidelines:
- [ ] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)

** PR Type
What kind of change does this PR introduce?

<!-- Please check the one that applies to this PR using "x". -->
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

** What is the current behavior?
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->

Issue Number: N/A

** What is the new behavior?

** Does this PR introduce a breaking change?
[ ] Yes
[ ] No

<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->

** Other information
@@ -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 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 [][version]

@@ -0,0 +1,202 @@
# Contributing to ng-seed/universal

We would love for you to contribute to **`ng-seed/universal`** and help make it even better than it is today! As a contributor,
here are the guidelines we would like you to follow:

- [Code of Conduct](#coc)
- [Issues and Bugs](#issue)
- [Feature requests](#feature)
- [Submission guidelines](#submit)
- [Coding rules](#rules)
- [Commit message guidelines](#commit)

## <a name="coc"></a> Code of Conduct
Help us keep **`ng-seed/universal`** open and inclusive. Please read and follow our [Code of Conduct][coc].

## <a name="issue"></a> Found a Bug?
If you find a bug in the source code, you can help us by [submitting an issue](#submit-issue) to our [GitHub Repository][github].

Even better, you can [submit a Pull Request](#submit-pr) with a fix.

## <a name="feature"></a> Missing a Feature?
You can *request* a new feature by [submitting an issue](#submit-issue) to our GitHub Repository.

If you would like to *implement* a new feature, please submit an issue with a proposal for your work first, to be sure that
we can use it.

Please consider what kind of change it is:
* For a **Major Feature**, first open an issue and outline your proposal so that it can be discussed.
This will also allow us to better coordinate our efforts, prevent duplication of work, and help you to craft the change
so that it is successfully accepted into the project.
* **Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).

## <a name="submit"></a> Submission guidelines
### <a name="submit-issue"></a> Submitting an Issue
Before you submit an issue, please search the issue tracker, maybe an issue for your problem already exists and the discussion
might inform you of workarounds readily available.

We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order
to reproduce bugs we will systematically ask you to provide a minimal reproduction scenario using

Having a live, reproducible scenario gives us wealth of important information without going back & forth to you with additional
questions like:
- version used
- 3rd-party libraries and their versions
- and most importantly: a use-case that fails

A minimal reproduce scenario using allows us to quickly confirm a bug (or point out coding problem) as
well as confirm that we are fixing the right problem. If plunker is not a suitable way to demonstrate the problem (*ex:
issues related to our npm packaging*), please create a standalone git repository demonstrating the problem.

We will be insisting on a minimal reproduce scenario in order to save maintainers time and ultimately be able to fix more

Interestingly, from our experience users often find coding problems themselves while preparing a minimal plunk. We understand
that sometimes it might be hard to extract essentials bits of code from a larger code-base but we really need to isolate
the problem before we can fix it.

Unfortunately we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you,
we are going to close an issue that don't have enough info to be reproduced.

You can file new issues by filling out our [new issue form](

### <a name="submit-pr"></a> Submitting a Pull Request (PR)
Before you submit your Pull Request (PR) consider the following guidelines:

* Search [GitHub]( for an open or closed PR that relates to your submission.
You don't want to duplicate effort.
* Make your changes in a new git branch:
git checkout -b my-fix-branch master
* Create your patch, **including appropriate test cases**.
* Follow our [Coding rules](#rules).
* Run the full test suite and ensure that all tests pass.
* Commit your changes using a descriptive commit message that follows our [commit message conventions](#commit).
Adherence to these conventions is necessary because release notes are automatically generated from these messages.
git commit -a
Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.
* Push your branch to GitHub:
git push origin my-fix-branch
* In GitHub, send a pull request to `universal:master`.
* If we suggest changes then:
* Make the required updates.
* Re-run the test suites to ensure tests are still passing.
* Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
git rebase master -i
git push -f
That's it, thanks for your contribution!

#### After your pull request is merged
After your pull request is merged, you can safely delete your branch and pull the changes from the main (upstream) repository:
* Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:
git push origin --delete my-fix-branch
* Check out the master branch:
git checkout master -f
* Delete the local branch:
git branch -D my-fix-branch
* Update your master with the latest upstream version:
git pull --ff upstream master

## <a name="rules"></a> Coding rules
To ensure consistency throughout the source code, keep these rules in mind as you are working:
* All features or bug fixes **must be tested** by one or more specs (unit-tests).
* All public API methods **must be documented**. (Details TBC).
* We follow [fulls1z3's Angular TSLint rules][angular-tslint-rules].

## <a name="commit"></a> Commit message guidelines
We have very precise rules over how our git commit messages can be formatted. This leads to **more readable messages** that
are easy to follow when looking through the **project history**. But also, we use the git commit messages to **generate
the `ng-seed/universal` change log**.

### Commit Message Format
Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format that includes
a **type**, an *optional* **scope** (*when applicable*) and a **subject**:
#### Without scope
<type>: <subject>
#### With scope
<type>(<scope>): <subject>

The **header** is mandatory and the **scope** of the header is optional.

Any line of the commit message cannot be longer 100 characters. This allows the message to be easier to read on GitHub as
well as in various git tools.

Footer should contain a [closing reference to an issue](
if any.

Samples: (even more [samples](
docs(changelog): update change log to alpha.4
fix(release): need to depend on latest rxjs and zone.js
The version in our package.json gets copied to the one we publish, and users need the latest of these.

### Revert
If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit.
In the body it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.

### Type
Must be one of the following:
* **build**: Changes that affect the build system or external dependencies (example scopes: gulp, npm, webpack)
* **ci**: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, etc)
* **docs**: Documentation only changes
* **feat**: A new feature
* **fix**: A bug fix
* **perf**: A code change that improves performance
* **refactor**: A code change that neither fixes a bug nor adds a feature
* **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
* **test**: Adding missing tests or correcting existing tests

* **packaging**: used for changes that change the package layout (*e.g. package.json, bundles, path changes, etc.*)
* **changelog**: used for updating the release notes in

### Subject
The subject contains succinct description of the change:
* use the imperative, present tense: "change" not "changed" nor "changes"
* don't capitalize first letter
* no dot (.) at the end

### Body
Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes". The body should include
the motivation for the change and contrast this with previous behavior.

### Footer
The footer should contain any information about **Breaking Changes** and is also the place to reference GitHub issues that
this commit **Closes**.

**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit
message is then used for this.

Oops, something went wrong.

0 comments on commit 358c4fc

Please sign in to comment.