67: Building a Healthy Community

We talk about ways we can all contribute to building a healthy Elixir community. The Elixir community is a welcoming, encouraging and helpful place and we want to help keep it that way! We talk about common problems facing maintainers, tips for engaging productively, the value of expressing appreciation, and much more!

Show Notes online - http://podcast.thinkingelixir.com/67

Elixir Community News

• https://www.erlang.org/news/149 – Erlang/OTP 24.1 was released


• https://github.com/livebook-dev/nerves_livebook – Nerves Livebook is now part of the Livebook organization on GitHub


• https://www.youtube.com/playlist?list=PLvL2NEhYV4ZtdiDIxP_rPMQ5VmVhs4CKJ – ElixirConf EU 2021 keynote videos


• https://www.youtube.com/watch?v=6sNmJtoKDCo – Saša Jurić's presentation on Clarity


• https://twitter.com/CodeBEAMio/status/1441149132278665235 – Code Beam America switched back to virtual


• https://twitter.com/elixirphoenix/status/1441020298141253633 – Phoenix.HTML from 3.0.0-3.0.3 had a security vulnerability. Please update to 3.0.4+


• https://hex.pm/packages/phoenix_html – Phoenix HTML package page


• https://www.phoenixframework.org/blog/phoenix-1.6-released – Phoenix 1.6.0 was released! This includes the esbuild by default change.


• https://fly.io/blog/how-we-got-to-liveview/ – Chris McCord's post telling the story of "How We Got to LiveView"


• https://thinkingelixir.com/petal-stack-in-elixir/ – Reminder of the PETAL stack and how central LiveView is to it.

Do you have some Elixir news to share? Tell us at @ThinkingElixir or email at [email protected]

Discussion Resources

• https://github.com/elixir-lang/elixir#issues-tracker-management – Explanation of the Elixir's Issue Tracker Management policy


• https://github.com/elixir-lang/elixir#proposing-new-features – Resource for proposing Elixir features


• https://github.com/elixir-lang/elixir/issues – Elixir's well maintained issue tracker


• https://www.chiark.greenend.org.uk/~sgtatham/bugs.html – How to Report Bugs Effectively


• https://opensource.guide/best-practices/ – GitHub's Best Practices for Maintainers


• https://go.darrenhardy.com/darrendaily/ – Darren Hardy daily email messages.


• https://darrenhardy.cDarren Daily-om/darrendaily-on-demand – Podcast form of the daily messages.


• https://www.youtube.com/watch?v=6Z6cFvXb9_A – YouTube video of the "jerk" segment called "A Simple Way to Change Other People"


• https://twitter.com/adamwathan – Adam Wathan, maintainer of TailwindCSS


• Points to consider when interacting with different projects and maintainers.


• Every project is different.


• Maintainers work in their spare time. They are not obligated to help you. Make it easier for them to reproduce problems.


• Provide good bug reports.


• Keep your emotions out of it.


• https://twitter.com/tylerayoung/status/1438824261947363329 – Tyler Young's comments on importance of maintainers setting a tone.


• https://twitter.com/redrapids/status/1438111195886673929 – Bruce Tate's call to action. Let people and project know you appreciate their work.

Find us online

• Message the show - @ThinkingElixir


• Email the show - [email protected]


• Mark Ericksen - @brainlid


• David Bernheisel - @bernheisel


• Cade Ward - @cadebward