my blog

GNOME

Entries feed

Sunday 5 March 2006

Request for GNOME 2.14 screenshots

We used to have nice user screenshots gallery in the past. Users like it: they love to be able to see how software can look before downloading it and installing it. So let's have a rocking gallery for 2.14!

Thanks to the wonderful art.gnome.org team, we now have a nice page to collect screenshots. The interface don't show you how to only see some categories (yet), but here are the GNOME 2.14 screenshots. Now, everyone, please use the screenshot tool and take a great screenshot of your desktop. Then go and submit it. If you don't have an art.gnome.org account and don't want to create one, please add a comment to this post with a link to your screenshot or send me a mail.

Note that you can add a small description to each screenshot, so it's a good way to tell everyone which theme, fonts, applications, etc. you're using.

Post your screenshot now!

Sunday 12 February 2006

Setting GNOME goals (or the story of my secret plans for GNOME 2.16)

I find it quite funny that:

  • while Kjartan and I were speaking about how fixing bugs is important, John posted about "GNOME 2.16: Polish, polish, polish" for the first time;
  • while I'm thinking of some secret plans about setting small goals, Elijah is talking about the difficulty to get some focus on specific goals.

I thought a bit about John's proposition, but I don't think it will work: we all have our agenda for GNOME and forcing everyone to just fix bugs is nearly impossible. I'd love to do so, but I'm not sure it can be done. But there's something else we can do.

I believe we need some global and concrete goals. For the past few release cycles, everyone has been working in a corner, with some (limited) interactions with other people. GNOME is a project, made of lots of small projects. We're working on the small projects, but maybe we've move too far away from the GNOME project. We need to work together again. Think cooperation. Think integration. Think consistency.

A good first step is to set small concrete goals that we should all try to achieve. The goals can vary a lot, don't need to be ambitious, don't need to be about code. But they need to be achievable in a small timeframe. Let me give you some examples of goals:

  • use "Finish" instead of "Close" where appropriate;
  • make drag and drop to the trash delete the dropped object (an idea that's been here for a long time);
  • move to GOption and get rid of popt;
  • migrate to gnome-doc-utils;
  • make file choosers have a preview widget when it can be useful;
  • etc.

If we can do all this, then it will be fantastic. Those are all small steps. But a lot of small steps is great move forward. And it will make us work together. I believe this will help us, as a project.

Now, what are my secret plans for GNOME 2.16? The GG project, the GNOME Goals: find such a goal every two weeks and make people achieve those goals.

The endless -Werror debate

Davyd: no need to copy all this complex autofoo stuff in your configure.in. Just use gnome-common and put GNOME_COMPILE_WARNINGS(yes) in your configure.in.

I tend to agree that a maintainer should use -Werror if available since it helps catch some nasty bugs. Forcing everyone to use it is another thing.

Monday 19 December 2005

Planet answers

Lucas: improving our relationship with potential new contributors is indeed most important. I buy your analysis on the barriers. Let me comment on the various barriers:

  • psychological (self-esteem? unclear initial steps? project is too big?): from what I have seen (on mailing lists, but also at some events), a lot of people just think GNOME is too big for them. And most of the time, they don't know how to start. GNOME Love is a good way to destroy this myth. But to make this effort even more effective, I think we need to spread the word. This is where local groups are important: there are a lot of events where GNOME is represented and if at all those events, local groups can talk about the GNOME Love and show a concrete example on how to contribute, then this is a big win.
  • social (community is not receptive? contributions not being considered?): we have a first problem here, since it's hard for a maintainer to find time to contribute and to review contributions (be it code or ideas). It just takes too much time... I'm interested in a magical recipe to help with this.
  • technical (bad platform docs? gobject is too complicated? don't know C programming?): it seems the most difficult part is to get a first build of GNOME. jhbuild is great, but I'm sure a lot of people would love to download a simple script that would do all the jhbuild configuration for them. Might be a nice python project :-) The waited-by-everyone library.gnome.org will also help here, I believe. I don't know what's its status, though.
  • cultural (don't speak english? doesn't have local group to share knowledge/information?): local groups are really important since they can spread the word. We should definitely help them as much as possible so they don't have to do a lot of work to start. Go, GNOME-BR, go! :-)

Quim: don't you have a global vision of the GNOME websites and the online channels we are using? When I read this, I think you have the vision :-) You can be the one. I agree that it's kind of difficult to find the right place to discuss this since there are a lot of people involved, but I would think gnome-web-list is the right place. Just announce it everywhere, like on the Planet. Try this:

Are you interested in the GNOME websites? If so, subscribe to gnome-web-list!

:-)

Friday 16 December 2005

GNOME devroom at FOSDEM

GNOME will have a devroom at the next FOSDEM. You can learn all the details about devrooms, but what you need to know is that it will be a place where a lot of GNOME people will be and it will rock!

GNOME-FR people are organizing the devroom (you can even see our page for that, but it's in French :-)). To make our devroom rock even harder, we want cool talks about GNOMEy things. Christophe sent a call for talks a few days ago two weeks ago (I'm late ;-)). There are already some interesting talks:

  • gtkmm and glom, by Murray
  • GnomeMeeting, by Damien
  • the GNOME community, by Dodji and Laurent
  • Developing GNOME apps in ruby, by Laurent (not the same Laurent)
  • Gscore, one of the first application making heavy use of cairo, by Sébastien
  • Kicking arse with GNOME advocacy, by Jeff

We also had some nice ideas of talks, waiting for talkers:

  • Developing with pygtk
  • a GNOME love talk
  • why will GNOME 2.14 be our best release?
  • ...

If you want to do a talk, then you win! I don't know what you win, but to know it, send a mail to Christophe and Laurent with your talk idea.

I know you all want to come to the GNOME devroom. So, everyone, please open your calendar and mark February 25 and 26th as two days where you'll be in Brussels.

- page 27 of 36 -

by Vincent