add PR guideline, update CONTRIBUTING.md, move spellcheck

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,33 @@
+# Description
+
+<!--
+
+A crisp summary
+
+Fixes #
+Ref #
+-->
+
+<!--
+Apply labels!
+-->
+
+## Checklist
+
+- [ ] Labels applied correctly? See the [contributing guidlines](../CONTRIBUTING.md).
+- [ ] Workspace compiles `cargo build --workspace`?
+- [ ] Workspace tests `cargo test --workspace`?
+- [ ] Applied `cargo +nightly fmt` with the version from CI?
+- [ ] Ran `cargo spellcheck` without any fallout? If any, update `.spellcheck/lingua.dic`.
+- [ ] Fixed any fallout caused by these changes in `cumulus`?
+- [ ] Referenced relevant companion pullrequests of `substrate` and `cumulus`?
+- [ ] Does the change mandate an _architecture design record_ being committed?
+
+<!--
+## Companions:
+
+Must be last!
+
+substrate companion: https://github.com/paritytech/substrate/pulls/
+cumulus companion: https://github.com/paritytech/cumulus/pulls/
+-->

.gitlab-ci.yml

@@ -273,7 +273,7 @@ spellcheck:
     - git fetch origin +${CI_DEFAULT_BRANCH}:${CI_DEFAULT_BRANCH}
     - echo "___Spellcheck is going to check your diff___"
     - cargo spellcheck list-files -vvv $(git diff --diff-filter=AM --name-only $(git merge-base ${CI_COMMIT_SHA} ${CI_DEFAULT_BRANCH} -- :^bridges))
-    - time cargo spellcheck check -vvv --cfg=scripts/gitlab/spellcheck.toml --checkers hunspell --code 1
+    - time cargo spellcheck check -vvv --cfg=.spellcheck/spellcheck.toml --checkers hunspell --code 1
         $(git diff --diff-filter=AM --name-only $(git merge-base ${CI_COMMIT_SHA} ${CI_DEFAULT_BRANCH} -- :^bridges))
   allow_failure:                   true
 
@@ -854,5 +854,3 @@ cancel-pipeline:
     PROJECT_ID:                    "${CI_PROJECT_ID}"
     PIPELINE_ID:                   "${CI_PIPELINE_ID}"
   trigger:                         "parity/infrastructure/ci_cd/pipeline-stopper"
-
-

CONTRIBUTING.md

@@ -8,7 +8,10 @@ There are a few basic ground-rules for contributors (including the maintainer(s)
 - **Non-master branches**, prefixed with a short name moniker (e.g. `gav-my-feature`) must be used for ongoing work.
 - **All modifications** must be made in a **pull-request** to solicit feedback from other contributors.
 - A pull-request _must not be merged until CI_ has finished successfully.
-- Contributors should adhere to the [house coding style](https://github.com/paritytech/polkadot/wiki/Style-Guide).
+- Contributors should apply `cargo +nightly fmt` with the version used in CI.
+- Synchronized changes must have annotations with the respective [companion PRs of substrate and cumulus](https://github.com/paritytech/substrate/blob/master/docs/CONTRIBUTING.adoc#updating-polkadot-as-well), tl;dr add the following lines at the _end_ of your PR description:
+  - `substrate companion: https://github.com/paritytech/substrate/pulls/#1234`
+  - `cumulus companion: https://github.com/paritytech/cumulus/pulls/#5678`
 
 ### Merging pull requests once CI is successful
 
@@ -33,6 +36,21 @@ When reviewing a pull request, the end-goal is to suggest useful changes to the
 - There exists a somewhat cleaner/better/faster way of accomplishing the same feature/fix.
 - It does not fit well with some other contributors' longer-term vision for the project.
 
+### Helping out
+
+We use labels to manage PRs and issues and communicate state of a PR. Please familiarize yourself with them. Furthermore we are organizing issues in milestones. Best way to get started is to a pick a ticket from the current milestone tagged easy or medium and get going or mentor and get in contact with the mentor offering their support on that larger task.
+Issues
+
+Please label issues with the following labels:
+
+    I-* Issue severity and type. EXACTLY ONE REQUIRED.
+
+    P-* Issue priority. AT MOST ONE ALLOWED.
+
+    Q-* Issue difficulty. AT MOST ONE ALLOWED.
+
+    Z-* More general tags on the issue, denoting context and resolution.
+
 ## Releases
 
 Declaring formal releases remains the prerogative of the project maintainer(s).