Update team page with council membership list #569
Conversation
There was a problem hiding this comment.
This looks good to me - it is a nice refresh to reflect the current team dynamics. I think there might be more stuff to improve as we learn about these roles more but IMO it's good to merge.
I'm not sure how to interpret the fact that everybody is on the council. As the group size is still within our stated target size, my feeling is that it's OK. But I'm wondering what circumstances would lead somebody to self-identify as maintainer instead of council? Maybe it is just most-appropriate for newer members of the team?
| " ", | ||
| ) | ||
|
|
||
| # team_titles = { |
There was a problem hiding this comment.
If you'd like to do something with these sections later on, could you leave a # TODO comment to explain why they're commented out?
There was a problem hiding this comment.
Added a note about what this was for - we could have a list like the 'inactive members' list for each team. Or we could list teams on the cards. Either way!
|
As I tried to describe in #497 (comment), I think there are several more folks that should be listed as team members / maintainers, who aren't listed yet, since we had before was mainly the one 'core team' which maps most directly to the council. Now that we have more distinct roles, it makes sense for more folks to be listed here. |
|
Ah yes, i missed that comment. I think that makes a lot of sense. Also good point that being a maintainer is usually scoped to one or more repositories, whereas steerco is more like the whole project. Maybe we should generate a list of each repository in the org with the listed maintainers for it. That way it will also be clear if a repository does not have a maintainer. |
|
Just to be clear, my comment above is not blocking, I think we should merge this and iterate |
Co-authored-by: Simon Li <orpheus+devel@gmail.com>
|
Anything blocking this from moving forward? |
|
pinging: @damianavila @ivanov @fperez Damian, Paul, and Fernando are members of the original SC who requested to be members of the JupyterHub Council as we transition away from the SC. Please can we add them in this PR? |
|
Sure! If @damianavila @ivanov @fperez could add
like what other folks have (you can see examples in the pr) in a comment, I'll add you to the PR. (that will also be a record of their intent, since I don't seem to have that) |
|
Thanks for the ping, done!. |
Co-authored-by: Tim Head <betatim@gmail.com>
add Paul Ivanov
|
Will do it tomorrow, thanks for the ping! |
|
I suggest that we merge this one in. If there are small adjustments to make, we can always do this in a subsequent PR, but it is an iterative improvement and will reflect the reality of our current team better than the docs currently do. Are there any objections to this idea? |
Update Damian's data
|
@choldgraf I think it's all set! |
|
There seem to be agreement that this should be merged so I'll go for it, it looks fine to me as well! |
closes #566
I added everyone who said at least 'maybe' for the Council, since we don't have too many (9), and folks can always step down.
Adds the team membership to each team member card. However, all currently active team members are steering council members. I added some more todos in #497 (comment) because we haven't updated the other team lists, which still need updating. Including recognizing several folks who I think ought to be current 'team members' by the new definition but aren't listed right now.