So far, I've included maintainers from related packages:

• @ankhers
• @couchemar
• @filalex77 @Br1ght0ne
• @gleber
• @happysalada
• @Havvy
• @sjmackenzie
• @yurrriq

@yurrriq please fix the merge conflict and if we have a positive reaction from everyone mentioned (thumbs up the first post maybe) we can merge this.

Sorry about that, I've rebased now and added @Br1ght0ne.

Should we update doc/languages-frameworks/beam.section.md to mention the team?

Should we update doc/languages-frameworks/beam.section.md to mention the team?

Might be a good idea.

With some cursory grepping, I wasn't able to find any mention of teams in other docs 😕

With some cursory grepping, I wasn't able to find any mention of teams in other docs 😕

I did not check this but if the others don't do it then it is fine without it.

@yurrriq thnaks a lot for doing this!

Can you add

• the gleam compiler?
• rebar3 build manager
• rebar build manager (Maybe not necessary, it's deprecated as far as I know and there are no existing maintainers)

When you have a moment

it's deprecated as far as I know and there are no existing maintainers

It would be still good to have some maintainers for it as long as it is in nixpkgs.

My name should be removed from anywhere I'm mentioned, but you should definitely NOT create a new team of people without asking for their permission.

My name should be removed from anywhere I'm mentioned, but you should definitely NOT create a new team of people without asking for their permission.

We can't purge logs and activity on GitHub. It is pretty normal to collect people who updated packages and where written as maintainer in a team and ask then for their permission to not miss anyone. Before merging we wait until their responses and remove anyone who does not want to be part of the team.

If you need one more maintainer, feel free to add me. I have been doing quite some work around the beam set recently

@yurrriq how about proceeding the other way around. Just adding people who have reacted.
so far I can see @Br1ght0ne, yourself, @DianaOlympos and me.
Let's keep it at that for now, people can always add themselves later on.
If we wait for everybody's approval we might struggle to merge this.
I don't think anyone who doesn't respond within a week will mind being taken off the maintainer's list of a package.

My intention was for this Draft PR to start these discussions regarding desired team members. Part of the reason it's marked as a draft is to ensure we don't make any changes without consent and buy-in from all involved. I figured it was better to have something tangible to discuss.

To be clear for those that have requested to be removed, as this PR exists currently, that would also remove you as maintainers of the specific BEAM packages. Is that the desired effect?

I've force pushed the following updates:

• Change the BEAM team members list to those who have actively expressed interest
• Set maintainers = lib.teams.beam.members on a few more BEAM-related expressions
  • Notably, this additionally removes @tazjin from pkgs/development/interpreters/elixir/generic-builder.nix
  • I notice the pgsql, webdriver, and hex packages currently have @ericbmerritt as the sole maintainer.

1. Should we set maintainers = lib.teams.beam.members for pgsql, webdriver, and hex packages too?
2. Would you like to be included in the BEAM team, @tazjin?
3. Would you like to be included in the BEAM team, @ericbmerritt?

If you need one more maintainer, feel free to add me. I have been doing quite some work around the beam set recently

@DianaOlympos, it looks like we'll need to add you to maintainers/maintainer-list.nix. I can do that now for convenience, otherwise feel free to PR against yurrriq/nixpkgs@beam-team.

I am fine with being added to this list with the caveat that I do not currently have a lot of time, at least until this virus clears up a little more in my area.

@yurrriq I would say yes to setting the beam team for pgsql, webdriver and hex.

@yurrriq Thanks for asking, unfortunately I don't have time for this at the moment (and - again unfortunately - I'm not using any BEAM languages for the time being :))

@yurrriq I would say yes to setting the beam team for pgsql, webdriver and hex.

Done. As I see it, we're waiting on feedback from Eric Merritt and Thomas Depierre before marking this ready for broader review.

@yurrriq @SuperSandro2000
it looks like @ericbmerritt is busy. How about we merge this for now, we can always make a new PR later?
Let me know if you think this is premature.

Looks like his last contribution was in 2016, so that seems fair to me.

I do not have much time for BEAM in Nixpkgs lately. I can not promise swift response, so If you need backup people on the list, feel free to include me.

@SuperSandro2000 when you have a moment, please take a look. No problem if you are busy.

is the list complete now?

@Mic92 yes that is my understanding.

I'd say it's complete for now anyway.

I could not invite @DianaOlympos to https://github.com/orgs/NixOS/teams/beam, because he is not in the nixos organisation yet.

@Mic92 i am in now

fixed.

Thanks, @Mic92 and @DianaOlympos!