As discussed at Flock, we're going to try an IRC meeting every other
week. I've setup a calendar for us on Fedocal that you can find here:
The first meeting will be in #fedora-meeting on August 27 at 15:00
UTC. I'll prepare an agenda and send it out at least one day before.
It will primarily be looking over the TODO list, but there might be
some other things on it.
I have linked to a few screenshots which I think cover my biggest issues
with Adwaita as it stands:
1) focus.png - 4 identical terminal windows. It's nearly impossible
to tell which one has focus. Sure, the titlebar text is a little darker,
and there might even be some shading around the focused window (but if
there is, it's invisible to me).
Proposed solution: Focused window should have a significantly darker
titlebar, maybe even a completely different color. I personally don't
care what it looks like (i.e. a designer should find something pretty)
as long as the visual distinction is clear.
2) eclipse.png - Eclipse with the package explorer and toolbar
visible. Look at all that white space! I'm pretty sure this is a desktop
theme issue and not an SWT issue because if I use the linked theme
(eclipse-gtkrc) as part of the GTK2_RC_FILES variable, I get the
results from eclipse2.png which is not perfect, but a *lot* better.
So maybe it's a GTK3/GTK2 issue, but either way, from a user's
perspective it still doesn't work properly.
For reference, see webstorm.png (ignore the broken kerning, I assume
that's just Swing sucking). Since Swing (I assume what's what
WebStorm/IntelliJ use) completely ignore the system theme (yay) it's a
great comparison. Personally, this is what I'd like to see my whole
system look like, except the native window title which is still gigantic.
Proposed solution: Tighten up white space all over the place. Toolbar
buttons, tabs, tree items, window titlebar, and all the other widgets
that I didn't happen to capture. I think it would still be visually
appealing (go look at a Mac, it's pretty dense and still pretty).
What do you think?
quick question I'd like to see some discussion about: Anaconda allows
setting a password to the root user, or to create a normal user during the
I think that we should hide the option to create a normal user (for the
workstation image only), since we already do this in gnome-initial-setup
where it makes more sense.
What do you think?
Does anyone know the status of the nightly compose of Fedora 21 workstation?
The builds have been failing for a while now with errors that don't make
much sense to me, and I could really use an up-to-date image to preform
testing and to evaluate our default offering.
Is anyone working on fixing this? Does anyone have an idea what causes this
This is largely directed to the WG, as a request to clarify a part of the workstation product tech spec. It relates to a thread on the anaconda list regarding os-prober, and a thread on this list regarding release criteria, both of which are referenced below.
I am cross posting to the server@ list as well, while they don't have a dual-boot requirement in their spec it stands to reason the ability to dual-boot Fedora Server/CentOS/RHEL version n and n+1 could come in handy when doing migrations while still having a fall back position. Perhaps replies should drop the other cross posting since the requirements for the two products are different? But I leave up to the person replying to decide.
The WorkstationTechnical Spec says:
"One aspect of storage configuration that will be needed is support for dual-boot setups (preserving preexisting Windows or OS X installations), since e.g. students may be required to run software on those platforms for their coursework."
1a. Does preserve preexisting include providing a working menu entry in the boot manager (e.g. in the GRUB menu)?
1b. Or is it sufficient to just preserve the installation data — meaning it's permissible for its bootability to be either non-obvious or broken?
2. If the answer to 1a. is yes, and 1b. is no, does this dual-boot requirement apply to both BIOS and UEFI?
3. If resources cannot meet the dual-boot requirement by ship time, should the installer inform the user that their previous installation will be preserved but may not be bootable?
4. Why is the preservation of an existing Linux OS, including a previous Fedora, not explicit in the spec? Should it be?
The answers to the above will help determine the scope of QA testing in this area, and avoid lengthy debate during blocker meetings. Maybe it'll provide some kick in the pants for old bugs with unimplemented solutions. Or maybe it will make it clear that the UX in this area doesn't need improvement and therefore effort testing and developing can be better spent elsewhere. So in any case, clarification will be helpful.
"grub2, 30_os-prober, os-prober: A Proposal"
Initial very rough Workstation release criteria draft
Recently I installed CentOS 7 on a workstation at a lab I work at and have
quickly become fond of an ncurses package called NetworkManager-tui. I
tried searching for this on Fedora 20 and yum reports the package cannot be
found. The package is in Fedora Rawhide, but installing it that way would
require updating nearly the entire distribution and it's not worth it.
1. Will this package be released on Fedora 20? Is this going to be a
Fedora 21 only release? If you are going to release it on Fedora 20 when?
2. Is there a way I could use Docker to install this and let it manage my
network connections on my host from a container?
3. Is Fedora 21 stable enough that I should just upgrade and not worry
Also, wanted to reach out and say that CentOS 7 is the best distribution
I've ever used and I'm counting down the days to the Fedora 21 release.
The 305million you're quoting comes from last year's Gartner report, where
they give that big number, but it's down 10% from the prior year and they
predicted another 10% fall for this year.
But check out this updated report from last month:
<http://www.gartner.com/newsroom/id/2791017> Here, they break out
traditional PCs from "ultramobiles and premium", and the traditional PC is
falling but the latter category is on the rise. They follow this up with
<http://www.gartner.com/newsroom/id/2793921>, which is were I think we find
the great new quote:
The PC market's installed based has been declining as buyers switched to
tablets and smartphones for entertainment and social media consumption.
The 2Q14 results suggest that the consumer installed base restructuring
peaked during 2013. We are seeing a slowdown in premium tablet sales,
which have already penetrated a large number of households. PCs are now
growing off a smaller installed base of newer devices, with more engaged
I think it's the "smaller installed base of more engaged users" is what's
really exciting for us.
Fedora Project Leader
Sorry, this isn't last minute yet, is it? :)
Earlier this year at DevConf, we did a session on Fedora.next, with an
overview presentation followed by a 3 minute report from each WG, and a
panel discussion. We're aiming to do this again at Flock, with a big joint
session on Friday.
Josh, you represented Workstation at DevConf -- do you want to do the
Fedora Project Leader
I recently blogged on the Fedora Magazine about the awesome addition of
the Solarized colour schemes in GEdit and GNOME-terminal in workstation
. And a commenter on that post asked the question: why not make it
Since terminal ships with the dark GTK theme turned on, we could set the
default color scheme there to Solarized Dark, and for gedit (that uses
the light GTK theme by default), enable Solarized Light by default.