Discussion: Driving this project forward?

## Background
This is the best place I could think of to post this sort of thing.

I was speaking with @axelson about this project on Elixir Slack today and we both agreed this project seems to be suffering due to no clear person driving it forward. If we look at the discussions about changing CI tooling in #458 there are some great ideas but no one is pushing it over the finish line.

## Questions

* Can we update the README to detail out who the maintainers of the project are?
* Should we publish a `ROADMAP.md` to show areas we think need to be added or revised?
* I have seen in several PRs there has been talk about things needing to be re-done, but no official list of things we can point to.
* Would shifting this project to being a "one stop shop" for Elixir in Emacs better drive adoption than the current separate extensions? Looking at how `evil-collection` works where it's distributed as one package, but you can still pick-and-choose functionality.
* In terms of licensing, do we want to enforce any sort of Emacs-compatible license in hopes of being merged into Emacs core OR do we want to keep this separate long term so it's not license-restricted in what it can do?
* How should we get more volunteers to step in and help maintain the project?
* How should we document how to get an entire Elixir mode configured?
* Should we publish instructions like in [this ElixirForum thread](https://elixirforum.com/t/emacs-elixir-setup-configuration-wiki/19196)?
* Should we combine our efforts with what ElixirLS is doing? Should we shift to a "we expect ElixirLS"?
* Do we want to support `polymode` for something like inline HTML templates

## Closing thoughts

Back earlier this year I spoke with @axelson and @Trevoke about how to help contribute to this project. Not without quite a bit of effort on my part, I was unable to figure out who to speak with or how to go about helping push this project forward. I'd love to close the gap between this extension and what VSCode is doing.