Make pull request from github page for your clone against master branch

Optionally make backport Pull Request(s) for landing a bug fix
into released aiohttp versions.

Note

The project uses Squash-and-Merge strategy for GitHub Merge button.

Basically it means that there is no need to rebase a Pull Request against
master branch. Just gitmergemaster into your working copy (a fork) if
needed. The Pull Request is automatically squashed into the single commit
once the PR is accepted.

We are trying hard to have good test coverage; please don’t make it worse.

Use:

$ make cov

to run test suite and collect coverage information. Once the command
has finished check your coverage at the file that appears in the last
line of the output:
openfile:///.../aiohttp/htmlcov/index.html

The CHANGES.rst file is managed using towncrier tool and all non trivial
changes must be accompanied by a news entry.

To add an entry to the news file, first you need to have created an
issue describing the change you want to make. A Pull Request itself
may function as such, but it is preferred to have a dedicated issue
(for example, in case the PR ends up rejected due to code quality
reasons).

Once you have an issue or pull request, you take the number and you
create a file inside of the CHANGES/ directory named after that
issue number with an extension of .removal, .feature,
.bugfix, or .doc. Thus if your issue or PR number is 1234 and
this change is fixing a bug, then you would create a file
CHANGES/1234.bugfix. PRs can span multiple categories by creating
multiple files (for instance, if you added a feature and
deprecated/removed the old feature at the same time, you would create
CHANGES/NNNN.feature and CHANGES/NNNN.removal). Likewise if a PR touches
multiple issues/PRs you may create a file for each of them with the
exact same contents and Towncrier will deduplicate them.

The contents of this file are reStructuredText formatted text that
will be used as the content of the news file entry. You do not need to
reference the issue or PR numbers here as towncrier will automatically
add a reference to all of the affected issues when rendering the news
file.

The easiest way is providing Pull Requests for issues in our bug
tracker. But if you have a great idea for the library improvement
– please make an issue and Pull Request.

The rules for committers are simple:

No wild commits! Everything should go through PRs.

Take a part in reviews. It’s very important part of maintainer’s activity.

Pickup issues created by others, especially if they are simple.

Keep test suite comprehensive. In practice it means leveling up
coverage. 97% is not bad but we wish to have 100% someday. Well, 99%
is good target too.

Don’t hesitate to improve our docs. Documentation is very important
thing, it’s the key for project success. The documentation should
not only cover our public API but help newbies to start using the
project and shed a light on non-obvious gotchas.

After positive answer aiohttp committer creates an issue on github
with the proposal for nomination. If the proposal will collect only
positive votes and no strong objection – you’ll be a new member in
our team.