5.1   Event Coordinator Report

1. PyCon AV Management

• Worked on creating the RFP for AV for 2014 and 2015. In the process of receiving proposals from companies.

2. PyCon Budgeting

• Working on budget for 2014

3. PyCon Electrical

• worked on RFP to send out to decorator vendors (such as Freeman and GES), this included info on electrical that will be needed in 2014. In the process of receiving the proposals from various companies.

4. Future Event Planning

• Started to outline the RFP for 2016/2017. We have an interest from the Denver CVB.
• We now also have interest from Philadelphia, Portland, and New York City. Working with all of these groups to get the best proposal from each city.

5. PyCon Hotel/CC Management

• Went through final bill, removed all charges that didn't belong, split up the charges based on categories in our budget and added each category to the ledger

6. PyCon Housing Management

• Worked on getting the final pick up numbers for 2013 and commission checks. Currently working on getting commission checks.

7. PyCon Registration Management

• Settling some lose ends with registration payments. We are almost done with all of our open payments.

8. PyCon Site Visits

• Working on getting Diana to Montreal for site visit in July.

9. PyCon Website Management

• Signed with Caktus. Working on launching the first phase July 1st, which will also open call for proposals.

5.2   Administrator Report

1. Board Agenda / Minutes

• I continue to write up the Board Agenda and keep it up to date.
• I continue to write up the Board Meeting minutes.

2. Grant and Award Notification

• I continue to notify respective parties of board resolutions.

3. Email and Communication

• I am continuing to monitor all PSF Board/Members mailing lists also making sure emails a re being answered/followed up on.
• I am continuing to read through all of the email threads that occur on the board/members mailing lists.
• I have started to send out the sponsors letters to PSF sponsor members. I am in the process of finishing that up and sending second notices. So far we have $76k in interest. I will now start to work on updating CiviCRM with updated PSF sponsor records/info.

4. Contributor Agreements

• collecting agreements coming through EchoSign and marking them in bug tracker. Going through all of the backlog from PyCon.

5. Documentation Upkeep and Wiki

• created the charter for the Bylaw WG and also the interaction sheet for future charters.

6. Other Conferences

• Please see the Event Coordinator Report for the detail.

5.3   Outreach and Education Report

1. Awards

• $767.27 for an introduction to Python Workshop at the 2013 American Library Association annual conference, led by Andromeda Yelton.
• $300 for a women's panel/mixer at SciPy 2013, organized by Kristen Thyng.

2. Discussions

• We received a request for sponsorship from the organizers of the Write/Speak/Code conference in New York City in June (http://www.writespeakcode.com/). We declined to sponsor this event due to an insufficient focus on Python and organizational concerns.

5.4   Sprint Committee Report

1. Summary

• We're sponsoring the scikit-learn sprint at the end of July. I've now got the payment request from them so I'm going to work with Kurt to get their funding.

2. Issues / Blockages

• None

3. Continued Activities from Last Month

• None, everyone is currently paid and up-to-date

4. New Activities

• We approved partial funding to a week-long sprint for the scikit-learn core developers in Paris. They're bringing together a lot of the major contributors for this and they're looking for several thousand dollars to help fund some of their travel. Since the event is much longer than what we normally sponsor, we're contributing $600, which is double our normal amount for a small one-day sprint.
• Because we've worked with these people in the past, and because it's going to fund travel, we're going to try and work this as an up-front payment rather than reimbursement. We trust that they're using the funds appropriately, but we're going to gather receipts for our records.

5.5   Communications Report

1. Summary

• Not much to share for this report, except we did post the announcement of the Code of Conduct, as well as place it in the repo and on the website. It received over 3400 views on the blog, and was retweeted 50 times (only trolled once).

2. Issues / Blockages

• None

3. Continued Activities from Last Month

• None

4. New Activities

• Put CoC into our hg repo: http://hg.python.org/coc/rev/689163936c9d Put CoC on the website: http://www.python.org/psf/codeofconduct/Reworked justification document into the blog announcement: http://pyfound.blogspot.com/2013/06/announcing-code-of-conduct-for-use-by.html
• The resolutions and minutes were also brought up to date this month, and were updated immediately after the last meeting as well, so that's back on track.

5.6   Marketing Material Report

• The marketing material project aims to design, produce and ship professional quality marketing material for Python.
• The first goal is to create a Python brochure which show-cases Python's application spaces, how it helps users to achieve their tasks and what its benefits are in a professional and educational setting.
• Please see this wiki page for more information on the effort: https://wiki.python.org/psf/PSF%20Python%20Brochure

1. Progress

• We've completed getting approvals from all content providers and have created a preview PDF which we can use to sell ad sponsorships and reference entries.
• Ad space is almost sold out. 5 ads are sold. There are two ad reservations and one 1/2 page ad slot is still available.
• The much more affordable reference entries appear to be much harder to sell. We've so far only sold 2, with 4 pending payment. That leaves 22-32 entries available.
• If you are interested in signing up as reference sponsor or know someone who might be interested, please refer them to the brochure site: http://brochure.getpython.info/
• Once we have the sponsors all signed up, we'll go to print with the brochure and have it distributed to the ad sponsors, reference sponsors, subscription sponsors and Python conferences, user groups, etc. via on-demand shipping.
• If you are the lead of a local user group, conference, educational institution and interested in receiving boxes with the brochure delivered to you at no additional costs, please contact the PSF or our team directly via brochure at getpython.info.

2. Issues

• The only issue at the moment is the slow progress in signing up reference entry sponsors.
• We'd really like to finish the project and go to print.

5.7   Community Relations Report

1. Summary

• With the PSF Community Relations we aim at creating closer bindings with the world-wide Python communities.
• Please see this wiki page for more information on the effort: https://wiki.python.org/psf/Community%20Relations

2. Progress

• There hasn't been much progress in the last months, mainly due to lack of time.
• The conference kits will likely be used at EuroPython 2013 and Python Brasil 2013 this year. Perhaps also at PyCon DE 2013 and other conferences.
• We still need local teams to staff the booths for these conferences.
• I'm continuing discussions with national and local groups, encourage people to make use of the Python events calendars (and help maintaining it) and help wherever I can.

3. Issues

• The budget the board approved for the conference kits is fully used up. I'll have to propose a budget position for marketing activities or use my directors allowance.

5.8   PSF Domains Report

• The PSF domains team takes care of managing and registering domains owned by the PSF.
• Please see this wiki page for more information on the effort: https://wiki.python.org/psf/PSF%20Domains

1. Progress

• The Gandi accounts were setup, access details sent to Kurt, Ewa, Noah.
• The ironpython.(net/com/org) domains were transferred to the PSF from Microsoft as first real-life test of the setup.
• I've registered the first batch of available "python" TLDs as discussed on the board list. These all redirect to python.org.
• Still pending is the registration of the python.china domain due to problems with the Chinese registry.
• I'm now busy with Kurt to get the existing PSF domains which he has access to transferred to Gandi. All but the psfb.org and the python.org domain have been transferred.
• Next week, I plan to start the transfer of the domains that Arc has access to.
• A new email alias psf-domains at python.org was setup, so that the board list no longer gets all the domain email.

2. Issues

• Some transfer problems like emails not coming through, but nothing serious.