diff --git a/criteria/welcome-contributors.md b/criteria/welcome-contributors.md
index 0feb8b3..262b519 100644
--- a/criteria/welcome-contributors.md
+++ b/criteria/welcome-contributors.md
@@ -51,6 +51,7 @@ redirect_from:
 * [Best Practices for the Governance of Digital Public Goods](https://ash.harvard.edu/publications/best-practices-governance-digital-public-goods) by the Ash Center for Democratic Governance and Innovation contains a playbook of different pracitces to implement in the governance along with case studies.
 * [Organization & Structure of Open Source Software Development Initiatives](https://web.archive.org/web/20220526100844/https://clinic.cyber.harvard.edu/files/2017/03/2017-03_governance-FINAL.pdf) by Cyberlaw Clinic has a good overview of different governance models.
 * [Governance of open source software: state of the art](https://link.springer.com/article/10.1007/s10997-007-9022-9) is an academic article on governance and might be useful for someone that needs solid arguments for their decisions.
+* [IEEE Open Source Maintainers Manual](https://opensource.ieee.org/community/manual/) by the Institute of Electrical and Electronics Engineers can provide some inspiration as it provides the policies, guidelines, advice, and requirements for project leads, maintainers, contributors and other participants involved in IEEE Open Source projects.
 
 ### The contribution guidelines SHOULD document who is expected to cover the costs of reviewing contributions.