Language Selection

English French German Italian Portuguese Spanish

Vincent Untz: Explaining GNOME 3

Filed under
Software
Interviews

The openSUSE Conference 2010 Sneak Peaks will introduce some speakers and talks to you. Today we feature the talk “Explaining GNOME 3″ from Vincent Untz.

Okay given the title of your talk, Explaining GNOME 3, i take it it will be about explaining gnome 3 right? What needs explaining there?

Ah, I guess, one thing to know about me too is that I submit talks with titles, without knowing what I’ll talk about Wink So it could well be that “Explaining GNOME 3″ turns out to be about something completely different. That being said, I might keep the submitted topic since GNOME 3 is a big step for the GNOME project, and what we are trying to achieve is not always crystal clear from the outside. There are at least two parts of the talks that I can think of right now, which will likely be of interest to the audience:

1. Why does the GNOME project need to do GNOME 3, instead of keeping the 2.x way forever? After all, GNOME 2.x is all about evolutionary steps, and that’s something we could keep doing.

2. The vision of what we want GNOME 3 to be. People do not always see the long-term vision of a project, and clarifying it does help understand the changes we’re implementing.

A third part that we feel is important is explaining GNOME Shell: it’s a big move where people feel it will directly affect their interaction with the computer

If you say GNOME 3 won’t be evolutionary, does this mean GNOME 3 will not be based on what currently is GNOME 2? After all evolution is about inheritance.

rest here




More in Tux Machines

Red Hat Announces General Availability of Red Hat Enterprise Linux 5.11

Red Hat, Inc. RHT, +0.07% the world's leading provider of open source solutions, today announced the availability of Red Hat Enterprise Linux 5.11, the final minor release of the mature Red Hat Enterprise Linux 5 Platform. Red Hat Enterprise Linux 5.11 reiterates Red Hat’s commitment to a 10-year product lifecycle for all major Red Hat Enterprise Linux releases and offers a a secure, stable, and reliable platform for critical enterprise applications. Read more

New Code Starts Lining Up For X.Org Server 1.17

X.Org Server 1.17 is planned for release at the start of 2015 and thus puts the closing of the merge window in the middle of October. While some xorg-server 1.17 code has already landed, more is on the way. X.Org Server 1.17 will continue with refining the in-server GLAMOR code that was merged with 1.16 for 2D acceleration in a generic manner over OpenGL. X.Org Server 1.17 is also looking to integrate the universal KMS mode-setting DDX driver. Keith Packard on Monday also shared several other code branches he's looking at as material for the 1.17 release. Read more

More Intel DRM Changes Queued For Linux 3.18, Including Old i830M Fixes

With the drm-next merge window for Linux 3.18 closing, Intel's open-source developers have submitted another round of changes for ultimately landing with the Linux 3.18 kernel. Intel has already sent in multiple pull requests of new DRM graphics driver code to push into drm-next for the Linux 3.18 merge window. Among the changes include various Cherryview improvements for the forthcoming low-power Atom SoC, and code clean-ups and continued Broadwell tweaks. Another Git pull request landed in drm-next over the night. Read more

Speeding up the Debian installer using eatmydata and dpkg-divert

The Debian installer could be a lot quicker. When we install more than 2000 packages in Skolelinux / Debian Edu using tasksel in the installer, unpacking the binary packages take forever. A part of the slow I/O issue was discussed in bug #613428 about too much file system sync-ing done by dpkg, which is the package responsible for unpacking the binary packages. Other parts (like code executed by postinst scripts) might also sync to disk during installation. All this sync-ing to disk do not really make sense to me. If the machine crash half-way through, I start over, I do not try to salvage the half installed system. So the failure sync-ing is supposed to protect against, hardware or system crash, is not really relevant while the installer is running. Read more