nordic-dev.net/nixpkgs
nordic-dev.net/nixpkgs
2
0
Fork 0
mirror of https://github.com/NixOS/nixpkgs.git synced 2024-12-15 10:12:58 +00:00
Code Issues Packages Projects Releases Wiki Activity
d3a2719fe8
nixpkgs/.github/STALE-BOT.md
slotThe 2c529c3cb8 Link to Libera, Matrix instead of Freenode 
The project has moved away from Freenode as an IRC network[1], and there
is now a quite large channel on Libera.  As such, we should point users
towards that instead.

This also changes all examples to refer to libera instead of freenode
as, with the recent deletion of all freenode channels, it is perhaps
where most communities are to be found nowadays.

Finally, also link to the official Matrix room[2] as an alternative to
IRC.

Related: https://github.com/NixOS/nixpkgs/pull/129384

[1]: https://discourse.nixos.org/t/join-us-on-matrix-at-nix-nixos-org-migrating-from-freenode
[2]: https://github.com/NixOS/rfcs/pull/94
2021-07-06 16:35:37 +02:00

3.5 KiB
Raw Blame History

Stale bot information

Suggestions for PRs

  1. GitHub sometimes doesn't notify people who commented / reviewed a PR previously, when you (force) push commits. If you have addressed the reviews you can officially ask for a review from those who commented to you or anyone else.
  2. If it is unfinished but you plan to finish it, please mark it as a draft.
  3. If you don't expect to work on it any time soon, closing it with a short comment may encourage someone else to pick up your work.
  4. To get things rolling again, rebase the PR against the target branch and address valid comments.
  5. If you need a review to move forward, ask in the Discourse thread for PRs that need help.
  6. If all you need is a merge, check the git history to find and request reviews from people who usually merge related contributions.

Suggestions for issues

  1. If it is resolved (either for you personally, or in general), please consider closing it.
  2. If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
  3. If you still have interest in resolving it, try to ping somebody who you believe might have an interest in the topic. Consider discussing the problem in our Discourse Forum.
  4. As with all open source projects, your best option is to submit a Pull Request that addresses this issue. We ❤️ this attitude!

Memorandum on closing issues

Don't be afraid to close an issue that holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

Useful GitHub search queries