Feedback on the blueprints suggests our target audience is not well identified, and our blueprints may have a claim to universality which would make them 'compete' with similar guidelines from other initiatives. We should clarify that:
[x] the blueprints are meant for internal purposes and are targeted at epiverse-trace projects and teams, even if we are happy with them being shared and reused elsewhere (https://github.com/epiverse-trace/blueprints/pull/22)
[x] better distinguish the definition of 'developers' and 'users'; mention that these are fluid and may evolve in the lifetime of a project
[ ] refer to documentation in the 'Decentralizing code...' section
[ ] PRs: promote polite and constructive discourse, as well as acknowledgement that all conversations (issues, discussions, PRs, etc.) are open and will reflect on the project at large
Target audience
Feedback on the blueprints suggests our target audience is not well identified, and our blueprints may have a claim to universality which would make them 'compete' with similar guidelines from other initiatives. We should clarify that:
Other points