aiidateam / aep Goto Github PK

We've started out with the status codes used also by the jupyter project:

• submitted - this should be the initial status when submitting the pull request to the AEP repository
• active - this AEP has been accepted and people are actively discussing and implementing it
• implemented - this AEP has been implemented
• postponed - this AEP is no longer active, might be interesting for the project but has noone willing to champion it
• rejected - this AEP has been rejected and will not be implemented
• withdrawn - this AEP has been withdrawn by the submitter but can be re-submitted if someone is willing to champion

In the context of discussions concerning PRs #11 and #21 a question arose about the right time to merge a PR:
Does it make sense to merge a PR once people have agreed to move forward in this direction or should a PR be merged only once all implementation details have been figured out (which, effectively, is after its implementation in aiida-core)?

The general feeling seemed to be that it would be useful to merge PRs in a draft stage as an intermediate form of saying "we agree that we want this to happen".
As it turns out, this also came up in the jupyter project jupyter/governance#13 (but has so far gone stale).

Alternatives for inspiration:

• ECMAScript (JavaScript): https://tc39.es/process-document/
• zeromq: jupyter/enhancement-proposals#11 (comment)