Rule 2: Make governance explicit.
Under governance - perhaps licence needs mentioning as well: examine and publish the licensing model to ensure that it is clear how people can contribute.
Rule 3: Make it clear that newcomers are welcome.
This is a personal experience from the SSI - about the extra steps that need to be taken for newcomers. We have a "welcome pack” for them detailing what infrastructure is in use, when and what for - e.g. website, communication (Twitter, Slack, mailing lists, Mailchimp, Zoom, Skype), software projects and general issue tracking (GitHub), file storage (DropBox, GitHub, Google Drive), various calendars, etc. and what accounts they need to set up and who is responsible for granting access. Then there are guidelines for using each of these pieces of infrastructure, e.g. what communication channels are used in which situations, website contribution guidelines, etc. You also cover some of these in your Rule 6: Make knowledge findable, but this is more about the initial set up.
Rule 6: Make knowledge findable
Perhaps this rule should be: "Make knowledge findable and up to date". And then somewhere in this section mention reviewing your documentation regularly and making sure that it is clear and up to date.
Rule 8: Provide an easy, complete, and up-to-date guide to contributing.
Maybe something about remembering to give credit for contributions, no matter how small (although you mention thanking people for contributions in Rule 10 - this rule may actually fit better actually under Rule 8.)
Rule 10: Follow up on success.
This rule feels nice to end with but also somehow feel thin. You mention mentoring under directing newcomers to project members with similar background and skillset but somehow I feel mentoring may need a bigger mention as this seems to be an important part of a successful and empowering community of practice - that and encouraging people to think about their self-growth and personal development as both a reason for and an outcome of continuing contribution. So maybe this could go in rule 10.
Rule 2: Make governance explicit. Under governance - perhaps licence needs mentioning as well: examine and publish the licensing model to ensure that it is clear how people can contribute.
Rule 3: Make it clear that newcomers are welcome. This is a personal experience from the SSI - about the extra steps that need to be taken for newcomers. We have a "welcome pack” for them detailing what infrastructure is in use, when and what for - e.g. website, communication (Twitter, Slack, mailing lists, Mailchimp, Zoom, Skype), software projects and general issue tracking (GitHub), file storage (DropBox, GitHub, Google Drive), various calendars, etc. and what accounts they need to set up and who is responsible for granting access. Then there are guidelines for using each of these pieces of infrastructure, e.g. what communication channels are used in which situations, website contribution guidelines, etc. You also cover some of these in your Rule 6: Make knowledge findable, but this is more about the initial set up.
Rule 6: Make knowledge findable Perhaps this rule should be: "Make knowledge findable and up to date". And then somewhere in this section mention reviewing your documentation regularly and making sure that it is clear and up to date.
Rule 8: Provide an easy, complete, and up-to-date guide to contributing. Maybe something about remembering to give credit for contributions, no matter how small (although you mention thanking people for contributions in Rule 10 - this rule may actually fit better actually under Rule 8.)
Rule 10: Follow up on success. This rule feels nice to end with but also somehow feel thin. You mention mentoring under directing newcomers to project members with similar background and skillset but somehow I feel mentoring may need a bigger mention as this seems to be an important part of a successful and empowering community of practice - that and encouraging people to think about their self-growth and personal development as both a reason for and an outcome of continuing contribution. So maybe this could go in rule 10.