There are some logistics that would need worked out. For example, Where
would the data go? Who would own it?
Also, I'm not convinced we need yet another place to discuss Beam when we
already have discussed the challenge of simultaneously monitoring mailing
lists, Stack Overflow, Slack, etc. While
Hi,
At the moment we don't really have a good way to collect any usage
statistics for Apache Beam. Like runner used etc. As many of the users
don't really have a way to report their usecase.
How about if we create a feedback page where users can add their pipeline
details and usecase.
Also, we can
You should be set to self assign issues. (Thanks Pablo)
Welcome!
On Fri, Sep 20, 2019, 12:21 PM dev wearebold
wrote:
> Hey my Jira username is johnpatoch69
>
> Thank you
>
> Regards,
>
> J
>
> Le 20 sept. 2019 à 20:57, Robert Burke a écrit :
>
> Absolutely! What's your Jira username? You can c
Hey my Jira username is johnpatoch69
Thank you
Regards,
J
> Le 20 sept. 2019 à 20:57, Robert Burke a écrit :
>
> Absolutely! What's your Jira username? You can create an account if you don't
> already have one, following the instructions here:
> https://beam.apache.org/contribute/#prerequis
Absolutely! What's your Jira username? You can create an account if you
don't already have one, following the instructions here:
https://beam.apache.org/contribute/#prerequisites
I'm here to help with most things Go SDK too, and provide timely reviews
and merges of Go PRs. Just be sure to mention
Thank you, Chad, for refreshing this conversation and adding the
perspective of Python 2 users of Beam who have not(yet) completed the
migration. My thoughts below.
- It is in the best interest of everyone to ensure a smooth migration for
Beam users. However a migration needs to happen since Pytho
Hi,
I’m John, I’d like to work on the Go SDK for Beam, mostly on the util stuff,
and I’ll need to create/assign tickets for my work.
Can someone add me as a contributor for Beam’s Jira issue?
Have a nice day
J.
And, yes, the fact that Jenkins jobs are separately evolving but pretty
tightly coupled to the repo contents is a serious problem that I wish we
had fixed. So verification of each PR was manual.
Could you tell a little bit more about what exactly were the problems back
then? Was that due to incomp
