HeartSaVioR commented on PR #56542: URL: https://github.com/apache/spark/pull/56542#issuecomment-5183867447
@sunchao I'd love to hear your opinion about the scope of the change since you are still reviewing this. Do you think this is something one (or a couple of) committer+ can review and merge in? IMHO this looks to touch multiple components and warrants SPIP; he already put the design doc as SPIP format. Instead of keep reviewing this, why not volunteer shepherd role of this SPIP and help getting this through SPIP process? @yugan95 Here is the guide page of SPIP process - https://spark.apache.org/improvement-proposals.html SPIP does mean the project is widely review among community, and we as community make a consensus with proceeding with the project. The process requires the proposer to at least have one PMC member (or be a PMC member) to have consensus with the project and take a role of shepherding the project. Since @sunchao is reviewing the PR, maybe you can coordinate with him for this part. The most important part for SPIP is the discussion rather than code. You'd love to be around in dev@ mailing list instead of here. Hope this helps! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
