Closed Ainali closed 1 year ago
Perhaps we could draw some inspiration from the CII Best Practices Badge:
https://bestpractices.coreinfrastructure.org/en/projects/1/0
Since this is still in an early stage, perhaps we should bring it up on next week's community call to be able to talk about it in depth without many preconceptions?
Here is the summary of the community call: https://blog.publiccode.net/community%20call/2021/02/11/notes-from-community-call-4-february-2021.html
A number of new issues should be created from this (like: build infrastructure, document process on About, promote certification) process before this issue is closed.
I think this can be closed thanks to the new standard-compliant repository.
It might not be too long before we have a codebase that is compliant with the requirements of the Standard. And the Standard talk about certification quite a lot in the Introduction. But what it does not explain is how this will be done in practice. Will we issue a paper diploma, do we make a pull request with text in the README file of the codebase or do we issue digital badges? And will have we have different levels for full compliance vs those that don't have all the MAYs or even some of the SHOULDs?