Roles: Remove sub-role for Learn Team

[pllim]

I think it is a little overkill to have so many sub-roles for Learn Team. 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.

This PR eliminates sub-role for Learn Team but kept them in parenthesis since I also notice you have sub-responsibility. This is not ideal but it is getting late and I cannot think of anything better. Ideas welcome. If we can make this more fluid, then when you move Learn staff around the team, you don't have to constantly come back to update this page.

Affected people in this listing:

• @eblur
• @kelle
• @adrn
• @mwcraig
• @eteq
• @jonathansick
• @stargaser
• @bmorris3

TODO (from #524 (comment)):

• learn/README.md to capture info removed from Roles page and move "the description at the bottom of the page" over
• Link to learn/ from roles

Depends on:

• Add Learn Team astropy-project#332

Also see:

• Implement CODEOWNERS astropy-learn/astropy-tutorials#580
• Implement CODEOWNERS astropy-learn/learn-astropy#71

[jonathansick]

This seems reasonable to me if it's easier to maintain the team page without all the sub-roles 👍

The fine-grained subroles might even be better maintained in other ways. e.g., a GitHub team for content editors could then let us assign PR reviews automatically.

[hamogu]

The learn team seems to coordinate within themselves with regular telecons. Also, I think several people are stepping back from active engagement, so maybe this is time to restructure it and summary a bit.

[pllim]

@jonathansick , is astropy-learn/learn-astropy#71 sufficient for follow-up? I get confused now between astropy-tutorials and learn-astropy. Is this the correct repo?

EDIT: I also opened astropy-learn/astropy-tutorials#580 just in case.

[pllim]

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

[jonathansick]

@jonathansick , is astropy/learn-astropy#71 sufficient for follow-up? I get confused now between astropy-tutorials and learn-astropy. Is this the correct repo?

@pllim Thanks for making those issues! astropy/astropy-tutorials is content-oriented and astropy/learn-astropy is infrastructure-oriented so that's a good expression of the editorial vs infrastructure sub-roles for example.

[eteq]

See my inline comment about workshop role. But also I feel like the discussion #524 applies here - that there is value in ensuring we don't lose the information of all the work. Should we maybe just copy over the info here?

[eteq]

I think the workshop coordinator work is really a distinct role that aligns with Learn but should be highlighted as a quite different set of work. Obviously it's part of the Learn effort, but I think we lose a lot of information by not recording this. After all one of the main points of the roles page is to know "who is doing this work, if anyone", and this is critical work.

Suggested change

	},
	},
	{
	"role": "Workshop Coordinator",
	"url": "Workshop_coordinator",
	"people": [
	"David Shupe",
	"Brett Morris",
	"Kelle Cruz"
	],
	"role-head": "Workshop Coordinator",
	"responsibilities": {
	"description": "Organize and coordinate Astropy workshops for training and outreach to users",
	"details": [
	"Maintain the astropy-workshops repository",
	"Oversee staffing/volunteers for workshops",
	"Identify opportunities for workshops in diverse geographic locations"
	]
	}
	},

[eteq]

(I had to do something a bit weird in the suggestion there, so @pllim , if you accept that you'll definitely want to wait for the CI to be sure I didn't break teh JSON)

[hamogu]

After discussion in the Coordination meeting, we believe that it's worthwhile to have relatively fine-grained roles, even if they might be unfilled. Names should be updated (or be replaced by "unfilled") in a separate PR.