brucearctor commented on issue #21089:
URL: https://github.com/apache/beam/issues/21089#issuecomment-1374046208

   @robertwb and @kennknowles -- I'm glad you're looking into this.  I have 
advised Nivaldo on strategies, with an eye on getting this to be something 
useful enough to warrant being merged into the proper project as another sdk.  
Your experience/knowledge attending to this will go a long way!  
   
   Maybe you two can dig a little into 
https://github.com/nivaldoh/beam/tree/rust_sdk and @nivaldoh can look at 
https://github.com/kennknowles/beam/tree/rust/sdks/rust -- suggesting that we 
wind only working on one or the other.
   
   I wonder if it'd be easier to keep @kennknowles 's eyes on progress if 
developed in his repo?  But, if the other is much further along might it better 
to jump into that [ @nivaldoh -- I assume you can give @kennknowles , @robertwb 
, and others relevant merge/commit permissions in your repo -- in things Beam 
they know their stuff and should absolutely be trusted ].  Else, it might then 
depend on the merge/migration path to get relevant bits into 
https://github.com/kennknowles/beam/tree/rust/sdks/rust, which I also imagine 
@nivaldoh might be open to taking on, as that could help solidify 
understandings, implementation.  
   
   I'll try to have a look to compare the repos over the weekend or sometime 
next week.  
   
   @nivaldoh - please advise on your thoughts/inclinations [ I've been sorta 
speaking for you, based on my read of you, motivation, inclinations when we've 
connected ]
   
   
   


-- 
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]

Reply via email to