5.1   Event Coordinator Report

1. PyCon AV Management

• Waiting to hear back from Carl and crew for the mid August extension. As mentioned before, we are waiting to see if Carl will get admittance to Canada on a work permit for PyCon Canada in early August. If it works out, we will start negotiations for PyCon 2014. At that point, David W. will start the permit process sooner for Carl and I will also have a contingency plan.

2. PyCon Budgeting

• Working on budget for 2014. It is 95% finished at this point and will be sent for review after August 12. Ledger is being kept up to date as well so we can hit the floor running
• Have shown Diana the budget and gone through rounds of questions she has had (and may continue to have)

3. PyCon Electrical

• nothing to report

4. Future Event Planning

• continuing to work on 2016/2017 RFPS.

5. PyCon Hotel/CC Management

• continuing to work on receiving the refunds from the CC and commission checks from hotels.

6. PyCon Housing Management

• Signed contract for housing management by CTE.
• Working on getting one or two contracts at cheaper hotels for Financial Aid

7. PyCon Registration Management

• Signed contract for reg management by CTE.
• Had conference call with CTE to go over logistics for how the site should work for PyCon 2014 and changes that we need made.
• Working with Diana and Mathieu on ways to improve CTE reporting to be able to mass communicate with tutorial attendees.

8. PyCon Site Visits

• nothing to report

9. PyCon Website Management

• Continuing (this includes Diana and Mathieu as well) to correspond with Caktus about their work on the website.
• Working on Financial Aid details for the us.pycon.org. The application process is being worked on currently. (this process will be done through us.pycon.org this year rather than a google form to ease some issues we had in 2013). Peter has also been assisting with review.

10. Legal Issues

• Mathieu L. has been looking into the details for presenters who will need work permits for PyCon 2014.
• Working on getting the conference registered with border control.

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 are being answered/followed up on.
• I am continuing to read through all of the email threads that occur on the board/members mailing lists.

4. Contributor Agreements

• collecting agreements coming through EchoSign and marking them in bug tracker.

5. Documentation Upkeep and Wiki

• working on helping with the 2013 PSF Budget and keeping it up to date

6. Other Conferences

• Please see the Event Coordinator Report for the detail.

5.3   Sprints Committee Report

1. Summary

• Nothing new in the pipeline, but since last report we sponsored two sprints: EuroPython and a group in Florence, Italy. We've also put together our list to re-certify the committee.

2. Issues / Blockages

• None

3. Continued Activities from Last Month

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

4. New Activities

• As mentioned in the summary, EuroPython, although old, is an event we sponsored but is mentioned here since I missed the last reports. We also sponsored a Django sprint at the end of July in Florence.
• A small discussion occurred on our list when a group requested funding for a sprint they did nearly nine months ago. We sometimes do sponsor sprints after the fact, although usually a very short time after (single digit days), and we've usually been in contact with the organizers in some way. Because of that, we rejected the request. It also brought up that while we don't have a formal policy, we have always been against sponsoring events that are explicitly "beer and wine" sprints as this one was. We've worked with requestors in the past to be more welcoming, but this isn't explicit policy - perhaps we should pencil this in somewhere.