#35 Correct maximum size for a couple of spins
Merged a year ago by bcotton. Opened a year ago by adamwill.
fedora-pgm/ adamwill/pgm_docs 202212-sizes-update  into  main

@@ -12,7 +12,7 @@ 

  |Name | Description | Maximum size

  

  |https://fedoraproject.org/wiki/Astronomy_Spin[Astronomy Spin] | The Astronomy Spin is a powerful completely open-source and free tool for astronomy amateurs and professionals. | 4 GB

- |https://fedoraproject.org/wiki/Changes/Cinnamon_Spin[Cinnamon Spin] | The Fedora Cinnamon spin provides advanced innovative features and a traditional user experience. | 2 GB

+ |https://fedoraproject.org/wiki/Changes/Cinnamon_Spin[Cinnamon Spin] | The Fedora Cinnamon spin provides advanced innovative features and a traditional user experience. | 2.6 GiB

  |https://fedoraproject.org/wiki/Changes/Comp_Neuro_Lab[Comp Neuro Lab] | Fedora Lab image for users working in Computational Neuroscience. | 4GB

  |https://fedoraproject.org/wiki/Design_Suite[Design Suite] | The Fedora Design Suite includes well-selected applications, fitting a variety of use cases. Whether you decide to work on publishing documents, creating images and pictures or even 3D content, the Design Suite has a fitting tool. | 4 GB

  |https://fedoraproject.org/wiki/Fedora_jam[Fedora Jam] | Fedora Jam is a full-featured audio creation spin. It includes all the tools needed to help create the music you want, anything from classical to jazz to Heavy metal. Included in Fedora jam is full support for JACK and JACK to PulseAudio bridging. | 4 GiB
@@ -21,7 +21,7 @@ 

  |https://fedoraproject.org/wiki/KDE[KDE] | KDE Plasma desktop | (see xref:f{release-version}/blocking.adoc[Blocking])

  |https://kinoite.fedoraproject.org/[Kinoite] | An rpm-ostree-based KDE Plasma desktop |

  |https://fedoraproject.org/wiki/LXDE_Spin[LXDE Spin] | The Fedora LXDE spin is meant to be a lightweight, but yet complete desktop based on LXDE, the Lightweight X11 Desktop Environment. | 2 GB

- |https://fedoraproject.org/wiki/MATE-Compiz_Spin[MATE-Compiz Spin] | The Fedora MATE spin is meant to provide users with a classic, lightweight and traditional looking desktop. | 2 GB		

+ |https://fedoraproject.org/wiki/MATE-Compiz_Spin[MATE-Compiz Spin] | The Fedora MATE spin is meant to provide users with a classic, lightweight and traditional looking desktop. | 3 GiB

  |https://fedoraproject.org/wiki/Changes/PythonClassroomLab[Python Classroom Lab] | The Fedora Python Classroom Lab makes it even easier for teachers and instructors to use Fedora in their classrooms or workshops. Ready to use operating system with important stuff pre-installed - either with GNOME or as a headless environment for Docker or Vagrant. | 2 GiB

  |https://fedoraproject.org/wiki/QA_Test_Day_Spin[QA Test Day Spin]|The purpose of this spin is to provide a model kickstart file to people organizing Test Days that can easily be tweaked for specific Test Days. |

  |https://fedoraproject.org/wiki/Robotics_Spin[Robotics Spin] | Create a spin that provides as many robotics related packages to the spin to maximize out-of-the-box usable hardware and software. Eventually provide out-of-the-box simulation environment for one or more scenarios. | 4 GiB		

In both of these cases, the maintainer actually decided on a larger maximum in the F31 cycle and updated the wiki page (which was used at that time), but the change was lost when the wiki page for the next release was made (presumably the program manager based it on the original version of the F31 page). To respect the maintainers' wishes we should correct these sizes. relval has been checking for these sizes all along, not the ones currently listed on the page.

Pull-Request has been merged by bcotton

a year ago

Perhaps I should just drop the sizes from these pages. Since relval takes actual action based on the sizes it knows about, it makes sense to keep that and drop this.

well, the way it's "supposed to work" is that the pages are the canonical definition and relval reflects those. I don't let people get the sizes changed in relval's definition without them being updated on the pages first. But updates to the pages need to be carried forward :D

relval's definitions live here, but they aren't much use as a canonical public record, they're very tied to how relval works (for a start, there's a catch-all default of 4.7G which is in the code, not that file). I wouldn't want to ditch the human-readable definitions if that's the only other record we have.

also, ugh, I just realized these should have been GB, not GiB. I'll send a follow-up.

well, the way it's "supposed to work" is that the pages are the canonical definition and relval reflects those. I don't let people get the sizes changed in relval's definition without them being updated on the pages first. But updates to the pages need to be carried forward :D

This is a topic for broader, later discussion, but I wonder if there's much value in having a canonical definition. I will argue with myself about that for a while. Thanks for the fixes.

I would say we want at least the release-blocking image size limits, as they really are key 'distro policy' - that is where we say it really matters to Fedora that the netinst images are CD size and the DVD images are...DVD size. If we don't have those pages we don't have a logical backing for blocking releases on images being oversize.

The ones for non-blocking images are much more in the line of conveniences for the maintainers, really. They, at least some of them, want to know if their images suddenly blow up way bigger than they're intended to be. Those ones we could maybe stop documenting and just handle between relval and bugzilla and the maintainers, with maybe just a generic note about how size checking is handled on the Spins page.

Metadata