Publishing OTP backlogs
The IEUG is working towards improving and formalising the process of community contributions. There are three types of changes: smaller changes, enhancements and bug fixes; major changes; Erlang Extension Proposals.
Smaller changes works well as it is today with the public issue tracker. It needs to be better documented. There is little guidance on how to handle big changes such as dirty schedulers. EEPs focus more on language changes which could be released in branches (e.g. maps) and, if accepted, get merged to a stable branch. The priority right now is on the backlogs. IEUG is working in facilitating the Erlang/OTP team in publishing an up-to-date work backlogs/roadmap.
Erlang package management system
The IEUG has investigated and compiled a list of requirements for an Erlang package manager, based on community opinions. It is the IEUG’s goal to work with the community and Ericsson in creating a standard and address any voids which exists in the existing Erlang tooling, funding necessary efforts required. In 2015, the IEUG funded two interns in assisting in the development of additional features in rebar3, the Erlang build tool, and Hex, the Elixir/Erlang package index.
The IEUG does not own the copyright to any of the Erlang source code. The copyrights are retained by the organizations and individuals that contributed the code, mainly Ericsson AB. Starting from OTP 18.0, Erlang is licensed under the open-source Apache License 2.0. The IEUG initiated and maintained a constructive dialogue with the Erlang/OTP team at Ericsson in an effort to transit from the Erlang Public License to the Apache License 2.0.
For most users, the details of the license are irrelevant. All of the licenses grant permission to use, modify, and redistribute the code in an non-restrictive way. For Erlang, an open and commonly accepted license means adoption at a wider and global level. The Erlang Public License is a derivative work of the Mozilla Public License (MPL) that contained different jurisdiction terms that are in accordance with the laws of Sweden. While the Apache License 2.0 is well known and compliant with the Open Source Definition approved by the Open Source Initiative.
Community website Erlang Central
The IEUG funded the redesign of the community website, erlangcentral.org. This included replacing the graphic design for the existing community website trapexit.org with a professional design, migrating the site content, and development of a new content management system for the site.
The aim was to engage the Erlang community while allowing users evaluating the technology to quickly get started. The functionalities of the website included social login, jobs, forums, community announcements, wiki, Erlang Times, Erlang project crawler.
To compare the new and old designs, visit http://erlangcentral.org/ and
The IEUG and Ericsson jointly funded a community manager to work closely with the Erlang/OTP team. The role of the community manager is to provide a single point of contact for projects, track and report on progress, and to facilitate a communication channel between the member companies, open source community, and Erlang/OTP team. The community manager also manages contents and social media of Erlang Central, encouraging user participation and growth.
The IEUG member companies (Basho Technologies, Klarna) have contributed code to the Erlang VM where new Erlang features help C and C++ code cooperate seamlessly with Erlang schedulers. The dirty scheduler was implemented by Basho and Klarna in close collaboration with the Erlang/OTP team at Ericsson. It was included in OTP 17.0 as an experimental functionality.
Public issue tracker
The IEUG members funded and set up a public issue tracker system for Erlang/OTP. This included replacing the erlang-bugs mailing list with a professional and modern issue tracking system that is compatible with the Erlang/OTP team’s internal systems and infrastructures. The issue tracker served as a first step towards the IEUG’s goal of improving and formalising the process of community contributions. To see the public issue tracker, visit: http://bugs.erlang.org.
For inquiries please contact firstname.lastname@example.org