5 files changed, 71 insertions, 48 deletions
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 00000000..4e4f6a77
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,33 @@
+---
+name: Bugs
+about: Crashes and other bugs
+labels: 'bug'
+---
+### Please read the following before submitting:
+- Please do NOT submit bug reports for questions. Ask questions on IRC at #sway on irc.freenode.net.
+- Proprietary graphics drivers, including nvidia, are not supported. Please use the open source equivalents, such as nouveau, if you would like to use Sway.
+- Problems with the Wayland version of Firefox are likely to be Firefox bugs. Start by submitting your issue to the Firefox Bugzilla and come back here only after they confirm otherwise.
+### Please fill out the following:
+- **Sway Version:**
+  - `swaymsg -t get_version` or `sway -v`
+- **Debug Log:**
+  - Run `sway -d 2> ~/sway.log` from a TTY and upload it to a pastebin, such as gist.github.com.
+  - This will record information about sway's activity. Please try to keep the reproduction as brief as possible and exit sway.
+- **Configuration File:**
+  - Please try to produce with the default configuration.
+  - If you cannot reproduce with the default configuration, please try to find the minimal configuration to reproduce.
+  - Upload the config to a pastebin such as gist.github.com.
+- **Stack Trace:**
+  - This is only needed if sway crashes.
+  - If you use systemd, you should be able to open the coredump of the most recent crash with gdb with
+    `coredumpctl gdb sway` and then `bt full` to obtain the stack trace.
+  - If the lines mentioning sway or wlroots have `??` for the location, your binaries were built without debug symbols. Please compile both sway and wlroots from source and try to reproduce.
+- **Description:**
+  - The steps you took in plain English to reproduce the problem.
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 00000000..f09cdf5b
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Questions
+    url: "http://webchat.freenode.net/?channels=sway&uio=d4"
+    about: "Please ask questions on IRC in #sway on irc.freenode.net"
diff --git a/.github/ISSUE_TEMPLATE/enhancement.md b/.github/ISSUE_TEMPLATE/enhancement.md
new file mode 100644
index 00000000..3ed45b01
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/enhancement.md
@@ -0,0 +1,13 @@
+---
+name: Enhancements
+about: New functionality
+labels: 'enhancement'
+---
+### Please read the following before submitting:
+- We are not accepting any new window management features unless they get implemented by i3. Please consider searching for or opening an i3 feature request.
+### Please fill out the following:
+- **Description:**
+Please describe in plain English what the enhancement is and what the use case is.
diff --git a/.github/ISSUE_TEMPLATE/i3_compat.md b/.github/ISSUE_TEMPLATE/i3_compat.md
new file mode 100644
index 00000000..4dfa21c3
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/i3_compat.md
@@ -0,0 +1,20 @@
+---
+name: i3 Compatibility
+about: Sway behaves differently from or lacks i3 functionality
+labels: 'i3-compat'
+---
+### Please read the following before submitting:
+- The following either do not make sense for Wayland or we have decided against supporting:
+  - `restart`
+  - `resource`
+  - saving and loading layouts
+  - the i3 sync protocol
+### Please fill out the following:
+- **i3 PR:**
+  - If this is new i3 functionality, please add a link to the i3 pull request.
+- **Description:**
+  - Please describe in plain English how Sway and i3's behaviors differ or what functionality Sway is lacking.
diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md
deleted file mode 100644
index 4b715aeb..00000000
--- a/ISSUE_TEMPLATE.md
+++ /dev/null
@@ -1,48 +0,0 @@
-If you want to ask a question, please check out the wiki. If you don't find an answer there, ask on IRC (#sway on irc.freenode.net). The issue tracker may not be used for questions.
-If you are using the Nvidia proprietary driver for any reason, you have two choices:
-1. Uninstall it and use nouveau instead
-2. Use X11+i3 and close your browser tab
-If `lsmod | grep nvidia | wc -l` shows anything other than zero, your bug report is not welcome here.
-Additionally, problems with Firefox are almost certainly Firefox bugs, not sway bugs. Start by submitting your issue to the Firefox Bugzilla and come back here only after they confirm otherwise.
-Otherwise, please include the following four components in your bug report: sway version, debug log, configuration (if applicable), and an explanation of steps taken to reproduce the issue. If sway crashes, also include a stack trace.
-Obtain your version like so:
-    swaymsg -t get_version
-If this doesn't work, use:
-    sway -v
-* Sway Version:
-Obtain a debug log by running the following command from a TTY:
-    sway -d 2> ~/sway.log
-This will record information about sway's activity when it's running. Briefly reproduce your problem and exit sway.  When preparing a debug log, brevity is important - start up sway, do the minimum work necessary to reproduce the error, then close sway.
-Upload the debug log to a pastebin service such as [gist.github.com](https://gist.github.com), and link to it below.
-* Debug Log:
-You should try to reproduce the issue with the default configuration. If you cannot, please reproduce with a minimal configuration, upload the config to a pastebin service, and link to it below.
-* Configuration File:
-Finally, explain the steps you took in plain English to reproduce the problem below.
-* Stack Trace, if sway crashes:
-If you use systemd, you should be able to open the coredump of the most recent crash with GDB like so:
-    coredumpctl gdb sway
-And then type `bt full` to obtain the stack trace.
-If the lines mentioning sway/wlroots have "??" for the location, your binaries were built without debug symbols, and the stack trace is unlikely to be useful. You can find instructions to compile sway from source [here](https://github.com/swaywm/sway/wiki/Development-Setup#compiling-as-a-subproject). Note that debug symbols are included in Meson builds by default.

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 00000000..4e4f6a77 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,33 @@
		1	---
		2	name: Bugs
		3	about: Crashes and other bugs
		4	labels: 'bug'
		5
		6	---
		7
		8	### Please read the following before submitting:
		9	- Please do NOT submit bug reports for questions. Ask questions on IRC at #sway on irc.freenode.net.
		10	- Proprietary graphics drivers, including nvidia, are not supported. Please use the open source equivalents, such as nouveau, if you would like to use Sway.
		11	- Problems with the Wayland version of Firefox are likely to be Firefox bugs. Start by submitting your issue to the Firefox Bugzilla and come back here only after they confirm otherwise.
		12
		13	### Please fill out the following:
		14	- Sway Version:
		15	- `swaymsg -t get_version` or `sway -v`
		16
		17	- Debug Log:
		18	- Run `sway -d 2> ~/sway.log` from a TTY and upload it to a pastebin, such as gist.github.com.
		19	- This will record information about sway's activity. Please try to keep the reproduction as brief as possible and exit sway.
		20
		21	- Configuration File:
		22	- Please try to produce with the default configuration.
		23	- If you cannot reproduce with the default configuration, please try to find the minimal configuration to reproduce.
		24	- Upload the config to a pastebin such as gist.github.com.
		25
		26	- Stack Trace:
		27	- This is only needed if sway crashes.
		28	- If you use systemd, you should be able to open the coredump of the most recent crash with gdb with
		29	`coredumpctl gdb sway` and then `bt full` to obtain the stack trace.
		30	- If the lines mentioning sway or wlroots have `??` for the location, your binaries were built without debug symbols. Please compile both sway and wlroots from source and try to reproduce.
		31
		32	- Description:
		33	- The steps you took in plain English to reproduce the problem.


diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 00000000..f09cdf5b --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
		1	blank_issues_enabled: false
		2	contact_links:
		3	- name: Questions
		4	url: "http://webchat.freenode.net/?channels=sway&uio=d4"
		5	about: "Please ask questions on IRC in #sway on irc.freenode.net"


diff --git a/.github/ISSUE_TEMPLATE/enhancement.md b/.github/ISSUE_TEMPLATE/enhancement.md new file mode 100644 index 00000000..3ed45b01 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/enhancement.md
@@ -0,0 +1,13 @@
		1	---
		2	name: Enhancements
		3	about: New functionality
		4	labels: 'enhancement'
		5
		6	---
		7
		8	### Please read the following before submitting:
		9	- We are not accepting any new window management features unless they get implemented by i3. Please consider searching for or opening an i3 feature request.
		10
		11	### Please fill out the following:
		12	- Description:
		13	Please describe in plain English what the enhancement is and what the use case is.


diff --git a/.github/ISSUE_TEMPLATE/i3_compat.md b/.github/ISSUE_TEMPLATE/i3_compat.md new file mode 100644 index 00000000..4dfa21c3 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/i3_compat.md
@@ -0,0 +1,20 @@
		1	---
		2	name: i3 Compatibility
		3	about: Sway behaves differently from or lacks i3 functionality
		4	labels: 'i3-compat'
		5
		6	---
		7
		8	### Please read the following before submitting:
		9	- The following either do not make sense for Wayland or we have decided against supporting:
		10	- `restart`
		11	- `resource`
		12	- saving and loading layouts
		13	- the i3 sync protocol
		14
		15	### Please fill out the following:
		16	- i3 PR:
		17	- If this is new i3 functionality, please add a link to the i3 pull request.
		18
		19	- Description:
		20	- Please describe in plain English how Sway and i3's behaviors differ or what functionality Sway is lacking.


diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md deleted file mode 100644 index 4b715aeb..00000000 --- a/ISSUE_TEMPLATE.md +++ /dev/null
@@ -1,48 +0,0 @@
1	If you want to ask a question, please check out the wiki. If you don't find an answer there, ask on IRC (#sway on irc.freenode.net). The issue tracker may not be used for questions.
2
3	If you are using the Nvidia proprietary driver for any reason, you have two choices:
4
5	1. Uninstall it and use nouveau instead
6	2. Use X11+i3 and close your browser tab
7
8	If `lsmod \| grep nvidia \| wc -l` shows anything other than zero, your bug report is not welcome here.
9
10	Additionally, problems with Firefox are almost certainly Firefox bugs, not sway bugs. Start by submitting your issue to the Firefox Bugzilla and come back here only after they confirm otherwise.
11
12	Otherwise, please include the following four components in your bug report: sway version, debug log, configuration (if applicable), and an explanation of steps taken to reproduce the issue. If sway crashes, also include a stack trace.
13
14	Obtain your version like so:
15
16	swaymsg -t get_version
17
18	If this doesn't work, use:
19
20	sway -v
21
22	* Sway Version:
23
24	Obtain a debug log by running the following command from a TTY:
25
26	sway -d 2> ~/sway.log
27
28	This will record information about sway's activity when it's running. Briefly reproduce your problem and exit sway. When preparing a debug log, brevity is important - start up sway, do the minimum work necessary to reproduce the error, then close sway.
29
30	Upload the debug log to a pastebin service such as [gist.github.com](https://gist.github.com), and link to it below.
31
32	* Debug Log:
33
34	You should try to reproduce the issue with the default configuration. If you cannot, please reproduce with a minimal configuration, upload the config to a pastebin service, and link to it below.
35
36	* Configuration File:
37
38	Finally, explain the steps you took in plain English to reproduce the problem below.
39
40	* Stack Trace, if sway crashes:
41
42	If you use systemd, you should be able to open the coredump of the most recent crash with GDB like so:
43
44	coredumpctl gdb sway
45
46	And then type `bt full` to obtain the stack trace.
47
48	If the lines mentioning sway/wlroots have "??" for the location, your binaries were built without debug symbols, and the stack trace is unlikely to be useful. You can find instructions to compile sway from source [here](https://github.com/swaywm/sway/wiki/Development-Setup#compiling-as-a-subproject). Note that debug symbols are included in Meson builds by default.