are a changing.
Disclaimer Yes, I had my mic backwards for the whole show. I apologize for the quality of my voice in here.
- Detroit Dev Day Notes
- Code Reviews and the importance of viewing the diff
- New Toys
- Events - 1DevDayDetroit Nov 4/5th
- OhioLinuxfest Recap:
Thanks for stopping by the booth everyone!
- Sourceforge Interview
- Elizabeth Naramore, Community Developer Manager
- Links of the week
- Rick's Mini Rant: Your anti pattern is called a tool
- Горсти талого снега by Калевала from Кукушкины дети
- Human Core by HiHate from Against All
- Natural 20s by Dual Core from Next Level
- Eighties Dance Music by The West Exit from Unearthed
- Imported by Irate Architect from Visitors
- The Four Seasons: Concerto in E Major, Op. 8/1, RV 269 - 'Spring': III. Allegro by Lara St. John from Vivaldi - The Four Seasons
- Never Happy by Drop Alive from Drop Alive
- Interview with Jason Smith
Jason is a developer for the Developer Experience (DX) team with
Canonical and works on the Unity desktop shell. In particualar the
launcher. We ask him how it's going, what the plans are for Natty, and what
we should be looking forward to in Natty+1.
Links Jason mentions in the interview
- Craig: Nadda
- Rick: Pro Python
We need your help. Craig and I have spoken our concerns about what Unity means to the future of Ubuntu. Thursday March 24th, we'll be interviewing Jason Smith of Canonical who works on the Unity team. We'd like to know what you'd ask him if you got a chance.
- How close are things to planned functionality for Natty?
- What kind of testing is going on behind the scenes?
- What types of users is Canonical targeting as the average Unity user?
Let us know what you'd like us to ask. Submit your question here in the comments or email the question to firstname.lastname@example.org
Thanks for your help!
In our last in the series of interview from PyCon 2011, Lococast sits down with Michael Foord and talk about some of the cool things he's working on at Canonical, how the new version of his Python mocking library Mock is doing, and a little bit about what's going on with IronPython in a post-Microsoft sanctioned project era.