tarballs.nixos.org is omitted from the change because urls from there
are always hashed and checked

The text is quite long and hard to read in hub (because it is one whole line
with no line breaks). Also simplified the language/sentence structure a bit for
non-native speakers.

It's a bit too spammy!

This is really essential thing that everyone should be doing.
A few extra notifications won't hurt anyone, and we should be tracking issues
to connect them to the best people who can handle them.

Co-Authored-By: Cole Helbling <cole.e.helbling@outlook.com>

ofborg does a better job at assigning people

'nix run' is an experimental command.

changelog: https://github.com/Mic92/nixpkgs-review/releases/tag/2.1.1

to reflect the introduction of issue templates

The configuration added is taken from RFC 0051, and is the first step
toward implementing it. Next, we will have to enable the stale bot by
installing the GitHub application.

https://github.com/NixOS/rfcs/blob/master/rfcs/0051-mark-stale-issues.md

Per https://github.com/NixOS/nixpkgs/pull/58147#issuecomment-478234495
sandboxing is not fully functional on macOS.

.github: specify where sandboxing can be run

Co-Authored-By: Jon <jonringer@users.noreply.github.com>

.github: remove macOS note

This commit adds myself as a CODEOWNER for the Haskell-related packages.

Signed-off-by: Austin Seipp <aseipp@pobox.com>

since the .github/SECURITY.md was added in the org-level repo, there are
now two entries in the list. So remove this-one.

The configuration is now done through the shared configuration repo:

https://github.com/nixos/.github

Create new categories for the issues:

* Bug report
* Packaging request
* Security

Add metadata information to the issues so that we may match issues to
maintainers using a bot in the future.

The old `.github/ISSUE_TEMPLATE.md` is being used by the "Open a regular
issue." link.

There have been a couple of instances where I have by chance noticed PRs
which add non-free licenses without them being appropriately marked. I'd
like to be notified of proposed changes to licenses to make it less
likely that this sort of thing slips by.

I'm listed as the maintainer for most of these already but would like to be
notified on changes.

It is faster, handles more edge cases and allows to test/review the built
packages interactively.

I'm happy to keep helping out with Haskell infrastructure where I can,
but I don't have a good system for handling the accidental codeowner
pings caused by target branch switches.