You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The team page lists names of subpackage maintainers but not GitHub usernames, which are not always obvious.
(One thing I miss from the Trac issue tracker is you could add sub-component "owners" who would be assigned to tickets relevant to their interest areas.)
In practice with Astropy a maintainer typically does this sort of triage manually but it would help for new contributors to get the right eyes on their work right away.
Reacted by Michael Seifert, Brigitta Sipőcz, Erik Tollerud and Adrian Price-Whelan
Good point - the catch is that I think it might make the page start looking really busy if all names also had usernames. Perhaps we should make the names instead be links to the github user page?
The easiest implementation would probably be to insert a mapping of names to github into the javascript that generates the table and have it automatically replace the text with the relevant hyperlink...
@embray , regard on your note about "links to github profiles and/or personal websites/social media" -- I am wary of the latter (personal website/social media) as some people might value privacy more than others, so if you want to do that, please make it opt-in only and optional.
Definitely anything anyone wants to put on the team page, even including GH profiles, should be opt-in. I think we need to create a database of some sort (as in a plain text file, such as a YAML file) where project contributors can add whatever they wish via a PR. This is how the Software Carpentry project manages its instructors page (which might also serve as inspiration for what we might like to do).
In order to make things not too busy, that might also suggest the need for two separate pages or listings: One that's just a gallery of project members, and another more like we already have listing project roles. Both pages could be generated from the same source data :)
Oh I didn't realize that was the case. I think what I had in mind was inverting it: By instead having a database of people, and for each person list any roles they adopt. There could still be a separate file like the above containing additional metadata about each role.
Activity
eteq commentedon Jun 5, 2019
Good point - the catch is that I think it might make the page start looking really busy if all names also had usernames. Perhaps we should make the names instead be links to the github user page?
The easiest implementation would probably be to insert a mapping of names to github into the javascript that generates the table and have it automatically replace the text with the relevant hyperlink...
pllim commentedon Sep 8, 2020
@embray , regard on your note about "links to github profiles and/or personal websites/social media" -- I am wary of the latter (personal website/social media) as some people might value privacy more than others, so if you want to do that, please make it opt-in only and optional.
embray commentedon Sep 9, 2020
Definitely anything anyone wants to put on the team page, even including GH profiles, should be opt-in. I think we need to create a database of some sort (as in a plain text file, such as a YAML file) where project contributors can add whatever they wish via a PR. This is how the Software Carpentry project manages its instructors page (which might also serve as inspiration for what we might like to do).
In order to make things not too busy, that might also suggest the need for two separate pages or listings: One that's just a gallery of project members, and another more like we already have listing project roles. Both pages could be generated from the same source data :)
pllim commentedon Sep 9, 2020
@embray , how is that different from what we already do (except the new concept of gallery)? We already have https://github.com/astropy/astropy.github.com/blob/master/roles.json and there are outstanding PRs to update it.
embray commentedon Sep 9, 2020
Oh I didn't realize that was the case. I think what I had in mind was inverting it: By instead having a database of people, and for each person list any roles they adopt. There could still be a separate file like the above containing additional metadata about each role.
pllim commentedon Oct 19, 2020
This is now a pre-requisite for astropy/astropy-project#160
dhomeier commentedon May 3, 2023
This could include adding actual links to their profile pages, see #498.
pllim commentedon Feb 29, 2024
I think this is duplicate of #183