Github messages for voidlinux
 help / color / mirror / Atom feed
* [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
@ 2022-03-30  5:34 classabbyamp
  2022-03-30  8:37 ` [PR REVIEW] " paper42
                   ` (51 more replies)
  0 siblings, 52 replies; 53+ messages in thread
From: classabbyamp @ 2022-03-30  5:34 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]

There is a new pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here for the bug report](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/bug-report.yml) and [here for the package request](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/pkg-request.yml)

[ci skip]

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 7290 bytes --]

From fd6d8f8a16c113daec2fb33d825ed00b9c5b03f4 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@kb6.ee>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 70 ++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  1 +
 .github/ISSUE_TEMPLATE/pkg-request.yml | 67 ++++++++++++++++++++++++
 .github/issue_template.md              | 14 ------
 4 files changed, 138 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..8870ae1cfe71
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,70 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        ### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Bug description
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: checkboxes
+    attributes:
+      label: Is this a new report?
+      options:
+        - label: I verified that there isn't already an open issue for this bug
+          required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..0086358db1eb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1 @@
+blank_issues_enabled: true
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..04b0eabd95e7
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,67 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        ### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+  - type: markdown
+    attributes:
+      value: >
+        ## Quality Requirements
+
+        To be included in the Void repository, software must meet **at least one** of the following requirements.
+        Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
+        If you believe you have an exception, start a PR and make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for the Void packages system.
+
+
+        In particular, new themes are highly unlikely to be accepted.
+        Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base.
+        New fonts may be accepted if they provide value beyond aesthetics
+        (e.g. they contain glyphs for a script missing in already packaged fonts).
+
+
+        Browser forks, including those based on Chromium and Firefox, are generally not accepted.
+        Such forks require heavy patching, maintenance and hours of build time.
+  - id: quality
+    type: checkboxes
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      options:
+        - label: "System: The software should be installed system-wide, not per-user"
+          required: false
+        - label: "Compiled: The software needs to be compiled before being used, even if it is software that is not needed by the whole system"
+          required: false
+        - label: "Required: Another package either within the repository or pending inclusion requires the package"
+          required: false
+  - type: markdown
+    attributes:
+      value: >
+        ## Release Status
+
+        Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
+        Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
+  - id: released
+    type: checkboxes
+    attributes:
+      label: Is the requested package released?
+      options:
+      - label: "Released: The software is available in a version announced by authors as ready-to-use by the general public"
+        required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
@ 2022-03-30  8:37 ` paper42
  2022-03-30  8:37 ` paper42
                   ` (50 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: paper42 @ 2022-03-30  8:37 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 205 bytes --]

New review comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r838263227

Comment:
this is an issue template, so "start a PR" is not relevant

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
  2022-03-30  8:37 ` [PR REVIEW] " paper42
@ 2022-03-30  8:37 ` paper42
  2022-03-30  8:40 ` paper42
                   ` (49 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: paper42 @ 2022-03-30  8:37 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 356 bytes --]

New review comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r838266819

Comment:
```suggestion
        while not meeting any of the following requirements, is a good candidate for inclusion in Void packages.
```
This sounds better to me, but I am not a native speaker, what do you think?

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
  2022-03-30  8:37 ` [PR REVIEW] " paper42
  2022-03-30  8:37 ` paper42
@ 2022-03-30  8:40 ` paper42
  2022-03-30 16:56 ` classabbyamp
                   ` (48 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: paper42 @ 2022-03-30  8:40 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 310 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1082793069

Comment:
I don't like that we have a lot of static text in the request issue template. The whole "Quality Requirements" section could be replaced with a link to Contributing.md.

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (2 preceding siblings ...)
  2022-03-30  8:40 ` paper42
@ 2022-03-30 16:56 ` classabbyamp
  2022-03-30 18:14 ` Chocimier
                   ` (47 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-03-30 16:56 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1083386755

Comment:
> I think it would be nice to have a checkbox for electron applications that would add the electron tag and maybe an option (and a new tag) for proprietary software.

Those could definitely be included as checkboxes, but it's beyond the scope of issue forms to dynamically add tags like that. The new [issue automation](https://docs.github.com/en/issues/trying-out-the-new-projects-experience/automating-projects) can probably do such a thing, but that would require a much larger change (migrating to the new issues/projects entirely). Using a bot that looks for the checkbox/text is another option, which could fit in well with the bot @0x5c has been hacking at that tries to autotag PRs based on changeset contents etc.

> I don't like that we have a lot of static text in the request issue template. The whole "Quality Requirements" section could be replaced with a link to Contributing.md.

Should've been a bit more clear there, the explanatory text does not get included in the final issue, it's just for the person filling out the form to read while the form is being filled.

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (3 preceding siblings ...)
  2022-03-30 16:56 ` classabbyamp
@ 2022-03-30 18:14 ` Chocimier
  2022-03-30 23:39 ` [PR REVIEW] " 0x5c
                   ` (46 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: Chocimier @ 2022-03-30 18:14 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 791 bytes --]

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1083459636

Comment:
Demoed at https://github.com/Chocimier/void-packages-org/issues, anybody feel free to play with.

We could use it, with some remarks: 
- free-form issue is too hard to find, consider making it a third template
- checkboxes re-introduce _tasks_ we have just got rid of
- mandatory checkboxes are dumb on their own anyway
- in bug report: there is no need for _update of package_ section
- in bug report: system info should not be mandatory, sometimes it's obvious it doesn't matter
- in bug report: _Bug description_ section should keep it's current name, _Actual behavior_
- in package request: there should be a field to provide homepage

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (4 preceding siblings ...)
  2022-03-30 18:14 ` Chocimier
@ 2022-03-30 23:39 ` 0x5c
  2022-03-31  0:38 ` 0x5c
                   ` (45 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: 0x5c @ 2022-03-30 23:39 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 179 bytes --]

New review comment by 0x5c on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r839050245

Comment:
Your suggestion sounds better to me

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (5 preceding siblings ...)
  2022-03-30 23:39 ` [PR REVIEW] " 0x5c
@ 2022-03-31  0:38 ` 0x5c
  2022-03-31  1:29 ` 0x5c
                   ` (44 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: 0x5c @ 2022-03-31  0:38 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 450 bytes --]

New comment by 0x5c on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1083866344

Comment:
> I think it would be nice to have a checkbox for electron applications that would add the electron tag and maybe an option (and a new tag) for proprietary software.

As Abby said, that's not directly possible. However, using a bot that looks for a specific variant of a magic string seems prone to breakage. 

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (6 preceding siblings ...)
  2022-03-31  0:38 ` 0x5c
@ 2022-03-31  1:29 ` 0x5c
  2022-04-01 17:49 ` [PR PATCH] [Updated] " classabbyamp
                   ` (43 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: 0x5c @ 2022-03-31  1:29 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

New comment by 0x5c on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1083942933

Comment:
> * checkboxes re-introduce _tasks_ we have just got rid of

This is behaviour we did not expect, as it was different at some point in the past (simply using text instead of markdown checkboxes). We'll do some tests to see what can be done about that, y/n dropdowns are likely to do the trick

> * mandatory checkboxes are dumb on their own anyway

The goal is to limit what can be requested (only released software, which is void's policy on new packages) and limit duplicates reports (which are extra work and are likely to create obsolete reports)

> * in bug report: there is no need for _update of package_ section

You're likely to have someone who considers old, but otherwise functioning, versions of packages to be "bugs". That text can be removed but it's not gonna be a meaningful change since it's not rendered in the final issue anyways.

> * in bug report: system info should not be mandatory, sometimes it's obvious it doesn't matter

I wonder if it's more obvious to maintainers than to bug reporters, and I suspect that without it being provided, the case it's needed would only be discovered beyond the point the reporter has gone AWOL

> * in bug report: _Bug description_ section should keep it's current name, _Actual behavior_
> * in package request: there should be a field to provide homepage

Consider those fixed

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (7 preceding siblings ...)
  2022-03-31  1:29 ` 0x5c
@ 2022-04-01 17:49 ` classabbyamp
  2022-04-01 17:52 ` classabbyamp
                   ` (42 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-01 17:49 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here for the bug report](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/bug-report.yml) and [here for the package request](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/pkg-request.yml)

[ci skip]

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 12678 bytes --]

From fd6d8f8a16c113daec2fb33d825ed00b9c5b03f4 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@kb6.ee>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH 1/2] .github/ISSUE_TEMPLATE: add bug report and package
 request issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 70 ++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  1 +
 .github/ISSUE_TEMPLATE/pkg-request.yml | 67 ++++++++++++++++++++++++
 .github/issue_template.md              | 14 ------
 4 files changed, 138 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..8870ae1cfe71
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,70 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        ### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Bug description
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: checkboxes
+    attributes:
+      label: Is this a new report?
+      options:
+        - label: I verified that there isn't already an open issue for this bug
+          required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..0086358db1eb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1 @@
+blank_issues_enabled: true
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..04b0eabd95e7
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,67 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        ### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+  - type: markdown
+    attributes:
+      value: >
+        ## Quality Requirements
+
+        To be included in the Void repository, software must meet **at least one** of the following requirements.
+        Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
+        If you believe you have an exception, start a PR and make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for the Void packages system.
+
+
+        In particular, new themes are highly unlikely to be accepted.
+        Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base.
+        New fonts may be accepted if they provide value beyond aesthetics
+        (e.g. they contain glyphs for a script missing in already packaged fonts).
+
+
+        Browser forks, including those based on Chromium and Firefox, are generally not accepted.
+        Such forks require heavy patching, maintenance and hours of build time.
+  - id: quality
+    type: checkboxes
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      options:
+        - label: "System: The software should be installed system-wide, not per-user"
+          required: false
+        - label: "Compiled: The software needs to be compiled before being used, even if it is software that is not needed by the whole system"
+          required: false
+        - label: "Required: Another package either within the repository or pending inclusion requires the package"
+          required: false
+  - type: markdown
+    attributes:
+      value: >
+        ## Release Status
+
+        Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
+        Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
+  - id: released
+    type: checkboxes
+    attributes:
+      label: Is the requested package released?
+      options:
+      - label: "Released: The software is available in a version announced by authors as ready-to-use by the general public"
+        required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

From 6b63116bacba45f724a933d3b542161812235314 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@kb6.ee>
Date: Fri, 1 Apr 2022 13:49:33 -0400
Subject: [PATCH 2/2] update templates [TEMP]

---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 11 ++++---
 .github/ISSUE_TEMPLATE/pkg-request.yml | 40 +++++++++++++++++++-------
 2 files changed, 36 insertions(+), 15 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
index 8870ae1cfe71..d3bd546ab414 100644
--- a/.github/ISSUE_TEMPLATE/bug-report.yml
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -5,7 +5,7 @@ body:
   - type: markdown
     attributes:
       value: >
-        ### Don't request an update of a package,
+        #### Don't request an update of a package,
         [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
         However, a quality pull request may help.
   - id: xuname
@@ -44,7 +44,7 @@ body:
   - id: description
     type: textarea
     attributes:
-      label: Bug description
+      label: Actual behaviour
       description: A clear and concise description of what the bug is
       placeholder: There was a crash when...
     validations:
@@ -65,6 +65,9 @@ body:
     type: checkboxes
     attributes:
       label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
       options:
-        - label: I verified that there isn't already an open issue for this bug
-          required: true
+        - Yes
+        - No
+      validations:
+        required: true
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
index 04b0eabd95e7..07d37e9ebaad 100644
--- a/.github/ISSUE_TEMPLATE/pkg-request.yml
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -5,7 +5,7 @@ body:
   - type: markdown
     attributes:
       value: >
-        ### Don't request an update of a package,
+        #### Don't request an update of a package,
         [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
         However, a quality pull request may help.
   - id: name
@@ -13,6 +13,15 @@ body:
     attributes:
       label: Package name
       placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
   - id: description
     type: textarea
     attributes:
@@ -21,6 +30,8 @@ body:
       placeholder: >
         Foobar9k is a music player that turns your music up to 11.
         It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
   - type: markdown
     attributes:
       value: >
@@ -28,8 +39,8 @@ body:
 
         To be included in the Void repository, software must meet **at least one** of the following requirements.
         Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
-        If you believe you have an exception, start a PR and make an argument for why that particular piece of software,
-        while not meeting any of the following requirements, is a good candidate for the Void packages system.
+        If you believe you have an exception, make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for inclusion in void-packages.
 
 
         In particular, new themes are highly unlikely to be accepted.
@@ -44,13 +55,17 @@ body:
     type: checkboxes
     attributes:
       label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+      multiple: true
       options:
-        - label: "System: The software should be installed system-wide, not per-user"
-          required: false
-        - label: "Compiled: The software needs to be compiled before being used, even if it is software that is not needed by the whole system"
-          required: false
-        - label: "Required: Another package either within the repository or pending inclusion requires the package"
-          required: false
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
   - type: markdown
     attributes:
       value: >
@@ -59,9 +74,12 @@ body:
         Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
         Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
   - id: released
-    type: checkboxes
+    type: dropdown
     attributes:
       label: Is the requested package released?
+      description: "The software is available in a version announced by authors as ready-to-use by the general public"
       options:
-      - label: "Released: The software is available in a version announced by authors as ready-to-use by the general public"
+        - Yes
+        - No
+      validations:
         required: true

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (8 preceding siblings ...)
  2022-04-01 17:49 ` [PR PATCH] [Updated] " classabbyamp
@ 2022-04-01 17:52 ` classabbyamp
  2022-04-01 17:53 ` classabbyamp
                   ` (41 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-01 17:52 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here for the bug report](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/bug-report.yml) and [here for the package request](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/pkg-request.yml)

[ci skip]

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 12979 bytes --]

From fd6d8f8a16c113daec2fb33d825ed00b9c5b03f4 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@kb6.ee>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH 1/2] .github/ISSUE_TEMPLATE: add bug report and package
 request issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 70 ++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  1 +
 .github/ISSUE_TEMPLATE/pkg-request.yml | 67 ++++++++++++++++++++++++
 .github/issue_template.md              | 14 ------
 4 files changed, 138 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..8870ae1cfe71
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,70 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        ### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Bug description
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: checkboxes
+    attributes:
+      label: Is this a new report?
+      options:
+        - label: I verified that there isn't already an open issue for this bug
+          required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..0086358db1eb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1 @@
+blank_issues_enabled: true
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..04b0eabd95e7
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,67 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        ### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+  - type: markdown
+    attributes:
+      value: >
+        ## Quality Requirements
+
+        To be included in the Void repository, software must meet **at least one** of the following requirements.
+        Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
+        If you believe you have an exception, start a PR and make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for the Void packages system.
+
+
+        In particular, new themes are highly unlikely to be accepted.
+        Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base.
+        New fonts may be accepted if they provide value beyond aesthetics
+        (e.g. they contain glyphs for a script missing in already packaged fonts).
+
+
+        Browser forks, including those based on Chromium and Firefox, are generally not accepted.
+        Such forks require heavy patching, maintenance and hours of build time.
+  - id: quality
+    type: checkboxes
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      options:
+        - label: "System: The software should be installed system-wide, not per-user"
+          required: false
+        - label: "Compiled: The software needs to be compiled before being used, even if it is software that is not needed by the whole system"
+          required: false
+        - label: "Required: Another package either within the repository or pending inclusion requires the package"
+          required: false
+  - type: markdown
+    attributes:
+      value: >
+        ## Release Status
+
+        Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
+        Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
+  - id: released
+    type: checkboxes
+    attributes:
+      label: Is the requested package released?
+      options:
+      - label: "Released: The software is available in a version announced by authors as ready-to-use by the general public"
+        required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

From d79bf2a3b102644fdf0c1f063e374624e4dfc3fc Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@kb6.ee>
Date: Fri, 1 Apr 2022 13:49:33 -0400
Subject: [PATCH 2/2] update templates [TEMP]

---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 13 +++++---
 .github/ISSUE_TEMPLATE/pkg-request.yml | 42 ++++++++++++++++++--------
 2 files changed, 38 insertions(+), 17 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
index 8870ae1cfe71..f419bc8e3b2d 100644
--- a/.github/ISSUE_TEMPLATE/bug-report.yml
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -5,7 +5,7 @@ body:
   - type: markdown
     attributes:
       value: >
-        ### Don't request an update of a package,
+        #### Don't request an update of a package,
         [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
         However, a quality pull request may help.
   - id: xuname
@@ -44,7 +44,7 @@ body:
   - id: description
     type: textarea
     attributes:
-      label: Bug description
+      label: Actual behaviour
       description: A clear and concise description of what the bug is
       placeholder: There was a crash when...
     validations:
@@ -62,9 +62,12 @@ body:
     validations:
       required: true
   - id: verified
-    type: checkboxes
+    type: dropdown
     attributes:
       label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
       options:
-        - label: I verified that there isn't already an open issue for this bug
-          required: true
+        - Yes
+        - No
+      validations:
+        required: true
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
index 04b0eabd95e7..80d16d15a0d2 100644
--- a/.github/ISSUE_TEMPLATE/pkg-request.yml
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -5,7 +5,7 @@ body:
   - type: markdown
     attributes:
       value: >
-        ### Don't request an update of a package,
+        #### Don't request an update of a package,
         [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
         However, a quality pull request may help.
   - id: name
@@ -13,6 +13,15 @@ body:
     attributes:
       label: Package name
       placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
   - id: description
     type: textarea
     attributes:
@@ -21,6 +30,8 @@ body:
       placeholder: >
         Foobar9k is a music player that turns your music up to 11.
         It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
   - type: markdown
     attributes:
       value: >
@@ -28,8 +39,8 @@ body:
 
         To be included in the Void repository, software must meet **at least one** of the following requirements.
         Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
-        If you believe you have an exception, start a PR and make an argument for why that particular piece of software,
-        while not meeting any of the following requirements, is a good candidate for the Void packages system.
+        If you believe you have an exception, make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for inclusion in void-packages.
 
 
         In particular, new themes are highly unlikely to be accepted.
@@ -41,16 +52,20 @@ body:
         Browser forks, including those based on Chromium and Firefox, are generally not accepted.
         Such forks require heavy patching, maintenance and hours of build time.
   - id: quality
-    type: checkboxes
+    type: dropdown
     attributes:
       label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+      multiple: true
       options:
-        - label: "System: The software should be installed system-wide, not per-user"
-          required: false
-        - label: "Compiled: The software needs to be compiled before being used, even if it is software that is not needed by the whole system"
-          required: false
-        - label: "Required: Another package either within the repository or pending inclusion requires the package"
-          required: false
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
   - type: markdown
     attributes:
       value: >
@@ -59,9 +74,12 @@ body:
         Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
         Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
   - id: released
-    type: checkboxes
+    type: dropdown
     attributes:
       label: Is the requested package released?
+      description: "The software is available in a version announced by authors as ready-to-use by the general public"
       options:
-      - label: "Released: The software is available in a version announced by authors as ready-to-use by the general public"
+        - "Yes"
+        - "No"
+      validations:
         required: true

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (9 preceding siblings ...)
  2022-04-01 17:52 ` classabbyamp
@ 2022-04-01 17:53 ` classabbyamp
  2022-04-01 17:54 ` classabbyamp
                   ` (40 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-01 17:53 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here for the bug report](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/bug-report.yml) and [here for the package request](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/pkg-request.yml)

[ci skip]

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 12995 bytes --]

From fd6d8f8a16c113daec2fb33d825ed00b9c5b03f4 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@kb6.ee>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH 1/2] .github/ISSUE_TEMPLATE: add bug report and package
 request issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 70 ++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  1 +
 .github/ISSUE_TEMPLATE/pkg-request.yml | 67 ++++++++++++++++++++++++
 .github/issue_template.md              | 14 ------
 4 files changed, 138 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..8870ae1cfe71
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,70 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        ### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Bug description
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: checkboxes
+    attributes:
+      label: Is this a new report?
+      options:
+        - label: I verified that there isn't already an open issue for this bug
+          required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..0086358db1eb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1 @@
+blank_issues_enabled: true
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..04b0eabd95e7
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,67 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        ### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+  - type: markdown
+    attributes:
+      value: >
+        ## Quality Requirements
+
+        To be included in the Void repository, software must meet **at least one** of the following requirements.
+        Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
+        If you believe you have an exception, start a PR and make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for the Void packages system.
+
+
+        In particular, new themes are highly unlikely to be accepted.
+        Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base.
+        New fonts may be accepted if they provide value beyond aesthetics
+        (e.g. they contain glyphs for a script missing in already packaged fonts).
+
+
+        Browser forks, including those based on Chromium and Firefox, are generally not accepted.
+        Such forks require heavy patching, maintenance and hours of build time.
+  - id: quality
+    type: checkboxes
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      options:
+        - label: "System: The software should be installed system-wide, not per-user"
+          required: false
+        - label: "Compiled: The software needs to be compiled before being used, even if it is software that is not needed by the whole system"
+          required: false
+        - label: "Required: Another package either within the repository or pending inclusion requires the package"
+          required: false
+  - type: markdown
+    attributes:
+      value: >
+        ## Release Status
+
+        Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
+        Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
+  - id: released
+    type: checkboxes
+    attributes:
+      label: Is the requested package released?
+      options:
+      - label: "Released: The software is available in a version announced by authors as ready-to-use by the general public"
+        required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

From d8594f6b05b850cfaf421e659ee6afb393c1aeb7 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@kb6.ee>
Date: Fri, 1 Apr 2022 13:49:33 -0400
Subject: [PATCH 2/2] update templates [TEMP]

---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 13 +++++---
 .github/ISSUE_TEMPLATE/pkg-request.yml | 44 ++++++++++++++++++--------
 2 files changed, 39 insertions(+), 18 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
index 8870ae1cfe71..1253ea301cbc 100644
--- a/.github/ISSUE_TEMPLATE/bug-report.yml
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -5,7 +5,7 @@ body:
   - type: markdown
     attributes:
       value: >
-        ### Don't request an update of a package,
+        #### Don't request an update of a package,
         [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
         However, a quality pull request may help.
   - id: xuname
@@ -44,7 +44,7 @@ body:
   - id: description
     type: textarea
     attributes:
-      label: Bug description
+      label: Actual behaviour
       description: A clear and concise description of what the bug is
       placeholder: There was a crash when...
     validations:
@@ -62,9 +62,12 @@ body:
     validations:
       required: true
   - id: verified
-    type: checkboxes
+    type: dropdown
     attributes:
       label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
       options:
-        - label: I verified that there isn't already an open issue for this bug
-          required: true
+        - Yes
+        - No
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
index 04b0eabd95e7..9b16ae4a93fe 100644
--- a/.github/ISSUE_TEMPLATE/pkg-request.yml
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -5,7 +5,7 @@ body:
   - type: markdown
     attributes:
       value: >
-        ### Don't request an update of a package,
+        #### Don't request an update of a package,
         [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
         However, a quality pull request may help.
   - id: name
@@ -13,6 +13,15 @@ body:
     attributes:
       label: Package name
       placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
   - id: description
     type: textarea
     attributes:
@@ -21,6 +30,8 @@ body:
       placeholder: >
         Foobar9k is a music player that turns your music up to 11.
         It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
   - type: markdown
     attributes:
       value: >
@@ -28,8 +39,8 @@ body:
 
         To be included in the Void repository, software must meet **at least one** of the following requirements.
         Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
-        If you believe you have an exception, start a PR and make an argument for why that particular piece of software,
-        while not meeting any of the following requirements, is a good candidate for the Void packages system.
+        If you believe you have an exception, make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for inclusion in void-packages.
 
 
         In particular, new themes are highly unlikely to be accepted.
@@ -41,16 +52,20 @@ body:
         Browser forks, including those based on Chromium and Firefox, are generally not accepted.
         Such forks require heavy patching, maintenance and hours of build time.
   - id: quality
-    type: checkboxes
+    type: dropdown
     attributes:
       label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+      multiple: true
       options:
-        - label: "System: The software should be installed system-wide, not per-user"
-          required: false
-        - label: "Compiled: The software needs to be compiled before being used, even if it is software that is not needed by the whole system"
-          required: false
-        - label: "Required: Another package either within the repository or pending inclusion requires the package"
-          required: false
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
   - type: markdown
     attributes:
       value: >
@@ -59,9 +74,12 @@ body:
         Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
         Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
   - id: released
-    type: checkboxes
+    type: dropdown
     attributes:
       label: Is the requested package released?
+      description: "The software is available in a version announced by authors as ready-to-use by the general public"
       options:
-      - label: "Released: The software is available in a version announced by authors as ready-to-use by the general public"
-        required: true
+        - "Yes"
+        - "No"
+    validations:
+      required: true

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (10 preceding siblings ...)
  2022-04-01 17:53 ` classabbyamp
@ 2022-04-01 17:54 ` classabbyamp
  2022-04-01 17:55 ` classabbyamp
                   ` (39 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-01 17:54 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here for the bug report](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/bug-report.yml) and [here for the package request](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/pkg-request.yml)

[ci skip]

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 12999 bytes --]

From fd6d8f8a16c113daec2fb33d825ed00b9c5b03f4 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@kb6.ee>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH 1/2] .github/ISSUE_TEMPLATE: add bug report and package
 request issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 70 ++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  1 +
 .github/ISSUE_TEMPLATE/pkg-request.yml | 67 ++++++++++++++++++++++++
 .github/issue_template.md              | 14 ------
 4 files changed, 138 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..8870ae1cfe71
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,70 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        ### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Bug description
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: checkboxes
+    attributes:
+      label: Is this a new report?
+      options:
+        - label: I verified that there isn't already an open issue for this bug
+          required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..0086358db1eb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1 @@
+blank_issues_enabled: true
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..04b0eabd95e7
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,67 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        ### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+  - type: markdown
+    attributes:
+      value: >
+        ## Quality Requirements
+
+        To be included in the Void repository, software must meet **at least one** of the following requirements.
+        Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
+        If you believe you have an exception, start a PR and make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for the Void packages system.
+
+
+        In particular, new themes are highly unlikely to be accepted.
+        Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base.
+        New fonts may be accepted if they provide value beyond aesthetics
+        (e.g. they contain glyphs for a script missing in already packaged fonts).
+
+
+        Browser forks, including those based on Chromium and Firefox, are generally not accepted.
+        Such forks require heavy patching, maintenance and hours of build time.
+  - id: quality
+    type: checkboxes
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      options:
+        - label: "System: The software should be installed system-wide, not per-user"
+          required: false
+        - label: "Compiled: The software needs to be compiled before being used, even if it is software that is not needed by the whole system"
+          required: false
+        - label: "Required: Another package either within the repository or pending inclusion requires the package"
+          required: false
+  - type: markdown
+    attributes:
+      value: >
+        ## Release Status
+
+        Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
+        Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
+  - id: released
+    type: checkboxes
+    attributes:
+      label: Is the requested package released?
+      options:
+      - label: "Released: The software is available in a version announced by authors as ready-to-use by the general public"
+        required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

From b0cba30abebed66b3f6a8b3015fc9af0559e5be5 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@kb6.ee>
Date: Fri, 1 Apr 2022 13:49:33 -0400
Subject: [PATCH 2/2] update templates [TEMP]

---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 13 +++++---
 .github/ISSUE_TEMPLATE/pkg-request.yml | 44 ++++++++++++++++++--------
 2 files changed, 39 insertions(+), 18 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
index 8870ae1cfe71..d9914f4d02dc 100644
--- a/.github/ISSUE_TEMPLATE/bug-report.yml
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -5,7 +5,7 @@ body:
   - type: markdown
     attributes:
       value: >
-        ### Don't request an update of a package,
+        #### Don't request an update of a package,
         [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
         However, a quality pull request may help.
   - id: xuname
@@ -44,7 +44,7 @@ body:
   - id: description
     type: textarea
     attributes:
-      label: Bug description
+      label: Actual behaviour
       description: A clear and concise description of what the bug is
       placeholder: There was a crash when...
     validations:
@@ -62,9 +62,12 @@ body:
     validations:
       required: true
   - id: verified
-    type: checkboxes
+    type: dropdown
     attributes:
       label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
       options:
-        - label: I verified that there isn't already an open issue for this bug
-          required: true
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
index 04b0eabd95e7..9b16ae4a93fe 100644
--- a/.github/ISSUE_TEMPLATE/pkg-request.yml
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -5,7 +5,7 @@ body:
   - type: markdown
     attributes:
       value: >
-        ### Don't request an update of a package,
+        #### Don't request an update of a package,
         [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
         However, a quality pull request may help.
   - id: name
@@ -13,6 +13,15 @@ body:
     attributes:
       label: Package name
       placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
   - id: description
     type: textarea
     attributes:
@@ -21,6 +30,8 @@ body:
       placeholder: >
         Foobar9k is a music player that turns your music up to 11.
         It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
   - type: markdown
     attributes:
       value: >
@@ -28,8 +39,8 @@ body:
 
         To be included in the Void repository, software must meet **at least one** of the following requirements.
         Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
-        If you believe you have an exception, start a PR and make an argument for why that particular piece of software,
-        while not meeting any of the following requirements, is a good candidate for the Void packages system.
+        If you believe you have an exception, make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for inclusion in void-packages.
 
 
         In particular, new themes are highly unlikely to be accepted.
@@ -41,16 +52,20 @@ body:
         Browser forks, including those based on Chromium and Firefox, are generally not accepted.
         Such forks require heavy patching, maintenance and hours of build time.
   - id: quality
-    type: checkboxes
+    type: dropdown
     attributes:
       label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+      multiple: true
       options:
-        - label: "System: The software should be installed system-wide, not per-user"
-          required: false
-        - label: "Compiled: The software needs to be compiled before being used, even if it is software that is not needed by the whole system"
-          required: false
-        - label: "Required: Another package either within the repository or pending inclusion requires the package"
-          required: false
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
   - type: markdown
     attributes:
       value: >
@@ -59,9 +74,12 @@ body:
         Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
         Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
   - id: released
-    type: checkboxes
+    type: dropdown
     attributes:
       label: Is the requested package released?
+      description: "The software is available in a version announced by authors as ready-to-use by the general public"
       options:
-      - label: "Released: The software is available in a version announced by authors as ready-to-use by the general public"
-        required: true
+        - "Yes"
+        - "No"
+    validations:
+      required: true

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (11 preceding siblings ...)
  2022-04-01 17:54 ` classabbyamp
@ 2022-04-01 17:55 ` classabbyamp
  2022-04-01 17:58 ` classabbyamp
                   ` (38 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-01 17:55 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here for the bug report](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/bug-report.yml) and [here for the package request](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/pkg-request.yml)

[ci skip]

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 7647 bytes --]

From 2a9c0b515b78ae8deac94c6724d91edc42c25ea2 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@kb6.ee>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  1 +
 .github/ISSUE_TEMPLATE/pkg-request.yml | 85 ++++++++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 159 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..d9914f4d02dc
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..0086358db1eb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1 @@
+blank_issues_enabled: true
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..9b16ae4a93fe
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,85 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Quality Requirements
+
+        To be included in the Void repository, software must meet **at least one** of the following requirements.
+        Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
+        If you believe you have an exception, make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for inclusion in void-packages.
+
+
+        In particular, new themes are highly unlikely to be accepted.
+        Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base.
+        New fonts may be accepted if they provide value beyond aesthetics
+        (e.g. they contain glyphs for a script missing in already packaged fonts).
+
+
+        Browser forks, including those based on Chromium and Firefox, are generally not accepted.
+        Such forks require heavy patching, maintenance and hours of build time.
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Release Status
+
+        Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
+        Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: "The software is available in a version announced by authors as ready-to-use by the general public"
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (12 preceding siblings ...)
  2022-04-01 17:55 ` classabbyamp
@ 2022-04-01 17:58 ` classabbyamp
  2022-04-02 21:39 ` [PR PATCH] [Updated] " classabbyamp
                   ` (37 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-01 17:58 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 331 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1086185045

Comment:
Updated to address most of the issues raised, I think. @Chocimier if you want to update your live version, go ahead. The links in the original comment should still work for previewing.

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (13 preceding siblings ...)
  2022-04-01 17:58 ` classabbyamp
@ 2022-04-02 21:39 ` classabbyamp
  2022-04-14 18:44 ` classabbyamp
                   ` (36 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-02 21:39 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here for the bug report](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/bug-report.yml) and [here for the package request](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/pkg-request.yml)

[ci skip]

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 7647 bytes --]

From c6c4ae792155e39bf54c2838078ebe03ce2953ef Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@kb6.ee>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  1 +
 .github/ISSUE_TEMPLATE/pkg-request.yml | 85 ++++++++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 159 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..d9914f4d02dc
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..0086358db1eb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1 @@
+blank_issues_enabled: true
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..9b16ae4a93fe
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,85 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Quality Requirements
+
+        To be included in the Void repository, software must meet **at least one** of the following requirements.
+        Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
+        If you believe you have an exception, make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for inclusion in void-packages.
+
+
+        In particular, new themes are highly unlikely to be accepted.
+        Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base.
+        New fonts may be accepted if they provide value beyond aesthetics
+        (e.g. they contain glyphs for a script missing in already packaged fonts).
+
+
+        Browser forks, including those based on Chromium and Firefox, are generally not accepted.
+        Such forks require heavy patching, maintenance and hours of build time.
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Release Status
+
+        Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
+        Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: "The software is available in a version announced by authors as ready-to-use by the general public"
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (14 preceding siblings ...)
  2022-04-02 21:39 ` [PR PATCH] [Updated] " classabbyamp
@ 2022-04-14 18:44 ` classabbyamp
  2022-04-14 18:44 ` classabbyamp
                   ` (35 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-14 18:44 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here for the bug report](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/bug-report.yml) and [here for the package request](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/pkg-request.yml)

[ci skip]

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 7647 bytes --]

From 448b65011a60d4bc04a334a7d67abe63249a3283 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@kb6.ee>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  1 +
 .github/ISSUE_TEMPLATE/pkg-request.yml | 85 ++++++++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 159 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..d9914f4d02dc
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..0086358db1eb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1 @@
+blank_issues_enabled: true
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..9b16ae4a93fe
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,85 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Quality Requirements
+
+        To be included in the Void repository, software must meet **at least one** of the following requirements.
+        Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
+        If you believe you have an exception, make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for inclusion in void-packages.
+
+
+        In particular, new themes are highly unlikely to be accepted.
+        Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base.
+        New fonts may be accepted if they provide value beyond aesthetics
+        (e.g. they contain glyphs for a script missing in already packaged fonts).
+
+
+        Browser forks, including those based on Chromium and Firefox, are generally not accepted.
+        Such forks require heavy patching, maintenance and hours of build time.
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Release Status
+
+        Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
+        Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: "The software is available in a version announced by authors as ready-to-use by the general public"
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (15 preceding siblings ...)
  2022-04-14 18:44 ` classabbyamp
@ 2022-04-14 18:44 ` classabbyamp
  2022-04-14 20:25 ` classabbyamp
                   ` (34 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-14 18:44 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here for the bug report](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/bug-report.yml) and [here for the package request](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/pkg-request.yml)

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 7658 bytes --]

From 6e6efe88ff29c824cd796db5e34e49c22480d04e Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  1 +
 .github/ISSUE_TEMPLATE/pkg-request.yml | 85 ++++++++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 159 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..d9914f4d02dc
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..0086358db1eb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1 @@
+blank_issues_enabled: true
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..9b16ae4a93fe
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,85 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Quality Requirements
+
+        To be included in the Void repository, software must meet **at least one** of the following requirements.
+        Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
+        If you believe you have an exception, make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for inclusion in void-packages.
+
+
+        In particular, new themes are highly unlikely to be accepted.
+        Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base.
+        New fonts may be accepted if they provide value beyond aesthetics
+        (e.g. they contain glyphs for a script missing in already packaged fonts).
+
+
+        Browser forks, including those based on Chromium and Firefox, are generally not accepted.
+        Such forks require heavy patching, maintenance and hours of build time.
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Release Status
+
+        Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
+        Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: "The software is available in a version announced by authors as ready-to-use by the general public"
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (16 preceding siblings ...)
  2022-04-14 18:44 ` classabbyamp
@ 2022-04-14 20:25 ` classabbyamp
  2022-04-14 20:38 ` [PR REVIEW] " paper42
                   ` (33 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-14 20:25 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here for the bug report](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/bug-report.yml) and [here for the package request](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/pkg-request.yml)

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 7832 bytes --]

From 26aaa1de846eccf7f946b33285091ee6fcd71945 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  5 ++
 .github/ISSUE_TEMPLATE/pkg-request.yml | 85 ++++++++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 163 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..d9914f4d02dc
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..a58023751793
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Other kind of issue
+    url: https://github.com/void-linux/void-packages/issues/new
+    about: For RFCs, tracking issues, etc (freeform text)
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..9b16ae4a93fe
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,85 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Quality Requirements
+
+        To be included in the Void repository, software must meet **at least one** of the following requirements.
+        Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
+        If you believe you have an exception, make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for inclusion in void-packages.
+
+
+        In particular, new themes are highly unlikely to be accepted.
+        Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base.
+        New fonts may be accepted if they provide value beyond aesthetics
+        (e.g. they contain glyphs for a script missing in already packaged fonts).
+
+
+        Browser forks, including those based on Chromium and Firefox, are generally not accepted.
+        Such forks require heavy patching, maintenance and hours of build time.
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Release Status
+
+        Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
+        Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: "The software is available in a version announced by authors as ready-to-use by the general public"
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (18 preceding siblings ...)
  2022-04-14 20:38 ` [PR REVIEW] " paper42
@ 2022-04-14 20:38 ` paper42
  2022-04-14 20:40 ` classabbyamp
                   ` (31 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: paper42 @ 2022-04-14 20:38 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 471 bytes --]

New review comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r850787479

Comment:
I am not sure I like labeling an issue as a bug when a bug report is filed. Now the "bug" label is assigned manually by a maintainer and I assign them only when I know the issue isn't a user error and someone was able to reproduce it. That said, I can see the other point of view - all bug reports should be labeled as such.

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (17 preceding siblings ...)
  2022-04-14 20:25 ` classabbyamp
@ 2022-04-14 20:38 ` paper42
  2022-04-14 20:38 ` paper42
                   ` (32 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: paper42 @ 2022-04-14 20:38 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 230 bytes --]

New review comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r850785265

Comment:
Could we mention that people can get these strings with `xbps-query -p pkgver foo`?

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (19 preceding siblings ...)
  2022-04-14 20:38 ` paper42
@ 2022-04-14 20:40 ` classabbyamp
  2022-04-14 20:43 ` [PR PATCH] [Updated] " classabbyamp
                   ` (30 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-14 20:40 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1099602209

Comment:
> free-form issue is too hard to find, consider making it a third template

We've found a way to make this work without adding a template:

![image](https://user-images.githubusercontent.com/5366828/163470639-0b985377-831d-4b01-b83f-7b437b7b6514.png)

A freeform/blank _template_ is not possible when using issue forms, and a freeform issue form is not really possible (it would have to be a single multi-line input and would add a weird title to the body of the issue). This solution also makes the button to create a blank issue less prominent than the bright green ones for bugs and requests.

The latest updates are available for live preview here: https://github.com/classabbyamp/void-packages-test/issues/new/choose
(note that the current link for freeform issues is pointed to the actual void-packages repo, as it will be after merging. It also currently shows the old issue template since this PR hasn't been merged)

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (20 preceding siblings ...)
  2022-04-14 20:40 ` classabbyamp
@ 2022-04-14 20:43 ` classabbyamp
  2022-04-14 20:46 ` [PR REVIEW] " classabbyamp
                   ` (29 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-14 20:43 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here for the bug report](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/bug-report.yml) and [here for the package request](https://github.com/classabbyamp/void-packages/blob/new-issue-templates/.github/ISSUE_TEMPLATE/pkg-request.yml)

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 7884 bytes --]

From 17d5c7219c42e11282d6005d65d7e4a30d98fe40 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  5 ++
 .github/ISSUE_TEMPLATE/pkg-request.yml | 85 ++++++++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 163 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..b8e0dd4eb0fc
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version (this can be found with `xbps-query -p pkgver foo`)
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..a58023751793
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Other kind of issue
+    url: https://github.com/void-linux/void-packages/issues/new
+    about: For RFCs, tracking issues, etc (freeform text)
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..9b16ae4a93fe
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,85 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Quality Requirements
+
+        To be included in the Void repository, software must meet **at least one** of the following requirements.
+        Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
+        If you believe you have an exception, make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for inclusion in void-packages.
+
+
+        In particular, new themes are highly unlikely to be accepted.
+        Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base.
+        New fonts may be accepted if they provide value beyond aesthetics
+        (e.g. they contain glyphs for a script missing in already packaged fonts).
+
+
+        Browser forks, including those based on Chromium and Firefox, are generally not accepted.
+        Such forks require heavy patching, maintenance and hours of build time.
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Release Status
+
+        Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
+        Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: "The software is available in a version announced by authors as ready-to-use by the general public"
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (21 preceding siblings ...)
  2022-04-14 20:43 ` [PR PATCH] [Updated] " classabbyamp
@ 2022-04-14 20:46 ` classabbyamp
  2022-04-14 20:50 ` 0x5c
                   ` (28 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-14 20:46 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 161 bytes --]

New review comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r850792267

Comment:
addressed

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (22 preceding siblings ...)
  2022-04-14 20:46 ` [PR REVIEW] " classabbyamp
@ 2022-04-14 20:50 ` 0x5c
  2022-04-14 20:57 ` Chocimier
                   ` (27 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: 0x5c @ 2022-04-14 20:50 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]

New review comment by 0x5c on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r850794673

Comment:
The form can apply more labels, which could be `unconfirmed` or `needs-triage`, to be removed by a maintainer when confirmed.

Another approach is keeping the automatic labels as-is, but adding to the repo the usage of a `confirmed` label, to be added by a maintainer when the bug in confirmed.  
This might be better if there's interest in excluding confirmed bugs from stalebot.

The idea of both approaches is to ensure that anything claimed to be a bug can actually be found without fumbling with github's horrible keyword search. Searching by labels is more capable and allows searching for combinations, ie: `label:bug -label:unconfirmed` to only find confirmed bugs.

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (23 preceding siblings ...)
  2022-04-14 20:50 ` 0x5c
@ 2022-04-14 20:57 ` Chocimier
  2022-04-14 20:58 ` [PR REVIEW] " 0x5c
                   ` (26 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: Chocimier @ 2022-04-14 20:57 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 260 bytes --]

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1099615352

Comment:
Remarks from paper42 to replace quality requirement with link and to not tag are right. Otherwise quite fine for me.

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (24 preceding siblings ...)
  2022-04-14 20:57 ` Chocimier
@ 2022-04-14 20:58 ` 0x5c
  2022-04-14 21:13 ` 0x5c
                   ` (25 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: 0x5c @ 2022-04-14 20:58 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]

New review comment by 0x5c on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r850794673

Comment:
The form can apply more labels, which could be `unconfirmed` or `needs-triage`, to be removed by a maintainer when confirmed.

Another approach is keeping the automatic labels as-is, but adding to the repo the usage of a `confirmed` label, to be added by a maintainer when the bug is confirmed.  
This might be better if there's interest in excluding confirmed bugs from stalebot.

The idea of both approaches is to ensure that anything claimed to be a bug can actually be found without fumbling with github's horrible keyword search. Searching by labels is more capable and allows searching for combinations, ie: `label:bug -label:unconfirmed` to only find confirmed bugs.

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (25 preceding siblings ...)
  2022-04-14 20:58 ` [PR REVIEW] " 0x5c
@ 2022-04-14 21:13 ` 0x5c
  2022-04-14 21:22 ` [PR REVIEW] " paper42
                   ` (24 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: 0x5c @ 2022-04-14 21:13 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

New comment by 0x5c on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1099626871

Comment:
> Remarks from paper42 to replace quality requirement with link and to not tag are right. Otherwise quite fine for me.

That text had to be edited to make it more comprehensible to package requesters, since the manual's wording is heavily intended for those who are writing a template, and mentions things like `If you believe you have an exception, start a PR and make an argument for why that particular piece of software, while not meeting any of the following requirements, is a good candidate for the Void packages system.`, which seems fairly nonconstructive in the context of a package request.

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (26 preceding siblings ...)
  2022-04-14 21:13 ` 0x5c
@ 2022-04-14 21:22 ` paper42
  2022-04-14 21:23 ` paper42
                   ` (23 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: paper42 @ 2022-04-14 21:22 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 342 bytes --]

New review comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r850813704

Comment:
![image](https://user-images.githubusercontent.com/23639164/163478507-f2e63719-96f2-4515-ab51-9403a4bbed2b.png)
Newlines are missing in a webkit based browser, but I don't think we can fix that.

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (27 preceding siblings ...)
  2022-04-14 21:22 ` [PR REVIEW] " paper42
@ 2022-04-14 21:23 ` paper42
  2022-04-14 21:23 ` classabbyamp
                   ` (22 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: paper42 @ 2022-04-14 21:23 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 193 bytes --]

New review comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r850814086

Comment:
I like the idea of an "unconfirmed" label :+1:

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (28 preceding siblings ...)
  2022-04-14 21:23 ` paper42
@ 2022-04-14 21:23 ` classabbyamp
  2022-04-14 21:23 ` classabbyamp
                   ` (21 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-14 21:23 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 211 bytes --]

New review comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r850814223

Comment:
works fine in chromium-based, but yeah I think you're right

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (29 preceding siblings ...)
  2022-04-14 21:23 ` classabbyamp
@ 2022-04-14 21:23 ` classabbyamp
  2022-04-14 21:25 ` paper42
                   ` (20 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-14 21:23 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 200 bytes --]

New review comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r850814448

Comment:
if you create the label, we can add it to the PR

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (30 preceding siblings ...)
  2022-04-14 21:23 ` classabbyamp
@ 2022-04-14 21:25 ` paper42
  2022-04-14 21:29 ` classabbyamp
                   ` (19 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: paper42 @ 2022-04-14 21:25 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 184 bytes --]

New review comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r850815141

Comment:
This is from Epiphany 42 (GNOME Web).

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (31 preceding siblings ...)
  2022-04-14 21:25 ` paper42
@ 2022-04-14 21:29 ` classabbyamp
  2022-04-14 21:48 ` [PR PATCH] [Updated] " classabbyamp
                   ` (18 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-14 21:29 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 287 bytes --]

New review comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r850818538

Comment:
hm, sounds like something that should be reported [upstream](https://github.com/github/feedback/discussions/categories/issues-feedback)

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (32 preceding siblings ...)
  2022-04-14 21:29 ` classabbyamp
@ 2022-04-14 21:48 ` classabbyamp
  2022-04-19 15:33 ` classabbyamp
                   ` (17 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-14 21:48 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here](https://github.com/classabbyamp/void-packages-test/issues/new/choose)

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 7899 bytes --]

From 3c9fcc5e7208531b0fd113f80042188d0fe3bf8d Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  5 ++
 .github/ISSUE_TEMPLATE/pkg-request.yml | 85 ++++++++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 163 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..91a62e57f168
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug", "unconfirmed"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version (this can be found with `xbps-query -p pkgver foo`)
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..a58023751793
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Other kind of issue
+    url: https://github.com/void-linux/void-packages/issues/new
+    about: For RFCs, tracking issues, etc (freeform text)
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..9b16ae4a93fe
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,85 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Quality Requirements
+
+        To be included in the Void repository, software must meet **at least one** of the following requirements.
+        Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
+        If you believe you have an exception, make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for inclusion in void-packages.
+
+
+        In particular, new themes are highly unlikely to be accepted.
+        Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base.
+        New fonts may be accepted if they provide value beyond aesthetics
+        (e.g. they contain glyphs for a script missing in already packaged fonts).
+
+
+        Browser forks, including those based on Chromium and Firefox, are generally not accepted.
+        Such forks require heavy patching, maintenance and hours of build time.
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Release Status
+
+        Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
+        Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: "The software is available in a version announced by authors as ready-to-use by the general public"
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (33 preceding siblings ...)
  2022-04-14 21:48 ` [PR PATCH] [Updated] " classabbyamp
@ 2022-04-19 15:33 ` classabbyamp
  2022-04-19 17:48 ` Chocimier
                   ` (16 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-19 15:33 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here](https://github.com/classabbyamp/void-packages-test/issues/new/choose)

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 7899 bytes --]

From 8afdd326d1774a7924518733616526a53ed8e9b3 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  5 ++
 .github/ISSUE_TEMPLATE/pkg-request.yml | 85 ++++++++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 163 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..91a62e57f168
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug", "unconfirmed"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version (this can be found with `xbps-query -p pkgver foo`)
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..a58023751793
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Other kind of issue
+    url: https://github.com/void-linux/void-packages/issues/new
+    about: For RFCs, tracking issues, etc (freeform text)
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..9b16ae4a93fe
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,85 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Quality Requirements
+
+        To be included in the Void repository, software must meet **at least one** of the following requirements.
+        Exceptions to the list are possible, and might be accepted, but are extremely unlikely.
+        If you believe you have an exception, make an argument for why that particular piece of software,
+        while not meeting any of the following requirements, is a good candidate for inclusion in void-packages.
+
+
+        In particular, new themes are highly unlikely to be accepted.
+        Simple shell scripts are unlikely to be accepted unless they provide considerable value to a broad user base.
+        New fonts may be accepted if they provide value beyond aesthetics
+        (e.g. they contain glyphs for a script missing in already packaged fonts).
+
+
+        Browser forks, including those based on Chromium and Firefox, are generally not accepted.
+        Such forks require heavy patching, maintenance and hours of build time.
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: >
+        ## Release Status
+
+        Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
+        Betas, pre-releases, and arbitrary VCS revisions won't be accepted.
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: "The software is available in a version announced by authors as ready-to-use by the general public"
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (34 preceding siblings ...)
  2022-04-19 15:33 ` classabbyamp
@ 2022-04-19 17:48 ` Chocimier
  2022-04-19 17:59 ` [PR PATCH] [Updated] " classabbyamp
                   ` (15 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: Chocimier @ 2022-04-19 17:48 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 342 bytes --]

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1102923782

Comment:
> edited to make it more comprehensible

I see no meaningful rewording, but if any is needed, please send PR changing proper documentation. Maintaining many copies of same text is not sustainable.

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (35 preceding siblings ...)
  2022-04-19 17:48 ` Chocimier
@ 2022-04-19 17:59 ` classabbyamp
  2022-04-19 18:00 ` classabbyamp
                   ` (14 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-19 17:59 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here](https://github.com/classabbyamp/void-packages-test/issues/new/choose)

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 6824 bytes --]

From 8185dc332fdbf6c7f368ad6d6d6a123fd7603e38 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  5 ++
 .github/ISSUE_TEMPLATE/pkg-request.yml | 64 ++++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 142 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..91a62e57f168
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug", "unconfirmed"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version (this can be found with `xbps-query -p pkgver foo`)
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..a58023751793
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Other kind of issue
+    url: https://github.com/void-linux/void-packages/issues/new
+    about: For RFCs, tracking issues, etc (freeform text)
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..af86e3a32132
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,64 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+
+        See [Manual.md](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality_requirements) for more details
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: |
+        The software is available in a version announced by authors as ready-to-use by the general public
+
+        See [Manual.md](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality_requirements) for more details
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index 25a0538174cc..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (36 preceding siblings ...)
  2022-04-19 17:59 ` [PR PATCH] [Updated] " classabbyamp
@ 2022-04-19 18:00 ` classabbyamp
  2022-04-19 18:00 ` classabbyamp
                   ` (13 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-19 18:00 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 271 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1102933842

Comment:
Updated.

![image](https://user-images.githubusercontent.com/5366828/164066781-8eb25537-7048-4cf5-bb76-8f7e53fe2ee6.png)


^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (37 preceding siblings ...)
  2022-04-19 18:00 ` classabbyamp
@ 2022-04-19 18:00 ` classabbyamp
  2022-05-01  6:36 ` [PR REVIEW] " 0x5c
                   ` (12 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-04-19 18:00 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 315 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1102933842

Comment:
Updated (link goes to quality requirements section).

![image](https://user-images.githubusercontent.com/5366828/164066781-8eb25537-7048-4cf5-bb76-8f7e53fe2ee6.png)


^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (38 preceding siblings ...)
  2022-04-19 18:00 ` classabbyamp
@ 2022-05-01  6:36 ` 0x5c
  2022-06-10 20:48 ` [PR PATCH] [Updated] " classabbyamp
                   ` (11 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: 0x5c @ 2022-05-01  6:36 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 161 bytes --]

New review comment by 0x5c on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r862430177

Comment:
Any news on this?

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (39 preceding siblings ...)
  2022-05-01  6:36 ` [PR REVIEW] " 0x5c
@ 2022-06-10 20:48 ` classabbyamp
  2022-06-10 20:51 ` classabbyamp
                   ` (10 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-06-10 20:48 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here](https://github.com/classabbyamp/void-packages-test/issues/new/choose)

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 6822 bytes --]

From 6a3338b503ac51dc40a946358a39b2f341d1af3f Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  5 ++
 .github/ISSUE_TEMPLATE/pkg-request.yml | 64 ++++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 142 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..91a62e57f168
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug", "unconfirmed"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version (this can be found with `xbps-query -p pkgver foo`)
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..a58023751793
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Other kind of issue
+    url: https://github.com/void-linux/void-packages/issues/new
+    about: For RFCs, tracking issues, etc (freeform text)
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..af86e3a32132
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,64 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+
+        See [Manual.md](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality_requirements) for more details
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: |
+        The software is available in a version announced by authors as ready-to-use by the general public
+
+        See [Manual.md](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality_requirements) for more details
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index b7f38da9fa5a..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://repo-default.voidlinux.org/void-updates/void-updates.txt. However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (40 preceding siblings ...)
  2022-06-10 20:48 ` [PR PATCH] [Updated] " classabbyamp
@ 2022-06-10 20:51 ` classabbyamp
  2022-06-10 20:52 ` [PR REVIEW] " classabbyamp
                   ` (9 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-06-10 20:51 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here](https://github.com/classabbyamp/void-packages-test/issues/new/choose)

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 6824 bytes --]

From 97718a2e1bfe8531fd38fb3ef0173b5ecebd0f64 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  5 ++
 .github/ISSUE_TEMPLATE/pkg-request.yml | 64 ++++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 142 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..c71dea1be09b
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug", "needs-testing"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version (this can be found with `xbps-query -p pkgver foo`)
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..a58023751793
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Other kind of issue
+    url: https://github.com/void-linux/void-packages/issues/new
+    about: For RFCs, tracking issues, etc (freeform text)
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..af86e3a32132
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,64 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://foobar9k.org
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+
+        See [Manual.md](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality_requirements) for more details
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: |
+        The software is available in a version announced by authors as ready-to-use by the general public
+
+        See [Manual.md](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality_requirements) for more details
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index b7f38da9fa5a..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://repo-default.voidlinux.org/void-updates/void-updates.txt. However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR REVIEW] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (41 preceding siblings ...)
  2022-06-10 20:51 ` classabbyamp
@ 2022-06-10 20:52 ` classabbyamp
  2022-06-10 20:56 ` [PR PATCH] [Updated] " classabbyamp
                   ` (8 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-06-10 20:52 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 251 bytes --]

New review comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#discussion_r894881162

Comment:
added the new `needs-testing` label to the bug report template by default, which should solve this.

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (42 preceding siblings ...)
  2022-06-10 20:52 ` [PR REVIEW] " classabbyamp
@ 2022-06-10 20:56 ` classabbyamp
  2022-06-10 20:59 ` classabbyamp
                   ` (7 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-06-10 20:56 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here](https://github.com/classabbyamp/void-packages-test/issues/new/choose)

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 6832 bytes --]

From c3449472c2045e59a7cdb21b964541c8dbf4abc8 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  5 ++
 .github/ISSUE_TEMPLATE/pkg-request.yml | 64 ++++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 142 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..c71dea1be09b
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug", "needs-testing"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version (this can be found with `xbps-query -p pkgver foo`)
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..a58023751793
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Other kind of issue
+    url: https://github.com/void-linux/void-packages/issues/new
+    about: For RFCs, tracking issues, etc (freeform text)
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..801dcf57fb0d
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,64 @@
+name: Package Request
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://example.com/foobar9k
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        **System:** The software should be installed system-wide, not per-user
+        **Compiled:** The software needs to be compiled before being used, even if it is software that is not needed by the whole system
+        **Required:** Another package either within the repository or pending inclusion requires the package
+
+        See [Manual.md](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality_requirements) for more details
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: |
+        The software is available in a version announced by authors as ready-to-use by the general public
+
+        See [Manual.md](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality_requirements) for more details
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index b7f38da9fa5a..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://repo-default.voidlinux.org/void-updates/void-updates.txt. However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (43 preceding siblings ...)
  2022-06-10 20:56 ` [PR PATCH] [Updated] " classabbyamp
@ 2022-06-10 20:59 ` classabbyamp
  2022-06-14 18:33 ` Chocimier
                   ` (6 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-06-10 20:59 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 270 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1152734353

Comment:
latest version of this is [live here](https://github.com/classabbyamp/void-packages-test/issues/new/choose). Any critiques?

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (44 preceding siblings ...)
  2022-06-10 20:59 ` classabbyamp
@ 2022-06-14 18:33 ` Chocimier
  2022-06-14 19:26 ` [PR PATCH] [Updated] " classabbyamp
                   ` (5 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: Chocimier @ 2022-06-14 18:33 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 250 bytes --]

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1155584837

Comment:
Quality requirements already say different things here and in contributing.md, can we get rid of the copy?

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (45 preceding siblings ...)
  2022-06-14 18:33 ` Chocimier
@ 2022-06-14 19:26 ` classabbyamp
  2022-06-14 19:27 ` classabbyamp
                   ` (4 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-06-14 19:26 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here](https://github.com/classabbyamp/void-packages-test/issues/new/choose)

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 6410 bytes --]

From 1108b2505d17b6fbcb57cf53bf30265ef868d0e9 Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  5 ++
 .github/ISSUE_TEMPLATE/pkg-request.yml | 59 +++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 137 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..c71dea1be09b
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug", "needs-testing"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version (this can be found with `xbps-query -p pkgver foo`)
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..a58023751793
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Other kind of issue
+    url: https://github.com/void-linux/void-packages/issues/new
+    about: For RFCs, tracking issues, etc (freeform text)
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..1dbbe572d069
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,59 @@
+name: Package Request
+title: "Package request: "
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://example.com/foobar9k
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        See [Manual.md](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality_requirements) for details
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: |
+        See [Manual.md](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality_requirements) for details
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index b7f38da9fa5a..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://repo-default.voidlinux.org/void-updates/void-updates.txt. However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (46 preceding siblings ...)
  2022-06-14 19:26 ` [PR PATCH] [Updated] " classabbyamp
@ 2022-06-14 19:27 ` classabbyamp
  2022-06-14 19:27 ` classabbyamp
                   ` (3 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-06-14 19:27 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 184 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1155628488

Comment:
> can we get rid of the copy?

done

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (47 preceding siblings ...)
  2022-06-14 19:27 ` classabbyamp
@ 2022-06-14 19:27 ` classabbyamp
  2022-06-14 19:33 ` Chocimier
                   ` (2 subsequent siblings)
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-06-14 19:27 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 263 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1155628488

Comment:
> can we get rid of the copy?

done (assuming you meant manual.md, contributing doesn't list quality requirements)

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (48 preceding siblings ...)
  2022-06-14 19:27 ` classabbyamp
@ 2022-06-14 19:33 ` Chocimier
  2022-06-14 19:39 ` [PR PATCH] [Updated] " classabbyamp
  2022-06-17  3:44 ` [PR PATCH] [Merged]: " classabbyamp
  51 siblings, 0 replies; 53+ messages in thread
From: Chocimier @ 2022-06-14 19:33 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 215 bytes --]

New comment by Chocimier on void-packages repository

https://github.com/void-linux/void-packages/pull/36411#issuecomment-1155633971

Comment:
"is this new" checkbox should go first to avoid wasting reporter's time

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Updated] .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (49 preceding siblings ...)
  2022-06-14 19:33 ` Chocimier
@ 2022-06-14 19:39 ` classabbyamp
  2022-06-17  3:44 ` [PR PATCH] [Merged]: " classabbyamp
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-06-14 19:39 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]

There is an updated pull request by classabbyamp against master on the void-packages repository

https://github.com/classabbyamp/void-packages new-issue-templates
https://github.com/void-linux/void-packages/pull/36411

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here](https://github.com/classabbyamp/void-packages-test/issues/new/choose)

A patch file from https://github.com/void-linux/void-packages/pull/36411.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-new-issue-templates-36411.patch --]
[-- Type: text/x-diff, Size: 6410 bytes --]

From 0783b96a03337fb32386aa42be2d0370085d986b Mon Sep 17 00:00:00 2001
From: classabbyamp <dev@placeviolette.net>
Date: Wed, 30 Mar 2022 00:51:29 -0400
Subject: [PATCH] .github/ISSUE_TEMPLATE: add bug report and package request
 issue forms

Co-authored-by: 0x5c <dev@0x5c.io>
---
 .github/ISSUE_TEMPLATE/bug-report.yml  | 73 ++++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml      |  5 ++
 .github/ISSUE_TEMPLATE/pkg-request.yml | 59 +++++++++++++++++++++
 .github/issue_template.md              | 14 -----
 4 files changed, 137 insertions(+), 14 deletions(-)
 create mode 100644 .github/ISSUE_TEMPLATE/bug-report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/pkg-request.yml
 delete mode 100644 .github/issue_template.md

diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000000..f1b15e39f792
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,73 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug", "needs-testing"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: verified
+    type: dropdown
+    attributes:
+      label: Is this a new report?
+      description: I verified that there isn't already an open issue for this bug
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
+  - id: xuname
+    type: input
+    attributes:
+      label: System Info
+      description: Output of `xuname` (part of [`xtools`](https://man.voidlinux.org/xtools.1))
+      placeholder: Void 5.x.y_z x86_64-musl ...
+    validations:
+      required: true
+  - id: packages
+    type: input
+    attributes:
+      label: Package(s) Affected
+      description: Affected package(s) including version (this can be found with `xbps-query -p pkgver foo`)
+      placeholder: foo-1.0.2_5, bar-5.6.7_1, baz-0.0.3_5, ...
+    validations:
+      required: true
+  - id: upstream
+    type: textarea
+    attributes:
+      label: Does a report exist for this bug with the project's home (upstream) and/or another distro?
+      description: If so, link it here (It's fine if there's none)
+      placeholder: |
+        For example:
+        https://bugs.kde.org/show_bug.cgi?id=432975
+        https://bugs.gentoo.org/767478
+  - id: expected
+    type: textarea
+    attributes:
+      label: Expected behaviour
+      description: A clear and concise description of what you expected to happen
+      placeholder: The package is supposed to do this thing.
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Actual behaviour
+      description: A clear and concise description of what the bug is
+      placeholder: There was a crash when...
+    validations:
+      required: true
+  - id: steps
+    type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Clear steps to reproduce the bug
+      placeholder: |
+        1. Do the thing
+        2. Do the other thing
+        3. ???
+        4. Crash :(
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000000..a58023751793
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Other kind of issue
+    url: https://github.com/void-linux/void-packages/issues/new
+    about: For RFCs, tracking issues, etc (freeform text)
diff --git a/.github/ISSUE_TEMPLATE/pkg-request.yml b/.github/ISSUE_TEMPLATE/pkg-request.yml
new file mode 100644
index 000000000000..1dbbe572d069
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/pkg-request.yml
@@ -0,0 +1,59 @@
+name: Package Request
+title: "Package request: "
+description: Request the addition of a package
+labels: ["request"]
+body:
+  - type: markdown
+    attributes:
+      value: >
+        #### Don't request an update of a package,
+        [We have a script for that](https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt).
+        However, a quality pull request may help.
+  - id: name
+    type: input
+    attributes:
+      label: Package name
+      placeholder: foobar9k
+    validations:
+      required: true
+  - id: homepage
+    type: input
+    attributes:
+      label: Package homepage
+      placeholder: https://example.com/foobar9k
+    validations:
+      required: true
+  - id: description
+    type: textarea
+    attributes:
+      label: Description
+      description: What does the package do?
+      placeholder: >
+        Foobar9k is a music player that turns your music up to 11.
+        It provides features X, Y, and Z, which other music players in Void don't.
+    validations:
+      required: true
+  - id: quality
+    type: dropdown
+    attributes:
+      label: Does the requested package meet the quality requirements?
+      description: |
+        See [Manual.md](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality_requirements) for details
+      multiple: true
+      options:
+        - System
+        - Compiled
+        - Required
+    validations:
+      required: true
+  - id: released
+    type: dropdown
+    attributes:
+      label: Is the requested package released?
+      description: |
+        See [Manual.md](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality_requirements) for details
+      options:
+        - "Yes"
+        - "No"
+    validations:
+      required: true
diff --git a/.github/issue_template.md b/.github/issue_template.md
deleted file mode 100644
index b7f38da9fa5a..000000000000
--- a/.github/issue_template.md
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- Don't request update of package. We have a script for that. https://repo-default.voidlinux.org/void-updates/void-updates.txt. However, a quality pull request may help. -->
-### System
-
-* xuname:  
-  *output of ``xuname`` (part of xtools)*
-* package:  
-  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
-
-### Expected behavior
-
-### Actual behavior
-
-### Steps to reproduce the behavior
-

^ permalink raw reply	[flat|nested] 53+ messages in thread

* Re: [PR PATCH] [Merged]: .github/ISSUE_TEMPLATE: add bug report and package request issue forms
  2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
                   ` (50 preceding siblings ...)
  2022-06-14 19:39 ` [PR PATCH] [Updated] " classabbyamp
@ 2022-06-17  3:44 ` classabbyamp
  51 siblings, 0 replies; 53+ messages in thread
From: classabbyamp @ 2022-06-17  3:44 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]

There's a merged pull request on the void-packages repository

.github/ISSUE_TEMPLATE: add bug report and package request issue forms
https://github.com/void-linux/void-packages/pull/36411

Description:
Co-authored-by: @0x5c 

This PR replaces the existing markdown-based issue template with two new [Github issue forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms), one for bug reports and one for package requests.

These ensure that the relevant information is asked for and the required information is provided. They also automagically tag issues with the `bug` and `request` tags. If preferred, new bug reports could be also be marked with a second `unconfirmed` or `needs triage` label, applied by the form.

Issues that do not fall under these types (like RFCs) can still be opened by clicking the "open a blank issue" button on the template chooser:
![image](https://user-images.githubusercontent.com/5366828/160756504-21812fa5-c0a0-4c9d-a454-7094fa034ef2.png)
This can be limited to maintainers by changing `blank_issues_enabled` to `false` in `.github/ISSUE_TEMPLATE/config.yml` if desired.

`config.yml` can also be used to add additional arbitrary links in the template chooser. Here's an example [config.yml](https://github.com/miaowware/qrm2/blob/master/.github/ISSUE_TEMPLATE/config.yml) and resulting [template chooser](https://github.com/miaowware/qrm2/issues/new/choose) in another project.

#### Testing the changes
- I tested the changes in this PR: **YES**
    A preview of the rendered templates can be seen [here](https://github.com/classabbyamp/void-packages-test/issues/new/choose)

^ permalink raw reply	[flat|nested] 53+ messages in thread

end of thread, other threads:[~2022-06-17  3:44 UTC | newest]

Thread overview: 53+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-30  5:34 [PR PATCH] .github/ISSUE_TEMPLATE: add bug report and package request issue forms classabbyamp
2022-03-30  8:37 ` [PR REVIEW] " paper42
2022-03-30  8:37 ` paper42
2022-03-30  8:40 ` paper42
2022-03-30 16:56 ` classabbyamp
2022-03-30 18:14 ` Chocimier
2022-03-30 23:39 ` [PR REVIEW] " 0x5c
2022-03-31  0:38 ` 0x5c
2022-03-31  1:29 ` 0x5c
2022-04-01 17:49 ` [PR PATCH] [Updated] " classabbyamp
2022-04-01 17:52 ` classabbyamp
2022-04-01 17:53 ` classabbyamp
2022-04-01 17:54 ` classabbyamp
2022-04-01 17:55 ` classabbyamp
2022-04-01 17:58 ` classabbyamp
2022-04-02 21:39 ` [PR PATCH] [Updated] " classabbyamp
2022-04-14 18:44 ` classabbyamp
2022-04-14 18:44 ` classabbyamp
2022-04-14 20:25 ` classabbyamp
2022-04-14 20:38 ` [PR REVIEW] " paper42
2022-04-14 20:38 ` paper42
2022-04-14 20:40 ` classabbyamp
2022-04-14 20:43 ` [PR PATCH] [Updated] " classabbyamp
2022-04-14 20:46 ` [PR REVIEW] " classabbyamp
2022-04-14 20:50 ` 0x5c
2022-04-14 20:57 ` Chocimier
2022-04-14 20:58 ` [PR REVIEW] " 0x5c
2022-04-14 21:13 ` 0x5c
2022-04-14 21:22 ` [PR REVIEW] " paper42
2022-04-14 21:23 ` paper42
2022-04-14 21:23 ` classabbyamp
2022-04-14 21:23 ` classabbyamp
2022-04-14 21:25 ` paper42
2022-04-14 21:29 ` classabbyamp
2022-04-14 21:48 ` [PR PATCH] [Updated] " classabbyamp
2022-04-19 15:33 ` classabbyamp
2022-04-19 17:48 ` Chocimier
2022-04-19 17:59 ` [PR PATCH] [Updated] " classabbyamp
2022-04-19 18:00 ` classabbyamp
2022-04-19 18:00 ` classabbyamp
2022-05-01  6:36 ` [PR REVIEW] " 0x5c
2022-06-10 20:48 ` [PR PATCH] [Updated] " classabbyamp
2022-06-10 20:51 ` classabbyamp
2022-06-10 20:52 ` [PR REVIEW] " classabbyamp
2022-06-10 20:56 ` [PR PATCH] [Updated] " classabbyamp
2022-06-10 20:59 ` classabbyamp
2022-06-14 18:33 ` Chocimier
2022-06-14 19:26 ` [PR PATCH] [Updated] " classabbyamp
2022-06-14 19:27 ` classabbyamp
2022-06-14 19:27 ` classabbyamp
2022-06-14 19:33 ` Chocimier
2022-06-14 19:39 ` [PR PATCH] [Updated] " classabbyamp
2022-06-17  3:44 ` [PR PATCH] [Merged]: " classabbyamp

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).