Skip to content
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

PHEP process items to monitor #27

Open
jtniehof opened this issue Mar 15, 2024 · 0 comments
Open

PHEP process items to monitor #27

jtniehof opened this issue Mar 15, 2024 · 0 comments

Comments

@jtniehof
Copy link
Contributor

In the spirit of "kill your darlings", I'm opening this issue to track concerns brought up in the PHEP-1 discussions (#22). The text was not modified because these are concerns where there was no clear good solution, and/or "watch and see how it goes" seemed a better approach. The "things to watch":

  • The consensus requirement opens itself to the possibility of a bad actor problem where one determined individual could block process (short-term answer: consider this a code of conduct issue).
  • The process seems heavy and could inhibit innovation.
  • The chosen balance between immutability and flexibility is pretty close to immutability and may not work out.
  • PyHC leadership is loosely defined.
  • Applicability (i.e. what holds packages to standards) is not defined.
  • The annual review / checkup process is required in PHEP-1 but not defined, and it's not clear how it will work in practice.

The goal is not to solve these here, but capture them as topics for future discussion once we have experience with the process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant