-
Notifications
You must be signed in to change notification settings - Fork 0
PDEP decision making #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: Irv Lustig <irv@princeton.com>
Co-authored-by: Terji Petersen <contribute@tensortable.com>
Co-authored-by: Simon Hawkins <simonjayhawkins@gmail.com>
Co-authored-by: Simon Hawkins <simonjayhawkins@gmail.com>
@noatamir can you merge in the current PR pandas-dev#51417 into here, and then do your changes on top of that so then it is clear which changes are from this PR versus the ones proposed (and hopefully accepted soon) in the pandas project? You might need a new PR here to make it clear, i.e., you first merge in that PR, push into main into your fork, and do a new PR with the new changes, or you could copy that PR to here, and then make this PR a merge into that copy of the PR. Hope what I am writing here makes sense. |
### PDEP-1 History | ||
|
||
- 3 August 2022: Initial version | ||
- 3 August 2022: Initial version ([GH-47938][47938]) | ||
- 15 February 2023: Version 2 ([GH-51417][51417]) clarifies the scope of PDEPs and adds examples |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add to History (once version 2 is merged)
The governance working group has been discussing the PDEP workflow and decision-making for some time now.
This PR proposes some formulation of the existing workflow to clarify and facilitate it for current and future authors, and voting members.
In our discussions, we assessed that a more structured process would help folks who submit the PDEP know how and when it can progress, and how to better engage with others.
The timelines were considered to facilitate an engaging discussion, and automation. We aim to make the lives of the PDEP authors easier by taking away the need to decide "has it been long enough", or "cat herding" folks to engage and clarify their comments so that PDEPs don't get large change requests that could have been clarified early on - late in the process.
We tried to make things as flexible and clear as possible. Being mindful of the needs of the authors, as well as those engaging in the discussion, be them voting members or not.
At this point, we would like to invite feedback. It might be that you need more clarity on the suggestions, have ideas for improvement, or aren't convinced that this will affect the current process positively.