Lucas Rocha

history | awk '{a[$2]++}END{for(i in a){print a[i] " " i}}' | sort -rn | head
130 vim
106 cd
74 ls
33 make
28 git
24 grep
19 sudo
18 rm
12 svn
11 touch

Yeah, yeah, I love vim!

It’s time to tell where I’m going. I’m sure this is not a surprise anymore to many :-)

I’m joining Havoc’s team at LiTL to work on a very exciting project.

Unfortunately,  I can’t tell anything about the project for now (actually, I think it will take some time until we can say anything). But yes, it’s GNOME-related and involves the development of a consumer product comprising hardware, software, and online services.

I’ll stay in Finland until June doing remote work and then move to London to work on a LiTL office there.

Woohoo!

The deadline for replying the roadmap info request is today and there are still quite many modules without fresh roadmap. I decided to wait on more week for the replies before starting to prepare the first draft.

Maintainers and developers, wake up! Reply today and win a nice trip to the moon! Just let me know if you haven’t seen any roadmap request in your inbox.

Google is now accepting student applications!

If you’re a university student and want to contribute to GNOME during GSoC, have a look at our GSoC wiki page, check our list of project ideas, read our wiki page with information for students, and follow the guide for student applicants!

You probably want to contribute to GNOME.
It’s so cool to be part of GNOME!
Our community will rock your world!
Join us!

In 2006, Dan Winship presented some ideas about the future of session management in GNOME. He wrote the initial code and defined this nice architecture which turns gnome-session into a more generic session management system and makes it easier to eventually replace the current XSMP-based session management with a saner and less cryptic D-Bus-based protocol in the future. On June 2007, he made a code drop on a branch called new-gnome-session and stopped working on that (for various personal reasons).

Since October 2007, I’ve been sparsely working on this new code (with full support from Dan) on my spare time by filling some gaps, fixing bugs, implementing missing features, etc. So, now the code reached a functional state and I’ve just merged the new-gnome-session branch in trunk. Vincent Untz and I will be working on making the new code shine for 2.24.

If you want to know the general ideas around the new gnome-session, read:

http://live.gnome.org/SessionManagement/NewGnomeSession

Most of the design and features described there are already implemented (if not all).

If you want to know what’s still missing and want to help us, read:

http://live.gnome.org/SessionManagement/Todo

The new gnome-session is fully compatible with current session clients (GnomeClient and others) and no code changes are required on existing apps. However, some simple changes are necessary on some basic components that run during the session such as gnome-settings-daemon, gnome-panel, nautilus, metacity, gnome-keyring, etc. I have most of the patches ready and I’ll be filing bugs for each component soon (actually, I’ve made other necessary changes in some modules during the 2.21/2.22 cycle already).

Big thanks to Dan! This important move would not be possible without his support and invaluable efforts.

There’s still a lot to do during this development cycle.

Testing and patches are more than welcome!

I really enjoyed my time at Nokia and Finland. I was very lucky to directly work with very talented and generous people. I’ve made some good friends here and it will be hard to say goodbye soon. My last day at Nokia is March 28th.

It’s too early to tell about what I’ll be doing in the near future. Exciting stuff, for sure. :-P

Update: Xan, Tommi and Johan (who doesn’t have a blog) are leaving too. See you around guys! :-)

As Adam has already announced, if you are GNOME developer and want GNOME to rock on the Google Summer of Code this year, don’t forget to add your ideas to our SoC project ideas page. We’ve got many ideas already but I’m sure we can have more. Go Go Go!

As part of our roadmap process, we’ve sent the roadmap information requests to all module maintainers/developers. If you are a maintainer/developer of a GNOME official module and haven’t received the cited message, just let us know about which modules we’ve missed.

As usual, as soon as we have a first draft of the GNOME 2.24 roadmap, we’ll heat up some discussions in desktop-devel-list about this and the future stable releases of GNOME in order to get feeback about the roadmap, discuss about potential cross-module plans, and so on.

On 2.22, we’ve made important changes in our Desktop and Platform. The upcoming 2.24 release has an important role on consolidating those changes and preparing the ground for pushing the project to new directions. Let’s make it happen!

I was just wondering why do we show disabled menu items in a context-sensitive menu? In this case, showing disabled operations to the user doesn’t bring any useful information. For example, have a look at this context-sensitive menu for a mounted USB stick in the Nautilus desktop area (see bug 522739):

What’s the point of showing all those disabled items? If it’s a context-sensitive menu, it should show only actions that make sense it that context, right?

I see the point of having disabled menu items in a main menubar for the sake of bringing awereness of all available actions in an application. However, for context-sensitive menus, it just doesn’t make any sense. Am I missing something?