All are welcome, contributions appreciated, I’m gonna start cooking around 3pm and probably close it down when the sun goes down.

Please RSVP:

http://www.mobaganda.com/opensourcebbq-june2010

or on Plancast

http://plancast.com/a/3pt9

There will be meat, and stuff that’s not meat, and beer. Contributions welcome, it’s open source after all.

Everyone that writes code is welcome. Please RSVP at http://www.mobaganda.com/opensourcebbq.

I live walking distance from MacAurthur BART, here is a map. When you get there just walk down the driveway in to the backyard.

Friday is also “open friday” at the couch.io office so you can come and work/play at the office during the day and then roll up to the BBQ around 4 if you like.

Disclaimer: Image is for effect only, hot rod BBQ will not be attending.

Mozilla

I started working at Mozilla 2 years ago. I started the day after my employment at the Open Source Applications Foundation ended. At this point I already took for granted some of the best parts of working at Mozilla; working for a public benefit organization, spending 100% of my time working on Open Source, working with very smart people in the open (lists, IRC, etc.).

But Mozilla is even more than all that. Succeeding at Mozilla means something more than a pat on the back and a good end of the year review. When you succeed at Mozilla you impact one of the most important products on the internet. You reach hundreds of millions of users and contribute to keeping the web an open and free (as in speech) world. There is no other place in the world you can work where you can conceivably have this kind of impact.

Mozilla as an organization is truly unique. Last year was the hardest I’ve ever had, i suffered a huge loss in my personal life and Mozilla was as supportive during this time as any of my friends or family. There are a lot of places that let you put so much of yourself in to the organization to help it attain it’s goals but there are only a handful that are there to support you when you need it.

Relaxed Inc.

I started using CouchDB in 2008 after a great talk by Jan Lehnardt at OSCON. I started using it right away and over the next year it re-shaped how I think about web development and applications. In the last 6 months my group at Mozilla has become a heavy CouchDB user and not just because of my own interest but because CouchDB was the only solution for some of the harder problems we needed to solve with our results storage.

As I’ve used CouchDB more and more and become a part of the CouchDB community I’ve had the pleasure of knowing some of the core contributors, three of which have decided to found a new startup around CouchDB; Jan Lehnardt, J Chris Anderson, and the creator of CouchDB Damien Katz. Shorty after they received their funding they made an offer. It’s an amazing opportunity and while the decision to leave Mozilla is one of the hardest I’ve ever had to make I’m very excited about my future at Relaxed.

The Future

I’m really looking forward to working with everyone at Relaxed. It’s an exciting time and I’m not 100% sure yet which projects I currently work on that I will still have time to maintain. In the next week or so I’ll be doing a blog post on all the libraries I currently work on and maintain (it’s a long list) and what their status is moving forward. I still maintain code I wrote long before I worked at Mozilla and have every intention of continuing to work on some of the projects I started at Mozilla.

One thing is certain. I’m not the guy who figures out how to test the browser any more. Windmill and Mozmill are important projects that I have every intention of supporting by making time for code reviews and community support but I won’t be available to put time in to new feature work and refactoring like I have in the past. Luckily there are solid communities behind both of these projects and I’m confident that there are people who can continue to drive them in the future.

I don’t know what is going to happen next, all I know is that it should be fun, it won’t be like anything I’ve done before, and will certainly continue to include lots JavaScript and Python.

For everyone who depends on me and the code I’ve written over the last few years I’ll be sure to keep you all up to date. And one thing I can promise is that if you want to fix anything in one my projects, fork it on github and send me a pull request and I will always find time to look at it

If you rely at all on the speed that Windmill runs tests, then this is your last guaranteed change free release.

However, we have done a lot of work to make this a great release:

Features:

• JQuery Selector Support
• Stability updates for Windows
• Moving all the deps into the Windmill tree, for easier installation
• Show controller method, for hi-lighting the DOM in your tests
• Improving the logic for JS Test reinjection between page loads
• Visual improvements
• Controller method for manually overriding dialogs
• Updating Firebug for Firefox 3.5 support

Bugs:

• Assertions and waits no longer scroll the page
• Fixing bugs with loading user extensions
• Wait for page load no longer fails tests, as your following action will do that if needed
• Increasing Firefox script timeout for large typing scripts
• Running Windmill on Windows Vista
• AssertText issues
• Rich Text Editor support

And many more!

As always come talk to us if you have issues in #windmill on freenode.

This has the jquery locator functionality, plenty of bug fixes, but most importantly — this will be the last release before a bunch of new features go in. If your tests rely on the speed that the current code base runs python tests (ie. the time between actions etc) then you will want to run this release.

Upcoming:

– flash testing work
- automatic waiting on UI actions
- new proxy work
- dramatic speed improvements

Please help us test!

This will be my first time at EuroPython and my first time in Europe!

I’ll be giving two talks, one on [Windmill](http://www.getwindmill.com) and one about [CouchDB](http://couchdb.apache.org/) and Python. The Windmill talk will be more or less the talk that I gave at [Open Source Bridge](http://opensourcebridge.org/) last week, which went very well. This is the first time I’ll be talking about CouchDB, the most exciting new technology on the web. The talk will mostly be about breaking our old data modeling habits that we developed to deal with SQL and what libraries and tools are available for interacting with CouchDB in Python.

I will also be in London for a few extra days after the conference so anyone interested in a meetup should ping me.

I’m putting together a new [Windmill talk](http://opensourcebridge.org/sessions/36) that tries to incorporate all the feedback we’ve received over the last year of speaking which I’ll be presenting on Thursday.

Mozilla is also a [sponsoring](http://opensourcebridge.org/sponsors/) the conference and there is going to be some great [Firefox related sprints in the hacker lounge](http://opensourcebridge.org/wiki/Hacker_Lounge). Dietrich is also giving what sounds like an awesome talk on extending Firefox called [Firefox Switchblade](http://opensourcebridge.org/sessions/251).

Hope to see you all there!

PS. I’ll also be at EuroPython and the Community Leadership Summit, more on those later

It’s finally time to:
easy_install -U windmill

Overview

This release now uses a home brewed proxy server, instead of CherryPy allowing us to handle both SSL and binary data like Flash exponentially better.

Also included in 1.2 is a polish of the Windmill command line output, bug fixes for running tests with Nose and full backwards compatible support for Python 2.4. All told 31 logged bug fixes, and countless others coming together to bring what we feel is a pretty big milestone.

Details

To use the newly built in SSL support for testing your application you must first install the Windmill certificate, which we have documented for MacOSX and Windows on the wiki.

Next, simply run Windmill the way you are used to, except adding the ’ssl’ switch. Everything else should be seemless. In order to make all this happen we had to add one dependency, pyOpenSSL. But if you aren’t using SSL, don’t worry about it. Otherwise, you can visit the launchpad pyOpenSSL page for more information on getting it setup.

Issues

When major changes happen in a project there are always issues. We have run all of our unit tests, and really appreciate all of the responses we have had informing us that you’re tests worked as expected with trunk/RC5. If you are seeing regressions, please come talk to us: Freenode on IRC, #windmill, mail the list, or log a bug in trac and we will be as responsive as we possibly can. This release was designed to add functionality, not change or break anything else.

What’s next

Next up we are planning some client side improvements slated for 1.3, as well as some new features for the JavaScript tests. Don’t worry — we plan to keep everything backwards compatible, stay tuned!

You can download the tarball here, we really appreciate your input!

The kind of things you should keep an eye out for:
- Regressed actions passing in your test
- Excessive output in stdout from the proxy
- Interaction with https sites
- Installation of the SSL cert
- Backwards compatibility with Python 2.4
- All browsers and platforms performing equally

Additionally, if you have the time or interest in running our unit tests on your platform, we have written up those instructions here.

Either log a bug in trac, talk to us in #windmill, or even twitter about your issue.. we look forward to flattening those bugs.

Thanks!