-
-
Notifications
You must be signed in to change notification settings - Fork 18.7k
PDEP-1 Revision (Decision Making) #53576
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
Changes from 1 commit
a9c499d
233c03e
45c95fc
0133e82
4ad9f80
8108b43
2b3c5ad
9092668
a737034
a59e759
48b3300
32fce5e
0530d29
288e005
809ae6f
d5a1869
88a7db9
97ba480
e18db08
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -84,7 +84,7 @@ for the expected format. | |
|
||
The initial status of a PDEP will be `Status: Draft`. This will be changed to | ||
`Status: Under discussion` by the author(s), when they are ready to proceed with the decision | ||
making process. | ||
making process. | ||
|
||
#### PDEP Discussion Timeline | ||
|
||
|
@@ -111,7 +111,7 @@ As the voting period starts, a VOTE issue is created which links to the PDEP dis | |
Each voting member may cast a vote by adding one of the following comments: | ||
|
||
- +1: approve. | ||
- 0: abstain. | ||
- 0: abstain. | ||
jorisvandenbossche marked this conversation as resolved.
Show resolved
Hide resolved
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we want to add a small explanation of how we understand "abstaining" or what it could mean? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Isn't that the one sentence reason thing on the next line? |
||
- Reason: A one sentence reason is required. | ||
- -1: disapprove | ||
- Reason: A one sentence reason is required. | ||
|
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.
Apologies if I havce missed this but it does appear that a "voting member" is explicitly defined?
The removed section seems to suggest that a voting member is anyone in the "core development team". Does pandas have any segregation between "active" and "inactive" core development members and does this have any bearing on their right to vote?
Is there any scope to specifically invite certain informed (non-core dev) parties to vote on issues? I would probably consider this an abuse of power and instead invite to participate in the discussion to influence members.
If votes are cast by core dev members does this have implications for inviting future members into the core dev team? i.e to not push for adding members of a group of similar, or friendly like minded individuals, perhaps from the same institution etc, that can build up substantial iunfluence?
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.
There's a bit of a chicken and egg issue here. We are planning on updating other governance documents to define who can vote. Right now, it is the core team, but it is likely we will not use that in the future.
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.
IMO we should also require a discussion to change this, hence my comment to define voting member in this PDEP now.