You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 goal is not to solve these here, but capture them as topics for future discussion once we have experience with the process.
The text was updated successfully, but these errors were encountered: