It took a while but we are now able to confirm we have rooms for the November 6 – 8 GNOME Boston Summit. For Saturday and Sunday we will be in the Tang Center again (part of the Sloan School) in the same rooms as last year. Monday is a little trickier since class is in session. We may have a couple of rooms spread out on the campus. We are still working out the best options there but we will have rooms on Monday to hack in.
Please go to the 2010 Summit page and tells us you are coming!
[read this post in:
ar de es fr it ja ko pt ru zh-CN ]
Comments Off
It is really great to see this year’s GUADEC videos being released so soon after the event. Thank you Flumotion and Fluendo!!!
My only gripe is that yet again my talk’s timeslot seems to have experienced technical difficulty and is not available (the file is only 27min long). Hopefully that is just a temporary glitch.
It is still an amazing feat of engineering that such as new technology such as WebM codec was used not only to provide archives of the conference but to also stream live. Not to mention the software and codec used are both Open Source.
[read this post in:
ar de es fr it ja ko pt ru zh-CN ]
Since GNOME’s move to using git and the fact that upstream is where all the cool kids hack I have decided to move D-Feet to the GNOME servers to make it easier for contributors to contribute and users to file bugs. That doesn’t mean I’m going to fix every feature request but it does mean others can help make D-Feet more useful.
I was sort of blown away that my humble little project was being used by more people than I had realized. I was even more amazed that it was mentioned in the literature for the GNOME Developer Training Days at this year’s GUADEC.
That is not to say I think D-Feet is a particularly shining example of how a D-Bus debugging app should be written. It kind of sucks but it does fill a niche, which is why I am starting a new design process for potentially developing a better D-Bus debugger. Here is the hitch, I don’t want feature requests, I don’t want your bug reports (those can go into bugzilla), what I want is your workflow. How do you debug your D-Bus apps? What are the pitfalls, the annoyances, the most repetitive tasks that you encounter? Please head to the Workflow Design page and add your own voice.
D-Feet is a D-Bus debugger written in PyGtk+ by John (J5) Palmieri
[read this post in:
ar de es fr it ja ko pt ru zh-CN ]
