The core sub projects, liboqs and oqs-provider had well-defined roles, responsibilities and expectations as documented in their respective GOVERNANCE.md files.
As part of their take-over, the LF/PQCA team has chosen to disregard and invalidate those files and rules: Maintainers for example don't have administrative GH rights any more, leading to all kinds of new discussions and complications, e.g., when doing releases.
Thereby (?) and at least in my mind there does not seem to exist a well-defined understanding as to which responsibilities and obligations PQCA assigns to contributors and maintainers and how these map to GH rights.
This issue is to propose a discussion as to what tasks, responsibilities and rights are to be assigned to contributors and maintainers. This should serve to let any present and future contributors and maintainers see what are the project's expectations towards them and also inform the (automated) setting of GH rights. If no discussion is wanted, this issue is to request the LF/PQCA team to post a documentation as to what they want maintainers and contributors do so present contributors and maintainers can adjust their expectations or contribution level accordingly.
For example, are maintainers in the PQCA sense
- still expected to know the code of a specific project inside-out (i.e., be active contributors) or not, i.e., have more of a "management" function?
- expected to do releases or should that be done by different people?
- expected to review & fix security vulnerabilities or is that to be delegated to people specializing in such task but not necessarily knowing the code?
- expected to review PRs and discussion entries or is that to be delegated to yet other team(s)?
- still to be attributed with the GH "maintainer" label (AFAIK externally understood as carried by people who know the code) or does that need to be reconsidered (IMO on a per-sub project basis)?
As usual, any input, e.g., pointers to existing documentation on these roles very welcome.
The core sub projects,
liboqsandoqs-providerhad well-defined roles, responsibilities and expectations as documented in their respective GOVERNANCE.md files.As part of their take-over, the LF/PQCA team has chosen to disregard and invalidate those files and rules: Maintainers for example don't have administrative GH rights any more, leading to all kinds of new discussions and complications, e.g., when doing releases.
Thereby (?) and at least in my mind there does not seem to exist a well-defined understanding as to which responsibilities and obligations PQCA assigns to contributors and maintainers and how these map to GH rights.
This issue is to propose a discussion as to what tasks, responsibilities and rights are to be assigned to contributors and maintainers. This should serve to let any present and future contributors and maintainers see what are the project's expectations towards them and also inform the (automated) setting of GH rights. If no discussion is wanted, this issue is to request the LF/PQCA team to post a documentation as to what they want maintainers and contributors do so present contributors and maintainers can adjust their expectations or contribution level accordingly.
For example, are maintainers in the PQCA sense
As usual, any input, e.g., pointers to existing documentation on these roles very welcome.