On Friday, November 15, the board of the Foundation voted for Barry Warsaw to receive a Community Service Award for Q3 2013. Barry's involvement in the Python community recently reached a significant milestone, as he retired the Python 2.6 line with its final security release (2.6.9). Since 2007, Barry acted as the release manager for 2.6, an instrumental release for a number of reasons, including working with the 3.x line to backport many features. He was simultaneously the 3.0 release manager at that time, which saw its first release two months after 2.6 came out.
Barry's involvement in the community extends long beyond contributions to the CPython project, into his work on the GNU Mailman project. He earned the 2008 Antonio Pizzagati Prize for Software in the Public Interest for his work on Mailman, which has become the world's most popular mailing list software, seen all around the web. It's rare to find a mailing list out there that isn't managed by Mailman.
He has also been a contributor to the Debian and Ubuntu projects, recently becoming a Debian Member in June. He has spent a good bit of time on Ubuntu's shift to Python 3, mapping out dependencies and working with upstream projects to ensure a quality port of their codebase.
When he's not jamming on Python, he's jamming on a bass guitar. Check out some of his music here.
Congratulations, and thanks for all of your hard work!
News from the Python Software Foundation
Tuesday, November 19, 2013
Monday, September 09, 2013
Cloud, HPC And Open Technologies Converge To Fuel Research, Innovation
When you put leaders of industry, research, and academia in a room for a day, what do you get? If you were at Argonne National Laboratory last month for the workshop on resource intensive open clouds, you got a taste of progress. The workshop was organized by leaders from Notre Dame University, Internet2, and Rackspace, in the interests of figuring out the next steps for the technical computing world, bridging old-world high performance computing with the new-world of cloud computing.
I was invited to this workshop on behalf of the PSF, and was excited by the prospect of being involved in an open and collaborative environment, tasked with figuring out how all of these sides of the story could come together. Many of the attendees are using OpenStack, an open cloud computing platform implemented in Python, and Python was a key technology for many of them in other ways. It looks like OpenStack-based and community-owned open clouds will likely become key points as the group progresses towards a better landscape to solve their computing needs, and if the past is any indication, Python will remain an important piece of the software powering it.
"The pace of innovation is accelerated and the diversity of solutions and approaches ensures that good solutions persist and not so good ones are quickly identified," said event organizer Paul Rad of Rackspace, on the topic of open and transparent workshops like this one.
My hope for this group is that future workshops can leverage some of our leaders in Python's large scientific community, many of whom are undoubtedly facing the challenges this workshop set out to improve on. Feel free to contact me at brian@python.org if you're interested in contributing to future efforts.
For more details on the workshop, see Paul's post on the subject at http://www.rackspace.com/blog/cloud-hpc-and-open-technologies-converge-to-fuel-research-innovation/. If you are interested in learning more about this initiative and/or in participating in future workshop sessions, please email OpenCloud@internet2.edu.
I was invited to this workshop on behalf of the PSF, and was excited by the prospect of being involved in an open and collaborative environment, tasked with figuring out how all of these sides of the story could come together. Many of the attendees are using OpenStack, an open cloud computing platform implemented in Python, and Python was a key technology for many of them in other ways. It looks like OpenStack-based and community-owned open clouds will likely become key points as the group progresses towards a better landscape to solve their computing needs, and if the past is any indication, Python will remain an important piece of the software powering it.
"The pace of innovation is accelerated and the diversity of solutions and approaches ensures that good solutions persist and not so good ones are quickly identified," said event organizer Paul Rad of Rackspace, on the topic of open and transparent workshops like this one.
My hope for this group is that future workshops can leverage some of our leaders in Python's large scientific community, many of whom are undoubtedly facing the challenges this workshop set out to improve on. Feel free to contact me at brian@python.org if you're interested in contributing to future efforts.
For more details on the workshop, see Paul's post on the subject at http://www.rackspace.com/blog/cloud-hpc-and-open-technologies-converge-to-fuel-research-innovation/. If you are interested in learning more about this initiative and/or in participating in future workshop sessions, please email OpenCloud@internet2.edu.
Thursday, September 05, 2013
Python Surpasses Standards, Reaches New Levels of Quality
Throughout Python's 20-plus year history, its quality has been in the hands of the volunteers around the world openly contributing to it. Thanks to Coverity, those volunteers have been pointed to many quality and security issues via Coverity Scan, a service which finds defects in C/C++ and Java projects at no cost.
As the CPython project includes over 370,000 lines of C code*, accounting for 42% of the codebase, a lot of it lies outside of the analysis tools our community has created to work with Python code. Since 2006, Coverity's scans of that code have found nearly 1,000 defects, 860 of which our contributors have fixed.
In an industry where the standard defect density is a rate of 1 per 1,000 lines of code, CPython has attained a rate of 0.005 defects per 1,000 lines, and "introduces a new level of quality for open source software," said Coverity.
“Python is the model citizen of good code quality practices, and we applaud their contributors and maintainers for their commitment to quality,” said Jennifer Johnson, chief marketing officer for Coverity.
The PSF and the rest of the community join Coverity in applauding all of those who have contributed their time and effort to make CPython a better project, along with the countless others who contribute to a powerful landscape of Python interpreters.
For more information, read Coverity's "Coverity Finds Python Sets New Level of Quality for Open Source Software" press release.
* generated using David A. Wheeler's 'SLOCCount'.
As the CPython project includes over 370,000 lines of C code*, accounting for 42% of the codebase, a lot of it lies outside of the analysis tools our community has created to work with Python code. Since 2006, Coverity's scans of that code have found nearly 1,000 defects, 860 of which our contributors have fixed.
In an industry where the standard defect density is a rate of 1 per 1,000 lines of code, CPython has attained a rate of 0.005 defects per 1,000 lines, and "introduces a new level of quality for open source software," said Coverity.
“Python is the model citizen of good code quality practices, and we applaud their contributors and maintainers for their commitment to quality,” said Jennifer Johnson, chief marketing officer for Coverity.
The PSF and the rest of the community join Coverity in applauding all of those who have contributed their time and effort to make CPython a better project, along with the countless others who contribute to a powerful landscape of Python interpreters.
For more information, read Coverity's "Coverity Finds Python Sets New Level of Quality for Open Source Software" press release.
* generated using David A. Wheeler's 'SLOCCount'.
Monday, August 05, 2013
Congratulations to Jessica McKellar, O'Reilly Open Source Award Recipient
The Python Software Foundation congratulates Jessica McKellar for winning a 2013 O'Reilly Open Source Award for her contributions to the Python community. The award was presented at OSCON in Portland, Oregon on July 26.
Jessica is an entrepreneur, software engineer, and open source developer from Cambridge, Massachusetts, USA. She is also a prolific volunteer in the Python community:
She is currently a Director for the Foundation and vice-chair of the PSF's Outreach and Education Committee. She is also an organizer for the largest Python user group in the world in Boston, Massachusetts, USA. With that group she runs the Boston Python Workshop, an introductory programming pipeline that has brought hundreds of women into the local Python community. The group has been so successful that it is being replicated in cities across the US.
She is tirelessly constructing new curricula and events that she play-tests with Boston Python and then pushes to the broader community under a permissive license to re-use and remix. Examples include an intro to Python workshop for first-time programmers, an intro to open source contribution workshop, a project-based intermediate Python workshop, and a CPython sprint for new contributors.
In addition to being a frequent conference speaker herself, Jessica has been evangelizing Python and PyCon in her role as the Diversity Outreach coordinator for PyCon 2014.
Thank you Jessica for all your contributions to the Python community.Jessica is an entrepreneur, software engineer, and open source developer from Cambridge, Massachusetts, USA. She is also a prolific volunteer in the Python community:
She is currently a Director for the Foundation and vice-chair of the PSF's Outreach and Education Committee. She is also an organizer for the largest Python user group in the world in Boston, Massachusetts, USA. With that group she runs the Boston Python Workshop, an introductory programming pipeline that has brought hundreds of women into the local Python community. The group has been so successful that it is being replicated in cities across the US.
She is tirelessly constructing new curricula and events that she play-tests with Boston Python and then pushes to the broader community under a permissive license to re-use and remix. Examples include an intro to Python workshop for first-time programmers, an intro to open source contribution workshop, a project-based intermediate Python workshop, and a CPython sprint for new contributors.
In addition to being a frequent conference speaker herself, Jessica has been evangelizing Python and PyCon in her role as the Diversity Outreach coordinator for PyCon 2014.
The PSF also congratulates the other winners of this year's award:
- Behdad Esfahbod of HarfBuzz
- Limor Fried of Adafruit Industries
- Valerie Aurora of the Ada Initiative
- Paul Fenwick of Perl
- Martin Michlmayr of the Debian Project
Wednesday, July 31, 2013
Sponsoring Teen Tech Camp in Durham, NC
The Python Software Foundation is happy to support an upcoming event in the Durham, NC area: Teen Tech Camp 2013! At the end of May, the board voted in favor of a $2000 grant to support the event that will use Python and the Raspberry Pi to teach local teens the joy of programming. For more information, see organizer Julia Elman's announcement, included below.
Local Teens Learn Computer Programming Using Raspberry Pi Microcomputers
Durham, NC – Refresh the Triangle is proud to announce Teen Tech Camp 2013, a one-day event to teach computer programming to area youth. The camp is the second to be hosted by Refresh the Triangle, in partnership with Durham County Library.
This year, students will learn basic Python computer programming concepts through the use of interactive curriculum with a Raspberry Pi, a pocket sized PC developed in the UK by the Raspberry Pi Foundation with the intention of promoting the teaching of basic computer science in schools.
Along with generous community volunteer support, a grant from the Python Software Foundation has made it so that each of the 20 students will receive his or her own Raspberry Pi, books and other materials to help further computer programing education.
Support from the following organizations has also helped to make this event possible: Ayima, Adzerk, Caktus Group, Greenlight Community Broadband, Linux New Media, Splatspace, Triangle Ecycling, TriLUG and TriPython.
The event will take place Tuesday, August 13, at the Southwest Durham Regional Library (3605 Shannon Rd., Durham, NC 27707) from 10:00AM – 5:00PM.
For more information about the Teen Tech Camp 2013 and/or to schedule interviews, please email me at: juliaelman@gmail.com
Wednesday, June 05, 2013
Announcing a Code of Conduct for use by the Python community
On 19 April, 2013, members of the Python Software Foundation voted to approve a Code of Conduct for use by the Python community. That code is now available on our website at http://www.python.org/psf/codeofconduct/. The content is included below:
What follows is text similar to the justification which was sent to our voting members, which serves as an introduction for why the Foundation wants to promote a code, along with details of why the code is written how it is, and how this code can be used.
The Python language is just over 20 years old, and the Python Software Foundation is just over 10 years old. Overall, the Python community as we know it today, is fairly young. While the community has grown nicely over the years, we’re at a great point where we can see growth in a number of areas if we take care to be explicitly welcoming.
Python generally is a welcoming place. When it comes to code, developers are more than happy to work with anyone who is willing to take the time to contribute. When it comes to user groups, leaders are happy to have anyone who is willing to show up. When it comes to conferences, organizers are happy to receive talks from anyone willing to submit.
When it comes to those willing to jump into these areas of the community, we’re unbalanced and not seeing the true spectrum of the greater community. It’ll take time, but we can advance towards a more diverse representation, one that we see throughout the rest of the community being increasingly populated by women, students, and with the popularity of pocket-sized computers, children will soon be in the ranks. We think we can do this is in part by ensuring a consistent and healthy environment for those wanting to be a part of it.
This Code of Conduct, or CoC, presents a set of traits that members of our community value and uphold. The traits are taken from the existing behaviors that we have experienced throughout our work around the community. These are traits that help get work done, help members feel included, and help Python succeed.
Python got to where it is by being open, and it’ll continue to prosper by remaining open. Being explicit about the many aspects of our openness will encourage participation and use by more people.
Python has experienced everything up through fanatical uptake, often attributed to the kindness and consideration of the community. It’s a home away from home for some. It got us this far and ensuring we remain as such will benefit everyone involved, old or new.
Python and just about everything associated with it runs thanks to the efforts of volunteers. In most cases, the same volunteers have been in their roles for years, thanks to a community that respects the time, effort, and contribution of all involved. We want to see those same contributors forge on while also growing more to join them. Python depends on this.
This CoC makes no attempt to tell a person what not to do. It’s not intended to be a checklist to make sure one is a good community member. It’s not a document of minimum standards, and it’s not a way to keep people out. No specific incident prompted the creation of this CoC.
This CoC should not be seen as something negative, and it’s not trying to change anything. Without this CoC, the Python community would continue on as it has since its inception. However, we think it’s time to be explicit in ensuring that everyone has a place in this community, and that is what the CoC is for.
The PSF supports and advocates for the use of the CoC throughout the community, but without adoption by specific areas, the CoC is merely a document that the Foundation is supportive of. The way it’s useful is that an area of the community can adopt the CoC and use it as a guideline for participation. It could be adopted by mailing lists, IRC channels, the bug tracker, user groups, sprints, and more.
For example, a mailing list could say that their membership should adhere to the CoC. Doing so sets an open, considerate, and respectful tone for the mailing list participants. It signals to everyone from first-timers to list veterans that the list is open to their ideas, is considerate of the efforts put forth, and will respectfully discuss the list’s topics. If that mailing list feels it is appropriate, they could choose to enact relevant policy around following the CoC. Sometimes a heated discussion may cross the line, so perhaps they ask particular parties to step back and observe for a bit to bring the discussion back on track.
The first application of the CoC is by us, the Python Software Foundation. Our members are expected to uphold the CoC when using our mailing list, representing our foundation, and representing the Python community.
As of yesterday, the python-ideas mailing list administrators announced that members of that list should adhere to the CoC. They call for people not following the code to be made aware of what they’re doing, or to do so privately via the administrators. By letting them know, they can hopefully work on their actions and make for a better environment moving forward. They also state a policy that people repeatedly going against the code could be removed. As administrator Brett Cannon stated in his announcement of the CoC adoption, he recalled only one instance when removal would have been appropriate in the history of the list throughout its 6.5 year history. What the adoption hopefully signals is that newcomers and veterans alike should feel that they can jump right in to a welcoming group and share their latest ideas with the Python development community.
http://python.org/psf/codeofconduct/ is where you can find the CoC on the Python website.
The code itself lives at http://hg.python.org/coc/, with the initial revision pushed as changeset 689163936c9d.
If you’re familiar with the codes of conduct for the Ubuntu and Fedora projects, the “considerate” and “respectful” points exist in both of them, along with many other codes. When this CoC was written, it started off on paper with a big list of traits, which was eventually trimmed down to a small handful. After reading many other codes and similar documents, it was trimmed down further into the three traits we have today: open, considerate, and respectful. From there, original text was written in support of the traits.
Another familiarity may be with the PyCon Code of Conduct and the PSF’s tie to PyCon, but that’s only similar in that it’s also called a Code of Conduct. That’s an entirely different document, written for use at an in-person conference.
Yes. Changes can be proposed as resolutions placed before the PSF’s Board of Directors, who may then vote on it. As was the case with the CoC itself, the board voted to approve that the wider membership would vote on the implementation, so depending on the change, that could also be the case.
The Python community is made up of members from around the globe with a diverse set of skills, personalities, and experiences. It is through these differences that our community experiences great successes and continued growth. When you're working with members of the community, we encourage you to follow these guidelines which help steer our interactions and strive to keep Python a positive, successful, and growing community.
A member of the Python community is:
Open
Members of the community are open to collaboration, whether it's on PEPs, patches, problems, or otherwise. We're receptive to constructive comment and criticism, as the experiences and skill sets of other members contribute to the whole of our efforts. We're accepting of all who wish to take part in our activities, fostering an environment where anyone can participate and everyone can make a difference.
Considerate
Members of the community are considerate of their peers -- other Python users. We're thoughtful when addressing the efforts of others, keeping in mind that often times the labor was completed simply for the good of the community. We're attentive in our communications, whether in person or online, and we're tactful when approaching differing views.
Respectful
Members of the community are respectful. We're respectful of others, their positions, their skills, their commitments, and their efforts. We're respectful of the volunteer efforts that permeate the Python community. We're respectful of the processes set forth in the community, and we work within them. When we disagree, we are courteous in raising our issues.
Overall, we're good to each other. We contribute to this community not because we have to, but because we want to. If we remember that, these guidelines will come naturally.
What follows is text similar to the justification which was sent to our voting members, which serves as an introduction for why the Foundation wants to promote a code, along with details of why the code is written how it is, and how this code can be used.
Why implement a Code of Conduct?
The Python language is just over 20 years old, and the Python Software Foundation is just over 10 years old. Overall, the Python community as we know it today, is fairly young. While the community has grown nicely over the years, we’re at a great point where we can see growth in a number of areas if we take care to be explicitly welcoming.
Python generally is a welcoming place. When it comes to code, developers are more than happy to work with anyone who is willing to take the time to contribute. When it comes to user groups, leaders are happy to have anyone who is willing to show up. When it comes to conferences, organizers are happy to receive talks from anyone willing to submit.
When it comes to those willing to jump into these areas of the community, we’re unbalanced and not seeing the true spectrum of the greater community. It’ll take time, but we can advance towards a more diverse representation, one that we see throughout the rest of the community being increasingly populated by women, students, and with the popularity of pocket-sized computers, children will soon be in the ranks. We think we can do this is in part by ensuring a consistent and healthy environment for those wanting to be a part of it.
What this Code of Conduct is
This Code of Conduct, or CoC, presents a set of traits that members of our community value and uphold. The traits are taken from the existing behaviors that we have experienced throughout our work around the community. These are traits that help get work done, help members feel included, and help Python succeed.
Python got to where it is by being open, and it’ll continue to prosper by remaining open. Being explicit about the many aspects of our openness will encourage participation and use by more people.
Python has experienced everything up through fanatical uptake, often attributed to the kindness and consideration of the community. It’s a home away from home for some. It got us this far and ensuring we remain as such will benefit everyone involved, old or new.
Python and just about everything associated with it runs thanks to the efforts of volunteers. In most cases, the same volunteers have been in their roles for years, thanks to a community that respects the time, effort, and contribution of all involved. We want to see those same contributors forge on while also growing more to join them. Python depends on this.
What this Code of Conduct is not
This CoC makes no attempt to tell a person what not to do. It’s not intended to be a checklist to make sure one is a good community member. It’s not a document of minimum standards, and it’s not a way to keep people out. No specific incident prompted the creation of this CoC.
This CoC should not be seen as something negative, and it’s not trying to change anything. Without this CoC, the Python community would continue on as it has since its inception. However, we think it’s time to be explicit in ensuring that everyone has a place in this community, and that is what the CoC is for.
Application of this Code of Conduct
The PSF supports and advocates for the use of the CoC throughout the community, but without adoption by specific areas, the CoC is merely a document that the Foundation is supportive of. The way it’s useful is that an area of the community can adopt the CoC and use it as a guideline for participation. It could be adopted by mailing lists, IRC channels, the bug tracker, user groups, sprints, and more.
For example, a mailing list could say that their membership should adhere to the CoC. Doing so sets an open, considerate, and respectful tone for the mailing list participants. It signals to everyone from first-timers to list veterans that the list is open to their ideas, is considerate of the efforts put forth, and will respectfully discuss the list’s topics. If that mailing list feels it is appropriate, they could choose to enact relevant policy around following the CoC. Sometimes a heated discussion may cross the line, so perhaps they ask particular parties to step back and observe for a bit to bring the discussion back on track.
The first application of the CoC is by us, the Python Software Foundation. Our members are expected to uphold the CoC when using our mailing list, representing our foundation, and representing the Python community.
As of yesterday, the python-ideas mailing list administrators announced that members of that list should adhere to the CoC. They call for people not following the code to be made aware of what they’re doing, or to do so privately via the administrators. By letting them know, they can hopefully work on their actions and make for a better environment moving forward. They also state a policy that people repeatedly going against the code could be removed. As administrator Brett Cannon stated in his announcement of the CoC adoption, he recalled only one instance when removal would have been appropriate in the history of the list throughout its 6.5 year history. What the adoption hopefully signals is that newcomers and veterans alike should feel that they can jump right in to a welcoming group and share their latest ideas with the Python development community.
Where does the code live?
http://python.org/psf/codeofconduct/ is where you can find the CoC on the Python website.
The code itself lives at http://hg.python.org/coc/, with the initial revision pushed as changeset 689163936c9d.
This looks familiar...
If you’re familiar with the codes of conduct for the Ubuntu and Fedora projects, the “considerate” and “respectful” points exist in both of them, along with many other codes. When this CoC was written, it started off on paper with a big list of traits, which was eventually trimmed down to a small handful. After reading many other codes and similar documents, it was trimmed down further into the three traits we have today: open, considerate, and respectful. From there, original text was written in support of the traits.
Another familiarity may be with the PyCon Code of Conduct and the PSF’s tie to PyCon, but that’s only similar in that it’s also called a Code of Conduct. That’s an entirely different document, written for use at an in-person conference.
Can we make changes to the code in the future?
Yes. Changes can be proposed as resolutions placed before the PSF’s Board of Directors, who may then vote on it. As was the case with the CoC itself, the board voted to approve that the wider membership would vote on the implementation, so depending on the change, that could also be the case.
Tuesday, April 30, 2013
Welcome Newly Elected Members
The Foundation recently held elections after PyCon 2013, and the results are in!
All members of the PSF are nominated by an existing member for their work in the Python community. We have quite a diverse set of community members joining us this year, with representation across many countries and individuals contributing to many areas of the Python world.
All members of the PSF are nominated by an existing member for their work in the Python community. We have quite a diverse set of community members joining us this year, with representation across many countries and individuals contributing to many areas of the Python world.
As with years past, a group of individuals known for their contributions of code, either to Python implementations or other projects in the Python ecosystem, were elected. We also have a number of members recognized for their work with PyCon and other Python conferences around the world. Community effort is another theme and we have several members known for their work building and expanding their local Python communities as well as the global community.
Please join us in welcoming all of the new members to the Foundation!
- Érico Andrei
- Kamon Ayeva
- Reimar Bauer
- Diana Clarke
- Robert Collins
- Simon Cross
- Katie Cunningham
- Kushal Das
- Ned Deily
- Jeremy Dunck
- Emmanuelle Gouillart
- Olivier Grisel
- Eric Holscher
- Mathieu Leduc-Hamel
- Chris Neugebauer
- Terri Oda
- Jason Pellerin
- Lynn Root
- Osvaldo Santana
- Hynek Schlawack
- Anthony Scopatz
- Barbara Shaurette
- Gael Varoquaux
- Stefan van der Walt
- Stephane Wirtel
The Board of Directors also held elections, and the spots of departing members were filled. The Foundation wishes to thank Steve Holden, Andrew Kuchling, and Martin von Löwis for all of their time devoted to Python, the PSF, and to its board over all of their long tenures with the organization.
Eight board members were re-elected to their positions, and three new members were elected to join the board under Van Lindberg's chairmanship. The new board members are:
- Brett Cannon
- Alex Gaynor
- Lynn Root
The full membership list is available at http://www.python.org/psf/members/.
Monday, March 25, 2013
Congratulations to Fernando Perez, Recipient of FSF’s Advancement of Free Software Award
On Saturday March 23, Dr. Fernando Perez was presented the Free Software Foundation’s annual Award for the Advancement of Free Software for his work on IPython. The award “is given annually to an individual who has made a great contribution to the progress and development of free software, through activities that accord with the spirit of free software.”
Fernando, who was elected to the PSF in 2010, received the award at LibrePlanet 2013, which took place at Harvard University in Cambridge, Massachusetts. He dedicated the award to the late John Hunter, creator of matplotlib, who passed away last August. John was posthumously awarded the Foundation’s Distinguished Service Award.
The Foundation congratulates Fernando on his great work on IPython and his efforts all around the community!
For more information, see the FSF’s announcement: https://www.fsf.org/news/2012-free-software-award-winners-announced-2
Wednesday, March 20, 2013
Farewell Malcolm
While we celebrated the Python community last week at PyCon, we quietly lost one of our own. Malcolm Tredinnick, core Django developer and longtime member of the PSF passed away this past weekend.
Malcolm embodied the type of ideals that we all strive for in the Python community. He was known both for his code and for his kindness, for his intelligence and his humanity. Malcolm was a regular in the #django channel on IRC. It might have been intimidating to new users to be chatting with the author of the Django ORM, but he always took the time to put people at ease and answer their questions.
We are grateful to have known Malcolm. We will miss him.
As Barbara Shaurette wrote:
"""
I encourage everyone to honor Malcolm's memory by following his example.
Submit that patch for a Django ORM ticket that you've putting off for a while.
Go into #django and help some new users.
Answer questions. Be nice.
"""
Memorial page on Storify
Official announcement on the Django website
Malcolm embodied the type of ideals that we all strive for in the Python community. He was known both for his code and for his kindness, for his intelligence and his humanity. Malcolm was a regular in the #django channel on IRC. It might have been intimidating to new users to be chatting with the author of the Django ORM, but he always took the time to put people at ease and answer their questions.
We are grateful to have known Malcolm. We will miss him.
As Barbara Shaurette wrote:
"""
I encourage everyone to honor Malcolm's memory by following his example.
Submit that patch for a Django ORM ticket that you've putting off for a while.
Go into #django and help some new users.
Answer questions. Be nice.
"""
Memorial page on Storify
Official announcement on the Django website
Monday, March 18, 2013
Python Software Foundation Reaches Settlement, Ends Trademark Dispute
via Marketwire
The Python Software Foundation has reached a settlement in its recent trademark dispute with PO Box Hosting Limited trading as Veber in Europe. The issue centered around Veber's use of the Python name for their cloud hosting services and their application for a figurative trademark incorporating the word "Python". While the Foundation retains the trademark for Python within the United States, it did not have a filing within the European Union. According to the terms of the settlement, Veber has withdrawn its trademark filing and has agreed to support the Python Software Foundation's use of the term.
The amicable agreement reached between the two sides will result in a rebranding of Veber's Python cloud server and backup services, which continue to be available at http://www.veber.co.uk. Veber will rebrand the Python services later under a yet to be determined name.
"We are happy to come to an agreement with Veber," said Van Lindberg, chairman of the Python Software Foundation. "What the PSF wants most is to support the global community of Python developers. To Veber's credit, they were willing to recognize the Python brand without protracted negotiations. We are grateful for Veber's support and we wish them luck in their business."
Tim Poultney, Managing Director of PO Box Hosting and Veber, said, "Veber are pleased to have reached a speedy and amicable agreement with the Python Software Foundation. The use of the Python name for our cloud server and backup business has ceased with the services now available in Europe from Veber. This agreement will remove potential confusion between the Python software language and our cloud services business."
The Foundation thanks the Python community for their immense outpouring of support throughout the dispute, both financially and through the letter writing campaign undertaken by organizations across European Union member states.
The Python Software Foundation has reached a settlement in its recent trademark dispute with PO Box Hosting Limited trading as Veber in Europe. The issue centered around Veber's use of the Python name for their cloud hosting services and their application for a figurative trademark incorporating the word "Python". While the Foundation retains the trademark for Python within the United States, it did not have a filing within the European Union. According to the terms of the settlement, Veber has withdrawn its trademark filing and has agreed to support the Python Software Foundation's use of the term.
The amicable agreement reached between the two sides will result in a rebranding of Veber's Python cloud server and backup services, which continue to be available at http://www.veber.co.uk. Veber will rebrand the Python services later under a yet to be determined name.
"We are happy to come to an agreement with Veber," said Van Lindberg, chairman of the Python Software Foundation. "What the PSF wants most is to support the global community of Python developers. To Veber's credit, they were willing to recognize the Python brand without protracted negotiations. We are grateful for Veber's support and we wish them luck in their business."
Tim Poultney, Managing Director of PO Box Hosting and Veber, said, "Veber are pleased to have reached a speedy and amicable agreement with the Python Software Foundation. The use of the Python name for our cloud server and backup business has ceased with the services now available in Europe from Veber. This agreement will remove potential confusion between the Python software language and our cloud services business."
The Foundation thanks the Python community for their immense outpouring of support throughout the dispute, both financially and through the letter writing campaign undertaken by organizations across European Union member states.
Tuesday, March 05, 2013
Get ready for Google Summer of Code
Python project contributors and student enthusiasts, mark your calendars: Google Summer of Code applications open soon!
Google Summer of Code is an annual, global program pairing student developers with mentors in open source projects for paid summer internships.
You can learn more about this year's Google Summer of Code here.
If your Python project is interested in participating in Google Summer of Code under the Python umbrella, it's time to start preparing your applications:
Read more about eligibility in the FAQ.
If you are interested in participating in Google Summer of Code under the Python umbrella, it's time to start exploring potential projects and practicing the tools of open source development:
Google Summer of Code is an annual, global program pairing student developers with mentors in open source projects for paid summer internships.
You can learn more about this year's Google Summer of Code here.
Python projects
Python serves as an umbrella organization for around a dozen open source Python projects each year. Last year Python core, mailman, Pandas, PyGame, Pylons, PySide, PySoy, scikit-learn, statsmodels, Tryton, and Twisted participated.If your Python project is interested in participating in Google Summer of Code under the Python umbrella, it's time to start preparing your applications:
- Tell the Python Google Summer of Code coordinators that your project wants to participate! Follow the instructions on the Python wiki.
- Review last year's projects and their idea pages.
- Start outlining candidate student projects. Good student projects are detailed, can be broken down into step-by-step goals, and are realistic in scope and difficulty for a 3-month student intern.
- Start gathering mentors. We recommend that each student have both a primary and backup mentor.
Important deadlines
- March 18: Mentoring organizations can begin submitting applications to Google.
- March 29: Mentoring organization application deadline.
Students
Google Summer of Code is a paid summer internship program for college/university students who will be 18 years of age or older on May 27, 2013. Participating in Google Summer of Code is a great way to develop real-world software engineering skills while giving back to an open source Python project you love.Read more about eligibility in the FAQ.
If you are interested in participating in Google Summer of Code under the Python umbrella, it's time to start exploring potential projects and practicing the tools of open source development:
- Read the Python Google Summer of Code guidelines.
- Review last year's projects and their idea pages.
- Start practicing the tools of open source development, including:
- IRC
- a revision control system like git or svn
- the diff and patch utilities
- bug trackers
Important deadlines
- April 8: List of accepted mentoring organizations published on theGoogle Summer of Code 2013 site.
- April 9 - 21: Student applicants discuss application ideas with mentoring organizations.
- April 22: Student application period opens.
- May 3: Student application deadline.
Monday, March 04, 2013
Introducing Electronic Contributor Agreements
We're happy to announce the new way to file a contributor agreement: on the web at http://www.python.org/psf/contrib/contrib-form/.
Through the use of Adobe's EchoSign, we got rid of the old hand-written, print out, scan or photograph, then fax or email of your form. It was a hassle for our contributors, and a hassle for our administrators. Faxes fail, mail gets lost, and sometimes pictures or scans turn out poorly. It was time to find a more user-friendly solution, and the Foundation is happy to finally offer this electronic form.
The new form is easy to fill out right on the site, guiding you through each of the required fields such as your name, bug tracker ID, address, and initial license. If you're signing the form on behalf of an organization, there's a check box to specify this, and then you are asked near the bottom to state your title in the organization. Lastly, your signature is either generated from your typed name, or you can draw your own or upload a signature file of your own.
Once you submit the form, you'll receive an email from echosign.com to verify the email address you entered. Once you click to confirm your address, the form will be emailed to the PSF and will be recorded.
We require all contributors to CPython to have a signed form, and we hope this makes it easier for potential contributors to join up and help make Python better. It's available just in time for PyCon and the CPython sprint that will be occurring March 18 through 21 in Santa Clara, California. Join us at the sprint, sign your contributor form, and help us fix some bugs or add some features!
Through the use of Adobe's EchoSign, we got rid of the old hand-written, print out, scan or photograph, then fax or email of your form. It was a hassle for our contributors, and a hassle for our administrators. Faxes fail, mail gets lost, and sometimes pictures or scans turn out poorly. It was time to find a more user-friendly solution, and the Foundation is happy to finally offer this electronic form.
The new form is easy to fill out right on the site, guiding you through each of the required fields such as your name, bug tracker ID, address, and initial license. If you're signing the form on behalf of an organization, there's a check box to specify this, and then you are asked near the bottom to state your title in the organization. Lastly, your signature is either generated from your typed name, or you can draw your own or upload a signature file of your own.
Once you submit the form, you'll receive an email from echosign.com to verify the email address you entered. Once you click to confirm your address, the form will be emailed to the PSF and will be recorded.
We require all contributors to CPython to have a signed form, and we hope this makes it easier for potential contributors to join up and help make Python better. It's available just in time for PyCon and the CPython sprint that will be occurring March 18 through 21 in Santa Clara, California. Join us at the sprint, sign your contributor form, and help us fix some bugs or add some features!
Tuesday, February 19, 2013
An Update on Our Trademark Issue
A few days ago, we reached out for help to gather evidence about the use of “Python” in Europe. We received an overwhelming response from the community, with hundreds of letters from individuals, companies, and universities, as well as scans of articles, book covers, conference T-shirts, and brochures. It has been truly been amazing to see.
Unfortunately, we also saw that there were a few who decided to directly attack the people and the company we are opposing. We put out a call for civility - and we want to emphasize that any hacktivism or threats will end up hurting the Python community in the long run. This is not who we are or how we act.
Although the issues have not yet been resolved, we are engaged in good-faith negotiations with the head of Veber, and we hope and expect that we will be able to announce a settlement soon.
Signed,
Van Lindberg
Chairman, Python Software Foundation
Unfortunately, we also saw that there were a few who decided to directly attack the people and the company we are opposing. We put out a call for civility - and we want to emphasize that any hacktivism or threats will end up hurting the Python community in the long run. This is not who we are or how we act.
Although the issues have not yet been resolved, we are engaged in good-faith negotiations with the head of Veber, and we hope and expect that we will be able to announce a settlement soon.
Signed,
Van Lindberg
Chairman, Python Software Foundation
Friday, February 15, 2013
Asking for civility during our trademark dispute
When we first announced our trademark issues yesterday, we immediately and continually received a great outpouring of support from our community. The number of supporting emails in our inbox is tremendous, and the financial support has been incredible. For this, we thank all of you.
However, it has come to our attention that the organization with which we are currently involved in a trademark dispute has been receiving messages from our community members, including threats. We ask that no matter who you support in this matter, that you remain civil in your communications and actions.
It is important that we maintain the positive and friendly atmosphere that Python is known for regardless of the situation at hand.
However, it has come to our attention that the organization with which we are currently involved in a trademark dispute has been receiving messages from our community members, including threats. We ask that no matter who you support in this matter, that you remain civil in your communications and actions.
It is important that we maintain the positive and friendly atmosphere that Python is known for regardless of the situation at hand.
Thursday, February 14, 2013
Python trademark at risk in Europe: We need your help!
For a French translation of this post, click here.
For anyone who works in a company that has an office in a EU Community member state, we need your help.
There is a company in the UK that is trying to trademark the use of the term "Python" for all software, services, servers... pretty much anything having to do with a computer. Specifically, it is the company that got a hold on the python.co.uk domain 13 years ago. At that time we weren't looking a lot at trademark issues, and so we didn't get that domain.
This hasn't been an issue since then because the python.co.uk domain has, for most of its life, just forwarded its traffic on to the parent companies, veber.co.uk and pobox.co.uk. Unfortunately, Veber has decided that they want to start using the name "Python" for their server products.
We contacted the owners of python.co.uk repeatedly and tried to discuss the matter with them. They blew us off and responded by filing the community trademark application claiming the exclusive right to use "Python" for software, servers, and web services - everywhere in Europe.
We got legal counsel in the UK and we (the PSF) are opposing the community trademark application, but our own trademark application hasn't yet matured. Accordingly, we are going with the trademark rights we have developed through using "Python" consistently over the past 20 years.
According to our London counsel, some of the best pieces of evidence we can submit to the European trademark office are official letters from well-known companies "using PYTHON branded software in various member states of the EU" so that we can "obtain independent witness statements from them attesting to the trade origin significance of the PYTHON mark in connection with the software and related goods/services." We also need evidence of use throughout the EU.
What can you do?
1. Do you work for a company that uses Python? Are in the EU, do you hire in the EU, or do you have an office in the EU? Could you write a letter on company letterhead that we can forward to our EU counsel?
We would want:
You can send a PDF copy of the letter to psf-trademarks@python.org
2. Do you have, or know of, anything that was published in the EU and uses "Python" to refer to Python-the-language? Can we get copies, pictures, or scans? This includes:
3. You can also help protect the Python intellectual property with financial support.
Since the costs of a trademark opposition are in the range of tens of thousands of dollars, we will need to find a way to refinance the legal costs of the opposition.
Please consider donating to the Python Software Foundation at:
http://www.python.org/psf/
or get in touch with me directly.
This is the first time the PSF has to take legal action to protect Python's intellectual property. Please do consider helping the PSF in any way you can. The threat is real and can potentially harm your business in Europe, especially if you are in the web hosting business and provide Python as part of your hosting plans.
Please let me know if there are any questions that I can answer. If you know someone who might have this information, please feel free to forward this.
Thanks,
Van Lindberg, Chairman
van@python.org
Python Software Foundation
[1] Class 9 - Computer software; Servers for web hosting; VPN [virtual private network] hardware; Internet servers; Internet servers.
[2] Class 42 - Design and development of computer hardware and software; Website hosting services; Hosting computer sites [websites]; Hosting the websites of others; Hosting of websites; Hosting the web sites of others on a computer server for a global computer network; Hosting websites on the Internet; Hosting the web sites of others; Web hosting services; Hosting of digital content, namely, on-line journals and blogs; Application service provider [ASP], namely, hosting computer software applications of others; Website hosting services; Hosting of digital content on the internet; Hosting of web sites; Hosting web sites; Hosting web sites for others; Hosting websites of others; Hosting of internet sites; Hosting the computer sites (web sites) of others; Web site hosting services; Hosting computer sites [web sites]; Hosting web sites of others; Rental of web servers; Servers (rental of web-); Servers (Rental of Web -).
For anyone who works in a company that has an office in a EU Community member state, we need your help.
There is a company in the UK that is trying to trademark the use of the term "Python" for all software, services, servers... pretty much anything having to do with a computer. Specifically, it is the company that got a hold on the python.co.uk domain 13 years ago. At that time we weren't looking a lot at trademark issues, and so we didn't get that domain.
This hasn't been an issue since then because the python.co.uk domain has, for most of its life, just forwarded its traffic on to the parent companies, veber.co.uk and pobox.co.uk. Unfortunately, Veber has decided that they want to start using the name "Python" for their server products.
We contacted the owners of python.co.uk repeatedly and tried to discuss the matter with them. They blew us off and responded by filing the community trademark application claiming the exclusive right to use "Python" for software, servers, and web services - everywhere in Europe.
We got legal counsel in the UK and we (the PSF) are opposing the community trademark application, but our own trademark application hasn't yet matured. Accordingly, we are going with the trademark rights we have developed through using "Python" consistently over the past 20 years.
According to our London counsel, some of the best pieces of evidence we can submit to the European trademark office are official letters from well-known companies "using PYTHON branded software in various member states of the EU" so that we can "obtain independent witness statements from them attesting to the trade origin significance of the PYTHON mark in connection with the software and related goods/services." We also need evidence of use throughout the EU.
What can you do?
1. Do you work for a company that uses Python? Are in the EU, do you hire in the EU, or do you have an office in the EU? Could you write a letter on company letterhead that we can forward to our EU counsel?
We would want:
- just a brief description of how Python is used at your company,
- how your company looks for and recognizes "Python" as only coming from the PSF, and
- your view that another company using term Python to refer to services, software, and servers would be confusing
You can send a PDF copy of the letter to psf-trademarks@python.org
2. Do you have, or know of, anything that was published in the EU and uses "Python" to refer to Python-the-language? Can we get copies, pictures, or scans? This includes:
- Books
- Pamphlets
- Conference programs or talks
- Job listings
- Magazines or other publications
- Prospectuses
3. You can also help protect the Python intellectual property with financial support.
Since the costs of a trademark opposition are in the range of tens of thousands of dollars, we will need to find a way to refinance the legal costs of the opposition.
Please consider donating to the Python Software Foundation at:
http://www.python.org/psf/
or get in touch with me directly.
This is the first time the PSF has to take legal action to protect Python's intellectual property. Please do consider helping the PSF in any way you can. The threat is real and can potentially harm your business in Europe, especially if you are in the web hosting business and provide Python as part of your hosting plans.
Please let me know if there are any questions that I can answer. If you know someone who might have this information, please feel free to forward this.
Thanks,
Van Lindberg, Chairman
van@python.org
Python Software Foundation
[1] Class 9 - Computer software; Servers for web hosting; VPN [virtual private network] hardware; Internet servers; Internet servers.
[2] Class 42 - Design and development of computer hardware and software; Website hosting services; Hosting computer sites [websites]; Hosting the websites of others; Hosting of websites; Hosting the web sites of others on a computer server for a global computer network; Hosting websites on the Internet; Hosting the web sites of others; Web hosting services; Hosting of digital content, namely, on-line journals and blogs; Application service provider [ASP], namely, hosting computer software applications of others; Website hosting services; Hosting of digital content on the internet; Hosting of web sites; Hosting web sites; Hosting web sites for others; Hosting websites of others; Hosting of internet sites; Hosting the computer sites (web sites) of others; Web site hosting services; Hosting computer sites [web sites]; Hosting web sites of others; Rental of web servers; Servers (rental of web-); Servers (Rental of Web -).
Wednesday, January 16, 2013
"Software Wars" the movie - featuring Python!
As the Software Wars indiegogo campaign comes to a close in the last 40 hours, did you know Python plays a role in the movie? Creator Keith Curtis wrote to us to mention that William Stein, creator of Sage, is interviewed and endorses Python's use for teaching mathematics to children. There are also plans to interview others in the community, perhaps some of the children making use of Python.
The creators greatly appreciate your contributions to make Software Wars possible!
The creators greatly appreciate your contributions to make Software Wars possible!
Monday, January 07, 2013
wiki.python.org Compromised
On December 28th, an unknown attacker used a previously unknown remote code exploit on http://wiki.python.org/. The attacker was able to get shell access as the "moin" user, but no other services were affected.
Some time later, the attacker deleted all files owned by the "moin" user, including all instance data for both the Python and Jython wikis. The attack also had full access to all MoinMoin user data on all wikis. In light of this, the Python Software Foundation encourages all wiki users to change their password on other sites if the same one is in use elsewhere. We apologize for the inconvenience and will post further news as we bring the new and improved wiki.python.org online.
If you have any questions about this incident please contact jnoller@python.org. Thank you for your patience.
Some time later, the attacker deleted all files owned by the "moin" user, including all instance data for both the Python and Jython wikis. The attack also had full access to all MoinMoin user data on all wikis. In light of this, the Python Software Foundation encourages all wiki users to change their password on other sites if the same one is in use elsewhere. We apologize for the inconvenience and will post further news as we bring the new and improved wiki.python.org online.
If you have any questions about this incident please contact jnoller@python.org. Thank you for your patience.
Wednesday, January 02, 2013
A Look Back at the PSF in 2012
2012 year was a good year for Python, and it was especially good for the Python Software Foundation. Here’s a look back at some of the highlights of the foundation’s actions in 2012. As always, you can find out about the resolutions that the board has passed at http://www.python.org/psf/records/board/resolutions/ and each meeting of the board of directors has minutes posted at http://www.python.org/psf/records/board/minutes/.
Overall, it was a great year, and we’re looking forward to an even better 2013. You can make it even better by making a contribution to the foundation at http://www.python.org/psf/donations/!
Conference Sponsorship
The foundation sponsored 18 conferences in 15 countries for a total of USD $32,661.53. Among those funded were a group of established conferences, and something we’re always happy to find out about: new conferences. The inaugural PyCarolinas, and PyCons in South Africa, Philippines, and Canada were newcomers to the conference scene, along with RuPy Brazil starting a new branch of the RuPy brand.
The following conferences were granted funding in the 2012 calendar year:
- PyCon Australia
- Kiwi PyCon
- PyArgentina
- EuroPython
- PythonBrazil
- PyOhio
- SciPy
- PyCon DE
- PyCon UK
- PyCon India
- PyCon Philippines
- PyCon PL
- PyCon ZA
- PyArkansas
- PyCon Canada
- PyData
- RuPy Brno
- RyPy Brazil
Code of Conduct
In keeping up with the current conference scene, the foundation moved to suggest that all conferences implement a Code of Conduct for their events. Many conferences have done so on their own, and the foundation agreed that it’s a good thing for all conferences to have in place.
A second resolution was passed, making it a requirement that PSF-funded conferences have a Code of Conduct in place. The foundation wants to support conferences that support their attendees, so the move was a natural fit.
Community Service Awards
Each quarter, the foundation selects one or two community members to be presented with a Community Service Award. The award aims to reward those who have made substantial contributions to the Python community, with the recipient receiving a certificate and either a free pass to PyCon or USD $500.
This year’s winners were:
Q2: Doug Hellmann and Thomas Heller
Distinguished Service Award
Matplotlib’s creator and longtime maintainer, John Hunter, passed away in August of 2012 after a brief battle with cancer. John’s contributions not only to Python but to computing, mathematics, and science, have changed the way people do things. His matplotlib project has existed for over 10 years, initiated during his post-doctoral studies while looking for alternatives to proprietary products in the same field, and his dedication to free software never faded throughout his leadership of the project. His efforts also extended into the recently created NumFOCUS Foundation, of which he was a member of the board.
When John passed away, the foundation wanted to do something for John’s significant achievements, thus the creation of the Distinguished Service Award and the choosing of him as the first recipient. The award is to be presented annually to a member of the community who has exhibited long lasting contributions of high impact, coming with a prize of USD $5,000.
The award was presented to John’s family at a memorial service at his alma mater, University of Chicago.
Frank Willison Memorial Award
Each year the foundation recommends the recipient of the annual Frank Willison Memorial Award, an award delivered in conjunction with O’Reilly Media to commemorate O’Reilly’s long time editor-in-chief and Python fan, Frank Willison, who passed away in 2001.
The 2012 recipient of the award was Jesse Noller, whose outstanding efforts have reached many areas of the Python community. Jesse began as a CPython contributor and has since gotten involved in PyCon, acting as the Program Committee chair in 2010 and 2011, and the conference chair in 2012 and 2013. His leadership of the 2012 conference lead to the breaking of just about every record, from sponsorship counts to talk proposals received, on up through attendance and into revenues. However, Jesse’s efforts extend far beyond CPython and PyCon, into the creation of many efforts around the Python community.
Hardware
One of the first actions of the year was approval for hardware purchases to replace an aging python.org infrastructure, thanks to a donation by Atlassian. Oregon State University’s Open Source Lab offered their services for hosting the new hardware, and for their services and commitment to open source, a donation of $3000 was made to them.
A few months later, the purchase of a long-term storage array was approved for use by the PSF and the Django Software Foundation, to be maintained by long-time PyCon video coordinator, Carl Karsten. Carl stores several terabytes of conference video from events such as PyCon, PyOhio, PyTexas, and other events.
Sponsor Members
While the foundation is made up mostly of individual members, sponsor members are a class of membership for organizations who make a yearly contribution to the foundation. Like any other members, sponsor members are put before the current membership for election, after being recommended to the membership by the board of directors.
2012 saw four organizations recommended and then approved by the membership:
Event Coordinator and Secretary
As the conference landscape has grown, not just with PyCon, the foundation’s largest event, but with events around the globe, the need arose for a dedicated employee to organize and work with the existing volunteers. Ewa Jodlowska, who formerly worked with a conference organization company, was hired to manage the logistics of a conference the size of PyCon and to assist the chairman in ensuring a successful and smooth event.
After a few months in this position, Ewa expanded her role to include secretarial duties for the foundation.
Conference Kits
As the foundation found itself sponsoring plenty of conferences this year, many which include booth space in an expo hall, several “conference kits” were purchased that could be sent around the world and used by members at the conference to represent the foundation. So far the kits have made their way to a few conferences since their purchase. If you see one at a conference near you, stop by and say hello!
http://i.imgur.com/ndVhW.jpg
Funding
The foundation has long held an open call for grant requests, and this year three were approved.
In April, the board approved a USD $5,000 request from Armin Rigo of the PyPy team for work on their Software Transactional Memory project. October saw the passing of a USD $5,000 grant to the developers of Kivy, a multi-touch framework, to assist in their efforts to port the project to Python 3. Also on the topic of Python 3 porting was a USD $1,000 grant for Mikhail Korobov to work with NLTK maintainer Steven Bird to complete their port of the library.
Raspberry Pi
In April a resolution was passed that the foundation would purchase 50 Raspberry Pi devices, to use as raffle prizes, to give to interested projects, and for other uses to allow the device to see wider use in the hands of Python users. Several have been given away, including most recently that one will be added to the Snakebite testing environment, which will then be added to CPython’s buildbot fleet.
New Website
After a request for proposal period over the summer, a redesign committee deliberated over the selections and suggested to the foundation’s board a combination bid between Revolution Systems, Project Evolution, and Divio to design and implement a new python.org. Work is currently underway, and Jesse Noller wrote about the project’s progress on November 28.
The redesign project was a long time in the making, and the RFP process went smoothly. The progress we’re seeing so far has been excellent and we’re looking forward to presenting the finished project.
Overall, it was a great year, and we’re looking forward to an even better 2013. You can make it even better by making a contribution to the foundation at http://www.python.org/psf/donations/!