[Design-team] The boot splash - time to think about it again

[Máirín Duffy]

On Fri, 2012-10-05 at 21:45 +0200, Elad Alfassa wrote:
> > It wasn't a throbber, it was a progress + throbber.
> If I recall correctly, it was just a throbber. I need to find that
> video again.
> Fact is progress makes no sense for boot.

Progress makes plenty of sense for boot if the boot involves a
long-running process like system updates or a relabel: those do not take
5 seconds. In fact, on my Intel M5 SSD, on an Intel i7 system with 8 GB
of RAM, normal boot of Fedora 17 takes a bit longer than 5 seconds. We
used to have throbbers in anaconda (in the form of the gtk
bounce-back-and-forth / 'cylon eyes' progress bars) for long-running
processes and received a bunch of actual complaints about it, because
people had no idea how long they were expected to wait and how far along
it had gone. 

It's really unfair for you to be placed as the middleman in something so
historically contentious. It would be preferable if the folks involved
would be willing to come here and make an actual case and lead a
discussion, including the problems they are looking to solve (we've had
the same plymouth splash for many releases now and I've never seen a
single complaint about it.) When a design is complete, it's too late -
we need real collaboration and communication so others can participate.
Waiting to force things or throw them over the wall when it's too late
is not being a good community player.

Certainly, though, willfully ignoring the governance of this team,
behaving like a child in IRC, and basically failing to initiate any sort
of communication to this team isn't going to be nearly as effective as
a mature and reasoned discussion that is respectful of the project's
governance.

~m