PolytreeDE
/
polybar
mirror of https://github.com/polybar/polybar.git
1
0
Fork 0
Code Releases Activity
polybar/SUPPORT.md

16 lines
1.3 KiB
Markdown
Raw Normal View History

Clearly separate issue and bug reports The issue tracker should be for bugs only. Right now actual bugs can easily fall through the cracks because we get stuck answering questions and basically providing tech support. This move is also intended to have more traffic to our subreddit and IRC channel with the hope that the community can also help itself out.
2018-10-27 12:56:48 +00:00
Getting Help
============
Add SUPPORT.md (#803) Adding this file to the root of the project will make a note appear when opening a new issue, asking the user to first read this document. As proposed in #802
2017-10-28 21:17:46 +00:00
Clearly separate issue and bug reports The issue tracker should be for bugs only. Right now actual bugs can easily fall through the cracks because we get stuck answering questions and basically providing tech support. This move is also intended to have more traffic to our subreddit and IRC channel with the hope that the community can also help itself out.
2018-10-27 12:56:48 +00:00
If you need help or troubleshooting tips or just have a question:
Add SUPPORT.md (#803) Adding this file to the root of the project will make a note appear when opening a new issue, asking the user to first read this document. As proposed in #802
2017-10-28 21:17:46 +00:00
Add debugging guide to SUPPORT.md
2020-11-26 19:16:39 +00:00
* If applicable, go through our [debugging guide](https://github.com/polybar/polybar/wiki/Debugging-your-Config).
migration: Update URLs jaagr/polybar -> polybar/polybar Travis changed their url for new projects to travis-ci.com
2019-05-06 11:51:49 +00:00
* Read the [Known Issues page](https://github.com/polybar/polybar/wiki/Known-Issues), maybe others had the same issue before.
* Read the [Wiki page](https://github.com/polybar/polybar/wiki) for the thing you have problems with.
Update markdown files to point to discussions
2022-03-07 19:53:55 +00:00
* Ask your question on [GitHub Discussions](https://github.com/polybar/polybar/discussions)
doc: Add Gitter room The Gitter room https://gitter.im/polybar/polybar should serve a similar purpose as the IRC room with the benefit that messages persist and can be received when offline. From now on gitter should be the place where the polybar community lives. Reddit is great for asking longer questions in the style of a forum but not so great for quick back and forth conversations. IRC is better in that aspect but has the serious downside that you have to stay connected to get an answer and messages are not logged (only by your client). Both reddit and IRC are here to stay and I will still check them regularly, but we should encourage people to join gitter.
2019-11-25 17:39:36 +00:00
* Join our Gitter room at [gitter.im/polybar/polybar](https://gitter.im/polybar/polybar)
readme: Feature subreddit and irc more prominently
2018-10-27 12:59:46 +00:00
* Ask in our reddit community at [r/polybar](https://www.reddit.com/r/polybar)
Change over all IRC mentions to libera (#2450)
2021-06-16 15:02:58 +00:00
* Join the official IRC channel `#polybar` on the [`irc.libera.chat:6697`](https://libera.chat/) network. If you don't get an answer try asking on [Gitter](https://gitter.im/polybar/polybar).
Clearly separate issue and bug reports The issue tracker should be for bugs only. Right now actual bugs can easily fall through the cracks because we get stuck answering questions and basically providing tech support. This move is also intended to have more traffic to our subreddit and IRC channel with the hope that the community can also help itself out.
2018-10-27 12:56:48 +00:00
* Ask on [Unix & Linux StackExchange](https://unix.stackexchange.com/). Though not all questions may be suited over there, make sure you're [on topic](https://unix.stackexchange.com/help/on-topic).
Add SUPPORT.md (#803) Adding this file to the root of the project will make a note appear when opening a new issue, asking the user to first read this document. As proposed in #802
2017-10-28 21:17:46 +00:00
Clearly separate issue and bug reports The issue tracker should be for bugs only. Right now actual bugs can easily fall through the cracks because we get stuck answering questions and basically providing tech support. This move is also intended to have more traffic to our subreddit and IRC channel with the hope that the community can also help itself out.
2018-10-27 12:56:48 +00:00
Please **do not** use the github issue tracker to ask for help or if you have a question, it is meant for bug reports and feature requests. Issues will be closed and you will be referred to the above resources.