Teams Responsibilities, permissions, criteria #18
Conversation
|
@jorisvandenbossche This is the part that would go "in the middle" of the governance document. |
|
I would maybe separate the steering committee from the other teams? |
Dr-Irv
changed the title
| #### Permissions | ||
|
|
||
| * Has permission to merge anything to the main branch of the _pandas _repository | ||
| * Only Team with PDEP voting rights |
There was a problem hiding this comment.
Yes, I can see how in the majority of cases this would be true. There are a couple of examples in the Clear examples for potential PDEPs and Borderline examples section of the PDEP such as Changing the build system to meson where this may no longer be appropriate?
I guess that once the governance documents are updated we will need to revisit the PDEP process to update some wording such as core development team anyway?
Is it worth starting that revision of PDEP-1 now in parallel with the governance revisions so that the language and responsibilities are consistent and not ambiguous ?
There was a problem hiding this comment.
I think we have to agree that once the governance changes are accepted, then we'll update PDEP-1.
|
Incidentally, do we know if the teams idea is going to work in practice? i.e. do we have core (library) members that have shown an interest in participating in the proposed teams? |
That's a really good question, and we'll have to discuss how to figure that out. The concept of the teams was discussed in Basel (I was not there), so I'm hopeful that people were aligned with the concept and would be willing to participate in more than one team. |
|
@Dr-Irv I don't seem to have permission to edit the title. typo Responsibilites -> Responsibilities |
Dr-Irv
changed the title
Thanks for pointing that out. I fixed it. |
|
@pandas-dev/pandas-core pinging for any further comments. |
|
Let's merge this as is (and as voted on). We can further tweak names and wording later, when starting to more formally implement those. |
This has a file that would be removed in the final governance acceptance, but is kept separate to allow discussion on the fundamental concepts of the steering committee and teams.This contains a file that describes the responsibilities, permissions and admissions criteria for the different teams.
Related to #17