Do you have an idea of the scope of the work that’s necessary here?
There is a process for design-reviews in TensorFlow:

  

      github.com
  

  
    tensorflow/community/blob/master/governance/TF-RFCs.md


    # TensorFlow Request for Comments (TF-RFC)

The purpose of a TensorFlow RFC is to engage the TensorFlow community in
development, by getting feedback from stakeholders and experts, and
communicating design changes broadly.

## Who is involved?

Any **community member** may help by providing feedback on whether the RFC will
meet their needs.

An **RFC author** is one or more community member who writes an RFC and is
committed to championing it through the  process.

An **RFC sponsor** is any maintainer who sponsors the RFC and will shepherd it
through the RFC review process.

A **review committee** is a group of maintainers who have the responsibility of
recommending the adoption of the RFC.




  This file has been truncated. show original

  

  
    
    
  

  


  

      github.com
  

  
    tensorflow/community/blob/master/governance/design-reviews.md


    # tf-design-reviews criteria

## Overview

The TensorFlow team has run internal and public design reviews for a while
now. This document tries to capture what type of questions get asked and
concerns get addressed in TF design reviews. It is intended to be used by design
authors as a way of spot checking whether a design review will be useful for
them and by design sponsors as a way of making sure a design proposal clears the
bar for review (ideally every topic in this document should be addressed by the
design proposal for it to be considered).

The main goal of tf-design-reviews is to socialize big changes to TF, document
them, and ensure all stakeholders get a chance to comment on planned
improvements before they’re implemented. Any time a change is made to TF that
will affect multiple aspects of its design or user interface, we should solicit
a design review. TF design reviews themselves are not binding: final approval
rests with whoever has the authority to approve the required code changes, and
the design review is a tool to get consensus and feedback on big changes before
actual approval.



  This file has been truncated. show original

  

  
    
    
  

  


But I guess that without a sponsor from the core team you’re somewhat stuck at the “Recruit a sponsor from the maintainers of the project”.