astropy.github.com Roles: Remove sub-role for community engagement coordinator

I think it is overkill to have so many sub-roles for community engagement. Infrastructure staff maintains multiple packages across the board (and manages releases for them too, etc) and yet we do not list all those packages on this page.

Affected people in this listing:

@mwcraig
@kelle
@eteq
@Cadair

TODO:

[x] community-engagement/README.md to capture info removed from Roles page
[x] Move TwitterGuidelines.md to community-engagement/ also
[x] Link to community-engagement/ from roles

Depends on:

https://github.com/astropy/astropy-project/pull/331

Mar 06 '23 22:03 pllim

Thanks so much for doing this!

I don't mind simplifying this page but I do want to make sure this information is captured somewhere. One goal of this page was to identify roles we want to make sure don't fall through the cracks. I would be more comfortable if this PR included a link to a README in the project repo.

@pllim , since this would be much easier for you than me, could you open a PR to project which creates a community-engagement/README.md with the information you want to remove here. You could also move the TwitterGuidelines.md in there.

Same for learn. Could you make a learn folder with the extra details you'd like to remove. Could also move a lot of the description at the bottom of the page.

And then link to those new pages in the description of each at the bottom of the page.

I could do all this myself, but it would take a while to move to the top of my list.

Mar 06 '23 23:03 kelle

The infrastructure team is well organized, talks to each other and coordinates among themselves who does what, so one contact is sufficient. On the other hand, the twitter person won't be able to help with a discourse configuration issue or the other way around, so they are listed as separate sub-roles. So, I think they should stay listed as separate sub-roles. If we hire a community manager who takes care of coordinating within this team, then we can remove it, but for now we need info on whom to contact for what problem.

Mar 07 '23 01:03 hamogu

The proposed change maintains the information about the realm of the person's involvement, but just condenses it onto one line.

So I agree completely with Moritz's comment and think the suggested change retains just enough of the necessary information.

But honestly, I don't have strong feelings one way or the other and hopefully we'll find a community engagement coordinator to take the primary role.

Mar 07 '23 01:03 kelle

@kelle , I don't know how I feel about the duplicated info but I opened https://github.com/astropy/astropy-project/pull/331 to address your request. As long as we remember to keep them in sync...

Mar 07 '23 04:03 pllim

I was envisioning MOVING the descriptive info from the webpage to the README, not duplicating (except names and roles).

Mar 07 '23 15:03 kelle

@kelle , I mean the names are duplicated. So if staff changes, now there is one more place to update or they are going to go out of sync. But I guess this is common problem across the board. 💭

Mar 07 '23 15:03 pllim

At Coordination Meeting 2024, group decision was made to keep the community manager role, so this PR is moot.

Jun 21 '24 16:06 pllim