Replies: 2 comments 3 replies
-
@Ainali I think that's a great idea. Do you have in mind something structured for the verification URL or are you thinking of a normal web page? |
Beta Was this translation helpful? Give feedback.
3 replies
-
@Ainali please open a PR on this, so we can put it to votes :-) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I would like to suggest a field to indicate compliance with Standard for Public Code. This would make it easy to discover this at a glance, and even make filtering in catalogs possible.
I would propose to not only make it a true or false, but that it also should show if a commitment to meet the requirements in the future has been made. This sends an important signal of the intention and trajectory of the codebase.
Accompanying this, a verification URL field would be handy, to either see the compliance or the documented public commitment. This would be mandatory unless, the compliance field is set to false.
Beta Was this translation helpful? Give feedback.
All reactions