pandas-dev
Determine initial composition of Teams #1
Each of the core team members should indicate which teams they wish to be a member of. Ideally, we would have at least 1 member of the current core team on each of the other teams. The longer descriptions of each team can be found at: https://github.com/pandas-dev/pandas-governance/blob/main/teams.md
For each team, we list the current members and who decides how new members can join.
- Core Library Team (Membership determined by team members)
- All current core team members. If you wish to drop from this team, now is the time to do so!
- pandas-stubs Team (Membership determined by team members)
- Irv Lustig
- Torsten Wörtwein
- Finance Team (Membership determined by Steering Committee)
- Matthew Roeschke
- Jeff Reback
- Joris Van den Bossche
- Patrick Hoefler
- Infrastructure Team (Membership determined by team members)
- Marc Garcia
- Matthew Roeschke
- Thomas Li
- Outreach Team (Membership determined by Team). Formerly "Communications Team"
- Marco Gorelli
- Marc Garcia
- Triage Team (Membership determined by Core Library Team)
- People with current Triage privilege in Github
- Documentation Team (Membership determined by team members)
- Contributor Community Team (Membership determined by Core Library Team)
- Website Team (Membership determined by Team)
For the last 3 teams, we need volunteers from the current core team to get those teams started.
In the comments below, each member of the current core team @pandas-dev/pandas-core should indicate the following:
- If you are currently on any of the above teams, and you wish to be removed.
- If you wish to be listed as a member of any of the above teams.
If you are currently on any of the above teams, there is no need to indicate whether you wish to continue. We will assume that you will continue as a member of that team.
Responses needed by October 25.
@pandas-dev/pandas-core
I won't be joining any of the teams at this point. Also not the ones I'm currently a member. The time I have for pandas right now is quite limited at the moment.
I won't be joining any of the teams at this point. Also not the ones I'm currently a member. The time I have for pandas right now is quite limited at the moment.
@datapythonista can you clarify the statement "not the ones I'm currently a member"? Do you still want to be on the core library team? If you're not on any teams, including the core library team, then we'd move you to the "Inactive Maintainer" status.
@datapythonista can you clarify the statement "not the ones I'm currently a member"? Do you still want to be on the core library team? If you're not on any teams, including the core library team, then we'd move you to the "Inactive Maintainer" status.
I meant infrastructure and communications. I'm happy to stay as an active core dev for now.
I'd like to be removed from the Infrastructure Team.
(I'm happy to stay on the Finance Team)
I'm willing to be on the documentation, contributor community, and outreach teams.
In addition to the teams I am already on, in practice I am also on the contributor community team.
And I would have the desire to be involved in documentation and outreach/website teams, but not entirely sure if I will have the time commitment.
but not entirely sure if I will have the time commitment.
I understand what you're saying here, but I do want to emphasize in general that by signing up for a team you are not committing to having bandwidth for any particular time period nor task. At least, that's my take.
I'm a bit late to respond, but I'd like to be on the contributor community team
What are our next steps here? I know we had a deadline of Oct 25 in the OP - do we still need more time to gather feedback or should we move forward?
hey - i'd like to be removed from outreach please
i'm not very active now, but I have made some changes which will affect 3.0, so I'd like to stay on core at least until then (after which, I'll reassess based on my activity level)
If you are currently on any of the above teams, there is no need to indicate whether you wish to continue. We will assume that you will continue as a member of that team.
yep. happy with the status quo. i.e. just the core team for now.
do we still need more time to gather feedback or should we move forward?
although from the instructions I didn't need to comment, hopefully this ticks me off the list if awaiting further comments
What are our next steps here? I know we had a deadline of Oct 25 in the OP - do we still need more time to gather feedback or should we move forward?
On my list of things to do is to list the members of the teams based on the feedback given here. Thanks for asking. I will be doing this by the next governance meeting next week.
@jorisvandenbossche is reaching out to some people who we hope are willing to be the "vote collector" for the first steering committee vote.
Based on the above, here is the proposed set of teams:
-
Core Library Team (Membership determined by team members)
- @WillAyd William Ayd
- @jreback Jeff Reback
- @jorisvandenbossche Joris Van den Bossche
- @TomAugspurger Tom Augspurger
- @bashtage Kevin Sheppard
- @noatamir Noa Tamir
- @fangchenli Fangchen Li
- @jbrockmendel jbrockmendel
- @lukemanley Luke Manley
- @datapythonista Marc Garcia
- @mroeschke Matthew Roeschke
- @simonjayhawkins Simon Hawkins
- @Dr-Irv Irv Lustig
- @alimcmaster1 Ali McMaster
- @attack68 JHM Darbyshire
- @topper-123 Terji Petersen
- @MarcoGorelli Marco Edward Gorelli
- @rhshadrach Richard Shadrach
- @lithomas1 Thomas Li
- @phofl Patrick Hoefler
-
pandas-stubs Team (Membership determined by team members)
- @Dr-Irv Irv Lustig
- @twoertwein Torsten Wörtwein
- @loicdiridollou Loic Diridollou
-
Finance Team (Membership determined by Steering Committee)
- @mroeschke Matthew Roeschke
- @jreback Jeff Reback
- @jorisvandenbossche Joris Van den Bossche
- @phofl Patrick Hoefler
-
Infrastructure Team (Membership determined by team members)
- @lithomas1 Thomas Li
- @WillAyd Will Ayd
-
Outreach Team (Membership determined by Team). Formerly "Communications Team"
- @WillAyd Will Ayd
- @rhshadrach Richard Shadrach
- @jorisvandenbossche Joris Van den Bossche
-
Triage Team (Membership determined by Core Library Team)
- @Moisan Thierry Moisan
- @jnothman Joel Nothman
- @afeld Aidan Feldman
- @tswast Tim Sweña (Swast)
- @jreback Jeff Reback
- @moink moink
- @asishm Asish Mahapatra
- @dsaxton Daniel Saxton
- @smithto1 Thomas Smith
- @hasB4K Mathis Felardos
- @fujiaxiang Jiaxiang
- @bashtage Kevin Sheppard
- @DriesSchaumont Dries Schaumont
- @martindurant Martin Durant
- @debnathshoham Shoham Debnath
- @noatamir Noa Tamir
- @ssche Sven
- @fangchenli Fangchen Li
- @lukemanley Luke Manley
- @fjetter Florian Jetter
- @charlesdong1991 Kaiqi Dong
- @DeaMariaLeon Dea María Léon
- @ParfaitG Parfait Gasana
- @Dr-Irv Irv Lustig
- @alimcmaster1 Ali McMaster
- @realead realead
- @AlexKirko Alex Kirko
- @attack68 JHM Darbyshire
- @alexhlim Alex Lim
- @cdknox Conner Knox
- @CloseChoice Tobias Pitters
- @MarcoGorelli Marco Edward Gorelli
- @erfannariman Erfan Nariman
- @mzeitlin11 Matthew Zeitlin
- @AnnaDaglis Anna Daglis
- @ivanovmg Maxim Ivanov
- @rhshadrach Richard Shadrach
- @lithomas1 Thomas Li
- @arw2019 Andrew Wieteska
- @ShaharNaveh Shahar Naveh
- @Aloqeely Abdulaziz Aloqeely
- @phofl Patrick Hoefler
- @natmokval Natalia Mokeeva
- @paulreece paulreece
-
Documentation Team (Membership determined by team members)
- @rhshadrach Richard Shadrach
- @jorisvandenbossche Joris Van den Bossche
-
Contributor Community Team (Membership determined by Core Library Team)
- @rhshadrach Richard Shadrach
- @jorisvandenbossche Joris Van den Bossche
- @noatamir Noa Tamir
-
Website Team (Membership determined by Team)
- @jorisvandenbossche Joris Van den Bossche
Based on the above, here is the proposed set of teams:
@Dr-Irv there are still only 4 teams in the pandas-dev organization. when will the teams be setup officially? now that the new governance is in place and the steering committee elected there are no blockers?
Also we have a pandas-stubs-triage-team that's not included in the governance structure.
Based on the above, here is the proposed set of teams:
@Dr-Irv there are still only 4 teams in the pandas-dev organization. when will the teams be setup officially? now that the new governance is in place and the steering committee elected there are no blockers?
It's on my TODO list to straighten out the memberships and email addresses of the teams.
Also we have a pandas-stubs-triage-team that's not included in the governance structure.
Yes, I should add that. Thanks.
It's on my TODO list to straighten out the memberships and email addresses of the teams.
the team mentions on Github for starters? private mailing lists would be maintained by the teams themselves?
just asking so to avoid mention people explicitly in github issues.
It's on my TODO list to straighten out the memberships and email addresses of the teams.
the team mentions on Github for starters? private mailing lists would be maintained by the teams themselves?
just asking so to avoid mention people explicitly in github issues.
We just had a steering committee discussion related to email aliases, and what I think we'll do is have a duplication of the GitHub teams and email aliases (which would be google groups managed by the pandas.pydata.org domain), but the infrastructure team (and steering committee) would have access to the 1Password account that allows management/creation of those groups.
Open to other suggestions on how to avoid the duplication and make it easier to manage.
Visibility and clarity within the GitHub organization I think is more of a priority, ensuring that contributors can easily identify relevant teams and mention them in discussions.
I have no opinion on management of mail groups and security. For best how to do that perhaps could team mention the infrastructure team ;)