Bug#846002: blends-tasks must not be priority:important (was Re: Bug#846002: Lowering severity)

[Steve McIntyre <steve@einval.com>]

On Tue, Dec 06, 2016 at 05:04:57PM +0100, Tollef Fog Heen wrote:
>]] Ole Streicher 
>
>> On 06.12.2016 10:37, Holger Levsen wrote:
>> > And this *is* still pretty confusing, though admitly better than it was
>> > half a year ago. 
>> 
>> The current implementation has a popcon of >5000, without a single
>> complaint or confusion documented in the web within the last six months.
>> This is at least *some* empirical evidence that it is not "pretty
>> confusing", and again I would ask you to show any better empirical data
>> here to support your own point.
>
>It's confusing enough that when I've had engineers from a provider
>install Debian for me, I have ended up with a desktop rather than server
>installation.  Should I have filed a bug about it?  Maybe.
>
>I think it would be better if we moved most of tasksel out of the
>installer entirely and had an app store of some sort where applications
>and blends could all be better presented with screenshots and
>all. That's obviously out of scope for stretch, and it's not something
>that the CTTE is going to do (if nothing else because you'd be far into
>«detailed design work» territory).  This would leave the installer with
>a «Do you want a graphical UI and/or sshd?» as a question/questions,
>rather than a list of tasks, some which make less sense today (CUPS) and
>some which are cryptic (what's the difference between LXDE and
>LXQt?).

I'm not so sure. I think that what we could really do with is a more
intelligent UI here to allow for multi-level choices:

 + Desktop UI?
   + Gnome
   + KDE
   ...
 + Server tasks
   + SSH server
   + File server
   + Web server
   ...
 + Debian Pure Blends
   + Astro
     + Astro option 1
     + Astro option 2
   + Debian-Edu
   ...

etc. I've pondered about how to do achieve that with the existing
debconf code, but not got very far yet. Including more descriptive
text and maybe even screen shots with each would be very helpful.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
  Getting a SCSI chain working is perfectly simple if you remember that there
  must be exactly three terminations: one on one end of the cable, one on the
  far end, and the goat, terminated over the SCSI chain with a silver-handled
  knife whilst burning *black* candles. --- Anthony DeBoer