A designer lost in Summer of Code

Although I don’t call myself a programmer, it is always nice to have a bit of knowledge of other areas in my pocket. And when it comes to web, Design and Code are so closely related that it’s hard to know only one thing.

This year I was one of the 27 lucky GNOME students selected for the coolest program of the Summer: I’ll spend the Brazilian Winter doing lots and lots of things for GNOME. My job is to Give GNOME a first class presence on the internet, and my mentor is the great Federico.

To accomplish such a proposal, I got defined five main tasks, that involves both programming and design planning:

Make the GNOME.org fully international.
WordPress was only agreed to be used as the CMS for gnome.org if it had support for localized content. Since there were no plugins that handle content translation using gettext (to integrate it with Damned Lies and use the same process that already exists for GNOME software), Lincoln Souza and I planned a plugin to make WordPress content translatable by using xml2po. Up to now it works for most of things but I’m right now finishing the plugin implementation (in fact I did a big revamp on the plugin code last week) and working on fixing all the bugs and adding features (like a nifty admin panel). With this plugin we’ll also be able to make any other wordpress-based website translatable. You can check my daily unstable code on Github.
Create a “Projects” section in the main website
This is an old idea to have in the website. The plan is to concentrate a list of cool projects that lives inside GNOME in a way that is good for users to beautifully discover each app (as a replacement of the main page of GNOME Projects, but with cooler categories filtering and graphics — and limited to projects that are useful for end-users). Each project will have a custom entry in WordPress, that will be fully editable in the website admin. The project page will be able to have some nice content about it, screenshots, rating, latest commits and latest translations (by fetching feeds), links to its website and to its mailing list.
Reorganize developer.gnome.org. Organize the content and give sufficient infrastructure for easy access and administration of this kind of information.
I still need to get in touch with the guys who take care of this. With the new developer.gnome.org, we got great improvement, but there is room for a lot more. Part of the idea to work on this comes from this discussion from Shaun McCance. His initial idea is to have an instance of WordPress that serves as a home for the development subdomain and other pages.
Migrate all the subdomains of the GNOME website to use the new layout, and polish each one to look integrated with the rest of the website ecosystem.
This is low priority, but it’s still on the list. The item is self explanatory :) . This is the current list I have of the subdomains that need love:

Create a new area on GNOME website that will focus on Community
This is be the most fun part of my proposal :) . My idea is to create a new subdomain in the GNOME website (maybe call it “community”, or “world” — as suggested by diegoe) that will group three things:

  1. The full list of members, located in the globe map (replacing this to use a much more dynamic system).
  2. Real time popping up balloons of what is happening in GNOME right now (including commits, blog posts, bug reports, wiki edits and translations). This can be done by integrating XML-RPC, REST or fetching RSS feeds will all those services. The geolocation would be known by the association of the email address. For example, if vdepizzol at gmail.com commits something, the system will know that this was done at Vitória, Brazil. The system will also have an area where the user can add himself, informing his email and other personal data. An admin area must be created to handle approval of such adds and to other minor edits.
  3. Provide a home for local groups. Now that the main website will be fully translatable, we need to find a place to keep the pages of the local groups around the world. And this subdomain looks like a great place for that.

It seems I’ll have an exciting winter :) . As you can see most of what I’m going to do for Summer of Code is still under planning. Any feedback, idea or suggestion is more than welcome!

In the following days I’ll start to post regularly about the status of each task, and what I’ll be working on. At the moment I’m working on WPPO plugin (for translation support in GNOME.org), and you can keep the updates on WPPO repository on Github.

This entry was posted in Uncategorized and tagged . Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

7 Comments

  1. Juanjo Marin
    Posted May 19, 2011 at 3:42 am | Permalink

    This plan is just awesome !!! Go for it !!!

  2. Torben Schnidt
    Posted May 19, 2011 at 4:24 am | Permalink

    Awesome! This sounds like a lot of work and I wonder if you can reach most of your goals within just a few summer weeks. Maybe Brazilian days have 48 hours, though?

    I am just a regular gnome user but I am really excited how gnome.org will represent the project after your improvements take place. Thanks in advance, good luck and have fun!

  3. Posted May 19, 2011 at 5:31 am | Permalink

    That sounds incredible. I’m looking forward to read your future progress reports. Keep up the good work!

  4. Posted May 19, 2011 at 6:06 am | Permalink

    This is a great plan! GNOME websites have been looking for some visual consistency for ages. And especially the new developer.gnome.org needs more polish. The new community subdomain would also be a nice things to ease introduction of newcommers in local groups.

    Have a nice winter ;-)

  5. Posted May 19, 2011 at 6:16 am | Permalink

    I’d be interested to hear more about your ideas for live.gnome.org.

  6. Posted May 19, 2011 at 9:10 am | Permalink

    You missed a few websites:
    http://foundation.gnome.org
    http://sysadmin.gnome.org

  7. Fred Muller
    Posted May 19, 2011 at 12:45 pm | Permalink

    You might want to get into touch with the author of this thread as well:
    https://mail.gnome.org/archives/marketing-list/2011-May/msg00011.html

    Thanks for presenting your plan.

8 Trackbacks

  1. By GSoC Weekly Update #1 on May 27, 2011 at 10:31 pm

    [...] Vinicius Depizzol Just another GNOME weblog Skip to content « A designer lost in Summer of Code [...]

  2. By GSoC Weekly Update #2 on June 6, 2011 at 2:04 am

    [...] This winter I’m part of Google Summer of Code: I’m working on improving the GNOME website. You can check all of my tasks here. [...]

  3. By GSoC Weekly Update #3 on June 12, 2011 at 3:38 pm

    [...] This winter I’m part of Google Summer of Code: I’m working on improving the GNOME website. You can check all of my tasks here. [...]

  4. By GSoC Weekly Update #4 on June 21, 2011 at 2:05 am

    [...] This winter I’m part of Google Summer of Code: I’m working on improving the GNOME website. You can check all of my tasks here. [...]

  5. By GSoC Weekly Update #5 on June 28, 2011 at 10:12 pm

    [...] This winter I’m part of Google Summer of Code: I’m working on improving the GNOME website. You can check all of my tasks here. [...]

  6. By GSoC Weekly Update #6 & 7 on July 13, 2011 at 1:41 am

    [...] This winter I’m part of Google Summer of Code: I’m working on improving the GNOME website. You can check all of my tasks here. [...]

  7. By GSoC Weekly Update #8 on July 19, 2011 at 10:05 pm

    [...] This winter I’m part of Google Summer of Code: I’m working on improving the GNOME website. You can check all of my tasks here. [...]

  8. By GSoC Weekly Update #9 & 10 on August 2, 2011 at 1:58 am

    [...] This winter I’m part of Google Summer of Code: I’m working on improving the GNOME website. You can check all of my tasks here. [...]

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>