wez/wezterm
1
1
Fork 0
mirror of https://github.com/wez/wezterm.git synced 2024-11-26 08:25:50 +03:00
Code Issues Projects Releases Wiki Activity

Add link to the Matrix/Riot room

Browse Source
This commit is contained in:
Wez Furlong 2020-01-26 12:02:43 -08:00
parent d19db3c87b
commit 2ad09cec36
3 changed files with 14 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -20,8 +20,8 @@ https://wezfurlong.org/wezterm/installation.html
This is a spare time project, so please bear with me. There are two channels for support:
* You can use the GitHub issue tracker to see if someone else has a similar issue, or to file a new one: https://github.com/wez/wezterm/issues
* There is a gitter room for (potentially!) real time discussions: https://gitter.im/wezterm/Lobby
* There is a [Gitter room](https://gitter.im/wezterm/Lobby) which is bridged to [the Matrix/Riot.im](https://riot.im/app/#/room/#gitter_wezterm=2Flobby:matrix.org) for (potentially!) real time discussions
The gitter room is probably better suited to questions than it is to bug
The Gitter/Matrix room is probably better suited to questions than it is to bug
reports, but don't be afraid to use whichever you are most comfortable using
and we'll work it out.

1
docs/SUMMARY.md
View File

@ -12,3 +12,4 @@
- [SSH](ssh.markdown)
- [Serial Ports & Arduino](serial.markdown)
- [Multiplexing](multiplexing.markdown)
- [Getting Help](help.markdown)

11
docs/help.markdown Normal file
View File

@ -0,0 +1,11 @@
## Getting Help
This is a spare time project, so please bear with me. There are two channels for support:
* You can use the GitHub issue tracker to see if someone else has a similar issue, or to file a new one: https://github.com/wez/wezterm/issues
* There is a [Gitter room](https://gitter.im/wezterm/Lobby) which is bridged to [the Matrix/Riot.im](https://riot.im/app/#/room/#gitter_wezterm=2Flobby:matrix.org) for (potentially!) real time discussions
The Gitter/Matrix room is probably better suited to questions than it is to bug
reports, but don't be afraid to use whichever you are most comfortable using
and we'll work it out.