Skip to contentSkip to conversation

Gitlab: Add issue templates

PATCH Superseded John Snow 5 participants 15 messages Jun 3, 2021

v3 of 4 Superseded Latest is v4 →

lore
Share & tools
lore

John Snow

author
#0 lore raw

v3 cover Gitlab: Add issue templates

Add "Bug" and "Feature Request" templates to the Gitlab interface to help improve the quality of newly reported issues.

To see what this looks like, I've temporarily allowed my Gitlab fork to diverge with these files merged. See my fork's "new issue" page to see it in action: https://gitlab.com/jsnow/qemu/-/issues/new?issue

These patches do not add a "default" template, the user still has to select one from the list. I recommend that someone with permissions updates the default template:

1. https://gitlab.com/qemu-project/qemu/edit
2. ctrl+f "Default description template for issues"
3. Update the default to the (suggested) below:

```
<!-- Select "Type: Issue" and choose one of the Description templates above. -->
```

We can use this cover letter to discuss/review the wording on that default template which exists outside of repository data.

V3:
- Add pointer to https://www.qemu.org/download/#source
- Add pointer to https://www.qemu.org/contribute/security-process/
- Remove blurb covering tracing instructions.

V2:
- Updated both templates based on feedback from Peter, Daniel, and Thomas.

John Snow (2):
GitLab: Add "Bug" issue reporting template
GitLab: Add "Feature Request" issue template.

 .gitlab/issue_templates/bug.md             | 63 ++++++++++++++++++++++
 .gitlab/issue_templates/feature_request.md | 32 +++++++++++
 2 files changed, 95 insertions(+)
 create mode 100644 .gitlab/issue_templates/bug.md
 create mode 100644 .gitlab/issue_templates/feature_request.md
Signature · 1 line
2.31.1
author
#1 lore raw

PATCH v3 1/2 GitLab: Add "Bug" issue reporting template

Based loosely on libvirt's template, written by Peter Krempa.

CC Peter Krempa <[email protected]>
---
 .gitlab/issue_templates/bug.md | 63 ++++++++++++++++++++++++++++++++++
 1 file changed, 63 insertions(+)
 create mode 100644 .gitlab/issue_templates/bug.md
.gitlab/issue_templates/bug.md new file +63 -0
new file mode 100644
index 00000000000..9445777252b
@@ -0,0 +1,63 @@
+<!--
+This is the upstream QEMU issue tracker.
+
+Before submitting a bug, please attempt to reproduce your problem using
+the latest development version of QEMU, built from source. See
+https://www.qemu.org/download/#source for instructions on how to do
+this.
+
+QEMU generally supports the last two releases advertised via
+https://www.qemu.org/. Problems with distro-packaged versions of QEMU
+older than this should be reported to the distribution instead.
+
+See https://www.qemu.org/contribute/report-a-bug/ for guidance.
+
+If this is a security issue, please consult
+https://www.qemu.org/contribute/security-process/
+-->
+
+## Host environment
+ - Operating system: (Windows 10 21H1, Fedora 34, etc.)
+ - OS/kernel version: (For POSIX hosts, use `uname -a`)
+ - Architecture: (x86, ARM, s390x, etc.)
+ - QEMU flavor: (qemu-system-x86_64, qemu-aarch64, qemu-img, etc.)
+ - QEMU version: (e.g. `qemu-system-x86_64 --version`)
+ - QEMU command line:
+   <!--
+   Give the smallest, complete command line that exhibits the problem.
+
+   If you are using libvirt, virsh, or vmm, you can likely find the QEMU
+   command line arguments in /var/log/libvirt/qemu/$GUEST.log.
+   -->
+   ```
+   ./qemu-system-x86_64 -M q35 -m 4096 -enable-kvm -hda fedora32.qcow2
+   ```
+
+## Emulated/Virtualized environment
+ - Operating system: (Windows 10 21H1, Fedora 34, etc.)
+ - OS/kernel version: (For POSIX guests, use `uname -a`.)
+ - Architecture: (x86, ARM, s390x, etc.)
+
+
+## Description of problem
+<!-- Describe the problem, including any error/crash messages seen. -->
+
+
+## Steps to reproduce
+1.
+2.
+3.
+
+
+## Additional information
+
+<!--
+Attach logs, stack traces, screenshots, etc. Compress the files if necessary.
+If using libvirt, libvirt logs and XML domain information may be relevant.
+-->
+
+<!--
+The line below ensures that proper tags are added to the issue.
+Please do not remove it.
+-->
+/label ~"kind::Bug"
Signature · 1 line
2.31.1
Reviewed-by on v3 1/2
#2 lore raw

Re: [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template

Quoted 8 lines · John Snow

Based loosely on libvirt's template, written by Peter Krempa.

CC Peter Krempa <[email protected]>
---
  .gitlab/issue_templates/bug.md | 63 ++++++++++++++++++++++++++++++++++
  1 file changed, 63 insertions(+)

create mode 100644 .gitlab/issue_templates/bug.md

#3 lore raw

Re: [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template

In reply to John Snow
Quoted 29 lines · John Snow

Based loosely on libvirt's template, written by Peter Krempa.

CC Peter Krempa <[email protected]>
---
 .gitlab/issue_templates/bug.md | 63 ++++++++++++++++++++++++++++++++++
 1 file changed, 63 insertions(+)
 create mode 100644 .gitlab/issue_templates/bug.md
.gitlab/issue_templates/bug.md new file +14 -0
new file mode 100644
index 00000000000..9445777252b
@@ -0,0 +1,63 @@
+<!--
+This is the upstream QEMU issue tracker.
+
+Before submitting a bug, please attempt to reproduce your problem using
+the latest development version of QEMU, built from source. See
+https://www.qemu.org/download/#source for instructions on how to do
+this.
+
+QEMU generally supports the last two releases advertised via
+https://www.qemu.org/. Problems with distro-packaged versions of QEMU
+older than this should be reported to the distribution instead.
+
+See https://www.qemu.org/contribute/report-a-bug/ for guidance.
+

.gitlab/issue_templates/bug.md line 24

Quoted 10 lines
.gitlab/issue_templates/bug.md new file +10 -0
+If this is a security issue, please consult
+https://www.qemu.org/contribute/security-process/
+-->
+
+## Host environment
+ - Operating system: (Windows 10 21H1, Fedora 34, etc.)
+ - OS/kernel version: (For POSIX hosts, use `uname -a`)
+ - Architecture: (x86, ARM, s390x, etc.)
+ - QEMU flavor: (qemu-system-x86_64, qemu-aarch64, qemu-img, etc.)
+ - QEMU version: (e.g. `qemu-system-x86_64 --version`)

I haven't reviewed earlier version, but I wonder about the "build from sources" use case (this is not a template for distributions but for the mainstream project), so maybe add:

## Build environment (in case you built QEMU from source)
- configure script command line: (e.g. ./configure --enable-nettle
--disable-glusterfs --disable-user)
- configure script summary output

Quoted 40 lines
.gitlab/issue_templates/bug.md new file +39 -0
+ - QEMU command line:
+   <!--
+   Give the smallest, complete command line that exhibits the problem.
+
+   If you are using libvirt, virsh, or vmm, you can likely find the QEMU
+   command line arguments in /var/log/libvirt/qemu/$GUEST.log.
+   -->
+   ```
+   ./qemu-system-x86_64 -M q35 -m 4096 -enable-kvm -hda fedora32.qcow2
+   ```
+
+## Emulated/Virtualized environment
+ - Operating system: (Windows 10 21H1, Fedora 34, etc.)
+ - OS/kernel version: (For POSIX guests, use `uname -a`.)
+ - Architecture: (x86, ARM, s390x, etc.)
+
+
+## Description of problem
+<!-- Describe the problem, including any error/crash messages seen. -->
+
+
+## Steps to reproduce
+1.
+2.
+3.
+
+
+## Additional information
+
+<!--
+Attach logs, stack traces, screenshots, etc. Compress the files if necessary.
+If using libvirt, libvirt logs and XML domain information may be relevant.
+-->
+
+<!--
+The line below ensures that proper tags are added to the issue.
+Please do not remove it.
+-->
+/label ~"kind::Bug"
author
#4 lore raw

Re: [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template

Quoted 8 lines · Philippe Mathieu-Daudé

I haven't reviewed earlier version, but I wonder about the "build from sources" use case (this is not a template for distributions but for the mainstream project), so maybe add:

## Build environment (in case you built QEMU from source)
- configure script command line: (e.g. ./configure --enable-nettle
--disable-glusterfs --disable-user)
- configure script summary output

Maybe just a little bit too much information. Even though I am pushing people to build from source, I actually think more reports are likely not to have done so.

We can always ask a follow-up question if we can't reproduce without the specific configuration and a good reporter will reply ;)

--js

#5 lore raw

Re: [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template

Quoted 5 lines · John Snow
Quoted 4 lines · Philippe Mathieu-Daudé

I haven't reviewed earlier version, but I wonder about the "build from sources" use case (this is not a template for distributions but for the mainstream project), so maybe add:

Quoted 8 lines
Quoted 4 lines

## Build environment (in case you built QEMU from source)
- configure script command line: (e.g. ./configure --enable-nettle
--disable-glusterfs --disable-user)
- configure script summary output

Maybe just a little bit too much information. Even though I am pushing people to build from source, I actually think more reports are likely not to have done so.

We need to bear in mind what % of bug reports do we actually need this information for. We don't want to be asking for information that we know is going to be irrelevant for (say) 60% of bug reports, because that wastes time of users.

My gut feeling is that while configure args are useful to know in many cases, I doubt it genuinely needed for more than a relatively small percentage of bug reports.

Regards,
Daniel

Signature · 3 lines
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
#6 lore raw

Re: [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template

In reply to John Snow
Quoted 15 lines · John Snow

Based loosely on libvirt's template, written by Peter Krempa.

CC Peter Krempa <[email protected]>
---
 .gitlab/issue_templates/bug.md | 63 ++++++++++++++++++++++++++++++++++
 1 file changed, 63 insertions(+)
 create mode 100644 .gitlab/issue_templates/bug.md
.gitlab/issue_templates/bug.md new file +0 -0
new file mode 100644
index 00000000000..9445777252b

.gitlab/issue_templates/bug.md line 7

Quoted 7 lines
.gitlab/issue_templates/bug.md new file +7 -0
@@ -0,0 +1,63 @@
+<!--
+This is the upstream QEMU issue tracker.
+
+Before submitting a bug, please attempt to reproduce your problem using
+the latest development version of QEMU, built from source. See
+https://www.qemu.org/download/#source for instructions on how to do
+this.

It's likely that those unfamiliar with QEMU, especially non-developers, won't be able to do this:

The wording requires the reader to figure out that "latest development version of QEMU" is none of the big 6.0.0, 5.2.0, etc download links at the top of the page but the small text "The latest development happens on the master branch" sentence below the fold. Then they need to look around the page to find out how to download the master branch and build from source.

I suggest referring directly to the build instructions instead of requiring the reader to make several connections in order to do what we're (indirectly) asking:

Before submitting a bug, please attempt to reproduce the problem with the latest qemu.git master built from source. See the "To download and build QEMU from git" section at https://www.qemu.org/download/#source
for instructions.

#7 lore raw

Re: [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template

Quoted 34 lines · Stefan Hajnoczi
Quoted 15 lines · John Snow

Based loosely on libvirt's template, written by Peter Krempa.

CC Peter Krempa <[email protected]>
---
 .gitlab/issue_templates/bug.md | 63 ++++++++++++++++++++++++++++++++++
 1 file changed, 63 insertions(+)
 create mode 100644 .gitlab/issue_templates/bug.md
.gitlab/issue_templates/bug.md new file +0 -0
new file mode 100644
index 00000000000..9445777252b

.gitlab/issue_templates/bug.md line 7

Quoted 7 lines
.gitlab/issue_templates/bug.md new file +7 -0
@@ -0,0 +1,63 @@
+<!--
+This is the upstream QEMU issue tracker.
+
+Before submitting a bug, please attempt to reproduce your problem using
+the latest development version of QEMU, built from source. See
+https://www.qemu.org/download/#source for instructions on how to do
+this.

It's likely that those unfamiliar with QEMU, especially non-developers, won't be able to do this:

The wording requires the reader to figure out that "latest development version of QEMU" is none of the big 6.0.0, 5.2.0, etc download links at the top of the page but the small text "The latest development happens on the master branch" sentence below the fold. Then they need to look around the page to find out how to download the master branch and build from source.

Quoted 8 lines

I suggest referring directly to the build instructions instead of requiring the reader to make several connections in order to do what we're (indirectly) asking:

Before submitting a bug, please attempt to reproduce the problem with the latest qemu.git master built from source. See the "To download and build QEMU from git" section at https://www.qemu.org/download/#source
for instructions.

I do wonder if this will discourage people from submitting a bug report, if they're unable to actually do this. We have a fairly frequent stream of users who seek help trying to build QEMU - usually they fail to even get the right depedancies installed.

Perhaps word it so it doesn't come across as such a strict sounding requirement ? I'm not entirely happy with the below text, but something more forgiving like:

If you are able to, it will facilitate QEMU bug triage if an attempt is made to reproduce the problem with the latest qemu.git master built from source. ...etc..

Regards,
Daniel

Signature · 3 lines
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
#8 lore raw

Re: [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template

Quoted 49 lines · Daniel P. Berrangé
Quoted 34 lines · Stefan Hajnoczi
Quoted 15 lines · John Snow

Based loosely on libvirt's template, written by Peter Krempa.

CC Peter Krempa <[email protected]>
---
 .gitlab/issue_templates/bug.md | 63 ++++++++++++++++++++++++++++++++++
 1 file changed, 63 insertions(+)
 create mode 100644 .gitlab/issue_templates/bug.md
.gitlab/issue_templates/bug.md new file +0 -0
new file mode 100644
index 00000000000..9445777252b

.gitlab/issue_templates/bug.md line 7

Quoted 7 lines
.gitlab/issue_templates/bug.md new file +7 -0
@@ -0,0 +1,63 @@
+<!--
+This is the upstream QEMU issue tracker.
+
+Before submitting a bug, please attempt to reproduce your problem using
+the latest development version of QEMU, built from source. See
+https://www.qemu.org/download/#source for instructions on how to do
+this.

It's likely that those unfamiliar with QEMU, especially non-developers, won't be able to do this:

The wording requires the reader to figure out that "latest development version of QEMU" is none of the big 6.0.0, 5.2.0, etc download links at the top of the page but the small text "The latest development happens on the master branch" sentence below the fold. Then they need to look around the page to find out how to download the master branch and build from source.

Quoted 8 lines

I suggest referring directly to the build instructions instead of requiring the reader to make several connections in order to do what we're (indirectly) asking:

Before submitting a bug, please attempt to reproduce the problem with the latest qemu.git master built from source. See the "To download and build QEMU from git" section at https://www.qemu.org/download/#source
for instructions.

I do wonder if this will discourage people from submitting a bug report, if they're unable to actually do this. We have a fairly frequent stream of users who seek help trying to build QEMU - usually they fail to even get the right depedancies installed.

Quoted 7 lines

Perhaps word it so it doesn't come across as such a strict sounding requirement ? I'm not entirely happy with the below text, but something more forgiving like:

If you are able to, it will facilitate QEMU bug triage if an attempt is made to reproduce the problem with the latest qemu.git master built from source. ...etc..

Sounds good.

Stefan

author
#9 lore raw

Re: [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template

Quoted 54 lines · Stefan Hajnoczi
Quoted 53 lines · Daniel P. Berrangé
Quoted 34 lines · Stefan Hajnoczi
Quoted 15 lines · John Snow

Based loosely on libvirt's template, written by Peter Krempa.

CC Peter Krempa <[email protected]>
---
  .gitlab/issue_templates/bug.md | 63 ++++++++++++++++++++++++++++++++++
  1 file changed, 63 insertions(+)

create mode 100644 .gitlab/issue_templates/bug.md

.gitlab/issue_templates/bug.md new file +0 -0
new file mode 100644
index 00000000000..9445777252b

.gitlab/issue_templates/bug.md line 7

Quoted 7 lines
.gitlab/issue_templates/bug.md new file +7 -0
@@ -0,0 +1,63 @@
+<!--
+This is the upstream QEMU issue tracker.
+
+Before submitting a bug, please attempt to reproduce your problem using
+the latest development version of QEMU, built from source. See
+https://www.qemu.org/download/#source for instructions on how to do
+this.

It's likely that those unfamiliar with QEMU, especially non-developers, won't be able to do this:

The wording requires the reader to figure out that "latest development version of QEMU" is none of the big 6.0.0, 5.2.0, etc download links at the top of the page but the small text "The latest development happens on the master branch" sentence below the fold. Then they need to look around the page to find out how to download the master branch and build from source.

Quoted 8 lines

I suggest referring directly to the build instructions instead of requiring the reader to make several connections in order to do what we're (indirectly) asking:

Before submitting a bug, please attempt to reproduce the problem with the latest qemu.git master built from source. See the "To download and build QEMU from git" section at https://www.qemu.org/download/#source
for instructions.

I do wonder if this will discourage people from submitting a bug report, if they're unable to actually do this. We have a fairly frequent stream of users who seek help trying to build QEMU - usually they fail to even get the right depedancies installed.

Perhaps word it so it doesn't come across as such a strict sounding requirement ? I'm not entirely happy with the below text, but something more forgiving like:

Quoted 8 lines
Quoted 3 lines

If you are able to, it will facilitate QEMU bug triage if an attempt is made to reproduce the problem with the latest qemu.git master built from source. ...etc..

Sounds good.

Stefan

I agree, thank you for this suggestion. I will work this in.

--js

author
#10 lore raw

Re: [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template

In reply to Daniel P. Berrangé
Quoted 53 lines · Daniel P. Berrangé
Quoted 34 lines · Stefan Hajnoczi
Quoted 15 lines · John Snow

Based loosely on libvirt's template, written by Peter Krempa.

CC Peter Krempa <[email protected]>
---
  .gitlab/issue_templates/bug.md | 63 ++++++++++++++++++++++++++++++++++
  1 file changed, 63 insertions(+)

create mode 100644 .gitlab/issue_templates/bug.md

.gitlab/issue_templates/bug.md new file +0 -0
new file mode 100644
index 00000000000..9445777252b

.gitlab/issue_templates/bug.md line 7

Quoted 7 lines
.gitlab/issue_templates/bug.md new file +7 -0
@@ -0,0 +1,63 @@
+<!--
+This is the upstream QEMU issue tracker.
+
+Before submitting a bug, please attempt to reproduce your problem using
+the latest development version of QEMU, built from source. See
+https://www.qemu.org/download/#source for instructions on how to do
+this.

It's likely that those unfamiliar with QEMU, especially non-developers, won't be able to do this:

The wording requires the reader to figure out that "latest development version of QEMU" is none of the big 6.0.0, 5.2.0, etc download links at the top of the page but the small text "The latest development happens on the master branch" sentence below the fold. Then they need to look around the page to find out how to download the master branch and build from source.

Quoted 8 lines

I suggest referring directly to the build instructions instead of requiring the reader to make several connections in order to do what we're (indirectly) asking:

Before submitting a bug, please attempt to reproduce the problem with the latest qemu.git master built from source. See the "To download and build QEMU from git" section at https://www.qemu.org/download/#source
for instructions.

I do wonder if this will discourage people from submitting a bug report, if they're unable to actually do this. We have a fairly frequent stream of users who seek help trying to build QEMU - usually they fail to even get the right depedancies installed.

Perhaps word it so it doesn't come across as such a strict sounding requirement ? I'm not entirely happy with the below text, but something more forgiving like:

Quoted 7 lines

If you are able to, it will facilitate QEMU bug triage if an attempt is made to reproduce the problem with the latest qemu.git master built from source. ...etc..

Regards,
Daniel

How about:

If you are able to, it will greatly facilitate bug triage if you attempt to reproduce the problem with the latest qemu.git master built from source. See https://www.qemu.org/download/#source for instructions on how to do this.

QEMU generally supports the last two releases advertised on
https://www.qemu.org/. Problems with distro-packaged versions of QEMU older than this should be reported to the distribution instead.

- I put an emphasis on facilitate (It's in YOUR interest to do this.)
- I rephrased "if an attempt is made to" to "if you attempt to", a less passive (and shorter) sentence.

#11 lore raw

Re: [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template

Quoted 70 lines · John Snow
Quoted 53 lines · Daniel P. Berrangé
Quoted 34 lines · Stefan Hajnoczi
Quoted 15 lines · John Snow

Based loosely on libvirt's template, written by Peter Krempa.

CC Peter Krempa <[email protected]>
---
  .gitlab/issue_templates/bug.md | 63 ++++++++++++++++++++++++++++++++++
  1 file changed, 63 insertions(+)

create mode 100644 .gitlab/issue_templates/bug.md

.gitlab/issue_templates/bug.md new file +0 -0
new file mode 100644
index 00000000000..9445777252b

.gitlab/issue_templates/bug.md line 7

Quoted 7 lines
.gitlab/issue_templates/bug.md new file +7 -0
@@ -0,0 +1,63 @@
+<!--
+This is the upstream QEMU issue tracker.
+
+Before submitting a bug, please attempt to reproduce your problem using
+the latest development version of QEMU, built from source. See
+https://www.qemu.org/download/#source for instructions on how to do
+this.

It's likely that those unfamiliar with QEMU, especially non-developers, won't be able to do this:

The wording requires the reader to figure out that "latest development version of QEMU" is none of the big 6.0.0, 5.2.0, etc download links at the top of the page but the small text "The latest development happens on the master branch" sentence below the fold. Then they need to look around the page to find out how to download the master branch and build from source.

Quoted 8 lines

I suggest referring directly to the build instructions instead of requiring the reader to make several connections in order to do what we're (indirectly) asking:

Before submitting a bug, please attempt to reproduce the problem with the latest qemu.git master built from source. See the "To download and build QEMU from git" section at https://www.qemu.org/download/#source
for instructions.

I do wonder if this will discourage people from submitting a bug report, if they're unable to actually do this. We have a fairly frequent stream of users who seek help trying to build QEMU - usually they fail to even get the right depedancies installed.

Perhaps word it so it doesn't come across as such a strict sounding requirement ? I'm not entirely happy with the below text, but something more forgiving like:

Quoted 7 lines

If you are able to, it will facilitate QEMU bug triage if an attempt is made to reproduce the problem with the latest qemu.git master built from source. ...etc..

Regards,
Daniel

How about:

If you are able to, it will greatly facilitate bug triage if you attempt to reproduce the problem with the latest qemu.git master built from source. See https://www.qemu.org/download/#source for instructions on how to do this.

Quoted 8 lines

QEMU generally supports the last two releases advertised on
https://www.qemu.org/. Problems with distro-packaged versions of QEMU older than this should be reported to the distribution instead.

- I put an emphasis on facilitate (It's in YOUR interest to do this.)
- I rephrased "if an attempt is made to" to "if you attempt to", a less passive (and shorter) sentence.

Fine with me

Regards,
Daniel

Signature · 3 lines
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
author
#12 lore raw

PATCH v3 2/2 GitLab: Add "Feature Request" issue template.

In reply to John Snow

Based on Peter Krempa's libvirt template, feature.md.

---
 .gitlab/issue_templates/feature_request.md | 32 ++++++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 .gitlab/issue_templates/feature_request.md
.gitlab/issue_templates/feature_request.md new file +32 -0
new file mode 100644
index 00000000000..fc58ca27634
@@ -0,0 +1,32 @@
+<!--
+This is the upstream QEMU issue tracker.
+
+Please note that QEMU, like most open source projects, relies on
+contributors who have motivation, skills and available time to work on
+implementing particular features.
+
+Feature requests can be helpful for determining demand and interest, but
+they are not a guarantee that a contributor will volunteer to implement
+it. We welcome and encourage even draft patches to implement a feature
+be sent to the mailing list where it can be discussed and developed
+further by the community.
+
+Thank you for your interest in helping us to make QEMU better!
+-->
+
+## Goal
+<!-- Describe the final result you want to achieve. Avoid design specifics. -->
+
+
+## Technical details
+<!-- Describe technical details, design specifics, suggestions, versions, etc. -->
+
+
+## Additional information
+
+
+<!--
+The line below ensures that proper tags are added to the issue.
+Please do not remove it.
+-->
+/label ~"kind::Feature Request"
Signature · 1 line
2.31.1
Reviewed-by on v3 2/2
#13 lore raw

Re: [PATCH v3 2/2] GitLab: Add "Feature Request" issue template.

Quoted 9 lines · John Snow

Based on Peter Krempa's libvirt template, feature.md.

---
  .gitlab/issue_templates/feature_request.md | 32 ++++++++++++++++++++++
  1 file changed, 32 insertions(+)

create mode 100644 .gitlab/issue_templates/feature_request.md