The post Moderna joins NumFOCUS Corporate Sponsors appeared first on NumFOCUS.

26 Jun 2019 6:02pm GMT

The post Moderna joins NumFOCUS Corporate Sponsors appeared first on NumFOCUS.

26 Jun 2019 6:02pm GMT

PyCon 2019 Transparency Report

The PyCon Code of Conduct sets standards for how our community interacts with others during the conference. A Code of Conduct without appropriate reporting and response procedures is difficult to enforce transparently, and furthermore a lack of transparency in the outcomes of Code of Conduct incidents leaves the community without knowledge of how or if the organizers worked to resolve incidents.

In our efforts to continue to improve how PyCon handles CoC incidents, staff, volunteers and community members participated in a CoC training prior to PyCon 2019. In having more people trained we provided a more thorough process for reporting and responses.

With that in mind, we have prepared the following to help the community understand what kind of incidents we received reports about and how the PyCon staff responded.

Overview

Reports

This year, PyCon Staff and Incident Responders were notified of 11 incidents. For summary purposes we categorized each report using a tenant of our standards and expectations of attendees.

13 incidents were reported this year, and 10 were considered to be potential PyCon Code of Conduct matters:

Two related to unwelcome sexual attention or advancement
Two related to content, written or verbal presentations
Five related to other conduct that is inappropriate for a professional audience including people of many different backgrounds
One related to privacy

Resolutions

Of the 10 potential PyCon Code of Conduct matters:

Eight were resolved on-site
One was resolved post-conference
One is still awaiting resolution

Summary of Reported Incidents

A presenter displayed publicly released classified materials on screen during a public presentation. An attendee with security clearance noted that this required a disclosure to their employer and other steps per policy. PyCon contacted the presenter and asked that a disclaimer be made before displaying similar material in the future so that those with clearances can choose to leave if necessary.
An attendee reported repeated advances and unwanted sexual attention from another attendee. PyCon has not resolved the incident and is awaiting confirmation from the reporter to do so.
An attendee with an impairment asked a question at a presentation regarding that impairment. The attendee felt dismissed by the presenter's response, this was compounded by the presenter serving as a non-expert contributor to research. The PyCon programming committee is considering an enhanced vetting process for presentations addressing medical and disability research.
An attendee reported concerns with the way that crowd control was handled and the behavior of volunteers at a talk that was at capacity. PyCon updated crowd control procedures on site for the remainder of the conference and will incorporate and iterate on these improvements moving forward.
An attendee reported personal attacks posted to a blog during by one community member against another community member, both in attendance at PyCon. PyCon's incident response team determined that this was not a Code of Conduct violation within their purview, but indicated the manners in which it was not within the broader Python community guidelines.
Prior to the conference, a volunteer reported inappropriate behavior by another volunteer during meetings leading up to PyCon. As this behavior had been previously reported and addressed, PyCon has removed the volunteer from their position.
An attendee reported concerns about recordings of tutorials including pans and zooms around the room during breaks. PyCon is working to implement and improve photo policies on site and will instruct future tutorial videographers to pause the recording during breaks.
An attendee reported an incident of sexual assault at another Python conference. PyCon's incident response team escalated this matter to the Python Software Foundation board.
Several attendees of a breakout event reported an interaction between an attendee of the event and a presenter that led to the attendee verbally lashing out and leaving the room. PyCon's incident response team conferred these reports to the organizers of the event. For future breakout events, PyCon will invite organizers to attend Code of Conduct incident response trainings to better equip them to address situations as they arise.
An attendee reported seeing another attendees phone displaying sexual imagery. PyCon contacted the second attendee to remind them to be cognizant of what apps they open and what content you view in the PyCon public space.
Several attendees reported feeling uncomfortable around an attendee who consistently wearing a hat intentionally reminiscent of a hat with charged political meaning. The attendee was asked to remove their hat.
An organizer for an Open Space reported being concerned that an attendee that was disruptive at PyCon 2018 would return. The attendee did not attend PyCon 2019.
A presenter reported feeling uncomfortable with personal correspondence they received from an attendee in the lead up to PyCon and requested that the attendee be asked not to attend their presentation. PyCon's incident response team deemed the correspondence to be unwanted sexual attention and asked that the attendee not go to the presentation. The attendee said they would not, and PyCon's incident response team confirmed that they did not attend the presentation or make any additional attempts to contact the presenter at PyCon.

26 Jun 2019 5:03pm GMT

PyCon 2019 Transparency Report

The PyCon Code of Conduct sets standards for how our community interacts with others during the conference. A Code of Conduct without appropriate reporting and response procedures is difficult to enforce transparently, and furthermore a lack of transparency in the outcomes of Code of Conduct incidents leaves the community without knowledge of how or if the organizers worked to resolve incidents.

In our efforts to continue to improve how PyCon handles CoC incidents, staff, volunteers and community members participated in a CoC training prior to PyCon 2019. In having more people trained we provided a more thorough process for reporting and responses.

With that in mind, we have prepared the following to help the community understand what kind of incidents we received reports about and how the PyCon staff responded.

Overview

Reports

This year, PyCon Staff and Incident Responders were notified of 11 incidents. For summary purposes we categorized each report using a tenant of our standards and expectations of attendees.

13 incidents were reported this year, and 10 were considered to be potential PyCon Code of Conduct matters:

Two related to unwelcome sexual attention or advancement
Two related to content, written or verbal presentations
Five related to other conduct that is inappropriate for a professional audience including people of many different backgrounds
One related to privacy

Resolutions

Of the 10 potential PyCon Code of Conduct matters:

Eight were resolved on-site
One was resolved post-conference
One is still awaiting resolution

Summary of Reported Incidents

A presenter displayed publicly released classified materials on screen during a public presentation. An attendee with security clearance noted that this required a disclosure to their employer and other steps per policy. PyCon contacted the presenter and asked that a disclaimer be made before displaying similar material in the future so that those with clearances can choose to leave if necessary.
An attendee reported repeated advances and unwanted sexual attention from another attendee. PyCon has not resolved the incident and is awaiting confirmation from the reporter to do so.
An attendee with an impairment asked a question at a presentation regarding that impairment. The attendee felt dismissed by the presenter's response, this was compounded by the presenter serving as a non-expert contributor to research. The PyCon programming committee is considering an enhanced vetting process for presentations addressing medical and disability research.
An attendee reported concerns with the way that crowd control was handled and the behavior of volunteers at a talk that was at capacity. PyCon updated crowd control procedures on site for the remainder of the conference and will incorporate and iterate on these improvements moving forward.
An attendee reported personal attacks posted to a blog during by one community member against another community member, both in attendance at PyCon. PyCon's incident response team determined that this was not a Code of Conduct violation within their purview, but indicated the manners in which it was not within the broader Python community guidelines.
Prior to the conference, a volunteer reported inappropriate behavior by another volunteer during meetings leading up to PyCon. As this behavior had been previously reported and addressed, PyCon has removed the volunteer from their position.
An attendee reported concerns about recordings of tutorials including pans and zooms around the room during breaks. PyCon is working to implement and improve photo policies on site and will instruct future tutorial videographers to pause the recording during breaks.
An attendee reported an incident of sexual assault at another Python conference. PyCon's incident response team escalated this matter to the Python Software Foundation board.
Several attendees of a breakout event reported an interaction between an attendee of the event and a presenter that led to the attendee verbally lashing out and leaving the room. PyCon's incident response team conferred these reports to the organizers of the event. For future breakout events, PyCon will invite organizers to attend Code of Conduct incident response trainings to better equip them to address situations as they arise.
An attendee reported seeing another attendees phone displaying sexual imagery. PyCon contacted the second attendee to remind them to be cognizant of what apps they open and what content you view in the PyCon public space.
Several attendees reported feeling uncomfortable around an attendee who consistently wearing a hat intentionally reminiscent of a hat with charged political meaning. The attendee was asked to remove their hat.
An organizer for an Open Space reported being concerned that an attendee that was disruptive at PyCon 2018 would return. The attendee did not attend PyCon 2019.
A presenter reported feeling uncomfortable with personal correspondence they received from an attendee in the lead up to PyCon and requested that the attendee be asked not to attend their presentation. PyCon's incident response team deemed the correspondence to be unwanted sexual attention and asked that the attendee not go to the presentation. The attendee said they would not, and PyCon's incident response team confirmed that they did not attend the presentation or make any additional attempts to contact the presenter at PyCon.

26 Jun 2019 5:03pm GMT

With PyCon US 2019 over, I decided to catch up with a PyCon first-timer, Katrina Durance. I was curious to see how she found the experience and what her highlights were. I also wanted to understand how attending a conference like PyCon influenced her programming chops.

Ricky: Let's start with the same questions I ask all my guests. How'd you get into programming? When did you start using Python?

Katrina: Python was my first programming course in grad school back in 2013. I also learned R and SQL. The two jobs I've been in since I graduated have been completely SQL-focused, so Python and R fell by the wayside.

Since I work at an arts college in Chicago (Columbia College Chicago) I'm able to take courses for free. We have a gaming program so all our programming courses are game related. Since I'm a gamer and a very visual learner, I decided to take a C# course where we worked on building small games. I liked it.

I really struggled a lot with Python when I first learned it, but working with a programming language in a visual context started to clarify a lot of concepts for me. I knew after that course that I wanted to build my skills to get into full-time programming. I eventually came up with a study plan and decided to return to my Python roots at the beginning of this year.

Ricky: This year you attended PyCon US for the first time. I'm curious why this year was your first. What changed or made you want to go this time around?

Katrina: What really clinched it was knowing that there was going to be a group from PythonistaCafe, and a big contingent from the Chicago Python User Group meetup there. So I knew I would see some friendly faces. I didn't feel I was doing it all alone.

Ricky: Everyone's PyCon experience is different. I'm wondering if you had a standout moment this year? Is there one thing that you'll remember synonymously with your first PyCon experience?

Katrina: The mentored sprints were a big deal for me. I ended up working on an issue on a tool (Hypothesis) that I didn't understand because I haven't learned much about testing at all yet.

I was feeling frustrated and concerned that everything would go over my head. But our mentor was amazing and so encouraging and showed me a bunch of things I was learning and kept me going to the end. Now I have a closed issue on the software with my name on it, which is pretty cool.

Ricky: We, of course, met face to face several times over the weekend. But most notably at the PythonistaCafe open space. How was your open space experience? Did you learn anything new, or were there any actionable takeaways?

Katrina: I was excited about the PythonistaCafe open space because of the chance to meet some of the folks I've interacted with or just seen on the forum, and I wasn't disappointed.

I hosted an open space for self-taught programmers like me. I was stunned when 30-ish people showed up. I did my best to manage it and got some positive feedback and helpful advice.

The PyCon Africa meetup was very enlightening because I learned that the reason we're not seeing a boom in innovation from Africa yet is that the internet is prohibitively expensive in every country represented in the room. It didn't matter if it was government regulated or privately owned. I would love to help figure out how to solve that problem.

PythonistaCafe Members Coming Together at a PyCon Open Space

Ricky: There is so much to do at PyCon that there's just not enough time to do it all. So was there anything you wish you had done or a talk you'd missed that you wish you hadn't? Anything you'd do differently next time?

Katrina: I felt PyCon was what I was hoping it would be for this first time around, to be honest. Next year I want to stay for the sprints, which people kept telling me were amazing.

Ricky: So for those reading this that have yet to go to their first PyCon, this might be the most important question… How did attending PyCon affect how you will write your Python code going forward?

Katrina: I had to talk about my code. When you're self-taught, you don't get a lot of opportunities to talk through your code. Through the conversations I had at PyCon, I was encouraged to be more deliberate about taking advantage of my Slack and local Python communities to practice those communication skills.

In other words, I need to notch up my courage and not worry if I'm not coding it or explaining it well yet. I just need to keep coding and explaining.

Ricky: Last but not least, what else do you get up to in your spare time? What other hobbies and interests do you have, aside from Python and coding? Anything you'd like to plug?

Katrina: I love all things Sci-Fi and weird: movies, TV series, books, etc. I'm a LEGO enthusiast and have a penchant for building lost temples out of my love for H. P. Lovecraft stories. I really like VR and enjoy playing games on my Oculus Go. I also make jewelry out of felt, found objects, or even LEGO pieces.

If you'd like to catch up with Katrina and say hi, drop her a message on Twitter.

If there's someone from the Python community that you'd love me to interview, leave a comment below and let me know.

[ Improve Your Python With 🐍 Python Tricks 💌 - Get a short & sweet Python Trick delivered to your inbox every couple of days. >> Click here to learn more and see examples ]

26 Jun 2019 2:00pm GMT