Good,
also if It is still not strictly standardized across all the ecosystem repositories  you could find a “contribution welcome” or “good first issue” labels in our GitHub Issues.
If you find an issue that you like please add a comment there to check if the team is still interested to review a PR and when confirmed you could try to shortly describe your proposed solution and submit a PR.
I suggest you to partecipate to the SIGs meetings.
A few of these are already announced in the forum as you can see in the SIG category (/cc @thea @Joana  I hope the all the SIGs could soon anounce all the next meetings in the forum to have a complete converage)
You contribution it is appreciated also replying to the help requests on this forum or posting new topics.
Finally remember to take a look at: Contribute to the TensorFlow community
And check  also the README.MD and CONTRIBUTING.MD of the specific repository.
They could have quite uneven contents but we are trying to standardized these  with a common template across all the ecosystem repos:

  
    
    
    Standardize Github community health files in the Ecosystem Special Interest Groups
  
  
    Hi, 
I would like to collect a little some feedback about the idea of standardizing a little bit a new candidate contributor experience across SIGs as we are moving forward a multi repositories/SIGs oriented ecosystem (e.g. see the new TF-micro and Keras standalone repos or TF core as product RFC). 
With this I hope that we could discuss a minimal set of common contents for the two main Github community health files. 
I have currently submitted two DRAFT PR to collect feedback and comments: 


R…
  


More in general, If you have any feedback to share on the contributing documentation or about any aspect of the contributing process please write a comment here.