Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 159

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 162

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 165

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 168

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 171

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 173

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 175

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 197

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 201

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 224

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 225

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 226

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 316

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 316

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 316

Warning: Creating default object from empty value in /home/jfcouture/jfcouture.com/wp-content/themes/platform/core/library/class.layout.php on line 316
New Garden Gnome At Code Genome

What do you call someone who works at Code Genome?

Garden Gnomes

That’s right, a garden gnome. (Apparently, some British dude had trouble saying the name of our company.)

Need test? Pass drug test passing drug test.

It is with great pleasure that I announce that a new gnome has joined the team: Pierre Olivier Martel. PO is our first rails garden gnome guru-to-be. Welcome aboard PO!

Popularity: 30% [?]

 

3 Responses to New Garden Gnome At Code Genome

  1. Thanks Djief! I’m very pleased to join this great team of garden gnomes! (Can I be the middle one in the picture? He looks damn happy!) I think I’m gonna learn a lot with you guys and soon become the ninja I’ve always dreamed to be when I was kid (although it didn’t involve computers at that time!).

    • Carlo says:

      Details======= + clutter (external deeendpncy): general consensus around it and people want to play with it there’s not a lot of code depending on it right now (not sure there’ll be anything in the 2.24 timeframe) but it’s a chicken & egg problem and people have really shown interest in it => approved It’s important to not have clutter-only UIs for now (for accessibility reasons), though. + libcanberra (external deeendpncy): some +1 on the lists, and already used in some parts of GNOME would have been nice to see it come earlier in the cycle => approved + libgda (external deeendpncy): applications using libgda are not ported to 4.0 yet no real support on the mailing list => rejected For the anjuta plugin using it: we suggest to either make it optional or ship it separetely of the main anjuta module. + PolicyKit & PolicyKit-gnome (external dependencies): the plan is to have PolicyKit-gnome in the desktop set for 2.26 people are already using it and there’s some good consensus around it helps improve accessibility of security-related UIs this is a good first step towards inclusion in the desktop set later => approved + WebKit/GTK+ (external deeendpncy): lots of community support accessibility support might not be good enough (no reply from WebKit/GTK+ people) epiphany will still use Gecko for 2.24 yelp is still using Gecko at the moment (there’s a WebKit branch) devhelp trunk is WebKit-only evolution people intend to use WebKit in 2.26 we’d prefer to avoid depending on both Gecko and WebKit at the same time => rejected for 2.24, but we’ll propose a general switch for 2.26 + conduit (desktop) amazing participation of the maintainer in the discussion the major problem still is the UI, though. We think it should be mainly integrated in the applications that will use synchronization instead of being a brand new UI. we really want what conduit offers => rejected, but we bless it as an external deeendpncy so that applications can start using it, and so that it gets ready for integration in 2.26. + empathy (desktop) we only consider the application here and trust the telepathy plans to offer LGPL libraries empathy is getting some support in the community we want to start telepathy integration => approved, but the licensing question is highly important to us and we really urge the telepathy community to fix this + project hamster (desktop) well-maintained people like it the main objection is about whether we should accept all good software in official GNOME or not. The release team thinks it’s something that the 3.0 proposal aims to fix, so that shouldn’t be considered at the moment. => approved if moved in GNOME SVN SVN module should be created (bug #545049), releases should be published on the GNOME FTP and the module should be added to Damned Lies. Also following the GNOME version numbers would be good. + gtksourceview 1 (removal from desktop set) => not an issue, so removed + libgnomeprint & libgnomeprintui (removal from desktop set) Mike Kestner will work on splitting the C# bindings out of gnome-desktop-sharp => will be removed once this is done

  2. Deangelo says:

    I see great earning potential on your website.

    I browse your site often on my smartphone and don’t see any ads.
    You can monetize all your mobile traffic very easily just by installing simple wp plugin, just search in google for – Dremosny’s mobile ads plugin

Leave a Reply to Deangelo Cancel reply

Your email address will not be published. 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>