From 5c5baaf17d688151d5c72eb6535ca499ba916fdf Mon Sep 17 00:00:00 2001 From: Ryan Mulligan Date: Thu, 23 Aug 2018 06:19:02 -0700 Subject: [PATCH] treewide: remove mailing list references --- .github/CONTRIBUTING.md | 2 +- README.md | 1 - doc/reviewing-contributions.xml | 9 +++++---- nixos/doc/manual/manual.xml | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 981036bf4a02..576beb18de6a 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -43,7 +43,7 @@ See the nixpkgs manual for more details on [standard meta-attributes](https://ni ## Writing good commit messages -In addition to writing properly formatted commit messages, it's important to include relevant information so other developers can later understand *why* a change was made. While this information usually can be found by digging code, mailing list archives, pull request discussions or upstream changes, it may require a lot of work. +In addition to writing properly formatted commit messages, it's important to include relevant information so other developers can later understand *why* a change was made. While this information usually can be found by digging code, mailing list/Discourse archives, pull request discussions or upstream changes, it may require a lot of work. For package version upgrades and such a one-line commit message is usually sufficient. diff --git a/README.md b/README.md index 86bc8534b3c4..004bba34530d 100644 --- a/README.md +++ b/README.md @@ -38,5 +38,4 @@ For pull-requests, please rebase onto nixpkgs `master`. Communication: * [Discourse Forum](https://discourse.nixos.org/) -* [Mailing list](https://groups.google.com/forum/#!forum/nix-devel) * [IRC - #nixos on freenode.net](irc://irc.freenode.net/#nixos) diff --git a/doc/reviewing-contributions.xml b/doc/reviewing-contributions.xml index 88bb1efdfd3c..b2a2675c3e65 100644 --- a/doc/reviewing-contributions.xml +++ b/doc/reviewing-contributions.xml @@ -605,10 +605,11 @@ policy. --> - In a case a contributor leaves definitively the Nix community, he should - create an issue or notify the mailing list with references of packages and - modules he maintains so the maintainership can be taken over by other - contributors. + In a case a contributor leaves definitively the Nix community, he + should create an issue or post on Discourse with + references of packages and modules he maintains so the + maintainership can be taken over by other contributors. diff --git a/nixos/doc/manual/manual.xml b/nixos/doc/manual/manual.xml index 61b21203f500..e9338efbc025 100644 --- a/nixos/doc/manual/manual.xml +++ b/nixos/doc/manual/manual.xml @@ -17,8 +17,8 @@ If you encounter problems, please report them on the nix-devel - mailing list or on the Discourse + or on the #nixos channel on Freenode. Bugs should be reported in