April 28, 2013
Following PyCon US, the Python Software Foundation (PSF) held a vote for directors of the PSF board. One of the nominees was Alex Gaynor. In recognition of his work on Django, PyPy, and CPython, Alex was admitted as a new PSF director.
Following this decision, Alex has decided to step down from the DSF board, as he feels he will be not be able to give his Django Software Foundation (DSF) board position the attention it deserves.
Alex filled the seat vacated by the resignation of Dan Cox in July 2012. The Django Software Foundation would like to thank Alex for his diligent service over the last year.
Of course, Alex won't be going too far. He will continue to be a member of the Django core team, and as a director of the PSF he will be in a position to represent Django's interests in the broader Python community.
As a result of Alex's resignation, the DSF is calling for nominations for a replacement board member.
Formal nominations for the open board seat may be made by any DSF member. If you're not a DSF member, and you've got an idea of someone you'd like to see on the DSF board, feel free to suggest the name - if someone in the official membership agrees with you, they can formally propose that name for nomination.
What does a DSF board member do? DSF board members are expected to participate in a monthly board teleconference, and follow up on any activities generated by that teleconference. Depending on the business presented to the board, this may result in additional work over the course of the month. The work will usually be administrative and organisational in nature -- for example, representing the board in legal discussions, or liaising with groups performing work on the DSF's behalf.
The call for nominees closes at 1200 UTC on May 10.
Of course, if you'd like to be involved in the formal nomination and voting process, you need to be a member of the DSF. Developer members are individuals appointed by the DSF board in recognition of their service to the Django community. Corporate members are those that have contributed financially to the DSF. If you are interested in becoming a corporate member of the DSF, you can find out more on our corporate membership page.
If you've got any other questions about the board election process, please get in touch.
April 1, 2013
When Adrian, Wilson, and I first started talking about open sourcing Django, we knew that we didn't want to just throw the code over a wall and walk away. We wanted to build a community around the code, and we wanted that community to be one we'd enjoy.
Well, we succeeded beyond anything any of us could have imagined. Today, the Django community is this amazing, vibrant, exciting, exuberant thing, spanning the globe, encompassing tens of thousands of people from all walks of life. It's a community I'm intensely proud of: open and welcoming, friendly and helpful, calm and considerate.
But, like every growing thing, we have some growing pains. As we grow past the point where it's reasonable to expect that everyone knows everyone else, our values risk dilution. If we want this community to remain one that lives up to its ideals, then we need to be explicit about what those ideas area. (After all, explicit is better than implicit!)
To that end, the Django core team and the Django Software Foundation are working on formally adopting a code of conduct. It's a statement of ideals: it's a way for us to articulate what it is we think makes our community so great. Today we're publishing a rough draft of that document. Think of it as a "beta" release: we think it works, and we like it, but we want community feedback before we adopt it formally.