[chore] Update ISSUE_TEMPLATE

[z-Fng]

Sync from BucketTemplate and apply local adaptations to replace the outdated issue templates.

[SorYoshino]

I had the same idea, but I am not entirely sure which applications are suitable for the Nonportable bucket. Below are the new criteria I derived based on the characteristics of the Nonportable bucket:

    options:
    - label: Reasonably well-known and widely used (e.g. if it's a GitHub project, it should have at least 500 stars and/or 150 forks)
      required: true
    - label: English interface (or at least English documentation)
      required: true
    - label: Latest stable version
      required: false
    - label: Full version (i.e. not a trial version)
      required: true
    - label: Fairly standard (un)installation processes (e.g., using version-specific download URLs; (un)installers that support command-line operation, at least silent (un)install)
      required: true

I think the Nonportable bucket should encourage the use of stable releases when available; if not, preview releases are acceptable. Trial versions, however, should not be accepted.

[z-Fng]

Regarding the 'Fairly standard (un)installation processes' requirement, is that really necessary for the Nonportable bucket?
Aside from that, I generally agree with the rest. We shouldn't relax the criteria too much, as the maintenance burden is already quite heavy.

[SorYoshino]

Regarding the 'Fairly standard (un)installation processes' requirement, is that really necessary for the Nonportable bucket?

To be honest, I am not entirely sure whether they are necessary. I mentioned them mainly for the following reasons:

• To align with “What does Scoop do?” — specifically, “Hides the graphical user interface (GUI) of wizard-style installers.”
  • Most manifests in the Nonportable bucket use silent installation, with the only possible GUI being the UAC prompt. Even for “Nonportable” applications, I think this principle should still be followed.
• To ensure that the installer supports offline installation.
  • Even if an installer supports command-line options, its functionality may be limited if it does not support offline installation. While maintaining a silent installation process, installers that lack offline support may not be easy to manage through Scoop.

---

I think the Nonportable bucket should encourage the use of stable releases when available; if not, preview releases are acceptable.

When both a stable release and a newer preview release are available, should we consider allowing the auto-update checker to detect preview versions?

For example, while investigating the auto-update failure for sshfs-np, I found that the latest available version is 3.7.21011, but it is a pre-release version.

[haussmann]

I am also not clear on the following:

• Does there have to be a free version, or is software allowed that is only available as a paid version?

Additionally: Could we add the requirements also to the Readme.md ? I did not even think to look into the issue template when I learnt about scoop.