Some thoughts after using the tool recently.

[m4rc1e]

I've been using the tool heavily for the past week and believe the following will improve the UX significantly

• Reports are currently just walls of text. Every check needs to be revisited and made as concise as possible. Using tables to present information where possible can help greatly. If users want more information, they should be able to click a link to bring up something more verbose from our guide.

• Should be easier to install for non-devs. Homebrew's installation is easy. Couldn't we have something which execs a curlable shell script? (this may be a terrible idea). A GUI would be ideal but this will be too much work so a bullet proof shell scipt + a youtube vid is sufficient,

• Consolidate and refactor checks e.g the metadata.pb checks could be consolidated into a single check which is simple, does the current metadata.pb file match a freshly generated file? I'm sure there are countless other checks that don't need to exist.

I'll make up examples tomorrow of how these reports should look imo.

[m4rc1e]

Here's an unedited report for Maven Pro.

(venv) Marcs-Air-2:fontbakery marcfoley$ fontbakery check-googlefonts ~/Type/fonts/ofl/mavenpro/MavenPro\[wght\].ttf
Start ... running 246 individual check executions.
 >> com.google.fonts/check/STAT/axis_order
    Check axis ordering on the STAT table.
    

      Rationale:                                                                
                                                                                
      This is (for now) a merely informative check to detect what's the axis    
      ordering declared on the STAT table of fonts in the Google Fonts          
      collection.                                                               
                                                                                
      We may later update this to enforce some unified axis ordering scheme,    
      yet to be determined.                                                     
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/3049


     INFO From a total of 1 font files, 0 of them (0.00%) lack                  
          a STAT table.                                                         
                                                                                
                                                                                
           And these are the most common STAT axis orderings:                   
           ('wght', 1)                                                          
                                                                                
                                                                                
          [code: summary]                                                       


    Result: INFO

 >> com.google.fonts/check/description/git_url
    Does DESCRIPTION file contain a upstream Git repo URL?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      The contents of the DESCRIPTION.en-us.html file are displayed on the      
      Google Fonts website in the about section of each font family specimen    
      page.                                                                     
                                                                                
      Since all of the Google Fonts collection is composed of libre-licensed    
      fonts, this check enforces a policy that there must be a hypertext link   
      in that page directing users to the repository where the font project     
      files are made available.                                                 
                                                                                
      Such hosting is typically done on sites like Github, Gitlab, GNU Savannah 
      or any other git-based version control service.                           
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/2523


     INFO Found a git repo URL:                                                 
          https://github.com/googlefonts/mavenproFont [code: url-found]         


    Result: INFO

 >> com.google.fonts/check/metadata/broken_links
    Does METADATA.pb copyright field contain broken links?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

    More info: https://github.com/googlefonts/fontbakery/issues/2550
               https://github.com/googlefonts/fontbakery/issues/4110

     FAIL The following links are broken in the METADATA.pb                     
          file: http://www.vissol.co.uk/mavenpro/ (status code: 404) [code:     
          broken-links]                                                         


    Result: FAIL

 >> com.google.fonts/check/vendor_id
    Checking OS/2 achVendID.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      Microsoft keeps a list of font vendors and their respective contact info. 
      This list is updated regularly and is indexed by a 4-char "Vendor ID"     
      which is stored in the achVendID field of the OS/2 table.                 
                                                                                
      Registering your ID is not mandatory, but it is a good practice since     
      some applications may display the type designer / type foundry contact    
      info on some dialog and also because that info will be visible on         
      Microsoft's website:                                                      
                                                                                
      https://docs.microsoft.com/en-us/typography/vendors/                      
                                                                                
      This check verifies whether or not a given font's vendor ID is registered 
      in that list or if it has some of the default values used by the most     
      common font editors.                                                      
                                                                                
      Each new FontBakery release includes a cached copy of that list of vendor 
      IDs. If you registered recently, you're safe to ignore warnings emitted   
      by this check, since your ID will soon be included in one of our upcoming 
      releases.                                                                 
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/3943


     WARN OS/2 VendorID value 'NONE' is not yet recognized. If                  
          you registered it recently, then it's safe to ignore this warning     
          message. Otherwise, you should set it to your own unique 4 character  
          code, and register it with Microsoft at                               
          https://www.microsoft.com/typography/links/vendorlist.aspx            
                                                                                
          [code: unknown]                                                       


    Result: WARN


 >> com.google.fonts/check/glyph_coverage
    Check Google Fonts glyph coverage.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      Google Fonts expects that fonts in its collection support at least the    
      minimal set of characters defined in the `GF-latin-core` glyph-set.       
                                                                                
    More info: https://github.com/googlefonts/fontbakery/pull/2488


     FAIL Missing required codepoints:                                          
                                                                                
                                                                                
           - 0x021A (LATIN CAPITAL LETTER T WITH COMMA BELOW)                   
                                                                                
           - 0x0312 (COMBINING TURNED COMMA ABOVE)                              
                                                                                
                                                                                
          [code: missing-codepoints]                                            


    Result: FAIL

 >> com.google.fonts/check/metadata/unreachable_subsetting
    Check for codepoints not covered by METADATA subsets.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      This check ensures that all encoded glyphs in the font are covered by a   
      subset declared in the METADATA.pb. Google Fonts splits the font into a   
      set of subset fonts based on the contents of the `subsets` field and the  
      subset definitions in the `glyphsets` repository.                         
                                                                                
      Any encoded glyphs which are not by any of these subset definitions will  
      not be served in the subsetted fonts, and so will be unreachable to the   
      end user.                                                                 
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/4097


     WARN The following codepoints supported by the font are                    
          not covered by any subsets defined in the font's metadata file, and   
          will never be served. You can solve this by either manually adding    
          additional subset declarations to METADATA.pb, or by editing the      
          glyphset definitions.                                                 
                                                                                
           • U+02C7 CARON: try adding one of: canadian-aboriginal, tifinagh     
           • U+02D8 BREVE: try adding canadian-aboriginal                       
           • U+02D9 DOT ABOVE: try adding canadian-aboriginal                   
           • U+02DB OGONEK: try adding canadian-aboriginal                      
           • U+0300 COMBINING GRAVE ACCENT: try adding one of: cherokee, coptic,
             old-permic, tai-le                                                 
           • U+0301 COMBINING ACUTE ACCENT: try adding one of: tifinagh, tai-le,
             coptic, cherokee, osage                                            
           • U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: cherokee,   
             math, coptic, tifinagh                                             
           • U+0303 COMBINING TILDE: try adding one of: syriac, math, glagolitic
           • U+0304 COMBINING MACRON: try adding one of: syriac, tifinagh,      
             caucasian-albanian, gothic, coptic, cherokee, osage                
           • U+0306 COMBINING BREVE: try adding one of: tifinagh, old-permic 28 
             more.                                                              
                                                                                
          Use -F or --full-lists to disable shortening of long lists.           
                                                                                
          Or you can add the above codepoints to one of the subsets supported by
          the font: latin, latin-ext, menu, vietnamese [code:                   
          unreachable-subsetting]                                               


    Result: WARN

 >> com.google.fonts/check/name/license
    Check copyright namerecords match license file.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      A known licensing description must be provided in the NameID 14 (LICENSE  
      DESCRIPTION) entries of the name table.                                   
                                                                                
      The source of truth for this check (to determine which license is in use) 
      is a file placed side-by-side to your font project including the          
      licensing terms.                                                          
                                                                                
      Depending on the chosen license, one of the following string snippets is  
      expected to be found on the NameID 13 (LICENSE DESCRIPTION) entries of    
      the name table:                                                           
                                                                                
      - "This Font Software is licensed under the SIL Open Font License,        
      Version 1.1. This license is available with a FAQ at:                     
      https://scripts.sil.org/OFL"                                              
                                                                                
      - "Licensed under the Apache License, Version 2.0"                        
                                                                                
      - "Licensed under the Ubuntu Font Licence 1.0."                           
                                                                                
      Currently accepted licenses are Apache or Open Font License. For a small  
      set of legacy families the Ubuntu Font License may be acceptable as well. 
                                                                                
      When in doubt, please choose OFL for new font projects.                   
                                                                                

     WARN Please consider using HTTPS URLs at name table entry                  
          [plat=3, enc=1, name=13] [code: http-in-description]                  

     WARN For now we're still accepting http URLs, but you                      
          should consider using https instead.                                  
                                                                                
          [code: http]                                                          


    Result: WARN

 >> com.google.fonts/check/name/license_url
    License URL matches License text on name table?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      A known license URL must be provided in the NameID 14 (LICENSE INFO URL)  
      entry of the name table.                                                  
                                                                                
      The source of truth for this check is the licensing text found on the     
      NameID 13 entry (LICENSE DESCRIPTION).                                    
                                                                                
      The string snippets used for detecting licensing terms are:               
                                                                                
      - "This Font Software is licensed under the SIL Open Font License,        
      Version 1.1. This license is available with a FAQ at:                     
      https://scripts.sil.org/OFL"                                              
                                                                                
      - "Licensed under the Apache License, Version 2.0"                        
                                                                                
      - "Licensed under the Ubuntu Font Licence 1.0."                           
                                                                                
      Currently accepted licenses are Apache or Open Font License. For a small  
      set of legacy families the Ubuntu Font License may be acceptable as well. 
                                                                                
      When in doubt, please choose OFL for new font projects.                   
                                                                                

     WARN Please consider using HTTPS URLs at name table entry                  
          [plat=3, enc=1, name=13] [code: http-in-description]                  

     WARN Please consider using HTTPS URLs at name table entry                  
          [plat=3, enc=1, name=13] [code: http-in-description]                  

     WARN Please consider using HTTPS URLs at name table entry                  
          [plat=3, enc=1, name=13] [code: http-in-description]                  

     WARN Please consider using HTTPS URLs at name table entry                  
          [plat=3, enc=1, name=14] [code: http-in-license-info]                 

     WARN For now we're still accepting http URLs, but you                      
          should consider using https instead.                                  
                                                                                
          [code: http]                                                          


    Result: WARN

 >> com.google.fonts/check/hinting_impact
    Show hinting filesize impact.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      This check is merely informative, displaying and useful comparison of     
      filesizes of hinted versus unhinted font files.                           
                                                                                

     INFO Hinting filesize impact:                                              
                                                                                
                           /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro.t… 
           Dehinted Size                                                 88.6kb 
           Hinted Size                                                   88.6kb 
           Increase                                                    24 bytes 
           Change                                                         0.0 % 
                                                                                
          [code: size-impact]                                                   


    Result: INFO

 >> com.google.fonts/check/old_ttfautohint
    Font has old ttfautohint applied?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      Check if font has been hinted with an outdated version of ttfautohint.    
                                                                                

     INFO Could not detect which version of ttfautohint was                     
          used in this font. It is typically specified as a comment in the font 
          version entries of the 'name' table. Such font version strings are    
          currently: ['Version 2.102'] [code: version-not-detected]             


    Result: INFO

 >> com.google.fonts/check/epar
    EPAR table present in font?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      The EPAR table is/was a way of expressing common licensing permissions    
      and restrictions in metadata; while almost nothing supported it, Dave     
      Crossland wonders that adding it to everything in Google Fonts could help 
      make it more popular.                                                     
                                                                                
      More info is available at: https://davelab6.github.io/epar/               
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/226


     INFO EPAR table not present in font. To learn more see                     
          https://github.com/googlefonts/fontbakery/issues/818 [code:           
          lacks-EPAR]                                                           


    Result: INFO

 >> com.google.fonts/check/gasp
    Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      Traditionally version 0 'gasp' tables were set so that font sizes below 8 
      ppem had no grid fitting but did have antialiasing. From 9-16 ppem, just  
      grid fitting. And fonts above 17ppem had both antialiasing and grid       
      fitting toggled on. The use of accelerated graphics cards and higher      
      resolution screens make this approach obsolete. Microsoft's DirectWrite   
      pushed this even further with much improved rendering built into the OS   
      and apps.                                                                 
                                                                                
      In this scenario it makes sense to simply toggle all 4 flags ON for all   
      font sizes.                                                               
                                                                                

     INFO These are the ppm ranges declared on the gasp table:                  
                                                                                
          PPM <= 65535: flag = 0x0F - Use grid-fitting - Use grayscale rendering
          - Use gridfitting with ClearType symmetric smoothing - Use smoothing  
          along multiple axes with ClearType®                                   
                                                                                
          [code: ranges]                                                        


    Result: INFO

 >> com.google.fonts/check/metadata/reserved_font_name
    Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf


     WARN METADATA.pb: copyright field ("Copyright 2011 The                     
          Maven Pro Project Authors (http://www.vissol.co.uk/mavenpro/), with   
          Reserved Font Name "Maven Pro".") contains "Reserved Font Name". This 
          is an error except in a few specific rare cases. [code: rfn]          


    Result: WARN

 >> com.google.fonts/check/metadata/consistent_repo_urls
    METADATA.pb: Check URL on copyright string is the same as in repository_url field.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      Sometimes, perhaps due to copy-pasting, projects may declare different    
      URLs between the font.coyright and the family.sources.repository_url      
      fields.                                                                   
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/4056


     FAIL Value of repository_url field is                                      
                                                                                
          But font copyright string has: http://www.vissol.co.uk/mavenpro/      
                                                                                
          [code: mismatch]                                                      


    Result: FAIL

 >> com.google.fonts/check/fontdata_namecheck
    Familyname must be unique according to namecheck.fontdata.com
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      We need to check names are not already used, and today the best place to  
      check that is http://namecheck.fontdata.com                               
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/494


     INFO The family name "MavenPro" seems to be already in                     
          use. Please visit http://namecheck.fontdata.com for more info. [code: 
          name-collision]                                                       


    Result: INFO

 >> com.google.fonts/check/fontv
    Check for font-v versioning.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      The git sha1 tagging and dev/release features of Source Foundry `font-v`  
      tool are awesome and we would love to consider upstreaming the approach   
      into fontmake someday. For now we only emit a WARN if a given font does   
      not yet follow the experimental versioning style, but at some point we    
      may start enforcing it.                                                   
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/1563


     INFO Version string is: "Version 2.102" The version string                 
          must ideally include a git commit hash and either a "dev" or a        
          "release" suffix such as in the example below: "Version 1.3;          
          git-0d08353-release" [code: bad-format]                               


    Result: INFO

 >> com.google.fonts/check/ligature_carets
    Are there caret positions declared for every ligature?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      All ligatures in a font must have corresponding caret (text cursor)       
      positions defined in the GDEF table, otherwhise, users may experience     
      issues with caret rendering.                                              
                                                                                
      If using GlyphsApp or UFOs, ligature carets can be defined as anchors     
      with names starting with 'caret_'. These can be compiled with fontmake as 
      of version v2.4.0.                                                        
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/1225


     WARN This font lacks caret position values for ligature                    
          glyphs on its GDEF table. [code: lacks-caret-pos]                     


    Result: WARN

 >> com.google.fonts/check/kerning_for_non_ligated_sequences
    Is there kerning info for non-ligated sequences?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      Fonts with ligatures should have kerning on the corresponding non-ligated 
      sequences for text where ligatures aren't used (eg                        
      https://github.com/impallari/Raleway/issues/14).                          
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/1145


     WARN GPOS table lacks kerning info for the following                       
          non-ligated sequences:                                                
                                                                                
                                                                                
           - f + i                                                              
                                                                                
           - i + l                                                              
                                                                                
                                                                                
          [code: lacks-kern-info]                                               


    Result: WARN

 >> com.google.fonts/check/name/rfn
    Name table strings must not contain the string 'Reserved Font Name'.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      Some designers adopt the "Reserved Font Name" clause of the OFL license.  
      This means that the original author reserves the rights to the family     
      name and other people can only distribute modified versions using a       
      different family name.                                                    
                                                                                
      Google Fonts published updates to the fonts in the collection in order to 
      fix issues and/or implement further improvements to the fonts. It is      
      important to keep the family name so that users of the webfonts can       
      benefit from the updates. Since it would forbid such usage scenario, all  
      families in the GFonts collection are required to not adopt the RFN       
      clause.                                                                   
                                                                                
      This check ensures "Reserved Font Name" is not mentioned in the name      
      table.                                                                    
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/1380


     WARN Name table entry contains "Reserved Font Name" for a                  
          family name ("Maven Pro") that differs from the currently used family 
          name (MavenPro), which is fine. [code: legacy-familyname]             


    Result: WARN

 >> com.google.fonts/check/repo/vf_has_static_fonts
    A static fonts directory with at least two fonts must accompany variable fonts
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      Variable font family directories kept in the google/fonts git repo may    
      include a static/ subdir containing static fonts.                         
                                                                                
      These files are meant to be served for users that still lack support for  
      variable fonts in their web browsers.                                     
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/2654


     WARN Please consider adding a subdirectory called                          
          "static/" and including in it static font files. [code: missing]      


    Result: WARN

 >> com.google.fonts/check/metadata/escaped_strings
    Ensure METADATA.pb does not use escaped strings.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      In some cases we've seen designer names and other fields with escaped     
      strings in METADATA files. Nowadays the strings can be full unicode       
      strings and do not need escaping.                                         
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/2932


     FAIL Found escaped chars at 'Copyright 2011 The Maven Pro                  
          Project Authors (http://www.vissol.co.uk/mavenpro/), with Reserved    
          Font Name '. Please use an unicode string instead. [code:             
          escaped-strings]                                                      


    Result: FAIL

 >> com.google.fonts/check/meta/script_lang_tags
    Ensure fonts have ScriptLangTags declared on the 'meta' table.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      The OpenType 'meta' table originated at Apple. Microsoft added it to OT   
      with just two DataMap records:                                            
                                                                                
      - dlng: comma-separated ScriptLangTags that indicate which scripts, or    
      languages and scripts, with possible variants, the font is designed for.  
                                                                                
      - slng: comma-separated ScriptLangTags that indicate which scripts, or    
      languages and scripts, with possible variants, the font supports.         
                                                                                
      The slng structure is intended to describe which languages and scripts    
      the font overall supports. For example, a Traditional Chinese font that   
      also contains Latin characters, can indicate Hant,Latn, showing that it   
      supports Hant, the Traditional Chinese variant of the Hani script, and it 
      also supports the Latn script.                                            
                                                                                
      The dlng structure is far more interesting. A font may contain various    
      glyphs, but only a particular subset of the glyphs may be truly "leading" 
      in the design, while other glyphs may have been included for technical    
      reasons. Such a Traditional Chinese font could only list Hant there,      
      showing that it’s designed for Traditional Chinese, but the font would    
      omit Latn, because the developers don’t think the font is really          
      recommended for purely Latin-script use.                                  
                                                                                
      The tags used in the structures can comprise just script, or also         
      language and script. For example, if a font has Bulgarian Cyrillic        
      alternates in the locl feature for the cyrl BGR OT languagesystem, it     
      could also indicate in dlng explicitly that it supports bul-Cyrl. (Note   
      that the scripts and languages in meta use the ISO language and script    
      codes, not the OpenType ones).                                            
                                                                                
      This check ensures that the font has the meta table containing the slng   
      and dlng structures.                                                      
                                                                                
      All families in the Google Fonts collection should contain the 'meta'     
      table. Windows 10 already uses it when deciding on which fonts to fall    
      back to. The Google Fonts API and also other environments could use the   
      data for smarter filtering. Most importantly, those entries should be     
      added to the Noto fonts.                                                  
                                                                                
      In the font making process, some environments store this data in external 
      files already. But the meta table provides a convenient way to store this 
      inside the font file, so some tools may add the data, and unrelated tools 
      may read this data. This makes the solution much more portable and        
      universal.                                                                
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/3349


     WARN This font file does not have a 'meta' table. [code:                   
          lacks-meta-table]                                                     


    Result: WARN

 >> com.google.fonts/check/fontbakery_version
    Do we have the latest version of FontBakery installed?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      Running old versions of FontBakery can lead to a poor report which may    
      include false WARNs and FAILs due do bugs, as well as outdated quality    
      assurance criteria.                                                       
                                                                                
      Older versions will also not report problems that are detected by new     
      checks added to the tool in more recent updates.                          
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/2093


     FAIL Current FontBakery version is                                         
          0.8.11a4.dev198+gedc351c0.d20230726, while a newer 0.8.13 is already  
          available. Please upgrade it with 'pip install -U fontbakery' [code:  
          outdated-fontbakery]                                                  


    Result: FAIL

 >> com.google.fonts/check/mandatory_glyphs
    Font contains '.notdef' as its first glyph?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      The OpenType specification v1.8.2 recommends that the first glyph is the  
      '.notdef' glyph without a codepoint assigned and with a drawing.          
                                                                                
      https://docs.microsoft.com/en-us/typography/opentype/spec                 
      /recom#glyph-0-the-notdef-glyph                                           
                                                                                
      Pre-v1.8, it was recommended that fonts should also contain 'space', 'CR' 
      and '.null' glyphs. This might have been relevant for MacOS 9             
      applications.                                                             
                                                                                

     WARN The '.notdef' glyph should contain a drawing, but it                  
          is blank. [code: notdef-is-blank]                                     


    Result: WARN

 >> com.google.fonts/check/required_tables
    Font contains all required tables?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      According to the OpenType spec                                            
      https://docs.microsoft.com/en-us/typography/opentype/spec                 
      /otff#required-tables                                                     
                                                                                
      Whether TrueType or CFF outlines are used in an OpenType font, the        
      following tables are required for the font to function correctly:         
                                                                                
      - cmap (Character to glyph mapping)                                       
      - head (Font header)                                                      
      - hhea (Horizontal header)                                                
      - hmtx (Horizontal metrics)                                               
      - maxp (Maximum profile)                                                  
      - name (Naming table)                                                     
      - OS/2 (OS/2 and Windows specific metrics)                                
      - post (PostScript information)                                           
                                                                                
      The spec also documents that variable fonts require the following table:  
                                                                                
      - STAT (Style attributes)                                                 
                                                                                
      Depending on the typeface and coverage of a font, certain tables are      
      recommended for optimum quality.                                          
                                                                                
      For example:                                                              
      - the performance of a non-linear font is improved if the VDMX, LTSH, and 
      hdmx tables are present.                                                  
      - Non-monospaced Latin fonts should have a kern table.                    
      - A gasp table is necessary if a designer wants to influence the sizes at 
      which grayscaling is used under Windows. Etc.                             
                                                                                

     INFO This font contains the following optional tables:                     
                                                                                
                                                                                
           - loca                                                               
                                                                                
           - prep                                                               
                                                                                
           - GPOS                                                               
                                                                                
           - GSUB                                                               
                                                                                
           - gasp                                                               
                                                                                
                                                                                
          [code: optional-tables]                                               


    Result: INFO

 >> com.google.fonts/check/superfamily/list
    List all superfamily filepaths
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      This is a merely informative check that lists all sibling families        
      detected by fontbakery.                                                   
                                                                                
      Only the fontfiles in these directories will be considered in             
      superfamily-level checks.                                                 
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/1487


     INFO /Users/marcfoley/Type/fonts/ofl/mavenpro [code:                       
          family-path]                                                          


    Result: INFO

 >> com.google.fonts/check/unreachable_glyphs
    Check font contains no unreachable glyphs
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      Glyphs are either accessible directly through Unicode codepoints or       
      through substitution rules.                                               
                                                                                
      In Color Fonts, glyphs are also referenced by the COLR table.             
                                                                                
      Any glyphs not accessible by either of these means are redundant and      
      serve only to increase the font's file size.                              
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/3160


     WARN The following glyphs could not be reached by                          
          codepoint or substitution rules:                                      
                                                                                
                                                                                
           - IJacute                                                            
                                                                                
           - caronalt                                                           
                                                                                
           - dotbelowcomb.case                                                  
                                                                                
           - hookabovecomb.case                                                 
                                                                                
           - ijacute                                                            
                                                                                
           - uni03020309                                                        
                                                                                
           - uni03060309                                                        
                                                                                
           - uni031B.case                                                       
                                                                                
           - uni0326.alt                                                        
                                                                                
                                                                                
          [code: unreachable-glyphs]                                            


    Result: WARN

 >> com.google.fonts/check/soft_hyphen
    Does the font contain a soft hyphen?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      The 'Soft Hyphen' character (codepoint 0x00AD) is used to mark a          
      hyphenation possibility within a word in the absence of or overriding     
      dictionary hyphenation.                                                   
                                                                                
      It is sometimes designed empty with no width (such as a control           
      character), sometimes the same as the traditional hyphen, sometimes       
      double encoded with the hyphen.                                           
                                                                                
      That being said, it is recommended to not include it in the font at all,  
      because discretionary hyphenation should be handled at the level of the   
      shaping engine, not the font. Also, even if present, the software would   
      not display that character.                                               
                                                                                
      More discussion at:                                                       
      https://typedrawers.com/discussion/2046                                   
      /special-dash-things-softhyphen-horizontalbar                             
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/4046
               https://github.com/googlefonts/fontbakery/issues/3486

     WARN This font has a 'Soft Hyphen' character. [code:                       
          softhyphen]                                                           


    Result: WARN

 >> com.adobe.fonts/check/freetype_rasterizer
    Ensure that the font can be rasterized by FreeType.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      Malformed fonts can cause FreeType to crash.                              
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/3642


    ERROR Failed with ModuleNotFoundError: No module named                      
          'freetype'                                                            
          ↳ File                                                                
          "/Users/marcfoley/Type/fontbakery/Lib/fontbakery/checkrunner.py", line
          183, in _exec_check                                                   
          for sub_result in result:  # Might raise.                             
          ↳ File                                                                
          "/Users/marcfoley/Type/fontbakery/Lib/fontbakery/profiles/universal.py
          ", line 1606, in com_adobe_fonts_check_freetype_rasterizer            
          import freetype                                                       


    Result: ERROR

 >> com.google.fonts/check/interpolation_issues
    Detect any interpolation issues in the font.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      When creating a variable font, the designer must make sure that           
      corresponding paths have the same start points across masters, as well as 
      that corresponding component shapes are placed in the same order within a 
      glyph across masters. If this is not done, the glyph will not interpolate 
      correctly.                                                                
                                                                                
      Here we check for the presence of potential interpolation errors using    
      the fontTools.varLib.interpolatable module.                               
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/3930


     WARN Interpolation issues were found in the font:                          
          - Contour 0 start point differs in glyph 'Lslash' between location    
          <fontTools.ttLib.ttGlyphSet._TTGlyphSetGlyf object at 0x110a0c6d0> and
          location <fontTools.ttLib.ttGlyphSet._TTGlyphSetGlyf object at        
          0x110a0c9a0> [code: interpolation-issues]                             


    Result: WARN

 >> com.google.fonts/check/math_signs_width
    Check math signs have the same width.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      It is a common practice to have math signs sharing the same width         
      (preferably the same width as tabular figures accross the entire font     
      family).                                                                  
                                                                                
      This probably comes from the will to avoid additional tabular math signs  
      knowing that their design can easily share the same width.                
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/3832


     WARN The most common width is 611 among a set of 2 math                    
          glyphs. The following math glyphs have a different width, though:     
                                                                                
          Width = 551: plus                                                     
                                                                                
          Width = 660: less                                                     
                                                                                
          Width = 638: equal                                                    
                                                                                
          Width = 649: greater                                                  
                                                                                
          Width = 622: logicalnot                                               
                                                                                
          Width = 585: plusminus                                                
                                                                                
          Width = 481: multiply                                                 
                                                                                
          Width = 628: divide                                                   
                                                                                
          Width = 566: minus                                                    
                                                                                
          Width = 568: lessequal, greaterequal                                  
                                                                                
          [code: width-outliers]                                                


    Result: WARN

 >> com.google.fonts/check/alt_caron:googlefonts
    Check accent of Lcaron, dcaron, lcaron, tcaron (derived from com.google.fonts/check/alt_caron)
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      Lcaron, dcaron, lcaron, tcaron should NOT be composed with quoteright or  
      quotesingle or comma or caron(comb). It should be composed with a         
      distinctive glyph which doesn't look like an apostrophe.                  
                                                                                
      Source: https://ilovetypography.com/2009/01/24/on-diacritics/             
      http://diacritics.typo.cz/index.php?id=5                                  
      https://www.typotheque.com/articles/lcaron                                
                                                                                

    ERROR Failed with TypeError: cannot unpack non-iterable                     
          float object                                                          
          ↳ File                                                                
          "/Users/marcfoley/Type/fontbakery/Lib/fontbakery/checkrunner.py", line
          183, in _exec_check                                                   
          for sub_result in result:  # Might raise.                             
          ↳ File "/Users/marcfoley/Type/fontbakery/Lib/fontbakery/profile.py",  
          line 1141, in override_wrapper                                        
          for status, message in result:  # Might raise.                        
          ↳ File                                                                
          "/Users/marcfoley/Type/fontbakery/Lib/fontbakery/profiles/universal.py
          ", line 1995, in com_google_fonts_check_alt_caron                     
          layer = font.default_master.get_glyph_layer(glyph.name)               
          ↳ File                                                                
          "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/fun
          ctools.py", line 981, in get                                          
          val = self.func(instance)                                             
          ↳ File                                                                
          "/Users/marcfoley/Type/fontbakery/venv/lib/python3.10/site-packages/ba
          belfont/Font.py", line 140, in default_master                         
          default_loc = {a.tag: a.map_forward(a.default) for a in self.axes}    
          ↳ File                                                                
          "/Users/marcfoley/Type/fontbakery/venv/lib/python3.10/site-packages/ba
          belfont/Font.py", line 140, in                                        
          default_loc = {a.tag: a.map_forward(a.default) for a in self.axes}    
          ↳ File                                                                
          "/Users/marcfoley/Type/fontbakery/venv/lib/python3.10/site-packages/ba
          belfont/Axis.py", line 110, in map_forward                            
          return piecewiseLinearMap(v, {k: v for k, v in self.map})             
          ↳ File                                                                
          "/Users/marcfoley/Type/fontbakery/venv/lib/python3.10/site-packages/ba
          belfont/Axis.py", line 110, in                                        
          return piecewiseLinearMap(v, {k: v for k, v in self.map})             


    Result: ERROR


 >> com.google.fonts/check/dsig
    Does the font have a DSIG table?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      Microsoft Office 2013 and below products expect fonts to have a digital   
      signature declared in a DSIG table in order to implement OpenType         
      features. The EOL date for Microsoft Office 2013 products is 4/11/2023.   
      This issue does not impact Microsoft Office 2016 and above products.      
                                                                                
      As we approach the EOL date, it is now considered better to completely    
      remove the table.                                                         
                                                                                
      But if you still want your font to support OpenType features on Office    
      2013, then you may find it handy to add a fake signature on a placeholder 
      DSIG table by running one of the helper scripts provided at               
      https://github.com/googlefonts/gftools                                    
                                                                                
      Reference: https://github.com/googlefonts/fontbakery/issues/1845          
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/3398


     WARN This font has a digital signature (DSIG table) which                  
          is only required - even if only a placeholder - on old programs like  
          MS Office 2013 in order to work properly. The current recommendation  
          is to completely remove the DSIG table. [code: found-DSIG]            


    Result: WARN

 >> com.google.fonts/check/dotted_circle
    Ensure dotted circle glyph is present and can attach marks.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      The dotted circle character (U+25CC) is inserted by shaping engines       
      before mark glyphs which do not have an associated base, especially in    
      the context of broken syllabic clusters.                                  
                                                                                
      For fonts containing combining marks, it is recommended that the dotted   
      circle character be included so that these isolated marks can be          
      displayed properly; for fonts supporting complex scripts, this should be  
      considered mandatory.                                                     
                                                                                
      Additionally, when a dotted circle glyph is present, it should be able to 
      display all marks correctly, meaning that it should contain anchors for   
      all attaching marks.                                                      
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/3600


     WARN No dotted circle glyph present [code:                                 
          missing-dotted-circle]                                                


    Result: WARN

 >> com.google.fonts/check/soft_dotted
    Ensure soft_dotted characters lose their dot when combined with marks that replace the dot.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

      Rationale:                                                                
                                                                                
      An accent placed on characters with a "soft dot", like i or j, causes the 
      dot to disappear. An explicit dot above can be added where required. See  
      "Diacritics on i and j" in Section 7.1, "Latin" in The Unicode Standard.  
                                                                                
      Characters with the Soft_Dotted property are listed in                    
      https://www.unicode.org/Public/UCD/latest/ucd/PropList.txt                
                                                                                
      See also:                                                                 
      https://googlefonts.github.io/gf-guide/diacritics.html#soft-dotted-glyphs 
                                                                                
    More info: https://github.com/googlefonts/fontbakery/issues/4059


     FAIL The dot of soft dotted characters used in                             
          orthographies must disappear in the following strings: i̊ i̋ j̀ j́ j̃ 
          j̄ j̈ j̑                                                              
          į̀ į́ į̂ į̃ į̄ į̌ ị̀ ị́ ị̂ ị̃ ị̄                                      
                                                                                
                                                                                
          The dot of soft dotted characters should disappear in other cases, for
          example: i̇ i̛̇ i̛̊ i̛̋ i̤̇ i̤̊ i̤̋ i̦̇ i̦̊ i̦̋ i̧̇ i̧̊ i̧̋ i̮̇ i̮̊   
          i̮̋ i̱̇ i̱̊ i̱̋ i̵̇ [code: soft-dotted]                               


    Result: FAIL


Total:

    ERROR: 2
    FAIL: 6
    WARN: 17
    INFO: 10
    SKIP: 43
    PASS: 168

[PPPPISPPPIPPPPPPPFPPPWFPWPPPPPWWPIPPSIIIPPPPPPPPPPPPPPPPPSPPPPPPPWPPSPPPPPSPFPSPPPPPPIIPPPPPPPPPSWWPPWPSWPSPSPSSSPPSPPPPPFPPSPPPWPPPPPPPPSPPPPPPFWPPPIPPPPISSWSWSPPEPPWWPSESSSPPSPPPPPPPPSPPPPPPPPPPPSPSPPPWPPPPPPPPPSSSSPPSSPPPPPPPPPPSSPPPPSSSSSSSWF] 100%

DONE!

    Meaning of check results:

    An ERROR is something wrong with FontBakery itself, possibly a bug.
    A FAIL is a problem with the font that must be fixed.
    A WARN is something that you should consider addressing.
    An INFO result simply prints something useful. Typically stats.
    A PASS means the font looks good for the given checking routine.
    And a SKIP happens when the check does not apply to the given font.

    If you get ERRORs, please help us improve the tool by reporting them at
    https://github.com/googlefonts/fontbakery/issues

    (but other kinds of bug reports and/or
     feature requests are also always welcome, of course!)

[m4rc1e]

Here's a quick edit:

(venv) Marcs-Air-2:fontbakery marcfoley$ fontbakery check-googlefonts ~/Type/fonts/ofl/mavenpro/MavenPro\[wght\].ttf
Start ... running 246 individual check executions.


-----
INFO:

 >> com.google.fonts/check/STAT/axis_order: INFO
    https://github.com/googlefonts/fontbakery/issues/3049

    Result: Table is in correct order


 >> com.google.fonts/check/description/git_url: INFO
    https://github.com/googlefonts/fontbakery/issues/2523

    Result: Url found

 
 >> com.google.fonts/check/hinting_impact: INFO
    Show hinting filesize impact.
    | Unhinted size | Hinted size | Change |
    ----------------------------------------
    | 88.6kb        | 88.6kb      | 0%     |


 >> com.google.fonts/check/old_ttfautohint: INFO         
    https://github.com/googlefonts/fontbakery/issues/4097

    Result: Fonts are not ttfautohinted


 >> com.google.fonts/check/epar: INFO
    https://github.com/googlefonts/fontbakery/issues/4097
    
    Result: No "EPAR" table in font


 >> com.google.fonts/check/gasp: INFO
    https://github.com/googlefonts/fontbakery/issues/4097

    Result: Gasp table is set to smooth
 

 >> com.google.fonts/check/fontdata_namecheck: INFO
    https://github.com/googlefonts/fontbakery/issues/494

    Result: Maven Pro already exists
 

 >> com.google.fonts/check/kerning_for_non_ligated_sequences: INFO
    https://github.com/googlefonts/fontbakery/issues/1145

    Result: kerning missing for f + i, i + l
 

 >> com.google.fonts/check/required_tables: INFO
    Font contains all required tables?
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

    Result: All tables present


 >> com.google.fonts/check/superfamily/list: INFO
    https://github.com/googlefonts/fontbakery/issues/1487                                                      

    Result: No super family detected


-----
WARN:


 >> com.google.fonts/check/metadata/unreachable_subsetting: WARN
    https://github.com/googlefonts/fontbakery/issues/4097

    Result: Following codepoints in font are not in any googlefonts subsets
    | Unicode | Character | glyphsapp name
    --------------------------------------
    | 0x02C7  | a         | canadian-aboriginal
    ...


 >> com.google.fonts/check/name/license: WARN
    https://github.com/googlefonts/fontbakery/issues/4097

    Result: "OFL.txt and MavenPro[wght].ttf use http. Use https url instead"


 >> com.google.fonts/check/metadata/reserved_font_name: WARN
    https://github.com/googlefonts/fontbakery/issues/4097
    
    Result: Reserved font name found in font license and OFL.txt


 >> com.google.fonts/check/ligature_carets: WARN
    https://github.com/googlefonts/fontbakery/issues/1225

    Result: No ligature carets for the following glyphs: f_f, f_f_i


 >> com.google.fonts/check/meta/script_lang_tags: WARN
    https://github.com/googlefonts/fontbakery/issues/2932
    Result: No meta table found



  >> com.google.fonts/check/mandatory_glyphs: WARN                                                                    
    https://docs.microsoft.com/en-us/typography/opentype/spec                 
   
    Result: .Notdef is empty. Include an outline



 >> com.google.fonts/check/unreachable_glyphs: WARN
    https://github.com/googlefonts/fontbakery/issues/3160


    Result: Following glyphs are inaccessible:
    - IJacute                                                                                                                             
    - caronalt                                                                                                                            
    - dotbelowcomb.case                                                                                                                   
    - hookabovecomb.case                                                                                                                  
    - ijacute                                                                                                                             
    - uni03020309                                                                                                                         
    - uni03060309                                                                                                                          
    - uni031B.case                                                                                                                       
    - uni0326.alt                                                        


 >> com.google.fonts/check/soft_hyphen: WARN
    https://github.com/googlefonts/fontbakery/issues/4046
    https://github.com/googlefonts/fontbakery/issues/3486

    Result: Font has a soft hyphen


 >> com.google.fonts/check/interpolation_issues: WARN
    https://github.com/googlefonts/fontbakery/issues/3930

    Result: Following glyphs have interpolation errors:
    - Lslash


 >> com.google.fonts/check/math_signs_width: WARN
    https://github.com/googlefonts/fontbakery/issues/3832

    Result: Following glyphs have differing widths:

    | Glyph | Width |
    -----------------
    | less  | 551   |
    | equal | 638   |


 >> com.google.fonts/check/dsig: WARN
    https://github.com/googlefonts/fontbakery/issues/3398

    Result: No DSIG table found


 >> com.google.fonts/check/dotted_circle: WARN
    Ensure dotted circle glyph is present and can attach marks.
    with /Users/marcfoley/Type/fonts/ofl/mavenpro/MavenPro[wght].ttf

    Result: No dotted circle glyph present
 


 ------
 FAILS:


 >> com.google.fonts/check/fontbakery_version: FAIL
    https://github.com/googlefonts/fontbakery/issues/2093

    Result: You're not using the latest version of fontbakery.
 
 
 >> com.google.fonts/check/metadata/escaped_strings: FAIL
    https://github.com/googlefonts/fontbakery/issues/2932

    Result: Found escaped strings in OFL.txt


 >> com.google.fonts/check/metadata/broken_links: FAIL
    https://github.com/googlefonts/fontbakery/issues/2550
    https://github.com/googlefonts/fontbakery/issues/4110

    Result: http://www.vissol.co.uk/mavenpro is not accessible (404 code)


 >> com.google.fonts/check/vendor_id: FAIL
    Checking OS/2 achVendID.
    https://github.com/googlefonts/fontbakery/issues/3943

    Result: "YNA " not recoginised


 >> com.google.fonts/check/glyph_coverage: FAIL
    https://github.com/googlefonts/fontbakery/pull/2488

    Result: Following codepoints are missing
    | Unicode | Character | Name
    -------------------------------------
    | 0x021A  | a         | LATIN LOWER A
    | 0x021A  | a         | LATIN LOWER A
 

 >> com.google.fonts/check/metadata/consistent_repo_urls: FAIL
    https://github.com/googlefonts/fontbakery/issues/4056

    Result: Mismatched repo urls

    | File               | String                           |
    ---------------------------------------------------------
    | OFL.txt            | www.github.com/googlefonts/maven |
    | MavenPro[wght].ttf | www.github.com/joeprince/maven   |




 >> com.google.fonts/check/soft_dotted: FAIL
    https://github.com/googlefonts/fontbakery/issues/4059


    Result: The dot of soft dotted characters used in                             
          orthographies must disappear in the following strings:
          i̊ i̋ j̀ j́ j̃ j̄ j̈ į̀ į́ į̂ į̃ į̄ į̌ ị̀ ị́ ị̂ ị̃ ị̄                                      
                                                                                
                                                                                
          The dot of soft dotted characters should disappear in other cases, for
          example:
          i̇ i̛̇ i̛̊ i̛̋ i̤̇ i̤̊ i̤̋ i̦̇ i̦̊ i̦̋ i̧̇ i̧̊ i̧̋ i̮̇ i̮̊ i̮̋ i̱̇ i̱̊ i̱̋ i̵̇ [code: soft-dotted]                               
 

 ------
 ERRORS:

 >> com.adobe.fonts/check/freetype_rasterizer: ERROR
    https://github.com/googlefonts/fontbakery/issues/3642

    Result: FreeType was not found


 >> com.google.fonts/check/alt_caron:googlefonts: Error
    https://ilovetypography.com/2009/01/24/on-diacritics/             
    http://diacritics.typo.cz/index.php?id=5                                  
    https://www.typotheque.com/articles/lcaron                                

    Result: Error with babelfont.

--------------------------------------------------------

Total:

    ERROR: 2
    FAIL: 6
    WARN: 17
    INFO: 10
    SKIP: 43
    PASS: 168

--------------------------------------------------------

    Meaning of check results:
    ERROR: Something wrong with FontBakery itself, possibly a bug.
    FAIL: Problem with the font that must be fixed.
    WARN: Something that you should consider addressing.
    INFO: Result simply prints something useful. Typically stats.
    PASS: Looks good for the given checking routine.
    SKIP: Happens when the check does not apply to the given font.

    If you get ERRORs, please help us improve the tool by reporting them at
    https://github.com/googlefonts/fontbakery/issues

    (but other kinds of bug reports and/or
     feature requests are also always welcome, of course!)

[m4rc1e]

Current report: 1,100 lines
New report: 262 lines

I've also grouped the checks by their result type which helps readability a lot.

[felipesanches]

Sure! Let's do it!

(except hiding rationales by default, which I think still needs further debate)

[felipesanches]

At #4216 (reply in thread) you seem to have conflated 2 different things. My point about the --succint flag was exclusively focused on refuting the idea of hiding rationales by default.

The fact that we have that flag (that works as the opposite of a "verbosity" flag) does not invalidate the points you made about the need to better organize / reword log messages and rationale texts, etc.

[m4rc1e]

No conflation here. I'm just pointing out that even succinct is too verbose (even if it drops rationales) and needs work.

[felipesanches]

even succinct is too verbose (even if it drops rationales) and needs work.

Agreed!

[felipesanches]

My understanding here is that, even if we keep rationale printing turned on (being optionally silenced by the --succint flag) we still need to make the output to be a bit less verbose by default. (and also better organized / checks refactored and better grouped, etc).