-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call for Contributors #274
Comments
Thanks for the invitation @axelson, I am interested. |
Fantastic, invitation sent! |
Definitely interested. I'll have more questions than answers initially, but I've lurked long enough I may as well participate where I can 😏 |
Hi @axelson!
I can certainly help with some of the issues, especially the ones directly related to |
@jsmestad Thanks! That is very much appreciated and I've given you triage privileges and we can move to commit rights in time :) @msaraiva Sent an invite. And I totally respect that and please don't feel pressured. But by having more people contributing we can spread the maintenance burden further :) so just help out where and when you can. |
I'm interested. I have a specific issue right now with frequent crashes due to elixir-editors/emacs-elixir#415 I'd like to see if I can help address that problem. If not then maybe some other low-hanging fruit that other people don't want to spend time on. |
@kentbull thanks for the offer! Please start sending PR's and helping with issues :) |
@axelson any low hanging fruit you can think of that would be like a 'hello-world' contribution to help me get familiar with the workflow and review style? |
@axelson Looks like I missed that one; someone else got to it first. Anything else look like a good option? |
I'm going to close it to not pollute issues. If anyone is interested in contributing or joining the maintainers, please reach out |
In order to keep development of ElixirLS sustainable I believe that we need some more active contributors with commit privileges as well some people assisting with investigating and responding to issues.
In particular I am curious if @lukaszsamson and @msaraiva are interested.
The text was updated successfully, but these errors were encountered: