It was brought to my attention that some popular Erlang projects have issues with tickets being submitted that use Elixir syntax in examples or in some other way are Elixir specific. For me, it's completely understandable, why that can be frustrating. The maintainer wants to make his software the best they can do it, yet they can't understand the reported problem - they don't know elixir well enough, or simply they don't want to learn it, and we can't blame them - we should be thankful for their great libraries. As an open source contributor, I can completely relate to that.
Fortunately, I think we can do something about it! I propose setting up a github team - either under the elixir organization or somewhere else - that could be simply @-mentioned in such issues. Members of the team would be able to translate the problematic code into erlang syntax, explain some elixir idioms and provide any other elixir-specific support to help solve the issue.
This will make lives of everybody easier - the issues will be solved faster, the maintainer will be less frustrated and any tension between communities that could arise from that kind of problems would have no reason to exit. I'm also sure we would be able to find couple people that could contribute in that way to the wider BEAM community.
PS. I urge all the maintainers of Elixir libraries wrapping some Erlang libraries to review if they give all the attribution that is necessary to the original project. Even if the license doesn't require it, it's simply the right thing to do.
PS2. The article that provoked this post: https://vagabond.github.io/rants/2017/01/03/hot-takes-on-elixir