[Bathrone]

Many thanks for taking on the bug report. Where the upstream mod developer is active it makes the most sense for the reports to go there.

So I was thinking of how to structure each package in light of my post above. Can I suggest something please below and ask if people

- Think it makes sense and is worth doing?
- Like the suggested values?
- Other comments?

So for each package in the mod list a small table like:

Package Name: (Package Name)
Description: (Single sentence of what it does)
Version: (Version number)
Status: (Dev/Beta/Stable)
Configuration Available: (Yes/No) meaning if the mod has configurable items or not that are available this is a key question in my eyes
Configuration Recommended: (Yes/No/Not Applicable) meaning if in the Sober Distro, if the default configs are "right" for the "general standard" of the distro or if it requires configuration to meet the standard
Raw Download Link: (link to download)
Mod Discussion Link: (where to look for upstream discussion, bug chasing etc)
Known Bugs or Issues: Meaning any bugs in the Sober standard config. Issues are things of note that arent the result of a functional defect with the mod

The required package dependency order is easily explained in the profile order of the mod enabler and doesnt need mention in the table I think

I therefore propose that we add detail around each package so its clear what users can do, what is recommended to be done and so on. Users are ofcourse free to do anything and in the Linux analogy again, thats fine, its a just a distro represents a "general standard" as a yardstick for figuring how to make all this mod soup compatible.