Github user holdenk commented on the issue:

    https://github.com/apache/spark/pull/15659
  
    That's a good question @rgbkrk - I think the closest is @davies but he has 
been pretty busy lately. I think its pretty clear that Spark is understaffed on 
Python maintainers - but it's sort of a hard cycle to fix given the current 
process for adding maintainers (although I'm optimistic that maybe some of the 
discussions from Cody's thread could perhaps help this). Many of the people who 
work in Python a lot (like myself & @HyukjinKwon ) are not maintainers.
    
    @JoshRosen has also done some Python work in the past but not a lot 
recently.
    
    Despite the lack of Python focused maintainers we are still often able to 
get some work in since the maintainers for each component will generally help 
out if your making a Python change related to their component (e.g. ML changes 
to Python are easier to have reviewed) - but since this is sort of core-Python 
it's a bit trickier.
    
    It's a bit of a stretch - but @srowen might be able to help with the review 
too since he does some reviews more related to the build - but not really 
Python.
    
    People that aren't maintainers but have some experience with Python can 
help with the review of course (e.g. @BryanCutler, @sethah, @HyukjinKwon  ) - 
and it can be a useful signal to core maintainers who don't have the Python 
background - but at the end of the day we do need a maintainer/committer to 
sign off on this.
    
    I'm hoping @mateiz's interest from our discussion on the previous PR is 
still present and we can get him to do the review - but otherwise I'll keep 
looking for someone else who would feel comfortable merging this. (Of course 
the longer discussion around the lack of Python ecosystem focused maintainers 
for Spark is something I'd also love to move forward but I think that really 
depends on the PMC and they haven't had the interest in having those 
discussions in public so there isn't a lot I can do).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to