kaitai-io / kaitai-io.github.io

Kaitai Project homepage
6 stars 9 forks source link

Download: reorder download options by popularity #19

Open generalmimon opened 2 years ago

generalmimon commented 2 years ago

Currently the "default" pre-selected download option at https://kaitai.io/#download is the Linux .deb. However, the download stats for the artifacts at https://github.com/kaitai-io/kaitai_struct_compiler/releases are the following (retreived via GitHub REST API using my little script ksc-release-download-stats.sh):

[
  {
    "name": "0.10",
    "assets": [
      {
        "name": "kaitai-struct-compiler-0.10.msi",
        "download_count": 7658
      },
      {
        "name": "kaitai-struct-compiler-0.10.zip",
        "download_count": 31609
      },
      {
        "name": "kaitai-struct-compiler_0.10_all.deb",
        "download_count": 9264
      }
    ]
  },
  {
    "name": "0.9",
    "assets": [
      {
        "name": "kaitai-struct-compiler-0.9.zip",
        "download_count": 199613
      },
      {
        "name": "kaitai-struct-compiler.msi",
        "download_count": 5742
      },
      {
        "name": "kaitai-struct-compiler_0.9_all.deb",
        "download_count": 7419
      }
    ]
  },
  {
    "name": "0.8",
    "assets": [
      {
        "name": "kaitai-struct-compiler-0.8.msi",
        "download_count": 20
      },
      {
        "name": "kaitai-struct-compiler-0.8.zip",
        "download_count": 8558
      },
      {
        "name": "kaitai-struct-compiler_0.8_all.deb",
        "download_count": 228
      }
    ]
  },

The universal .zip is a clear winner. So I guess it makes sense to offer it as the first (default) option, followed by Linux .deb and Windows .msi. According to stats at https://formulae.brew.sh/formula/kaitai-struct-compiler, Homebrew is a bit less popular, so it comes after .zip, .deb and .msi.

KOLANICH commented 2 years ago

We also need to do something with the unstable builds hosted on Cloudsmith. Either advertise them as official. Or replace them. Currently we neither advertise them, no host ourselves. Of course hosting them ourselves (or at least on GitHub Pages but using KS keys, not CloudSmith ones) is preferred, but if implementing it takes more than a year (as it has already taken, if I understand right), we should just advertise the CloudSmith repo.