Some work for the Erlang SIG

[Timothée Floure]

Hello everyone,

I discussed the following points with Randy and Jeremy during Flock 2018 but
didn't find (or take) the time to send this mail before.

First of all, rebar3 is now in rawhide [0]: I know that a few packages were
waiting on it, and some existing package only build with rebar2 (which has been
deprecated for a while) due to a mix of hack and chance. I think we should
rework Peter's packaging guidelines [1] to:
  * Replace rebar2 by rebar3 (following upstream) to build all of our Erlang
    packages (do we need to announce a change?)
  * Make better use of the Hex package repository [2]
  * Push them to the official guidelines [3]

As for the Erlang SIG itself, I'd like to extend it to the elixir language [4],
which is built atop the Erlang environment and is already packaged (I
co-maintain it) in Fedora. It would also be nice (mentioned by Randy if I
remember well) for the erlang SIG to be able to access any erlang library in
dist-git as it is already done for some other language-specific SIGs.

What do you think? Can I go ahead and start working on mentioned tasks?

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1638743
[1] https://fedoraproject.org/wiki/User:Peter/Erlang_Packaging_Guidelines
[2] https://hex.pm/
[3] https://fedoraproject.org/wiki/Packaging_Committee#Guideline_Change_Procedur...
[4] https://elixir-lang.org/

Cheers,

[Peter Lemenkov]

Hello All!

ср, 12 дек. 2018 г. в 21:42, Timothée Floure :
> Replace rebar2 by rebar3 (following upstream) to build all of our Erlang
> packages (do we need to announce a change?)

Sounds good. I believe that we should keep current rebar2 macros
(rename it) and use rebar3 as a default builder.
> Make better use of the Hex package repository [2]

Sounds good as well. Not sure if rebar3 has a support for hexpm yet.
> Push them to the official guidelines [3]

Since we don't have official guidelines yet, this one is the easiest :)
> As for the Erlang SIG itself, I'd like to extend it to the elixir language [4],
> which is built atop the Erlang environment and is already packaged (I
> co-maintain it) in Fedora. It would also be nice (mentioned by Randy if I
> remember well) for the erlang SIG to be able to access any erlang library in
> dist-git as it is already done for some other language-specific SIGs.

Good catch. I think we need some dedicated bot for that (mass changes, etc).
> What do you think? Can I go ahead and start working on mentioned tasks?

Sure go on!

[Timothée Floure]

One more thing: do we want a bug tracker for the SIG? We only have per-package
bugs for now, an erlang pagure project might make sense to track changes across
the whole set of erlang packages.

[Randy Barlow]

Hey Timothée!

On Wed, 2018-12-12 at 21:41 +0100, Timothée Floure wrote:
> First of all, rebar3 is now in rawhide [0]: I know that a few
> packages were
> waiting on it, and some existing package only build with rebar2
> (which has been
> deprecated for a while) due to a mix of hack and chance. I think we
> should
> rework Peter's packaging guidelines [1] to:
> Replace rebar2 by rebar3 (following upstream) to build all of our
>
> Erlang
>     packages (do we need to announce a change?)
> Make better use of the Hex package repository [2]
> Push them to the official guidelines [3]

+1
> As for the Erlang SIG itself, I'd like to extend it to the elixir
> language [4],
> which is built atop the Erlang environment and is already packaged (I
> co-maintain it) in Fedora. It would also be nice (mentioned by Randy
> if I
> remember well) for the erlang SIG to be able to access any erlang
> library in
> dist-git as it is already done for some other language-specific SIGs.

+1. We have an erlang FAS group (I just added you to it), but it
doesn't seem I can add that FAS group to permissions in Pagure, so I
filed a ticket to request that:

https://pagure.io/fedora-infrastructure/issue/7456
> What do you think? Can I go ahead and start working on mentioned
> tasks?

+1