community


Are you getting excited?  GNOME’s flagship conference, GUADEC, is taking off in a little over a week in Den Haag, The Netherlands.  I’ve got my bags packed and a draft of my talk written.

With one more concert tonight in New York City, I set off tomorrow evening for a much needed vacation in Macon, France where I will be learning classic French cooking at Robert Ash’s cooking school.  The first lesson happens on my birthday, when I will be turning a nice and ripe 33.  Fresh fare such as bar à la crème de fenouil avec ses pommes dauphinoises, confit de canard, and profiteroles au chocolat, among others are set to be learned.  I’ve been playing with the idea of having a fund raising dinner with all the proceeds going to the GNOME Foundation during this year’s Boston Summit.  Perhaps after the course I will feel confident enough to trade donations for my cooking.

Afterwards there are a couple of days of layover in Amsterdam between when the course ends and GUADEC begins.  At GUADEC I am going to be devoting most of my time to whipping PyGObject into glorious introspection shape.   Please join us at the BOFs to learn more, help us hack or get help porting your apps to utilize the power of introspection.  There will be a BOF on general GObject Introspection on Monday the 26th between 14:00-16:00 and on PyGObject(PyGI) on Thursday the 29th between 14:00-18:00.  Otherwise you can find myself or any of the other introspection and GNOME python hackers any time during GUADEC.  If you are a newbie developer looking for something to hack on to get your name out there while learning some core GNOME technologies,  there are some really easy bits to sort of take control of and run with.  There is a lot of detail work such as fixing annotations or doing simple overrides that would take little effort to get up to speed with but make a huge impact on the final quality of the introspected bindings.  Heck, find me over a glass of beer at one of the after parties and I will wax poetic on the thing needed to be done to finish the last mile of our Python plans.

After GUADEC, Colin Walters and I will be travelling to Berlin, both to save airfare by flying out on a weekday and to decompress after a week of non-stop hacking.   I’m looking forward to seeing many old friends and making new ones.  Let’s make GUADEC rock and continue to push GNOME to continue to excel at excellence.  With this year’s focus on GNOME 3 and the underlying technologies that support it there will be a lot of exciting things to see and hack on.

GNOME Foundation Sponsored

Im attending GUADEC!

[read this post in: ar de es fr it ja ko pt ru zh-CN ]

I will be at Farmingdale College tonight giving a talk to LILUG.  It is a draft of my “The Future is JavaScript” talk I will be presenting at GUADEC in a little over two weeks.  I will also be talking about what it has been like working for an Open Source company for the last five years, along with how to get started working within the community.

[read this post in: ar de es fr it ja ko pt ru zh-CN ]
Source: English Wikipedia, original upload 3 August 2004 by Finlay McWalter

Source: English Wikipedia, original upload 3 August 2004 by Finlay McWalter

I’m double checking now but as of this afternoon I was told we have two rooms in the Stata Center and one in Walker, November 6th-8th. I’ll post details and final confirmation as soon as I get them. Thanks goes to Walter Bender and Felice Gardner for all the leg work.

[read this post in: ar de es fr it ja ko pt ru zh-CN ]

I’ll be heading to GUADEC this year thanks to the generous support the GNOME Foundation Travel Committee but that won’t be my first stop in my mega marathon travelling month of July.

  • I will first be travelling to NY around the 8th for the God Street Wine reunion concerts and will be making a pit stop at the Long Island Linux Users Group to give a dry run of my GUADEC talk entitled “The Future is JavaScript” which will continue with my theme from last year of continuing to meld the GNOME Desktop with the web platform (this year focusing on what JavaScript brings to the table)
  • I fly out of JFK Airport on the 17th for Lyon France where I am taking the week long Robert Ash cooking course at Rue du Lac in Macon, Burgundy
  • The class ends on the 23rd and my Hotel is booked for the 25th in The Hague so I am not quite sure if I will stay in Lyon or start my way up.  I know I have some GNOME friends living between Lyon and The Hague so I am offering to cook dinner for anyone who will let me crash at their place for a couple of days before GUADEC.
  • And then there is the main event – GUADEC.  My talk is on Wednesday the 28th at noon.  It shouldn’t be missed.
  • To relax a bit more, save money on airfare and because I love Germany, I am heading to Berlin for a couple of days before flying back to the US

If anyone is going to be in any of the areas I will be in and wants to hang out.  Let me know and I’ll see if I can make time.

[read this post in: ar de es fr it ja ko pt ru zh-CN ]

I’m going to be starting the process for setting up the Boston Summit. That basically means getting the space at MIT and then a budget from the board. Last year we saw an issue with the timing of other GNOME related conferences. This year we have a choice of two dates – the usual Columbus day weekend, October 9th-11th or piggyback the weekend after the Linux Plumbers Conference, November 6th-8th.

I’m leaning towards keeping Columbus day weekend because it is easier to get rooms, and it reduces confusion by having it at the same time every year.

The reasons for piggybacking the Plumbers Conference is that a number of our fellow GNOMies will already be in Boston and we might get a few stragglers from other parts of the Linux stack to stop by and offer their perspective.

I want to get the foundation members’ opinion on this. Ultimately it will be up to the board to make a final decision but I plan to have a concrete date by the middle of June if not sooner.

I hope you are all getting excited to reflect on the work done in the past year and plan the future of the GNOME platform. I hope to see as many of you as possible at GUADEC and the Boston Summit this year!

[read this post in: ar de es fr it ja ko pt ru zh-CN ]

What a week. Get six smart people in the same room together, spend a little bit of money to get them there and get them comfortable, and good things happen. An in-depth praise for the hackfest process, which the GNOME Foundation Board has been putting more and more resources into every year, will have to wait until another blog post. Right now I want to thank our sponsors and quickly recap what was accomplished. First out sponsors, who made this possible:

  • The GNOME Foundation board for providing the framework for the hackfest and travel assistance to Tomeu
  • OLPC for providing us free space and all the water we could drink at their office in Cambridge.
  • Canonical for making sure we were awake after the social events by providing us with coffee
  • Red Hat, for feeding us with a nice Portuguese meal which we shared with the D-Conf/GSettings hackfest guys who were sponsored by Novell
  • Myself, for sponsoring a couple of after hours social events to keep us all sane and allow us to discuss the future in a more social environment

I would also like to thank Walter Bender for helping us find a venue and Jeorge Castro for being the liaison between us and the Foundation. He is off to a great start as the newest Board Member.

Now to the meat of what was accomplished:

  • PyGI saw its first formal release
  • We suckered relative new comer Zack Goldberg into ongoing maintainership of PyGI
  • Cairo, callback and virtual function support was added to PyGI
  • pygobject and pygi both sprouted py3k branches on GNOME’s git servers which both fully compile and pass their unit tests (which probably means we need more unit tests). We aren’t going to move these to master for some time. But if you grab the branches and test them out the process will be much quicker.
  • We were written up in Ars Technica

Right now I am porting D-Feet to use PyGI and will be testing out my D-Bus Python py3k branch after I get that up and running. D-Feet is a good test because it uses the GenericTreeModel from PyGtk as well as GtkBuilder elements. In both cases I have found places where I have had to add overrides to PyGI to complete the bindings. For instance, in the Builder I need to override gtk_builder_connect_signals which in C searches for C symbols which match symbols in the XML description file. This is useless in Python so I need to modify it to work the same way PyGTK works. Namely, by being able to pass in a dictionary or object with name/python function mappings (e.g. {’on_click’: on_click_handler}). It is not all that hard, especially since PyGI overrides are written in Python and not in C like PyGtk overrides. However I do have to get the exception behaviour correct so that might take some time.

All and all we are in excellent shape so start porting your apps and file bugs!!!

[read this post in: ar de es fr it ja ko pt ru zh-CN ]

For those of you who haven’t seen Tomeu Vizoso’s blog on the hackfest we are trying to pull together this is a second call to PyGObject, Python 3 and GtkIntrospect hackers who might want to join us in getting the future of the Python bindings to GTK sorted out.

At issue are a couple of roadblocks to the continual maintenance of the the bindings. First is the lack of support for Python 3.0 and second is the unclear picture of how GNOME 3 effects us. The current plan is to finish the work done on PyGI (Python GObjectIntrospect support for PyGObject), at the same time making sure it all works under both Python 2.x and Python 3.x. Moving to the PyGI bindings should make the maintenance burden somewhat lighter for our busy maintainers.

If you have something you can contribute and are interested in attending our hackfest please take a look at the wikipage and e-mail myself or Tomeu. While this is being sponsored by the GNOME Foundation, you don’t need to be a Foundation member to be considered for an invite. We hope to be finalizing things soon and getting a budget to send to the board for approval.

[read this post in: ar de es fr it ja ko pt ru zh-CN ]

Many people feel that in the open source/free software community openness is about letting everyone become privy to any comment/decision/situation that may happen within a project. For the most part this is the goal we strive for but at the end of the day there are things that should remain private until they become real concerns for the public at large.

The issue is we have diverse communities that rarely agree 100% even among the best of friends. It becomes counter productive when these disagreements become the source of misinformed news articles without general consensus allowed to form within the community itself.

Forget the community for a minute. As individuals we often need to think before we speak in order to make sure we say exactly what we meant to say. The same goes for diverse groups. They must work out the directions they go in in an atmosphere that is free from the chilling effect of having to watch what they say because their intentions may be misinterpreted.

There is also the point of being able to freely express an opinion without fear of outward reprisals. There is a reason Democracy subsists on the concept of private ballots. It allows even the most unpopular opinions to at least be registered while individuals can be sure they won’t be ostracized. The openness comes from being free to dispute results, protest and influence them through public action, not from knowing the individual’s specific vote.

We strive to be inclusive with everyone who has a stake in what we do but when it becomes counter productive one needs to redress the situation so that we continue to move forward. It does no one any good to dwell on speculation from quarters which are ill informed and just looking for traffic grabbing sensationalism. It is perfectly fine to exclude them from discussions they have no stake in and let them feed on the results, judging the community based on its final actions and consensus.

[read this post in: ar de es fr it ja ko pt ru zh-CN ]

For those who are going to FUDCon on the FUDBus, expecially those flying to Boston first, remember to bring your Passport.  Luckly these days they check both ways but at one point you could get into Canada without a passport but would be screwed on the way back. In any case I thought I would remind people as I had run into a problem where I didn’t check for my passport until a week before my sisters wedding in Italy. Sure enough I couldn’t find it and ended up having to get it done the night before I left. Not to mention the years it took off my life trying to figure out the best way to tell my twin sister I might not be able to make it to her wedding :) See you all at FUDCon!!!

[read this post in: ar de es fr it ja ko pt ru zh-CN ]

Having followed its development for a long time now and used other video editing software I can say that PiTiVi is an awesome app that is only going to get better. Sure it isn’t perfect yet but that is software development for you. It takes time to get all the features in and make them solid.

One of the great parts of Open Source Software is you get to see it develop and grow. It is also one of the biggest misunderstood aspects of such software. In a world where people are gripped by the next best thing – a collective psychosis of product ADD – where patience is no longer a virtue but an outdated notion of an age long gone, evolution is about as exciting as watching paint dry. Just a reminder that even products that seem to just appear overnight, in reality had long periods of closed development to receive polish (and even then they aren’t always great but for some reason people tend to forgive shortcomings in something they bought as opposed to something they got for free).

Knowing the drive behind the developers working on PiTiVi I am confident that in time PiTiVi will become one of the prime examples of FOSS development. For now it is useful enough for some my basic editing needs and every time I try a new version it just gets that much more useful. Keep up the hard work!!!

[read this post in: ar de es fr it ja ko pt ru zh-CN ]

Next Page »