<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.gnome.desktop">
    <title>gmane.comp.gnome.desktop</title>
    <link>http://blog.gmane.org/gmane.comp.gnome.desktop</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48948"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48944"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48942"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48927"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48926"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48921"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48920"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48919"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48911"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48909"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48907"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48905"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48904"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48885"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48884"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48871"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48839"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48811"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48784"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnome.desktop/48773"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48948">
    <title>GObject error handling questions</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48948</link>
    <description>&lt;pre&gt;1. Is there a way for a GObject constructor to fail and report an error?

2. Is it possible to attach additional information to GError (file where
the error came from, line and column)? If not, what is the standard way
to report these?

3. How to localize errors?
&lt;/pre&gt;</description>
    <dc:creator>Nikita Churaev</dc:creator>
    <dc:date>2013-05-21T01:11:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48944">
    <title>GNOME 3.8.2 Release</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48944</link>
    <description>&lt;pre&gt;Hello all,

GNOME 3.8.2 is available right now on, full of fixes, documentation and
translation updates, get its sources from our servers, or binaries from
your distribution servers, and enjoy this second update to GNOME 3.8.

We are now moving back deep into development territory, there will be
no further coordinated 3.8 releases (individual module maintainers may
still publish new stable tarballs); our next release will be 3.9.2, to
be published at the end of the month.

Our complete schedule is at https://live.gnome.org/ThreePointNine#Schedule


==============================
Release Details and References
==============================

The lists of updated modules and changes are available here:
  core   -  http://download.gnome.org/core/3.8/3.8.2/NEWS
  apps   -  http://download.gnome.org/apps/3.8/3.8.2/NEWS

The source packages are available here:
  core   -  http://download.gnome.org/core/3.8/3.8.2/sources/
  apps   -  http://download.gnome.org/apps/3.8/3.8.2/sources/

And if you want to compile GNOM&lt;/pre&gt;</description>
    <dc:creator>Frederic Peters</dc:creator>
    <dc:date>2013-05-16T08:15:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48942">
    <title>(allow-none) for properties</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48942</link>
    <description>&lt;pre&gt;Do I have to mark properties that allow NULL strings or objects with
(allow-none)?
&lt;/pre&gt;</description>
    <dc:creator>Nikita Churaev</dc:creator>
    <dc:date>2013-05-15T19:51:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48927">
    <title>Combined system status updates</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48927</link>
    <description>&lt;pre&gt;Hi all,

Me, Jon and Jakub have reviewed the combined system status designs in
the attempt to address the feedback that we've got. A fresh round of
wireframes are now on the wiki [1]. I think that they resolve the most
serious issues that have been raised.

Allan

[1] https://live.gnome.org/GnomeShell/Design/Guidelines/SystemStatus#Update_Proposal

--
IRC:  aday on irc.gnome.org
Blog: http://afaikblog.wordpress.com/
&lt;/pre&gt;</description>
    <dc:creator>Allan Day</dc:creator>
    <dc:date>2013-05-13T11:02:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48926">
    <title>Request to Bring forward one Gnome 3.6 feature</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48926</link>
    <description>&lt;pre&gt; This feature could be added for 3.10 and would be appreciated by end-users like myself

As a beta tester for Fedora 19, I did a Fedora 19  with Gnome 3.8 and subsequently added the default  KDE Desktop as well.

For testing, one user has KDE as his desktop, the other (me) Gnome.

Justification


So, how many icons did I find in the Gnome ALL area?

If you do select all that a "yum groupinstall"  will do for gnome and kde, the number I achieved was 183.

On my computer I show 30 icons per screen, so to peruse the ALL list I had to browse screens.  
The ALL display shows only the program names in alphabetical sequence, with games, wordprocessors, and other applications shown intermingled.  Searching by scrolling takes time.

Frequent or Recent
Eventually Frequent or Recent fills with 30 entries. If we can't find the program in the thirty, we have to select ALL, and scroll the 183 icons.   

We still use desktops and mouses, or synaptic pads on laptops.  That scrolling is necessary as there is no grou&lt;/pre&gt;</description>
    <dc:creator>Leslie S Satenstein</dc:creator>
    <dc:date>2013-05-12T19:48:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48921">
    <title>The problem of GNOME3 is not the GNOME Shell</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48921</link>
    <description>&lt;pre&gt;Hello!

This message contains some proposals to address what I see as some
problems in GNOME 3 and the GNOME release process. I send it originally
to the mailing-list gnome-devel-list, which was wrong because it's topic
are the libraries of GNOME.

The dash, the overview, the efficient keyboard usage and the clean
notification-area with the seperation from the message-tray are just a
great approach. GTK3 looks awesome within GNOME3! It was brave to give
up the old concept of an "Desktop" and replace it. And it was the right
decision!



Please don't take the following explanation as attack on you or your
work. What I want is helping you and GNOME!

The problem of GNOME3 is not the GNOME Shell, it is the constant removal
of features. To make this even more worse, the developers don't
communicate their plans and didn't react on well meant critic. Instead
the developers believe that the bloggers, the press or the users just
hate new things like the GNOME Shell[1].

GNOME 3.0 introduced a complete new user-inter&lt;/pre&gt;</description>
    <dc:creator>bugs</dc:creator>
    <dc:date>2013-05-12T15:35:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48920">
    <title>The bunch of examples</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48920</link>
    <description>&lt;pre&gt;I will keep this short! Not. I tried but failed! So please pick what
you are interested in. And don't take it personal. I can only apologize
for my own unfair and unpolite behaviour.

// nautilus - create empty file
Every file-browser does manage files, this includes the creation of
"empty files", not only "empty directories". This function was removed
with "3.6". Nautilus doens't fullfill the basic requirement of a
file-browser. This is wrong!
Instead users are forced to use the XDG-Directory "Templates" to create
a template for an empty file. But that is not possible, because for this
you need to create an empty file. This is weird!

Bug reports:
https://bugzilla.gnome.org/show_bug.cgi?id=324253
https://bugzilla.gnome.org/show_bug.cgi?id=676838
https://bugzilla.gnome.org/show_bug.cgi?id=683735
Screenshot:
http://i.imgur.com/CkkOlSL.png
Example:
Create an empty file "main.cpp", which can be double-clicked and edited
within Gedit with propper syntax-hightlighting.
Proposal: "Create empty file" should just be&lt;/pre&gt;</description>
    <dc:creator>bugs</dc:creator>
    <dc:date>2013-05-12T15:41:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48919">
    <title>TARBALLS DUE: GNOME 3.8.2</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48919</link>
    <description>&lt;pre&gt;Hello all,

It's time for a second update to the 3.8 version, many modules got
new fixes, translations, and documentation, let's give those to our
users.

Tarballs are due on 2013-05-13 before 23:59 UTC for the GNOME 3.8.2
stable release, which will be delivered on Wednesday. Modules which
were proposed for inclusion should try to follow the unstable schedule
so everyone can test them.  Please make sure that your tarballs will
be uploaded before Monday 23:59 UTC: tarballs uploaded later than that
will probably be too late to get in 3.8.2. If you are not able to make
a tarball before this deadline or if you think you'll be late, please
send a mail to the release team and we'll find someone to roll the
tarball for you!


For more information about 3.9, the full schedule, the official
module lists and the proposed module lists, please see our colorful 3.9
page:
   http://www.gnome.org/start/unstable

For a quick overview of the GNOME schedule, please see:
   http://live.gnome.org/Schedule


Cheers,

        Fre&lt;/pre&gt;</description>
    <dc:creator>Frederic Peters</dc:creator>
    <dc:date>2013-05-12T09:10:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48911">
    <title>start contributing to GNOME</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48911</link>
    <description>&lt;pre&gt;Hi everyone!

I am Puja Singh,a third year undergraduate from Netaji Subhash Engineering
College,Kolkata,India.

I have been wondering for quite a few time to start contributing to GNOME,
specificaly on projects like GCompris and Banshee.

I already have gtk and the necessary libraries installed in my machine,and
I have started to get familiar with the environment. I also joined the
Gnome translation team(Hindi),a few weeks back,though I would really love
to contribute technically.

Here are few of my works,(not great) I have been working upon lately:

1. http://avenirnsec.com/ (the website of my college's annual tech fest)
2. my github profile ( https://github.com/Puja0708 )
3. working on cloud computing for last 1.5 years,and have a paper published
in a Springer journal ( LNISCT , conference by IDES and ACEEE ).

Kindly consider me to be guided properly to be able to be a regular
contributor to Gnome.

Thankyou
Regards
Puja
_______________________________________________
desktop-devel-list mailing list
des&lt;/pre&gt;</description>
    <dc:creator>Puja Singh</dc:creator>
    <dc:date>2013-04-19T10:16:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48909">
    <title>gnome 3.8.1 files</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48909</link>
    <description>&lt;pre&gt;hi

i just wanted to know what files i need to download, the order i need to
compile to make, maybe, a single .deb and .rpm file of the gnome 3.8.1
desktop enviroment


http://ftp.gnome.org/pub/GNOME/core/3.8/3.8.1/sources/

thank you!
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list&amp;lt; at &amp;gt;gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list&lt;/pre&gt;</description>
    <dc:creator>W S</dc:creator>
    <dc:date>2013-04-24T01:04:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48907">
    <title>ANNOUNCE: New mailing list for Infrastructure-related announcements</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48907</link>
    <description>&lt;pre&gt;Hi,

lately I've been thinking about what could be the best way to announce
Infrastructure-related maintenances, downtimes, outages. As of now I kept
sending my mails to multiple mailing lists at once (foundation-list,
desktop-devel-list, devel-announce-list) but I feel that wasn't the best
way to achieve my goal.

As of today, a new mailing list exists for these kind of announces [1],
someone could argue that this is yet-another-mailing-list but I'm
completely sure that having a specific and targeted mailing list will
definitely help everyone out. The improvements:

1. subscribing to the new list will make sure that you don't lose any
maintenance, downtime, outage announcement
2. you can track when a specific maintenance will happen or has happened in
the past and what was done.
3. the GNOME Sysadmin team has finally a place to send its announcements to
making sure they reach the wider audience as possible.

Have an awesome day and please take a little minute to subscribe to the new
list.


[1] https://mail&lt;/pre&gt;</description>
    <dc:creator>Andrea Veri</dc:creator>
    <dc:date>2013-05-08T14:34:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48905">
    <title>Background Opacity in gnome-terminal 3.8.1</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48905</link>
    <description>&lt;pre&gt;Hi

I'm wondering why background opacity feature was removed in
gnome-terminal 3.8.1? From the bug report
https://bugzilla.gnome.org/show_bug.cgi?id=695371 , it seems that this
feature was removed on purpose. However, I couldn't find any further
explanations on why this great feature was removed.

Maybe we should bring it back? My personal usage of this feature is
status bar in Emacs. Status bar in Emacs was set to be black
background with white text. So if there is some opacity in the
terminal, I was able to see the status bar and minibuffer more
clearly.

Are there any other concerns?

Thanks
Mike
&lt;/pre&gt;</description>
    <dc:creator>Mike</dc:creator>
    <dc:date>2013-05-07T00:55:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48904">
    <title>GNOME 3.9.1</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48904</link>
    <description>&lt;pre&gt;GNOME 3.9 development is starting up, with the 3.9.1 snapshot that is
marking the beginning of this development cycle. Features are still
being proposed and discussed [1].

To compile GNOME 3.9.1, you can use the jhbuild [2] modulesets [3]
(which use the exact tarball versions from the official release).

[1] http://live.gnome.org/ThreePointNine/Features
[2] http://library.gnome.org/devel/jhbuild/
[3] http://download.gnome.org/teams/releng/3.9.1/

The release notes that describe the changes between 3.8.1 and 3.9.1
are available. Go read them to learn what's new in this release:

core - http://download.gnome.org/core/3.9/3.9.1/NEWS
apps - http://download.gnome.org/apps/3.9/3.9.1/NEWS

The GNOME 3.9.1 release is available here:

core sources - http://download.gnome.org/core/3.9/3.9.1
apps sources - http://download.gnome.org/apps/3.9/3.9.1


WARNING! WARNING! WARNING!
--------------------------

This release is a snapshot of early development code. Although it is
buildable and usable, it is primarily intended f&lt;/pre&gt;</description>
    <dc:creator>Matthias Clasen</dc:creator>
    <dc:date>2013-05-03T23:48:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48885">
    <title>GNOME throbber inconsistencies?</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48885</link>
    <description>&lt;pre&gt;Hi,
The GTK+ throbber is a dotted animation, but the one used in clutter apps / UIs use a different icon - instead of dots, it uses longer lines. Is this a design decision? If it is please consider the points made below:
    - It is inconsistent without an obvious reason as to why this is

    - The clutter-themed throbber is also used in the Adwaita cursor theme (forked from DMZ-Black(?)), and with the lines which are thicker than the dotted GTK one, it makes the cursor look excessively cluttered (pun not intended), especially in the in progress cursor (I don't know what it is called, but it is the one in between the (O) loader, in Windows it is the Hourglass, and  in OSX it is the spinning beach ball, and the normal cursor. It is basically the normal cursor with the circle attatched. It takes up nearly all space in its allocated circle). See  the second and third cursors from the following link for case in point:
        http://codzoyer.deviantart.com/art/Adwaita-Cursors-for-Windows-208885897

In my opinio&lt;/pre&gt;</description>
    <dc:creator>Marco Scannadinari</dc:creator>
    <dc:date>2013-04-30T16:41:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48884">
    <title>3.9.1 tarballs due</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48884</link>
    <description>&lt;pre&gt;The development cycle inexorably marches on, and without anybody
noticing, the 3.9.1 release is already upon us ! I hadn't noticed this
until today, so I'll extend the tarball deadline until tonight, and
hope that we can get at least a few releases done.

Sorry for the late notice,

Matthias
&lt;/pre&gt;</description>
    <dc:creator>Matthias Clasen</dc:creator>
    <dc:date>2013-04-30T16:02:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48871">
    <title>gnome-control-center/panels/wacom - button mapping panel</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48871</link>
    <description>&lt;pre&gt;
I hope to do some work on wacom tablet button mapping in gnome control
center. First mockup of new individual button mapping panel:
http://firszt.eu/wacom-icons/mockup_of_wacom__button_mapping_panel.png

Roadmap: 
1. Change existing panel to simple button list + add a new panel
activated after clicking on a button (mockup)
2. First version would include only existing or already coded features -
single keystroke, on screen help, monitor switch, OLED labels matching
mapping. The last one is waiting for review on bugzilla.
3. Add option to edit label i.e. to show "Save" instead of "Ctrl-S" on
tablet
4. Add option to select an icon instead of label.
5. Implement keystroke sequences.

Please let me know what do you think about it.

P.S. Sorry for the noise if you got this email twice
&lt;/pre&gt;</description>
    <dc:creator>Przemo Firszt</dc:creator>
    <dc:date>2013-04-28T15:33:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48839">
    <title>New GnomeGoal proposal: InstalledTests</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48839</link>
    <description>&lt;pre&gt;See:

https://live.gnome.org/GnomeGoals/InstalledTests


I'm in the process of transitioning to that page from
https://docs.google.com/document/d/1DXgGEKTbC4ed1DFW3Mu-48TpHtq-xdfhDtwoUOWWcHg/edit

Comments appreciated; I have prototype branches of gnome-ostree,
gnome-desktop-testing, and gjs that implement this, but it's all subject
to change.
&lt;/pre&gt;</description>
    <dc:creator>Colin Walters</dc:creator>
    <dc:date>2013-04-25T14:21:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48811">
    <title>A doube about gvariant</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48811</link>
    <description>&lt;pre&gt;Hi:

         I have a doubt about the use of gvariant.

         In the source file: glib-2.34.3/gio/tests/gdbus-test-codegen.c:860,
foo_igen_bar_call_test_primitive_types_sync uses a address of
ret_val_bytestring, which is a local variable which type is gchar *. After
function returns, ret_val_bytestring will be pointed to a memory section,
and I know this section is got from a inner gvariant variable. But does
someone can tell me when and how should I release this memory?

         Any suggestion is appreciate!

 

fred

 

---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) 
is intended only for the use of the intended recipient and may be confidential and/or privileged of 
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is 
not the intended recipient, unauthorized use, forwarding, printing,  storing, disclosur&lt;/pre&gt;</description>
    <dc:creator>jiangpengfei</dc:creator>
    <dc:date>2013-04-23T09:21:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48784">
    <title>Touchscreen Compatibility [was: Feature proposal: combined systemstatus menu]</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48784</link>
    <description>&lt;pre&gt;Hi Alberto,

Alberto Ruiz &amp;lt;aruiz&amp;lt; at &amp;gt;gnome.org&amp;gt; wrote:

It is a bit, so I'm moving this to a new thread. Touch compatibility
is only one of a host of drivers for this proposal.

I'll respond to your comments regarding the system status proposal
itself in the original thread.


There has certainly been discussion in the past. We talked about it
last GUADEC during one of the BoFs, for example.

I agree that it's difficult to be completely agnostic when it comes to
input devices. That said, the number of devices shipping with touch
screens in combination with other input devices is on the increase. I
think it would be a really bad situation if people wanted to install
GNOME on their laptop, would be unable to use their touchscreen with
it.

So as an initial goal, I'm hoping that we'll be able to have a good
form of touch compatibility, with a target of laptops with
touchscreens.

I don't think we have the resources to create several versions of
GNOME for different types of devices.


To a certain extent we do have &lt;/pre&gt;</description>
    <dc:creator>Allan Day</dc:creator>
    <dc:date>2013-04-22T15:26:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48773">
    <title>Feature proposal: combined system status menu</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48773</link>
    <description>&lt;pre&gt;Hi all,

This is something that me, Jon and Jakub have been thinking about for
some time, and is now at the stage where we can start to think about
implementation. I'm proposing it as a feature for 3.10 [1].

The main element of the design is to combine the sound, network,
bluetooth, power and user menus into a single menu. This will enable
us to resolve a number of UX issues we've encountered with the
existing design (badness on touch, difficulties having the user name
in the top bar, lots of complexity in some menus, like network,
virtually none in others, like sound...). It will also give us greater
flexibility, and will allow us to deal with some features - like
airplane mode - in a more elegant and discoverable manner.

More details are outlined on the wiki [2]. If you do look at the
designs, please pay particular attention to the example scenarios -
these give a clearer idea of what the menu will actually look like.
The designs aren't finalised yet, so comments and ideas are welcome.

It should be said&lt;/pre&gt;</description>
    <dc:creator>Allan Day</dc:creator>
    <dc:date>2013-04-22T13:36:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnome.desktop/48772">
    <title>GIT MAINTENANCE: 23th Apr, 11:00 - 12:30 GMT+2</title>
    <link>http://comments.gmane.org/gmane.comp.gnome.desktop/48772</link>
    <description>&lt;pre&gt;Hi,

I'm currently migrating git.gnome.org to a new machine, there will be a
little downtime tomorrow 23th April from 11:00 - 12:30 GMT+2.

The service involved will be shutdown to prevent any data loss during the
move. As always I'll make sure to follow-up this e-mail to confirm that the
move went smoothly.

Have an awesome day,


&lt;/pre&gt;</description>
    <dc:creator>Andrea Veri</dc:creator>
    <dc:date>2013-04-22T12:46:15</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.gnome.desktop">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.gnome.desktop</link>
  </textinput>
</rdf:RDF>
