You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Alan Myrvold <am...@google.com> on 2018/03/14 18:47:54 UTC
New beam contributor experience?
There is a contribution guide at
https://beam.apache.org/contribute/contribution-guide/
Has anyone had challenges / pain points when getting started with new
contributions?
Any suggestions for making this better?
Alan
Re: New beam contributor experience?
Posted by Andrew Pilloud <ap...@google.com>.
To add more to what Anton said, the 'mvn clean verify' step takes hours and
fails frequently due to bad tests. I spent the first few days working with
beam trying to figure out what was wrong with my system when I was just
hitting test flaps. If we're going to gradle that would be a great place to
update. If not, adding directions on how to skip the tests in maven and
just run the build would be good too.
Andrew
On Wed, Mar 14, 2018 at 11:54 AM Anton Kedin <ke...@google.com> wrote:
> Not sure if it was mentioned in other threads, but it probably makes sense
> to add gradle instructions there.
>
>
> On Wed, Mar 14, 2018 at 11:48 AM Alan Myrvold <am...@google.com> wrote:
>
>> There is a contribution guide at
>> https://beam.apache.org/contribute/contribution-guide/
>> Has anyone had challenges / pain points when getting started with new
>> contributions?
>> Any suggestions for making this better?
>>
>> Alan
>>
>
Re: New beam contributor experience?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Good point. As mentioned, maybe the contribution guide is not enough, we
also have the "low hanging fruit" tagged Jira that new contributors can
take a look.
Maybe for both users and new contributors, it would be great to have
additional concrete examples. Today, the game examples is great but
mostly Java SDK focused and very "streaming" oriented.
We have additional samples (both batch and streaming) today with the
Java SDK (https://github.com/jbonofre/beam-samples). If you think it
could help, please let me know, I would be more then happy to cleanup
and polish to prepare a PR.
We are also planning to add Python example there.
Regards
JB
On 14/03/2018 23:01, Gaurav Thakur wrote:
> I agree with Pablo, it would be great if there is place someone new like
> me can go and find out what would be some good starting points to start
> contributing.
>
> Apologies if there is such a place already somewhere, I would appreciate
> some directions in that case.
>
> Thanks, Gaurav
>
> On Thu, Mar 15, 2018 at 8:13 AM, Pablo Estrada <pabloem@google.com
> <ma...@google.com>> wrote:
>
> Some things that we have found working with our friends at IBM are:
>
> - No Python install from code documentation (which I've brought up
> before, and I believe is a known issue)
> - The process to pick up a JIRA is not very clear. It seems that
> there are a lot of implicit conventions (is discussion required? how
> do I know if I can start working on a jira?)
>
> Best
> -P.
>
> On Wed, Mar 14, 2018 at 11:54 AM Anton Kedin <kedin@google.com
> <ma...@google.com>> wrote:
>
> Not sure if it was mentioned in other threads, but it probably
> makes sense to add gradle instructions there.
>
>
> On Wed, Mar 14, 2018 at 11:48 AM Alan Myrvold
> <amyrvold@google.com <ma...@google.com>> wrote:
>
> There is a contribution guide at
> https://beam.apache.org/contribute/contribution-guide/
> <https://beam.apache.org/contribute/contribution-guide/>
> Has anyone had challenges / pain points when getting started
> with new contributions?
> Any suggestions for making this better?
>
> Alan
>
> --
> Got feedback? go/pabloem-feedback
>
>
Re: New beam contributor experience?
Posted by Gaurav Thakur <ga...@gmail.com>.
I agree with Pablo, it would be great if there is place someone new like me
can go and find out what would be some good starting points to start
contributing.
Apologies if there is such a place already somewhere, I would appreciate
some directions in that case.
Thanks, Gaurav
On Thu, Mar 15, 2018 at 8:13 AM, Pablo Estrada <pa...@google.com> wrote:
> Some things that we have found working with our friends at IBM are:
>
> - No Python install from code documentation (which I've brought up before,
> and I believe is a known issue)
> - The process to pick up a JIRA is not very clear. It seems that there are
> a lot of implicit conventions (is discussion required? how do I know if I
> can start working on a jira?)
>
> Best
> -P.
>
> On Wed, Mar 14, 2018 at 11:54 AM Anton Kedin <ke...@google.com> wrote:
>
>> Not sure if it was mentioned in other threads, but it probably makes
>> sense to add gradle instructions there.
>>
>>
>> On Wed, Mar 14, 2018 at 11:48 AM Alan Myrvold <am...@google.com>
>> wrote:
>>
>>> There is a contribution guide at https://beam.apache.org/
>>> contribute/contribution-guide/
>>> Has anyone had challenges / pain points when getting started with new
>>> contributions?
>>> Any suggestions for making this better?
>>>
>>> Alan
>>>
>> --
> Got feedback? go/pabloem-feedback
>
Re: New beam contributor experience?
Posted by Pablo Estrada <pa...@google.com>.
Some things that we have found working with our friends at IBM are:
- No Python install from code documentation (which I've brought up before,
and I believe is a known issue)
- The process to pick up a JIRA is not very clear. It seems that there are
a lot of implicit conventions (is discussion required? how do I know if I
can start working on a jira?)
Best
-P.
On Wed, Mar 14, 2018 at 11:54 AM Anton Kedin <ke...@google.com> wrote:
> Not sure if it was mentioned in other threads, but it probably makes sense
> to add gradle instructions there.
>
>
> On Wed, Mar 14, 2018 at 11:48 AM Alan Myrvold <am...@google.com> wrote:
>
>> There is a contribution guide at
>> https://beam.apache.org/contribute/contribution-guide/
>> Has anyone had challenges / pain points when getting started with new
>> contributions?
>> Any suggestions for making this better?
>>
>> Alan
>>
> --
Got feedback? go/pabloem-feedback
Re: New beam contributor experience?
Posted by Anton Kedin <ke...@google.com>.
Not sure if it was mentioned in other threads, but it probably makes sense
to add gradle instructions there.
On Wed, Mar 14, 2018 at 11:48 AM Alan Myrvold <am...@google.com> wrote:
> There is a contribution guide at
> https://beam.apache.org/contribute/contribution-guide/
> Has anyone had challenges / pain points when getting started with new
> contributions?
> Any suggestions for making this better?
>
> Alan
>