Older blog entries for oubiwann (starting at number 267)

4 Oct 2011 (updated 4 Oct 2011 at 20:02 UTC) »

Two Months at BlueLibris

Back for a Quick Write

Well, I've been at BlueLibris for two months and a day, now... and each one of those days I've wanted to blog about something that's happened. On occasion, I've G+'ed about something, but in general I've just been too busy to take a breath, much less use that breath to write some informal prose.

I've taken a few photos during this time, and put them up on flickr in this set; smaller versions are peppered throughout this post :-)

The First Day

Half Moon Bay, about 30 minutes from work.
I was born in California, but left when I was 8 years old. I returned after high school and lived for 2 years (1990-1992) in Northern California to attend language school. As a consultant and later an employee of various companies, I made regular trips out to the Valley and Bay Area, so was no stranger when I arrived in August this year. However, it was quite a shock to be actually working and living here!

After I left Canonical, I headed out from Colorado and took a few weeks off to go on a meditation retreat up in the Siskiyou Mountains of Oregon. This area was deeply reminiscent of the Colorado mountains, of which I am so fond. Such environs are my natural habitat... so imagine my shock when I was hurled 50 years into the future, deposited in something like a night scene from Bladerunner. 'Cause that's exactly how it felt :-) Not bad... just very, very different. Even though I'd been to the Valley a bunch of times in the past 10 years or so, it never really hit home... until it was my home.

Note the executive dress: shorts and flip-flops.
In the morning, the bright sun washed away visions of flying cars and robots. I was greeted by palm trees and traffic. After an hour commute from the East Bay to Menlo Park, what I had only seen in Google Maps was now staring me in the face: my new office building :-)

I had arrived early at 9:00am, so the place was locked up tight. I took that opportunity to meet some of the neighbors, walk around a bit, and then read up on the interesting facilities we were renting for our offices.

The text describes the facility's power.
I'd seen the solar panels of the building in the Google Maps satellite view, and had just assumed that this was a common accoutrement of California architecture. Turns out, our entire complex is soloar powered -- 100%! Our laptops, servers, monitors, microwave, fridge, and air condition all run on the Sun :-) This info was covered in great detail by one of the boards posted out in front of our small office complex.

Eventually, Soroush showed up, I introduced myself, and we made our way inside. The interior was even cooler than the exterior :-) There's a large open space where most people sit, a dark cave for the software engineers, an unused loft upstairs that looks down over the open space, and a cute little kitchen area adjacent to (and part of) the loft.

The Intervening Weeks

Within a day or two, I'd purchased some bean bags, nerf guns, nerf balls, action figures, and die cast cars. It was starting to feel like a start-up :-) (And the nerf gun fights reamain a regular brain-break for many of us!). A few days after that, Tim Hyland bought some sling-shot monkeys... I think we use these even more than the nerf products!

Playtime aside, the work has been very grueling. We all work late hours (but have a good time hanging out while we do so), wear many hats, and have more responsibilities than we care to enumerate. Equally, however, we're all deeply invested in the company, believe in the services we're providing to the health and other industries, and most of all are committed to the success of the company.

On that note, most of us were involved in ventures during the dot boom/bomb, and accrued wisdom from that area on how to conduct ourselves responsibly, even in the midst of all the excitement our innovations are generating.

I look forward to the time (soon!) when I'll be able to post more about these :-) For now, though, I can be very general and give a brief overview of our tech.

Our Technology

Matt playing along with a thumbs-up :-)
I worked on several device projects for Canonical, but never were we actually building our own hardware like we do at BlueLibris. This has been a fascinating introduction to a part of the tech world with which I am starting to gain some familiarity: circuitry design, component integration, plastics work -- the list goes on and on. Soroush Salehian and Matt Maibach lead these efforts, with Ram Fish weighing in regularly with his extensive EE background. These are the guys iterating on the hardware for our real-time, 3G health monitoring device.

As events are generated on the device, they get pushed up to "the cloud" where additional processing and heuristics are performed. We're working with lots of maths, machine learning, custom algorithms, etc., all in a distributed computing environment. We're using nosql solutions for long-term storage, and a Python-based framework for web management tools. We're in the process of converting the original application into a JavaScript-driven suite of applications. We're also giving the Python an overhaul in anticipation of significantly increased load and general usage over the next year (we've got some exciting partnerships and customers -- both existing and forth-coming). Henry Messenger and myself are working on these bits right now. To get the device talking to the cloud and collecting all the right data, we have the talented Kent Ryhorchuk hacking like a madman and consuming the APIs we're providing him.

There are other software development efforts in the works that I can't really talk about... but given the space, I'm sure you can imagine the possibilities :-)

Future Posts

I've run out of time for now, but I do want to mention that with BlueLibris, there is a tantalizing connection to where I see technology going in the next 10-20 years (ultra large-scale systems), and I'd like to say more about that soon. Furthermore, we should have some nice news-worthy items that will get their own press releases, but I'll be making community-friendly updates here on that as well. I'm also taking steps to make sure that we contribute back to the open source community, and will have posts relating to those efforts as well.

So watch this space, and look for more developments soon... :-)


Syndicated 2011-10-04 18:41:00 (Updated 2011-10-04 19:58:53) from Duncan McGreggor

Two Months at BlueLibris

Back for a Quick Write

Well, I've been at BlueLibris for two months and a day, now... and each one of those days I've wanted to blog about something that's happened. On occasion, I've G+'ed about something, but in general I've just been too busy to take a breath, much less use that breath to write some informal prose.

I've taken a few photos during this time, and put them up on flickr in this set; smaller versions are peppered throughout this post :-)

The First Day

Half Moon Bay, about 30 minutes from work.
I was born in California, but left when I was 8 years old. I returned after high school and lived for 2 years (1990-1992) in Northern California to attend language school. As a consultant and later an employee of various companies, I made regular trips out to the Valley and Bay Area, so was no stranger when I arrived in August this year. However, it was quite a shock to be actually working and living here!

After I left Canonical, I headed out from Colorado and took a few weeks off to go on a meditation retreat up in the Siskiyou Mountains or Oregon. This area was deeply reminiscent of the Colorado mountains, of which I am so fond. Such environs are my natural habitat... so imagine my shock when I was hurled 50 years into the future, deposited in something like a night scene from Bladerunner. 'Cause that's exactly how it felt :-) Not bad... just very, very different. Even though I'd been to the Valley a bunch of times in the past 10 years or so, it never really hit home... until it was my home.

Note the executive dress: shorts and flip-flops.
In the morning, the bright sun washed away visions of flying cars and robots. I was greeted by palm trees and traffic. After an hour commute from the East Bay to Menlo Park, what I had only seen in Google Maps was now staring me in the face: my new office building :-)

At 9:00am, I had arrived early, so the place will locked up tight. I took that opportunity to meet some of the neighbors, walk around a bit, and then read up on the interested facilities we were renting for our offices.

The text describes the facility's power.
I'd seen the solar panels of the building in the Google Maps satellite view, and had just assumed that this was a common accoutrement of California architecture. Turns out, our entire complex is soloar powered -- 100%! Our laptops, servers, monitors, microwave, fridge, and air condition all run on the Sun :-)

This was covered in great detail by one of the boards posted out in front of our small office complex. Eventually, Soroush showed up, I introduced myself, and we made our way inside.

The inside was even cooler than the outside :-) There's a large open space where most people sit, a dark cave for the software engineers, an unused loft upstairs that looks down over the open space, and a cute little kitchen area upstairs.

The Intervening Weeks

Within a day or two, I'd purchased some bean bags, nerf guns, nerf balls, action figures, and die cast cars. It was starting to feel like a start-up :-)(And the nerf gun fights are a regular brain-break for many of us!). A few days after that, Tim Hyland bought some sling-shot monkeys... I think we use these even more than the nerf products!

Playtime aside, the work has been very grueling. We all work late hours (but have a good time hanging out while we do so!), wear many hats, and have more responsibilities than we care to enumerate. Equally, however, we're all deeply invested in the company, believe in the services we're providing to the health and other industries, and most of all are committed to the success of the company. Most of us were involved in ventures during the dot boom/bomb, and accrued wisdom from that area on how to conduct ourselves responsibly, even in the midst of all the excitement our innovations are generating.

I look forward to the time (soon!) when I'll be able to post more about these :-) For now, though, I can be very general and give a brief overview of our tech.

Our Technology

Matt playing along with a thumbs-up :-)
I worked on several device projects for Canonical, but never were we actually building our own hardware like we do at BlueLibris. This has been a fascinating introduction to a part of the tech world with which I am starting to gain some familiarity: circuitry design, component integration, plastics work -- the list goes on and on. Soroush Salehian and Matt Maibach lead these efforts, with Ram Fish weighing in regularly with his extensive EE background. These are the guys iterating on the hardware for our real-time, 3G health monitoring device.

As events are generated on the device, they get pushed up to "the cloud" where additional processing and heuristics are performed. We're working with lots of maths, machine learning, custom algorithms, etc., all in a distributed computing environment. We're using nosql solutions for long-term storage, and a Python-based framework for web management tools. We're in the process of converting the original application into a JavaScript-driven suite of applications. We're also giving the Python an overhaul in anticipation of significantly increased load and general usage over the next year (we've got some exciting partnerships and customers -- both existing and forth-coming). Henry Messenger and myself are working on these bits right now. To get the device talking to the cloud and collecting all the right data, we have the talented Kent Ryhorchuk hacking like a madman and consuming the APIs we're providing him.

There are other software development efforts in the works that I can't really talk about... but given the space, I'm sure you can imagine the possibilities :-)


Syndicated 2011-10-04 17:55:00 (Updated 2011-10-04 17:55:57) from Duncan McGreggor

24 Jun 2011 (updated 26 Mar 2012 at 15:02 UTC) »

Physical Beings with Digital Lives

2001A Space Odyssey
There's a lot that one could say about that title. In fact, it could be the title of a high-volume collaborative blog... That aside, here's the context for this post: books. Books and Reality. And data.
This post got so long that I now need to add a list of sections here, just to make it more accessible. My apologies :-/

Mini Table of Contents
  • Books
  • Books in the Sky
  • Yeah, I Know: Go Social
  • Human Data History
  • Reality Merges
  • Conclusion
Books


I have tons of books. Actual, physical books. Walls of them. Some I use all the time (reference). Some I read once a year (good books that support multiple reads). Others I've only read once, perhaps as far back as high school (when I started collecting). My bookshelves are like a random associative memory array: reading each title or the act of pulling one from the shelf brings back a flood of memories, relived experiences, sometimes actual sense perceptions. It's a powerfully visceral activity.

But that's just my books. When I'm at friends' homes or offices, I cannot keep my eyes off their bookshelves. It's an irresistible compulsion. I linger and browse, often past any semblance of socially acceptable time limits. My conversational replies experience a rapid exponential die-off -- in duration, gaps, and semantic value -- culminating in grunts and finally silence. (My favorite offices to visit so far? friend mathematicians/maths professors!)

Books in the Sky


Oddly, I love books in digital format. I never really got hung up on the bit about not having the paper entity in my hands (though I have turned a digital book reader over, expecting the next page... though that was deep in the plot of a Greg Egan novel!). Traveling as much as I do, I'm in heaven with ebooks. I feel like Superman, carrying around a library with me everywhere I go.

But when I passed a bookshelf the other day on my way out the door and fell under the spell of a book-memory flashback, I realized what was going away as I transitioned to virtual books. And the painful question arose: How am I going to nurture future layers of book-mulch and text-humus with this new æthereal, cloud-bound library I'm building?

How can I share with others, my stacks of books? How will I browse friends' books in their offices, asking about author X and title Y? How will we borrow from each other? What can be done to add this and related missing richness back into our lives once we adopt the virtual versions?

Light-emitting walls that can display titles from your Amazon account? Virtual over-lays visible with wearable/immersive computing accessories? Whatever we end up with, a gimmick isn't going to cut it. It will need to reflect the same depth of history that stacks of physical books have come to represent to us and the collective human psyche since we first started gathers works of the written word.

Yeah, I Know: Go Social


I'm hung up on books here, I admit it. But the same goes equally well for much of what we experience in online social media as well. Everyone's trying to make a buck on people chatting, playing games, reading, etc. Business as usual.

But the problem is that everyone coming up with their own little solution, one piece at a time. Google, Facebook, LinkedIn, Last.fm, etc. "We socialize X." Wow. Good for you. Now, for every activity or group I'm interested in, I've got some tiny little corner of the internet that I need to pay attention to.
Right.

Maybe I'm just an online social idiot, but this isn't working for me. Too many places and pieces. The physical analogy would be me spending all day on the road, hitting all the social hot spots in the Colorado Front Range. Ain't gonna happen. Ever.

Human Data History


The social data scene is a big stick up my butt. I really don't like it there and I'd love to get rid of it. It's poorly engineered, primitive state makes me grumpy. I don't own a thousand hammers [1]; I don't want a thousand of anything that all do basically the same thing [2]. Most of us probably don't own hundreds of houses, either (for ourselves, that is). We keep most of our stuff in the same location or two.

Speaking of houses, let's talk about settlement. How did we choose where to set up camp, towns, etc.? Trade routes, availability of resources (direct physical presence or presence by virtue of trade routes). Are we doing that now on the internet? Are we looking at the analog to fertile valleys, productive rivers, and protected harbors? Whose priorities do we have in mind? As we set up virtual presences, are we in locations that benefit businesses? Or ourselves?

If we choose the latter, the businesses will come because the people are there. If we do it the other way around, we'll be looking for new virtual homes if the businesses close shop or change the rules too much.

Coming back to data (but on the same anthropological note), historically we've had distinct divisions of our data:
  • the secure location of our huts/houses/castles
  • what we presented about ourselves in adornment/fashion (public data)
  • what we could carry with us in bags/crates/vehicles
Because of their prevalence in our history, any attempt at realizing personal data in a virtual environment would do well to reflect on these. We're naturally already predisposed to such approaches; such divisions are things that anyone can intuitively grasp.

The problem is that we're all used to a single platform: our mutually agreed-upon reality. There's no such thing online yet. And if there were, who would own/run it? Monopolies are eventually overthrown. We hate them. So how do we get around this?

Reality Merges


This very naturally led to thoughts on digital lives in general. And this is more than just a question of usability or human-computer interaction. Rather, this is a question that borders on the metaphysical: how do we solve the problem of syncing divergent realities? Reality-reality interaction.

The problem shouldn't be minimalized by analogy: this isn't a "simple" matter of ensuring that the data in my address book on Google is the same as what's on my iPhone. My self-perception, many reminders of self-reflection, etc., take place as a result of various interactions I have with my surroundings: both real[3] and virtual. No problem. Except that the things that remind me are also things that others can see and interact with as well. Often, they will have associations that spark a neural cascade for them too.

I've had many conversations take place around objects in a shared environment where the name of the object was never mentioned, it was implicitly understood. When there's no shared object (or concept), we have to name the object, define it, share some basic associations, make sure that we're talking about the same thing, etc. Thats all prelude. Only with that done, can we have genuine communication take place around the given concept.

Now rinse and repeat for everything you want to talk about that revolves around or is at least related to something that exists virtually for you and isn't part of your shared, physical environment.
I can't imagine many useful general solutions to this. In fact, I can only imagine one (given our biological wiring): use what we know (in our bones) and overlay or augment our visual reality with another.

With augmented shared realities, there's no platform. You just need hardware that runs it and senses that can perceive it. Just like reality. At that point, we can start sharing what we want, allowing access to data about ourselves and what we like by dumping it into a shared perceptual space, regardless of the original data source. Merged.

Obviously, we're not there yet. We're going to need crazy improvements in mobile technology, storage, computer vision, etc. But once the technology catches up, I think we'll see some powerful needs being filled. And we might start coming out of the internet dark ages...

Conclusion


None of this is new; Pick up any number of books by Charlie Stross[4], and there's all sorts of fun to be had by exploring his ideas. But the point of this post wasn't to be new. While we're all busy enjoying the latest fad in social media, I think it's important we think about where the progressive succession of fads is taking us. At each point, there's a natural next step (more accurately, set of possible next steps). Let's look more than just one in front of us and let's not forget what our biology has made us. We may not be able to engineer truly wise decisions about our future, or even make our lives better/more efficient. But it would be nice if we could at least not make things worse :-)

Footnotes


[1] I think I have three, actually.
[2] This is one of the reasons I'm a big fan of http://ping.fm.
[3] Here I mean "real" in the "conventional" (shared) reality sense of Mahdyamikas. Ultimate reality... well, that's a topic for an entirely different sort of post...
[4] Check out his Amazon page: http://www.amazon.com/Charles-Stross/e/B001H6IW0Q/. Accelerando is probably his most praised book (and likely my favorite), but the ideas touched on in this blog post are explored in other works of his, most notably Glasshouse and Halting State.

Syndicated 2011-06-23 23:44:00 (Updated 2012-03-26 14:30:30) from Duncan McGreggor

21 Jun 2011 (updated 24 Jun 2011 at 01:02 UTC) »

txStatsD Preview

Sidnei da Silva (of Plone fame) has recently created a Launchpad project for an async StatsD implementation. He's got code in place for review by any Twisted kingpins who'd like to give it a glance.

statsD was originally created in 2008 as a Perl implementation at Flickr for their statistics counting, timing, and graphing needs. Engineers at Etsy ported this work to Node.js (which Sidnei based his version on). A few months ago a regular Python implementation was created (also based on Node.js).

More than another (excellent) addition to the tx family, txStatsD will provide folks with the luxury of collecting stats using a Python server without having to write any blocking code :-) Sidnei also implemented a graphite protocol and client factory for passing the messages along.

Enjoy, and let him know what you think!

Syndicated 2011-06-21 17:34:00 (Updated 2011-06-24 00:12:03) from Duncan McGreggor

8 Jun 2011 (updated 26 Mar 2012 at 15:02 UTC) »

The Future of Personal Data: A Followup

The Next Step

A few years ago, I wrote a post about the Future of Personal Data as a result of all the ultra large-scale systems reading and exploration I was doing. Google was foremost in my mind when writing that, but Apple has since come into the spotlight here as well.

Recently, Matt Zimmerman has decided to leave Canonical and join forces with Singly, an exciting startup company focused on secure user data storage and the socialization of (and development around) that data. In this blog post, the following core values were given about the software underlying Singly:
  • I own my personal data
  • I want my data to be useful to me
  • I make the decisions to protect or share my
I would like to see the following added:
  • I make the decisions on how my data is used
  • If my data is sold, I should get a return for this
This is not petulance speaking :-) This comes from a historical perspective on social and economic fairness. Witness the changes in individual rights and personal finance since the industrial revolution...

Fair Market Value

There are probably many solvent entities out there who would claim users are already getting a return for the use of their data: free email and office docs from Google, free cloud services from Apple, etc. But I would imagine that there are massive margins being made on user data, and services (as valuable as they may be) are a paltry return for such a gold mine. I cannot help but be reminded of the selling price of Manhattan Island or Alaska (in 2011 values, the Lenape Indians got around $29.61/square mile; the Russians got about $150.77/square mile).

Money makes a good point, but personal data (and this post) isn't about the almighty coin. This is about clearly defining who owns what and ensuring that those who don't want to be taken advantage of, aren't. This is about identifying exploitation, and building something better and longer-lasting in its place.

Who's Going to Pay for What?

In David Pakman's "Disruption" blog post about Singly, he makes the following comment:
"I cannot see consumers getting into the business of selling their data to marketers so they can see personalized advertising. Instead, I believe marketers will be encouraged to offer value to us in exchange for access to our data."
I have to agree with him... but I can only offer a qualified agreement. True, I find it hard to believe that users will be selling their data directly to marketers. From the user-side, the pain of inconvenience would not likely be worth the payoff; at the marketer end, individual data is useless, and munging an in-house-built collection would incur a lot of overhead not part of their core business.

However, users' data stored in lockers, updated regularly, pre-processed, has enormous value in the market. Right now, Apple and Google are making eye-crossing amounts of money from data just like this. Again, I would imagine that this data is only really valuable in large quantities and for interesting, identifiable demographics

If users provide their data, but in exchange only get a "nicer app" or a "useful utility" I'm going to cry "foul!" (unless someone can show me the actual numbers involved and unequivocally prove that fair exchange is occurring).

You Say Disruption, I Say Revolution

Instead, if a service such as Singly, were to offer a co-op style dividend payment system to all of its users, that would seem to be much more fair. Not only that, it would be the beginning of a market revolution. This is not to say that co-ops are some perfect economic model, but rather that the data we, as users, generate is of immense value. The more that Singly has, the greater potential for revenue. The more buzz that builds around Singly users generating revenue from their data, the more users they get. With mass-adoption, a new sub-economy is born.

Perhaps a better model than co-op is that of a mutual fund investment firm. Each Singly user has a portfolio of data. Depending upon each user's preferences, any or all of that data could be used by Singly to generate revenue. Some groups of users will generate more than others, and users in these groups would get greater returns.

Whichever analogy you prefer, with a little exploration it seems fairly clear that opportunities for a large payout are present. For instance, I like to imagine a world where entities like Apple and Google can't harvest user data, but must go through brokers whom users have given their permission to sell their data for the most profit. I also imagine there's a lot of lawmaking that would have to take place... and even more lobbying.

Even with that, Google and Apple would still make money hand over fist (or they'd become brokers themselves) -- enough to continue providing free services. Yet at the same time, users would be in control of their data; they'd be financing (or financially augmenting) their data-consumption lives with said data.

With the right press coverage, Singly could find themselves not only swamped with a massively growing user base, but at the very center of a new economy. With the right level of negotiation and coordination, businesses could buy into this new paradigm without losing their shirts in the disruption.

A Plea

In summary, I applaud the goals and vision of Singly. I, for one, would deeply appreciate writing applications against their data locker (to any Facebook or any of its dubious applications), where a user's rights are clear and protected. That being said, Sinlgy would have my eternal allegiance if they also took up the cause of rights for user data in the market place; if they helped transform the current nascent data economy into a world economy capable of achieving as-yet unimagined financial heights.

And if not Singly, my loyalty would be given to whomever did do this.


Syndicated 2011-06-08 16:29:00 (Updated 2012-03-26 14:31:02) from Duncan McGreggor

Packt: A Publishing House for the Future

Since I first heard of them several years ago, I've viewed Packt as the underdog in the world of technical book publishing. In the past year or so, Packt seems to have gained greater and greater influence: their catalog continues to grow, they are attracting talented and knowledgeable engineers as authors, and their titles are things that I'm actually interested in.

Two examples of this are the books Expert Python Programming and Zenoss Core Network and System Monitoring. I received a copy of the former and blogged about my take on it. For the Zenoss book, last year I agreed to be a technical reviewer and am currently preparing a blog post on my pre- and post-publishing experiences.

In both cases, I agreed to work with Packt based solely on the technical merits of their works. However, my experience as a technical reviewer with them was so positive (I have had consistently excellent experiences with their staff over extended periods of time and on long-running conversations) that I have not only agreed to review more titles, but have read up on Packt themselves a bit. Here are some highlights from their wikipedia article:
  • They published their first book in 2004 (the same year Ubuntu started!).
  • Packt offers PDF versions of all of their books for download.
  • When a book written on an open source project is sold, Packt pays a royalty directly to that project.
  • As of March 2008, Packt's contributions to open source projects surpassed US $100,000 (I would love an updated stat on this, if anyone has a newer figure).
  • They went DRM-free in March 2009.
  • Packt supports and publishes books on smaller projects and subjects that standard publishing companies cannot make profitable.
  • Their stream-lined business model aims to give authors high royalty rates and the opportunity to write on topics that standard publishers tend to avoid.
  • Bonus: they also run the Open Source Content Management System Award.
These guys have some keys things going for them:
  • They've got what appears to be a lean approach to business.
  • They know how to effectively crowd-source, keeping their overhead low.
  • They are rewarding both the authors as well as the open source projects.
  • Their titles continue to grow in diversity and depth.
  • The have an outstanding staff.
Oh, and I really like the user account management in their website! When I log in, I see a list of owned books, source code links for them, clear/clean UI, very easy to navigate. I can't emphasize this enough to vendors, service providers, etc.: if you want a loyal user base:
  1. make a good product that lasts a long time;
  2. make simple and great tools that enhance the experience of those products, that truly improve the experience of your users.

All in all, Packt really appear to be leaders in publishing innovation, taking lessons learned from the frontier of open source software and applying that to the older industry of publication production. I would encourage folks to evaluate Packt for themselves: if you like what you see, support them in readership and authorship :-)

I, for one, will continue to review titles that appeal to me personally and that I think others would enjoy as well. I have two books in the queue and three pending blog posts for the following titles:
And who knows, if I feel like writing a technical book at some point, you may see me in the Packt catalog, too ;-)


Syndicated 2011-05-23 14:40:00 (Updated 2011-05-23 20:57:50) from Duncan McGreggor

Call for Testing: nVidia Cards in Ubuntu Natty

I was supposed to write this blog post early yesterday morning, since the first results from community testing are going to be examined today... but we're still going to need on-going data. So not all is lost :-)

We're working very hard with chip vendors to make sure folks are getting the best experience possible running Unity in the forth-coming release of Ubuntu (Natty). Jean-Baptiste Lallement has posted to the QA mail list, asking for committed volunteers to test the nVidia drivers in Unity on a weekly basis. You can read his email here:
Jean-Baptiste links to detailed instructions in his email. The QA Tracker for this effort is here (but please be sure to read his email and follow the instructions that he links to):
We look forward to hearing from you!


Photo Credits: jackyalcine (slightly modified)

Syndicated 2011-03-16 13:33:00 (Updated 2011-03-16 13:36:24) from Duncan McGreggor

Uncle Canonical Wants U!

you and uTouch, that is. And more!

Do you love Ubuntu? Are you an HCI freak? Are you an X hacker, kernel driver maintainer, Linux input enthusiast, Qt or GTK application developer, C/C++ hacker?

Do you enjoy being part of online technical communities? Are you actively involved in open source projects? Do you enjoy advocating for software?

Do you love test-driven development and thirst for high-quality open source software running on devices with touch interfaces?

Does the idea of working from home in your own time-zone, on cutting-edge, strategic projects at Canonical have you sitting on the edge of your seat?

If so, then please send me your resumé/CV! I'm looking for a few brilliant engineers as we grow our Product Strategy teams (DX, Design, and others).

Syndicated 2011-01-21 14:08:00 (Updated 2011-01-21 15:09:28) from Duncan McGreggor

Canonical and Codethink at Bostom GNOME Summit

Today is the second day of the Boston GNOME Summit, and the second day of Canonical providing morning sustenance for the hackers here. Codethink and Canonical coordinated these efforts, with Codethink sponsoring food later today. It warms my heart that we can do this sort of thing.

Yesterday Cody Russell and I held a session about getting a gesture API into GTK 3.x. There were a great many questions about the uTouch framework, how we're handling multi-touch in the absence of MT support in X (coming in XInput 2.1), and what sort of dependencies would be needed (none! if GEIS is present on the system, gesture support will be added at build-time). At the end of the session, there was a consensus for Cody to present his plans to the GTK developers list and then to start getting branches reviewed for merge. We're hoping to make it for GTK 3.2.

In this vein, Cody and I have been hacking on libgrope for GTK compatibility, and this is serving as the sandbox for the GTK 3 gesture API development. My efforts have been focused on creating the GTK 2 Python C extension for grope. Given that the last time I coded C was in 1989 (and then a bit later in the mid-90s, when I had to hack a slackware driver to get ethernet working), this has been quite an effort. However, after a night and morning of hacking, I've got a handle on C extensions and am using the example code I wrote as the basis for pygrope. I've even managed to rope Barry Warsaw into reviewing the C extension code for us, to be sure we're not doing anything too crazy :-)

The Python C extension will be of immediate use to us in our test harness for gestures and exercising the stack. We will be creating a GTK app for recording user gestures for later playback and inclusion in test suites.

Syndicated 2010-11-07 16:54:00 (Updated 2010-11-07 17:19:22) from Duncan McGreggor

258 older entries...

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!