Skip to content
This repository was archived by the owner on Feb 5, 2020. It is now read-only.

Project: Erlang

Jump to bottom
bryanhuntesl edited this page Feb 5, 2019 · 4 revisions
  • Website: http://erlang.org/
  • Responsible: Brujo Benavides
  • If you have any questions, send an e-mail to beam-community AT googlegroups DOT com

Ideas are listed in no particular order. Students providing their own ideas are also welcome!

Idea #1: Erlang Code Formatter

Implement a configurable code formatter in the style of the Elixir Formatter but for Erlang code.

Expected results: An Erlang application that formats code, published in hex and a rebar3 plugin that uses it to add a rebar3 format command that formats all the code in a project.

Knowledge prerequisites: Erlang. Knowledge about the Erlang AST and/or the modules erl_syntax, erl_prettyptr, etc… is a bonus.

Possible Mentors: Brujo Benavides

Idea #2: Elvis Improvments

Elvis is the Erlang linter (it's used through rebar3 lint and also on its own. There is an active developer community (inaka behind it, but there are 50 open issues. The project needs some grooming and several issues must be solved to finally get it to version 1.0.0.

Expected results: Elvis 1.0.0.

Knowledge prerequisites: Erlang. Knowledge about the Erlang AST is a plus.

Possible Mentors: Brujo Benavides and the Inaka community.

Idea #3: Multi-node distributed tracing with Redbug

massemanet/redbug redbug - restricted debugging utility is an easy to use and most importantly safe abstraction on top of Erlang's built in tracing system.

redbug is a tool to interact with the Erlang trace facility. It will instruct the Erlang VM to generate so-called 'trace messages' when certain events (such as a particular function being called) occur. It uses a safe subset of the tracing functionality, and exits if it feels overloaded, e.g. if it gets flooded by trace messages. It runs in the background, collecting trace messages, until it reaches one of its termination criteria (number of messages/file size or elapsed time). The trace messages are either printed (i.e. human readable) to a file or to the screen....

Redbug currently supports tracing upon one node (local or remote) - it would be very useful if it could be extended or serve as the inspiration for a new tracing library which could provide the same functionality but for an array of Erlang nodes.

Expected results: Redbug with multi-node distributed tracing.

Possible Mentors: Bryan Hunt

Clone this wiki locally