Joining Rackspace

by Jesse Noller


The Switch

So, as you read in my goodbye post; I'm switching over to a new role at Rackspace starting today, April 15th. The short version is that I am coming on board to help improve and evolve the way Rackspace cooperates with the open source community internally and externally. Of course, I'm crazy excited about this - as I said before:

...if could meld the open source/community work with my "day job" I could do a lot more. I could be more - I could tap into skills I've grown and developed in all of my "lives" and do even more.

If I could bring together the worlds I operate in I could potentially do even more within the Python community, the Open Source world, at my "day job", etc. But things like that don't exist, roles like that are fleeting and rare.

Ah. But roles like this do exist, come to find out, and I managed to be offered one at Rackspace, already working on leading the way with open source and the open cloud in a myriad of ways. They don't just want to be a "big company" - they want to be a great company.

Values

What’s compelling is that Rackspace wants to be/is recognized as one of the world's greatest service companies. This means a fundamental shift away from a “product” driven cycle of development and internal structure - if you’re a service company, you need to hold values like Rackspace's dear:

  • Fanatical Support in all we do.
  • Results first, substance over flash.
  • Committed to Greatness
  • Full Disclosure and Transparency
  • Passion for our Work
  • Treat fellow Rackers like Friends and Family

Interestingly - these values, especially fanatical support directly align with my personal beliefs, and more importantly how you compete with entrenched players in the "cloud" space (see "How do you compete with Google")

But going back to product - we all know services are fundamentally products, but there’s several methods of development. What Rackspace wants to become is “Open First” - this means they see the value in the services they provide, and the fanatical support, but they want develop the software they use for those services and products (especially the Rackspace Cloud) in the Open - this means Open Source all the way down.

Open first means that rather than develop internally and then push externally, development of tools, services, etc will eventually happen in a truly OSS fashion: as open source projects first, and then deployed and utilized internally to Rackspace (as they now do with Openstack/Rackspace Cloud). This means internal changes in development processes, legal processes and much more, much of which is already under way.

This of course means I will be working on internal developer advocacy and changes so that this vision becomes reality: software will be developed in the open, open source will be rewarded, community involvement will be critical for individual developers, support, marketing, etc.

Rackspace doesn’t just want to ship code though: they want to get deeply involved in the developer community as a whole (not just Python). They want to be building products and services that developers want to use and open source projects that developers want to use and contribute to.

Rackspace wants to make itself an awesome place for developers - they want it to be a place where developers can come and write code that doesn’t just benefit Rackspace, but the whole developer community and open source world as a whole. They want to raise the profile of those internal developers who get involved, they want to openly communicate with developers internally and externally.

But that’s just some of the internal pieces.

Externally

Externally, Rackspace wants to get more developers involved with its cloud platform and OSS projects. Rackspace wants to support the community as a whole, via outreach, education, code, getting involved in hack spaces, workshops and more.

Rackspace has always been known for fanatical support. What that means for Rackspace as “the Open Cloud company” is that they offer fanatical support for developers. Essentially Rackspace being a great place for developers to work and contribute in every dimension.

Strive to make Rackspace the place where every developer wants to work; make Rackspace services the ones that every developer wants to use. Work to make Rackspace’s Open Source projects the best of breed solutions in their areas (such as OpenStack).

This is important as it represents a shift for Rackspace, but the dedication to this vision comes from all levels within the company. Thats why I’m coming on board - to help drive this vision, bringing together my community work within the Python community, wider developer community and my own development skills.

Some of the things that are on my mind/list:

  • Lower the barrier to entry and friction for internal developers contributing externally.
  • Lower the barrier to entry and friction for external developers to contribute to Rackspace OSS projects (For example, OpenStack and others)
  • Lower the barrier to entry and friction for developers to leverage Rackspace’s cloud services. This means making those services not just easy to use, but robust, compelling and enabling for developers.
  • Supporting outreach groups, workshops, hacker spaces, meetups, conferences, etc - not just within the Python community, but other languages and communities.
    • Rackspace is already supporting conferences, startups and much more - I want to work with them to extend this everywhere within the development community.
  • Internal support for developer/development R&D and more.

Excited Much?

Yeah, I'm pretty excited - nervous, yes - but excited. This represents a huge leap of faith for me. Moving my family across the country, taking on a much larger calling, combining two worlds (product development, community work) and a lot more.

I'm sitting here, outside in San Antonio on a bench waiting for the shuttle to the "Castle" filled with thoughts of the future and what it could hold. I'm shaking, I'm nervous, but it's going to be amazing.


2012: A year in Review.

by Jesse Noller


Well - of course, it's that time again to take a look back at the year and think reflect (if you've got the mental bandwidth) on the previous year. I'm not a huge fan of memes, but I've made it a bit of a self-task to always do something to remind me later. I've broken this up into personal and Python components of course - feel free to skip around.

Overall? I have to call 2012 a bit of a wash. Maybe it's because I'm tired or burned out - I'm not sure. I feel like it's been two steps forward and two steps back. For every good thing, there's been a correlating bad thing or thing that makes me put my head in my hands and go "why?!".

Python & Community Stuff

If I had to write a state of the Python Union talk; it would be "great things are afoot". Python 3.3 was an epic release of Python and Python 3 adoption and porting in general is trending up at a pace this year that's even surprising to me, and I see a lot of stuff behind the scenes.

A lot of this has to do with the general cycle of things - Python 2.7 has been out for awhile, and major libraries and frameworks have, through their natural release cycles, begun dropping support of older versions of Python allowing them to work towards code bases that support 2.x and 3.x. As for Python 3 itself? The number of Good Things in terms of fixes and features is making it more and more attractive. With things like Guido's new async PEP coming around, packaging work and a lot more? Things look pretty good from where I'm sitting. The PSF has been steadily feeding the fire by funding ports of key libraries and frameworks to Python when grant requests come in - and it's growing.

I'm not about to make any grandiose claims like "2013 is the year of the Python 3 x" - but I can tell you with some of the things I personally know about going on, it's going to be a big year.

Community in General

For the community in general - we're seeing growth across the board. The number of companies I know of using Python (and potentially therefore PyCon sponsors) is growing quite healthly despite the concerns of many that newer languages would cannibalize the community and the companies adopting the language. This is, in large part because Python Is Safe. The community is welcoming and open, the language is infinitely approachable. More and more cool things are being made and released in it as OSS every day - continued, steady growth has been Python's story for years now.

It's not trendy; I know. If you frequent online forums you'll see tons of noise about Node.js, Rust, Ruby, etc, etc. Sure, all of those are going to grow and to an extent, we've seen the maturity (I'll call it "slowing down" for the sake of my point) that Python has coming to other communities as they grow older, become safer. No - Python isn't a headline grabber, and no, if you live in the technology echo chambers you probably feel like it's not the Next Hot Thing, but hey - I'll take steady and continous growth over explosive growth and implosive shrink any day.

The community has grown more and more towards a focus towards outreach and brining people in. On the technology front projects like the Raspberry Pi are giving us inroads to schools and education and the maker community in general.

The continued explosive growth of outreach and education groups such as PyLadies, OpenHatch/Workshops, PyStar, CodeChix, LadyCoders, Women Who Code, Code Scouts and many more has seen Python as a community grow more and more organized in probably one of the most important areas we can today. Our awareness has shifted, matured and grown. This, as well as reaching into education more and more and encouraging the next generation of Python Programmers will be our key driver to maintain the growth and increasing diversity of the community. Oh, and don't forget reaching into data science and scientific community even more - the recently formed NumFOCUS Foundation should see nicely to that.

Growing up is hard to do - for example, the recent announcement of the Code of Conduct requirement the PSF put in place (the Foundation is, as far as I am aware the first grant providing organization to do this).

As I say in that post, it's a sign of not just the times, but of an increased inward focus on things we can do better at.

We've also seen more and more discussion and debates about civility within the community in general - luckily, Python has avoided too many of the PR disasters that have affected other communities, but we still have miles to go before we sleep. We have to continue to prove that Python as a language and community is something You Are Welcome in, and Something You Can Count on. I said it long ago - I wouldn't trade this community and all the friends I have made for anything.

Of course, who can forget that we're also growing up on our - I'm sorry to say this - marketing. Everything I've already listed is a form of marketing, but an extentsion of that is our, as they say, copy. Python.org is getting a major site redesign - a project that I've spent probably five years cooking, and would not have happened except for the heroic efforts of a great many people.

All in all; as I've said before, the future looks bright for the community.

Sadly, 2012 was not without it's losses. We sadly lost John Hunter, author of Matplotlib as well as Kenneth Gonsalves, founder and leader of the India Python Software Society. Both will be dearly missed within our ranks.

PyCon

2012 saw, yes - the largest PyCon US ever. 2300 attendees - almost 200 sponsors. I've spent most of the last few years working on PyCon US, and 2012 was no different. The team and I started working on PyCon 2013 before PyCon 2012's main conference days were even over (well, technically we started working on it before PyCon 2012 even started). PyCon 2013 is going to be even bigger, although we've capped attendance at 2500 attendees. We've got more events such as PyPgDay, PyData SV, the Education Summit, Let's Learn Python (for kids), another PyCon 5k and a stunning list of talks and tutorials. A stunning array of sponsors and partners and so much more.

And I'm, not even close to done yet with things for PyCon 2013.

Ignoring PyCon US for a minute: 2012 also so explosive growth in the number of other Python/PyCon conferences. Just see PyCon.org for an example. The first PyCon South Africa? The first PyCon Canada? PyCarolinas? Too much amazing is going on - this is why anytime someone asks me if we're shrinking I sort of laugh.

New Projects

I've already mentioned the voluminous PyCon 2013 and Python.org Redesign which consumes much of my time - but I've found some time to slip in some new Projects for the community here and there including From Python Import Conference, continued work for the Python Software Foundation (and a FAQ for it), and a cross language/community effort called Speak Up! which I still need to formally announce. Speak Up! is aimed at mentoring new people (and those looking to hone their craft) by leveraging mentorship, teaching and an excellent set of mentors (we're adding more weekly).

Quoting it's mission:

The mission of the Speak Up! project is to assist in the guidance and mentorship of potential technical speakers, tutorial presenters and attendees of conference, user groups and other community events. We hope by providing access to mentors from many programming languages who are seasoned speakers, conference organizers, or other volunteers we can grow not just the gender diversity of speakers at technical events, but the diversity of speakers at technical conferences as a whole.

Through positive, reinforcing, polite, and safe actions - we all can increase the diversity of voices in our communities, conferences and elsewhere.

In Summary

Much of what I wrote in my 2011 wrap up still applies, more than ever. Design and our (Python/Community) interface to the world matters more than ever. Things are growing and new projects and companies are coming online every day. Hacking on Python - the community more than ever - has absorbed more and more of the time I have. It's worth it though. To stand back and see yeild of the labor of so many dedicated programmers, hackers, community leaders and groups have poured into the community continues to make me proud to serve. Even if I have an unhealthy addiction to fighting the fight online and arguing with "the internet".

So yeah. Maybe it's time to update my Gittip page. Somehow, I ignored my own advice in my 2011 wrapup and kept adding and spinning off new projects so much for taking it easy. And these are the ones I can talk about publicly right now.

The Personal Side

Well. Reading back on my 2011 Personal Portion post, well, I've managed to stay healthy (weight lifting, diet, running), I've kept up the standing desk discipline, but lost the time to do Bikram (tradeoffs, they're a thing).

Addison; our youngest has thrived - through a combination of early intervention - and early diagnosis, she's now about to turn 10 months old. She says daddy, and mommy (albeit in the toddler way). Her gross motor skills are impressive, she's a total love bug and has come to be one of the happiest toddlers I have ever known. Abby, now in kindergarten, also continues to thrive - scarily intelligent and perceptive, she's about everything you'd expect in a five year old version of me (she got my personality… Not sure if this is good).

Sadly, the brink my family found ourselves on did not abate. After the turn of the year we realized given the fact we had to lose an income due to everything else going on, climbing debt, and many other factors - it would be best for us to sell our home (our first) at a loss or to give it up entirely. It became a yolk rather than a blessing, and after the bank with whom we tried to work told my wife "we didn't tell you to have a second kid (referring to Addison)", well - that sealed the deal. At PyCon 2012 I was negotiating with them while also doing the conference, and we managed to pull off a short sale.

We're still on the hook for a large sum, thanks to the short sale, but we're in a good apartment, and we're able to do more things and focus more on the girls. We had to go back to two incomes - given the hole we had found ourselves in, it was impossible for one of us to stay home with the girls.

Inside all of this, my wife Dusty got sick - very sick. That incurred more time off, more expenses. Luckily we didn't have the house hanging over our heads, but we passed through some pretty bad times. We spent more time in emergency rooms, asking our friends for help, ducking out of work or comforting the girls that mommy would be ok than I care to admit or discuss.

While Dusty never got a prognosis that gives us resolution or a path forward; she's stable and healthier now (although the migraines that triggered it all haven't abated). Towards the tail end of this year, we've seen things finally begin to stabilize and fall into the rhythm we so desperately need as a family.

2012 has not been an easy year on any of us family-wise. But we're still here, and we still hold each other close and I've got that hope that I can finally begin to say "it's going to be ok" and not to have it feel like I'm lying to myself.

It's been a rough year, but we've grown closer as a family, and we've gotten to spend more time where it counts - with each other. Two beautiful daughters, a beautiful loving wife - I am blessed and I know it.

Just take a look at my Instagram page. My letter to my wife from Feburary still applies more than ever.

Resolutions?

I'm so not going there. I've got projects on the burner that aren't public, a conference and a family to work on, and a smattering of other projects (oh yeah, and a full time job I love). I'm not resolving to do anything except "keep it going".

And maybe I can step back after this year. Dunno. I doubt it.

I can't stop watching this.

I can't stop watching this.


Followups: Code of Conduct, PyCon, Speakup...

by Jesse Noller


Just a few random bits from the newsphere:

The Code of Conduct

First up, the Python Software Foundation Code of Conduct announcement generated a fair amount of feedback, triggering my own essay on the matter, since I'm the one who sorta pushed it through and argued it. You can see some feedback on HN here and here, but for the greater part, the emails/tweets and feedback from outreach groups and people has been overwhelmingly supportive, and makes me once again proud to serve. Fundamentally, the PyCon US one may not be perfect, but in conjunction with the diversity statement and response guide; it's a good start. 

There are concerns I've heard through the back channels that this is the start of NoFunPyCon, some of which are aired quite... Acerbically, some rationally. It is my fundamental belief that these don't hold a lot of water, but perhaps there's some word smithing for the PyCon one that could be done to assuage those concerns. This is also why the PSF board resolution specifically cites the Ada Initiative template, and not PyCon US'.

PyCon 2013

PyCon 2013 is already turning out to be amazing - in the past few weeks we've announced the list of accepted talks (including a 6th talk track) and tutorials, PyPgDay, PyData SV, even more partnerships with outreach groups, a survey about childcare, Start up Row - this adds to the Let's Learn Python tutorial for kids, the PyCon 5k, an amazing line up of Keynote speakers and a lot more.

We're not done yet. Proposal submissions for Poster session presentations is still open, financial aid applications are due by December 31st, and registration is limited to 2500 attendees: if you're thinking about delaying registering: I don't recommend it, fwiw. Register now - we've already sold out of early bird tickets!

Oh, and on the fence about sponsoring? Read what Walt Disney Animation Studios, via the always amazing Paul Hildenbrandt had to say about that! We have a stunning array of sponsors almost all of them hiring Python hackers - and we've got room for more!

New Project: Speakup.io

I've spun up a new project to help with speaker mentorship, diversity and generally helping people who might not feel strong enough to present get help, track call for papers, collect ideas, practice their talks and much more. The goal of the Speak Up! project is to really guide anyone who wants or needs help speaking or "getting in the door". We've got an impressive list of mentors already, and some great discussions happening on the mailing list. I should do a proper announcement soon. The code is on github too.

New Project: From Python Import Conference

This is another one of those "finally getting to it" projects. It's been on my (and many other people's) to do list to start distilling the collective knowledge of various conference organizing teams (across programming languages, conference sizes, etc) into a helpful guide. Everyone is welcome to contribute (source is on github)! More to come.

Python.org Redesign

The redesign is proceeding: oh yes, yes it is. Project Evolution's Jason Hogue posted a status update the other day you should take a look at. If you have feedback you want to shoot to us, drop us a line at psf-redesign@python.org.

I think that's about it. I admit to a certain amount of mental discombobulation with everything going on. Maybe I'll add a to do item to fix that. Until then:

30ZaE.gif