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
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, 201
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 req
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
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 wrote:
> There is a contribution guide at
> https://beam.apache.org/contribute/contribution-guide/
> Has anyone had challenges / pain points
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
