Podcast appearances and mentions of ada initiative

The Mad Writers keep referring to building your community and this week they are putting their money where their mouth is. They are joined by Crystal Huff who has been involved in ALL THE CONS. She also fights the kyriarchy professionally through giving workshops and for example consulting companies on creating a welcoming environment as well as dealing with Impostor Syndrome. The panelists cover how to deal with horrible situations, how to get new people without losing all of the old ones and how to make sure the community doesn't die because the people who started it are tired. The entire episode is full of amazing content, you may want to have a notepad handy!Notable NotesReadercon 2012 incident summary Crystal's consultation and training Wiscon Readercon Arisia 4th Street Fantasy Worldcon 75Crystal Huff is the Executive Director of Inclusion Through Innovation and former Executive Director of The Ada Initiative. She has a long history of professional and volunteer efforts in technology and geek culture, with a particular commitment to anti-harassment and impostor syndrome work. Crystal runs science fiction conventions in her spare time, most notably the 75th World Science Fiction Convention in Helsinki, Finland. She speaks fluent English, rusty American Sign Language, and beginner Finnish cussing.Crystal can be found online at crystalhuff.com and on Twitter as @arisiacrystal and @CrystalMHuffRecommended Reading Crystal's recommendation: The Paper Menagerie and Other Stories by Ken Liu    Tim's recommendation: Air Vol. 1: Letters from Lost Countries by G. Willow Wilson and M.K.Perker    Jay's recommendation: The Noble Approach: Maurice Noble and the Zen of Animation Design   Nina's recommendation: Alif the Unseen by G. Willow WilsonPlease support Mad Writers Union by reviewing it on iTunes or Stitcher! You can subscribe to this show on iTunes or via RSS.Intro and outro music comes from “Cephalopod” by Kevin MacLeod (incompetech.com); licensed under Creative Commons: By Attribution 3.0

AM: Hi again everyone, and welcome to The Secret Sauce, a short podcast by Palantir.net, that offers a quick piece of advice to help your business run smoother.  I’m Allison Manley, an Account Manager here at Palantir, and today’s advice comes from one of the Founders of Palantir, George DeMet, who is going to address the need for having a code of conduct at your organization or event. GD: Hi, my name is George DeMet, and I’m the founder and CEO of Palantir.net. Today, I’m going to be talking about codes of conduct and how they can help make communities, organizations, and events more inclusive. First, a little bit of background. I’m currently the acting chair of the Drupal Community Working Group, whose mission is to uphold the Drupal Code of Conduct in order to maintain a friendly and welcoming community for the Drupal project. In the past, I have also helped write codes of conduct for open source community events, including DrupalCon, and have provided consultation and guidance to organizations and groups who are looking to adopt codes of conduct for themselves. In its simplest form, a code of conduct is a policy used by an organization to establish the standards for behavior and appropriate conduct when interacting with others in a defined space like a conference, workplace, project, or event venue. Almost any venue that serves the public, such a theater, museum, sports arena, or ice skating rink, has a code of conduct posted that sets expectations for people so that they don’t engage in unsafe behavior that interferes with the ability of others to enjoy that space. In the context of technology communities, codes of conduct fill a similar function, helping to create inclusive spaces where people can feel safe and welcome to contribute. Unfortunately, what we’ve seen all too frequently is that even as more and more people are participating in open source and other technology communities, the number of incidents of harassment has also increased. Technology communities in general, and open source projects in particular, frequently suffer from a lack of diversity, with low participation rates by women, people of color, and other marginalized populations who are frequently the targets of harassing behavior. A well-written and implemented code of conduct can help address those issues by making it clear that communities value openness and diversity, and are committed to providing an inclusive space that is free from harassment and where all kinds of people can contribute in a professional manner.  Just having a code of conduct won’t get rid of every issue, but making sure that everyone underst ands the values of your community and the ground rules for interacting with others makes a huge difference. A good code of conduct will have the impact of making it easier for everyone to participate in your community. So, how do you go about drafting a code of conduct? Fortunately, there’s a ton of great resources out there that provide a great foundation that you can build upon to meet the needs of your organization or community. Don’t worry, we’ll provide links to all of these in the description of this episode, as well as on our website at palantir.net. For conferences and other events looking for a good anti-harassment policy, the Ada Initiative’s Conference Code of Conduct is a great example for others to use. What it does well is make it clear that harassment will not be tolerated at the event, provides examples of what kinds of behaviors constitute harassment and tells folks how they can let event staff or organizers know if they feel they’ve been subjected to harassing behavior.  The code of conduct that we use at Palantir for meetups and other events that we host is based heavily on the Ada Initiative code, with some additional language borrowed from the code of conduct used by the Drupal Association for DrupalCons and other events.  It’s very important that everyone who attends your event be aware that you have a code of conduct and be able to easily access it. That means that in addition to having it posted on your event website, you should also have a printed copy on display at the event itself, usually near the entrance or event registration desk, and if you have a printed program guide, it should be included in there as well. It’s also a really good idea to mention the code of conduct at the beginning of your event or during an opening plenary session and point out who to talk to if someone has something to report. Which brings us to the question of enforcement. One mistake a lot of events make is adopting a code of conduct, but not creating sufficient mechanisms to enforce it. In some cases, where the behavior in question is endangering the physical safety of another attendee or breaking the law, the answer is obvious: event staff needs to immediately remove the perpetrator from the premises and call the cops if necessary. Often though, the answers aren’t always that clear-cut, and it’s important that your event staff or the person in charge of enforcing the code of conduct knows how to handle the situation. Ideally, you want to have multiple people who are empowered to handle code of conduct reports, and you need to have those people fully understand and appreciate the responsibility they have, as well as be folks who attendees can feel safe talking to and can trust to handle their reports with discretion.  Now a community code of conduct operates on most of the same principles as an event code of conduct. While an event code is largely designed to govern in-person interactions at a conference, meetup, or other event, a community code of conduct helps set the standards for conduct when it comes to the way we collaborate and communicate with others.  I believe a community code of conduct should be built around and reinforce the shared values of the community in question.  In my work with the Drupal Community Working Group, a lot of the issues that we deal with are not harassment issues, but conflicts between people who are really frustrated with one thing or another and end up lashing out at each other in negative and unproductive ways. In those cases, we usually find ourselves in less of an enforcement role and more of a mediator role. One of the core tenets of our community code of conduct that is we treat each other with respect, even when when we disagree, and often just reminding people of that can be enough to alleviate the situation. Sometimes however, you do end up with a situation that requires a greater level of intervention, and that’s where it’s really important to have a good conflict resolution policy and process. In the Drupal community, we encourage people to work things out between themselves whenever possible, asking for help from others as needed. We think this approach helps give people more control over the outcome of their dispute and is more likely to lead to a lasting resolution.  If that’s not possible though, folks can escalate to the Community Working Group, and we’ll do  what we can to help resolve the situation. We are very clear, though, that under no circumstances is bullying or harassment tolerated within our community, no matter how long you’ve been in the community or how many contributions you’ve made.  In addition to the resources we provide on the Drupal Community Working Group pages, another good place to check out is the Django project code of conduct, which has also been adopted by the jQuery Foundation and others. The Contributor Covenant and the Citizen Code of Conduct are also fantastic starting points for community codes of conduct that are used by a wide variety of projects and communities. There’s been a lot of discussion and debate about codes of conduct in various open source communities lately, and there’s been a lot of misinformation floating around out there. What I can tell you based on my experience is that no matter what kind of community you’re involved with, having a well-written and enforced code of conduct helps create a more level playing field for participation and an environment that helps encourage contribution and involvement that you would not get otherwise.  Thanks! AM: That’s the end of this week’s Secret Sauce. For more great tips or links to some resources regarding a code of conduct, please check out the transcription of this podcast on our website at Palantir.net. You can also follow us on twitter at Palantir. Have a great day!Resources: Ada Initiative Conference Code of Conduct:  http://confcodeofconduct.com/ Palantir.net Code of Conduct:  https://www.palantir.net/code-of-conduct Drupal Community Working Group: https://www.drupal.org/governance/community-working-group  Django Code of Conduct: https://www.djangoproject.com/conduct/  Contributor Covenant: http://contributor-covenant.org/  Citizen Code of Conduct: http://citizencodeofconduct.org/  Codes of Conduct 101 + FAQ http://www.ashedryden.com/blog/codes-of-conduct-101-faq

Leigh Honeywell And Ari Rubenstein are Senior Staff Security Engineers at Slack. I saw Leigh on Wendy Nather's panel during RSA Conference 2016 and was interested in getting some insight into what's going on at Slack when it comes to DevOps. As luck would have it, Ari was in the audience, so we were able to step outside into the hallway and talk about how DevOps, security and engineering work together at Slack. About Leigh Honeywell Leigh reboots computers and makes hackerspaces. Leigh is a Security Engineer at Slack. Prior to Slack, she worked at Salesforce.com, Microsoft, Symantec, and Bell Canada. Her career has included everything from stringing cable and building phone systems to responding to some of the most serious computer security incidents in industry history, shipping software to a billion people, and protecting infrastructure running companies’ critical business communications. Her community work includes founding the HackLabTO hackerspace in Toronto, Canada, and the first feminist hackerspace, the Seattle Attic Community Workshop, as well as advising countless others and speaking about hackerspace cultures, collaboration, and open source software. She is Chief Security Officer of Double Union, a women’s hackerspace in San Francisco. She is a former administrator of the Geek Feminism wiki and blog, and current adviser to the Ada Initiative, the SECTor security conference, and the Magic Vibes Corporation. Leigh has a Bachelors of Science from the University of Toronto where she majored in Computer Science and Equity Studies. About Ari Rubenstein Senior Staff Security Engineer - Developed tooling for Security Automation, Detection, and Response - Implemented multiple open-source technologies to gain visibility on a company-wide level - Led feature reviews and architecture critiques - Discovered multiple vulnerabilities in Open Source Software, and committed fixes upstream - Performed code audits and static analysis - Collaborated cross-organization on Security topics with Sales, Accounts, Engineering, and Executive teams - Managed public-facing bug bounty program for product security issues - Provided guidance for customer questions and support tickets

Check out RailsClips!   01:53 - Michele Titolo and Women Who Code Introduction Twitter Blog Facebook 02:15 - Origin Story 501(c) Organization 03:11 - Stated Mission “Inspire women to excel in technology careers” 04:12 - Mentorship Glassbreakers (A peer mentorship community for professional women) 08:54 - Getting Started and Getting Involved 11:27 - Value 12:42 - Remote/Virtual Membership/Communication 15:08 - What Makes Women Who Code Different (from other groups)?     18:02 - Is there a need for groups like this? What issues do these address? 22:34 - Implementing Diversity into the Workplace Job Postings Michele's tweet about a job posting Practical and Universal Interview Questions Workplace Culture Benefits Communication & Teamwork Cate Hudson: Programmers and Racecars 32:29 - Terminology (Using words like “guys”) 35:16 - Is it really harder for women to get jobs? Resume Anonymization Dropping Out/Reentering the Tech Industry Re-Recruit From the Leaky Pipeline (Model View Culture article) 43:13 - The Community at Large (How can we help make the community more open and welcome?) Inclusive Events Codes of Conduct Change Within *Your Own* Organization (Advocacy) Learning About Other People (Be Empathetic; Be Respectful) 46:08 - Are there people who can help people/companies diversify? Ashe Dryden The Diverse Team by Ashe Dryden The Ada Initiative Natural Introductions 49:49 - How can I help? (as a man) Donations Fund Club AlterConf Volunteering 51:47 - Study Resources (Proof) Model View Culture Cosmodrome (from Brianna Wu)   Groups and Mailing Lists (mentioned in this episode) Glassbreakers Women Who Code SF (San Francisco) DevChix Tech LadyMafia   Girls Who Code Black Girls Code PyLadies Ladies Who Code RailsBridge App Camp For Girls Girl Develop It Mobile Bridge Geekettes PowerToFly MotherCoders The Ada Initiative Fund Club AlterConf Picks Power Up Your Animations! with Marin Todorov (Alondo) Poker Theory & Analytics (Alondo) Paracord (Chuck) Soto Pocket Torch (Chuck) Kate Heddleston: How Our Engineering Environments are Killing Diversity (Michele) Ashe Dryden: The Responsibility of "Diversity" (Michele) Conference proposal writing: From brainstorm to submit @ 360iDev 2015 (Michele)

Check out RailsClips!   01:53 - Michele Titolo and Women Who Code Introduction Twitter Blog Facebook 02:15 - Origin Story 501(c) Organization 03:11 - Stated Mission “Inspire women to excel in technology careers” 04:12 - Mentorship Glassbreakers (A peer mentorship community for professional women) 08:54 - Getting Started and Getting Involved 11:27 - Value 12:42 - Remote/Virtual Membership/Communication 15:08 - What Makes Women Who Code Different (from other groups)?     18:02 - Is there a need for groups like this? What issues do these address? 22:34 - Implementing Diversity into the Workplace Job Postings Michele's tweet about a job posting Practical and Universal Interview Questions Workplace Culture Benefits Communication & Teamwork Cate Hudson: Programmers and Racecars 32:29 - Terminology (Using words like “guys”) 35:16 - Is it really harder for women to get jobs? Resume Anonymization Dropping Out/Reentering the Tech Industry Re-Recruit From the Leaky Pipeline (Model View Culture article) 43:13 - The Community at Large (How can we help make the community more open and welcome?) Inclusive Events Codes of Conduct Change Within *Your Own* Organization (Advocacy) Learning About Other People (Be Empathetic; Be Respectful) 46:08 - Are there people who can help people/companies diversify? Ashe Dryden The Diverse Team by Ashe Dryden The Ada Initiative Natural Introductions 49:49 - How can I help? (as a man) Donations Fund Club AlterConf Volunteering 51:47 - Study Resources (Proof) Model View Culture Cosmodrome (from Brianna Wu)   Groups and Mailing Lists (mentioned in this episode) Glassbreakers Women Who Code SF (San Francisco) DevChix Tech LadyMafia   Girls Who Code Black Girls Code PyLadies Ladies Who Code RailsBridge App Camp For Girls Girl Develop It Mobile Bridge Geekettes PowerToFly MotherCoders The Ada Initiative Fund Club AlterConf Picks Power Up Your Animations! with Marin Todorov (Alondo) Poker Theory & Analytics (Alondo) Paracord (Chuck) Soto Pocket Torch (Chuck) Kate Heddleston: How Our Engineering Environments are Killing Diversity (Michele) Ashe Dryden: The Responsibility of "Diversity" (Michele) Conference proposal writing: From brainstorm to submit @ 360iDev 2015 (Michele)

Rachel Chalmers knows your Achilles heel. After two plus decades sitting in Silicon Valley's front row watching start-up technology companies, she has a very clear idea of the single biggest cause of start-up failure.  Rachel was kind enough to sit down for a few minutes at the Montgomery Summit and talk about it. Listen in to hear what she sees as most critical for entrepreneurial success. My Guest Rachel Chalmers has been a long time observer and analyst in the world of technology.  She describes herself as a failed English teacher.  She received a BA degree in English from the University of Sydney and a master’s in philosophy, with a focus on Anglo-Irish literature, from Trinity College, Dublin.  But her time hanging out with engineering students pointed her towards technology writing. She started her career writing for MIS Magazine and Computerwire during the mid-late 90's.  In 2000 she moved to the 451 Group and focused infrastructure computing for the enterprise.  As she puts it she covered: "tools for programmers, power systems administrators and data center operators...and virtualization. Lots and lots and lots of virtualization." Then in mid-2013 Rachel joined Ignition Partners as a principal investing in enterprise software companies such as BlueData, Carmelo Systems, StreamSets, StrongLoop and Wit.ai Since 201 Rachel has been an adviser to the Ada Initiative, a non-profit that supports women in open technology and culture. Resources & Links Rachel's email:  Rachel [AT] ignitionpartners [DOT] com LinkedIn Twitter: @rachelchalmers Ignition Partners website The Ada Initiative I also mentioned a presentation by Bill Gross of IdeaLab from the Montgomery Summit.  Here's his slides for the same presentation at a different conference. The whole thing is good, but slide 20 is the key factors in failure. There's also a 15 minute video of his presentation from a conference in Europe. Bill Gross CEO of Idealab from Vator Subscribe With Your Favorite App Share With Entrepreneurial Colleagues & Friends Connect With Me Why a Venture Capital Podcast About Failure? From early childhood you always hear the saying “Learn from your mistakes.” In the venture capital industry you frequently hear “Fail fast” to learn and get to the right idea. Great advice. So, for this venture capital podcast I interview venture capital backed entrepreneurs about what they learned when their start-up didn't go as planned. I hope you can learn from their valuable experience. The post Shut-up and Listen! Rachel Chalmers Explains the Biggest Mistake You Can Make appeared first on Venture Capital Coroner's Report.

Karen and Bradley interview Deb Nicholson of Open Invention Network, GNU MediaGoblin and Open Hatch. Show Notes: Segment 0 (00:36) Karen announced her pregnancy. (01:50) Bradley will be at OSCON, Karen might be, and Karen will be at GUADEC. Bradley will be at LinuxCon North America and LinuxCon Europe. (03:00) Segment 1 (04:40) Deb Nicholson was previously on the show as Episode 0x25: FOSDEM 2012 Patents Panel. (06:00) Deb mentioned Linux System Definition, which is the OIN-published list of things that OIN members license their patents to each other on. (07:12) Deb and Bradley are debating Bradley's comment regarding Deb's points on the panel on 0x25. If you go back to listen to 0x25, the context for the comment they're debating starts around 38:00 in 0x25. (19:20) It's possible etymology of the verb “to harp” may indeed come from the musical instrument, not harpy. (31:00) Karen mentioned The Ada Initiative. (32:52) Segment 2 (38:54) Bradley and Karen talk about plans for upcoming shows. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on on Twitter and and FaiF on Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Karen and Bradley interview Deb Nicholson of Open Invention Network, GNU MediaGoblin and Open Hatch. Show Notes: Segment 0 (00:36) Karen announced her pregnancy. (01:50) Bradley will be at OSCON, Karen might be, and Karen will be at GUADEC. Bradley will be at LinuxCon North America and LinuxCon Europe. (03:00) Segment 1 (04:40) Deb Nicholson was previously on the show as Episode 0x25: FOSDEM 2012 Patents Panel. (06:00) Deb mentioned Linux System Definition, which is the OIN-published list of things that OIN members license their patents to each other on. (07:12) Deb and Bradley are debating Bradley's comment regarding Deb's points on the panel on 0x25. If you go back to listen to 0x25, the context for the comment they're debating starts around 38:00 in 0x25. (19:20) It's possible etymology of the verb “to harp” may indeed come from the musical instrument, not harpy. (31:00) Karen mentioned The Ada Initiative. (32:52) Segment 2 (38:54) Bradley and Karen talk about plans for upcoming shows. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).