When you have an idea for something to add or change in Bluefin, or maybe it is suggested to you by someone else, how do you decide whether to include it or not?
Does the project have documented principles or tenets that guide this decision making?
Different users will have different preferences for how “tricked out” they would like Bluefin to be. Many will want for it to stay very close to Fedora with only basic QoL issues addressed, others would be happy to see the customisation go further and deeper (I have seen requests for scheduler changes for example). Both are valid positions, but have different trade offs in terms of UX, robustness, maintenance burden, etc.
… but as a user, can you help me understand how the project is making these decisions, what is the threshold for acceptable deviation from Fedora, and is that documented somewhere?
Generally speaking Bluefin is complete from a feature perspective, not looking to do major layout changes or things like that. We pick a few default apps but leave most of that to the end user.
The scheduler thing is handy because it’s not a heavy lift and is just running a binary in a terminal to switch it so people can safely play. Also since Bazzite is already using it it’s much easier for us, not sure we would have pursued it otherwise.
bluefin:gts is fine being more vanilla but we want bluefin:stable to be a tad more agressive since it’s following the latest GNOME release so the scheduler stuff will land there (opt in) and we’ll see where it lands. That’s probably the only major feature we’re adding this cycle, everything else is just ingestion and maintenance.