damccorm commented on issue #18479: URL: https://github.com/apache/beam/issues/18479#issuecomment-3945383748
> > > I'm happy to contribute to any part of this project. Is there an aspect of the implementation where an additional contributor would be helpful? > > > > > > This is great idea! Yes, I think if we have more contributors, we can slightly change the scope and add more features, namely full stateful ParDo and splittable DoFn support. I'm not sure what the exact rules of GSoC are, can a single task have multiple people working on it? Maybe [@damccorm](https://github.com/damccorm) might know? > > As far as I know, each GSoC project can have only one contributor. But if GSoC allows it would be great I think this is correct, there can only be one contributor per project. I think one of the goals is to decouple the fates of the 2 contributors (e.g. it avoids the problem if one contributor does a great job and the other does not). With that said, if we can do some scoping and divide this up, though, there's not a reason we couldn't have 2 GSOC projects which collectively add a more fully featured runner. We'd just want to be clear on a division of responsibilities as much as is possible, and formally they would be 2 projects, not 1. @je-ik if you want to try this, I think it is fine -- 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]
