VMware collection maintainers

[mariolenz]

@goneri doesn't maintain vmware.vmware_rest any more. I'm afraid that, although some people are actively working on the collection and are preparing a new release, there are no named maintainers right now :-/

On the other hand, I'd like to add myself as the maintainer of community.vmware. Just realized this hasn't been documented yet.

[goneri]

Thank you @mariolenz .

[felixfontein]

The group ping is fine from my side. Let's quickly talk about this at today's community WG meeting.

[mariolenz]

The group ping is fine from my side. Let's quickly talk about this at today's community WG meeting.

Probably the same in #334

[felixfontein]

@gotmax23 mentioned on Matrix that he doesn't like the team reference; he'll write something about that here later when he has time, we'll continue the discussion then.

[gotmax23]

Yeah, I'm really not a fan of the team reference. It's not visible to non @ansible-collections members who is in that team, and we cannot directly ping that team from this repository.

[mariolenz]

Yeah, I'm really not a fan of the team reference. It's not visible to non @ansible-collections members who is in that team, and we cannot directly ping that team from this repository.

Better than documenting a wrong maintainer or nothing 🤷

[felixfontein]

Yeah, I'm really not a fan of the team reference. It's not visible to non @ansible-collections members who is in that team, and we cannot directly ping that team from this repository.

I think not being able to ping them from this repository is OK, the main purpose is to be able to ping the maintainers on issues directly in their repository. Not being able to see the members of the team is more of a problem. This makes it impossible to directly take the current list of team members and ping them from here (if necessary).

I personally think it would be OK to allow teams in Ansible-owned organizations such as ansible-collections and ansible-network, since there we can ask the Community Team to ping internally (if we don't have access).

[mariolenz]

Not being able to see the members of the team is more of a problem. This makes it impossible to directly take the current list of team members and ping them from here (if necessary).

How about about documenting the maintainers as https://github.com/orgs/ansible-collections/teams/cloud? Or maybe ansible-collections/cloud (https://github.com/orgs/ansible-collections/teams/cloud)?

I really think the "we would prefer to not have to maintain a static list of staff in multiple places" argument is a pretty a good one.

[felixfontein]

I created a topic on the forum to discuss this: https://forum.ansible.com/t/collection-maintainer-information-for-collections-included-in-ansible/2562

[felixfontein]

Marking this PR and #334 as drafts.

[gotmax23]

Yeah, I think listing the team members manually is good for now. Thanks @mariolenz!

[gotmax23]

@felixfontein, @Andersson007, can one of you give this a look also?

[felixfontein]

I've commented on Matrix, I'd like to see a link to the GH team as a comment. That information is IMO the main source of truth, not that explicit list, so it should really be there.