Skip to content

Commit

Permalink
housekeeping: updated stalebot message (#1653)
Browse files Browse the repository at this point in the history
  • Loading branch information
ghuntley authored and reactiveuibot committed May 20, 2018
1 parent 6f61685 commit 10b7797
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions .github/stale.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,14 +15,13 @@ exemptLabels:
- proposal
- contributor-experience
- developer-experience
- ¯\_(ツ)_/¯


# Label to use when marking an issue as stale
staleLabel: waiting-for-response-or-contribution

# Comment to post when marking an issue as stale. Set to `false` to disable
markComment: >
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We do this because it helps reduce the workload of our extremely busy maintainers. If you want this issue progressed faster please start talks with a maintainer with how you can help out. There are so many ways to contribute to open-source and the most valued are often not code related. We are always looking for more help and look after those who stick around. Say howdy to one of the maintainers or browse https://reactiveui.net/contribute/ for ideas on where to start your journey.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want this issue progressed faster please start a conversation about raising a pull-request or [coordinating your pull-request with a maintainer](https://reactiveui.net/slack) to get it merged. Understand that [if folks like yourself don't contribute, ReactiveUI won't grow](https://reactiveui.net/blog/2018/05/reactiveui-succession). You may or may not know this but ReactiveUI is maintained by unpaid volunteers. The maintainers put up a big marketing front but at it's core is a couple of passionate folks. ReactiveUI cares about open-source sustainability as maintainers have a serious load on their shoulders. Consumers shouldn't be naive in thinking that the latest update to a nuget package just magically materializes from the ethers. These things happen because our peers make them happen. No-one wants a tragedy of the commons situation. I urge you to get involved. Thank-you.
# Comment to post when closing a stale issue. Set to `false` to disable
closeComment: false

0 comments on commit 10b7797

Please sign in to comment.