Dustin Ingram

@di_codes

Python developer advocate , maintainer, member, and organizer.

Austin, TX
Joined November 2017

Tweets

You blocked @di_codes

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @di_codes

  1. 5 hours ago

    I noticed some folks talking about what a for-profit PyPI might look like, so I wrote up some of the challenges that aren't usually considered:

    Undo
  2. Retweeted
    Mar 30

    Interested in attending but need a ticket? has two tickets available for the community! Message me and first two takers get a complimentary registration. I'll also drink a Topo Chico or two with you (this offer is open to everyone).

    Undo
  3. Mar 28

    Conference organizers: Have you heard about Conduct Hotline yet? We'll be using it for next month, it's already dope and only gonna get better.

    Undo
  4. Mar 28
    Undo
  5. Mar 28

    Best part of having Aja as a manager: Having a manager who makes sure you get visibility for your work, and doesn't just take the credit. And recognizes that being an advocate doesn't necessarily mean you are good at advocating for yourself. We're the lucky ones!

    Undo
  6. Retweeted
    Mar 21

    "Developer Advocate" is also about advocating internally for the external developers. You might not realize this from the outside. DAs are essential to the product feedback loop.

    Show this thread
    Undo
  7. Retweeted
    Mar 22

    Thanks to for supporting improvements to PyPI's security, accessibility, and internationalization. The first project progress report is now up:

    Undo
  8. Mar 22

    I've started a new discussion topic, "The next manylinux specification"

    Undo
  9. Mar 20

    This workshop definitely fills a need for conferences and events, online communities and projects. It's like a fire drill: you hope it never actually happens, but you've seen it happen elsewhere, and if it does happen, you're going to be really glad you know where the exit is.

    Show this thread
    Undo
  10. Mar 20

    After every scenario, we came back into the main group to discuss our different experiences, and what worked, what didn't work, what we learned, etc. In total there were 14 of us, plus Sage... half the benefit of this workshop is in the other attendees who join you! (4/5)

    Show this thread
    Undo
  11. Mar 20

    For each, we broke out into multiple 1:1 groups to role-play different scenarios. Each scenario felt very realistic, but also had unique challenges for both parties, and spanned a variety of different types of communities and issues. (3/5)

    Show this thread
    Undo
  12. Mar 20

    First, we discussed some frameworks for receiving CoC reports, reporting them to the rest of your team, and responding to them, including templates for each that we can re-use for our own communities, as well as a guide for making a safe(r) event/community. (2/5)

    Show this thread
    Undo
  13. Mar 20

    Just finished this CoC training on behalf of . Sage did a fantastic job running the workshop -- highly recommended. (1/5)

    Show this thread
    Undo
  14. Mar 19

    I'm glad that most people got this right: Python 3.0 came before Python 2.7! But I'm also glad to have some data that shows that the misconception exists, at least for a small percentage of folks. It's not intuitive! And hopefully those folks know now too. 🌈The More You Know🌟

    Undo
  15. Mar 18

    Pop quiz: Which came first? (Don't look it up, go with your gut!)

    Undo
  16. Mar 15

    Spoiler: we're just gonna put up on the screen for 50 minutes.

    Undo
  17. Retweeted
    Mar 14

    Interested in volunteering at PyTexas? We have a number of roles we can use help with. Read more and sign up here:

    Undo
  18. Mar 14

    Congratulations for this incredible achievement! 🥧

    Undo
  19. Mar 13

    For all you interested in FOSS, licenses or tech law: Are you aware of the new Blue Oak license? What do you think? "Blue Oak is the best permissive open source software license we know how to write."

    Undo
  20. Mar 13

    Almost a year after launching the new , we're putting the band back together! Along w/ & , joins the team to add some security and accessibility improvements. We're on a mission from... the 😉

    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·