Comment 12 for bug 1305839

So, it's been noted that this is slightly different from the desktop/ubiquity case only in that the ubiquity case presents the user up-front with the "do you want non-free stuff?" toggle on an installer page, while maas is putting it in a settings page.

So, for starters, I think the settings page is the *right* place for it to live. It's a setting. That's where I should go if I want to turn it off and on.

That said, it's a valid point that this is a setting most people won't go looking for, and it'll just be weirdly confusing when they go to install on certain hardware and it just doesn't work. Since we can't, apparently, talk certain hardware vendors (*cough*) into shipping free drivers, I proposed the following:

1) Keep the master toggle in the settings page. That's where it belongs. That's where I'd go to turn it off and on.
2) When installing the maas master node (ie: the maas package itself), present my with a debconf question that reads similarly to the ubiquity prompt, "blah blah non-free stuff, blah blah, you might need it for certain hardware support" (list specific HP servers and other things, if that's helpful to make people know they want/need the feature), default that to off, but set the priority high enough that they'll see the question.
3) Make the response to that debconf question twiddle the same config file that the settings page in the web UI does.
4) Profit.

This would, I think, satisfy the visibility issue, while not turning this into a "do we need to take this to the TB to vote it down and then try to come up with ways to compromise our ideals against usibility" argument.