Simon Cozens

Description/article. It's a GF-only thing so it only affects our process, and it's not as sprawling as metadata.pb.

Just to keep track of a few checks I have been merging as I look at porting them: * `DSIG` is now just an unwanted table, `com.google.fonts/check/dsig` moves into `com.google.fonts/check/unwanted_tables`...

Okay, so let's combine a number of thoughts we've been having recently: * Badges for quality assurance * Checks should have "severity" as well as PASS/FAIL/WARN * Some checks can't...

"Achievements" would be nice, but there's already a kind of de-facto standard for build/QA badges: 

  https://shields.io/#dynamic-badge

Just have one per section. This is what sections are for. :-)

Returning to this after a discussion yesterday: @Lorp suggested that Fontbakery could be used for project management. The idea would be that a JSON file in the font repo could...

Well, maybe this doesn't need to be part of `FontBuilder` - so long as `write_fonts` provides the functionality somewhere. There's a lot of fontTools code out there which needs porting....

Yep, I'd come to that conclusion. I'll come up with an interface inside of Fontspector that does what I need, and we'll see if it makes sense to upstream.

There are two bugs here; one is that tate changed the document language, which the PR above fixes. This makes it harder to see the other bug, which I need...