search

simoncozens / fontspector

Skrifa/Read-Fonts-based sketch for a font QA tool
Apache License 2.0
7 stars 1 forks source link

Rationale and proposal fields are not optional #5

Closed felipesanches closed 3 months ago

simoncozens commented 4 months ago

I love this for rationale (and I love how the type system can enforce this for us), but private profile checks might not have public proposal URLs...

felipesanches commented 4 months ago

but private profile checks might not have public proposal URLs...

I believe that mandatory rationale and proposal fields are part of the project's culture. If there's going to be any burden, it should be on those who do not yet follow that policy of documenting the font problems.

They should at least have private URLs (or other kinds of identifiers, perhaps to a private issue tracker, or any other tool used to track proposals).

In the worse case, it could state proposal="private" or proposal="unknown" and that would be a recurring reminder that they should be documenting these things, even when working in a private profile.