Re: [ANNOUNCE] New committer announcement: Michael Luckey

[David Morávek]

Congrats Michael! 

D.

> On 28 Feb 2019, at 03:27, Ismaël Mejía  wrote:
> 
> Congratulations Michael, and thanks for all the contributions!
> 
>> On Wed, Feb 27, 2019 at 6:30 PM Ankur Goenka  wrote:
>> 
>> Congratulations Michael!
>> 
>>> On Wed, Feb 27, 2019 at 2:25 PM Thomas Weise  wrote:
>>> 
>>> Congrats Michael!
>>> 
>>> 
 On Wed, Feb 27, 2019 at 12:41 PM Gleb Kanterov  wrote:
 
 Congratulations and welcome!
 
> On Wed, Feb 27, 2019 at 8:57 PM Connell O'Callaghan  
> wrote:
> 
> Excellent thank you for sharing Kenn!!!
> 
> Michael congratulations for this recognition of your contributions to 
> advancing BEAM
> 
>> On Wed, Feb 27, 2019 at 11:52 AM Kenneth Knowles  wrote:
>> 
>> Hi all,
>> 
>> Please join me and the rest of the Beam PMC in welcoming a new 
>> committer: Michael Luckey
>> 
>> Michael has been contributing to Beam since early 2017. He has fixed 
>> many build and developer environment issues, noted and root-caused 
>> breakages on master, generously reviewed many others' changes to the 
>> build. In consideration of Michael's contributions, the Beam PMC trusts 
>> Michael with the responsibilities of a Beam committer [1].
>> 
>> Thank you, Michael, for your contributions.
>> 
>> Kenn
>> 
>> [1] 
>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
 
 
 
 --
 Cheers,
 Gleb

Re: Added a Jira beginner's guide to the wiki.

[Kenneth Knowles]

Genius. I love it. This will save me so much clicking time.

Kenn

On Wed, Feb 27, 2019 at 5:20 PM Udi Meiri  wrote:

> My favorite way to navigate JIRA is using a Chrome search engine.
> You configure it like this:
> [image: Screenshot from 2019-02-27 17-11-26.png]
> (URL is:
> https://issues.apache.org/jira/secure/QuickSearch.jspa?searchString=%s)
>
> And search by writing in the location bar:
> "j BEAM-1234" will take you to that specific issue
> "j beam unresolved udim" will show all unresolved issues assigned to udim
>
>
> On Tue, Feb 26, 2019 at 9:22 PM Ahmet Altay  wrote:
>
>> Thank you Daniel, this is great information.
>>
>> On Fri, Feb 22, 2019 at 11:47 AM Daniel Oliveira 
>> wrote:
>>
>>> Hi everyone,
>>>
>>> In a recent thread in this list I mentioned that it might be nice to
>>> have a short guide for our Jira on the wiki since there were some aspects
>>> of Jira that I found a bit unintuitive or not discover-able when I was
>>> getting into the project. I went ahead and wrote one up and would
>>> appreciate some feedback, especially from any contributors that may be new
>>> to Beam and/or Jira.
>>>
>>>
>>> https://cwiki.apache.org/confluence/display/BEAM/Beam+Jira+Beginner%27s+Guide
>>>
>>> The main two aspects that I want to make sure I got right are:
>>>
>>> 1. Covering details that are often confusing for new contributors, such
>>> as ways Beam uses Jira that might be unique, or just unintuitive features.
>>>
>>> 2. Keeping it very brief and duplicating as little documentation as
>>> possible. I don't want this to get outdated, so I'd much rather link to a
>>> source of truth when possible.
>>>
>>> If anyone has any details I missed that they'd like to add, or feel that
>>> they could edit the guide a bit to keep it brief and cut out unnecessary
>>> info, please go ahead. Also, I'm hoping that this guide could be linked
>>> from the Contribution Guide  on
>>> the website if people find it useful, so feedback on that front would be
>>> great too.
>>>
>>

Re: [ANNOUNCE] New committer announcement: Michael Luckey

[Ismaël Mejía]

Congratulations Michael, and thanks for all the contributions!

On Wed, Feb 27, 2019 at 6:30 PM Ankur Goenka  wrote:
>
> Congratulations Michael!
>
> On Wed, Feb 27, 2019 at 2:25 PM Thomas Weise  wrote:
>>
>> Congrats Michael!
>>
>>
>> On Wed, Feb 27, 2019 at 12:41 PM Gleb Kanterov  wrote:
>>>
>>> Congratulations and welcome!
>>>
>>> On Wed, Feb 27, 2019 at 8:57 PM Connell O'Callaghan  
>>> wrote:

 Excellent thank you for sharing Kenn!!!

 Michael congratulations for this recognition of your contributions to 
 advancing BEAM

 On Wed, Feb 27, 2019 at 11:52 AM Kenneth Knowles  wrote:
>
> Hi all,
>
> Please join me and the rest of the Beam PMC in welcoming a new committer: 
> Michael Luckey
>
> Michael has been contributing to Beam since early 2017. He has fixed many 
> build and developer environment issues, noted and root-caused breakages 
> on master, generously reviewed many others' changes to the build. In 
> consideration of Michael's contributions, the Beam PMC trusts Michael 
> with the responsibilities of a Beam committer [1].
>
> Thank you, Michael, for your contributions.
>
> Kenn
>
> [1] 
> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Gleb

Re: Added a Jira beginner's guide to the wiki.

[Udi Meiri]

My favorite way to navigate JIRA is using a Chrome search engine.
You configure it like this:
[image: Screenshot from 2019-02-27 17-11-26.png]
(URL is:
https://issues.apache.org/jira/secure/QuickSearch.jspa?searchString=%s)

And search by writing in the location bar:
"j BEAM-1234" will take you to that specific issue
"j beam unresolved udim" will show all unresolved issues assigned to udim


On Tue, Feb 26, 2019 at 9:22 PM Ahmet Altay  wrote:

> Thank you Daniel, this is great information.
>
> On Fri, Feb 22, 2019 at 11:47 AM Daniel Oliveira 
> wrote:
>
>> Hi everyone,
>>
>> In a recent thread in this list I mentioned that it might be nice to have
>> a short guide for our Jira on the wiki since there were some aspects of
>> Jira that I found a bit unintuitive or not discover-able when I was getting
>> into the project. I went ahead and wrote one up and would appreciate some
>> feedback, especially from any contributors that may be new to Beam and/or
>> Jira.
>>
>>
>> https://cwiki.apache.org/confluence/display/BEAM/Beam+Jira+Beginner%27s+Guide
>>
>> The main two aspects that I want to make sure I got right are:
>>
>> 1. Covering details that are often confusing for new contributors, such
>> as ways Beam uses Jira that might be unique, or just unintuitive features.
>>
>> 2. Keeping it very brief and duplicating as little documentation as
>> possible. I don't want this to get outdated, so I'd much rather link to a
>> source of truth when possible.
>>
>> If anyone has any details I missed that they'd like to add, or feel that
>> they could edit the guide a bit to keep it brief and cut out unnecessary
>> info, please go ahead. Also, I'm hoping that this guide could be linked
>> from the Contribution Guide  on the
>> website if people find it useful, so feedback on that front would be great
>> too.
>>
>


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [ANNOUNCE] New committer announcement: Michael Luckey

[Ankur Goenka]

Congratulations Michael!

On Wed, Feb 27, 2019 at 2:25 PM Thomas Weise  wrote:

> Congrats Michael!
>
>
> On Wed, Feb 27, 2019 at 12:41 PM Gleb Kanterov  wrote:
>
>> Congratulations and welcome!
>>
>> On Wed, Feb 27, 2019 at 8:57 PM Connell O'Callaghan 
>> wrote:
>>
>>> Excellent thank you for sharing Kenn!!!
>>>
>>> Michael congratulations for this recognition of your contributions to
>>> advancing BEAM
>>>
>>> On Wed, Feb 27, 2019 at 11:52 AM Kenneth Knowles 
>>> wrote:
>>>
 Hi all,

 Please join me and the rest of the Beam PMC in welcoming a new
 committer: Michael Luckey

 Michael has been contributing to Beam since early 2017. He has fixed
 many build and developer environment issues, noted and root-caused
 breakages on master, generously reviewed many others' changes to the 
 build. In
 consideration of Michael's contributions, the Beam PMC trusts Michael with
 the responsibilities of a Beam committer [1].

 Thank you, Michael, for your contributions.

 Kenn

 [1] https://beam.apache.org/contribute/become-a-committer/#an-apache-
 beam-committer

>>>
>>
>> --
>> Cheers,
>> Gleb
>>
>

DRAFT - Apache Beam Board Report - March '19

[Kenneth Knowles]

Hi all

Our next project report to the ASF Board of Directors is due March 13th.
I've seeded a draft here:
https://docs.google.com/document/d/1jzWUewo5_KDeAVuEHw7p0ahJXHJ2qteATmnwhx3c5Js/edit?usp=sharing

Please help to eliminate all the TODOs by adding suggestions.

Kenn

Re: [ANNOUNCE] New committer announcement: Michael Luckey

[Thomas Weise]

Congrats Michael!


On Wed, Feb 27, 2019 at 12:41 PM Gleb Kanterov  wrote:

> Congratulations and welcome!
>
> On Wed, Feb 27, 2019 at 8:57 PM Connell O'Callaghan 
> wrote:
>
>> Excellent thank you for sharing Kenn!!!
>>
>> Michael congratulations for this recognition of your contributions to
>> advancing BEAM
>>
>> On Wed, Feb 27, 2019 at 11:52 AM Kenneth Knowles  wrote:
>>
>>> Hi all,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new committer:
>>> Michael Luckey
>>>
>>> Michael has been contributing to Beam since early 2017. He has fixed
>>> many build and developer environment issues, noted and root-caused
>>> breakages on master, generously reviewed many others' changes to the build. 
>>> In
>>> consideration of Michael's contributions, the Beam PMC trusts Michael with
>>> the responsibilities of a Beam committer [1].
>>>
>>> Thank you, Michael, for your contributions.
>>>
>>> Kenn
>>>
>>> [1] https://beam.apache.org/contribute/become-a-committer/#an-apache-
>>> beam-committer
>>>
>>
>
> --
> Cheers,
> Gleb
>

Re: [ANNOUNCE] New committer announcement: Michael Luckey

[Tim Robertson]

Congrats Michael and welcome.

On Thu, Feb 28, 2019 at 7:41 AM Gleb Kanterov  wrote:

> Congratulations and welcome!
>
> On Wed, Feb 27, 2019 at 8:57 PM Connell O'Callaghan 
> wrote:
>
>> Excellent thank you for sharing Kenn!!!
>>
>> Michael congratulations for this recognition of your contributions to
>> advancing BEAM
>>
>> On Wed, Feb 27, 2019 at 11:52 AM Kenneth Knowles  wrote:
>>
>>> Hi all,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new committer:
>>> Michael Luckey
>>>
>>> Michael has been contributing to Beam since early 2017. He has fixed
>>> many build and developer environment issues, noted and root-caused
>>> breakages on master, generously reviewed many others' changes to the build. 
>>> In
>>> consideration of Michael's contributions, the Beam PMC trusts Michael with
>>> the responsibilities of a Beam committer [1].
>>>
>>> Thank you, Michael, for your contributions.
>>>
>>> Kenn
>>>
>>> [1] https://beam.apache.org/contribute/become-a-committer/#an-apache-
>>> beam-committer
>>>
>>
>
> --
> Cheers,
> Gleb
>

Re: [ANNOUNCE] New committer announcement: Michael Luckey

[Gleb Kanterov]

Congratulations and welcome!

On Wed, Feb 27, 2019 at 8:57 PM Connell O'Callaghan 
wrote:

> Excellent thank you for sharing Kenn!!!
>
> Michael congratulations for this recognition of your contributions to
> advancing BEAM
>
> On Wed, Feb 27, 2019 at 11:52 AM Kenneth Knowles  wrote:
>
>> Hi all,
>>
>> Please join me and the rest of the Beam PMC in welcoming a new committer:
>> Michael Luckey
>>
>> Michael has been contributing to Beam since early 2017. He has fixed many
>> build and developer environment issues, noted and root-caused breakages on
>> master, generously reviewed many others' changes to the build. In
>> consideration of Michael's contributions, the Beam PMC trusts Michael with
>> the responsibilities of a Beam committer [1].
>>
>> Thank you, Michael, for your contributions.
>>
>> Kenn
>>
>> [1] https://beam.apache.org/contribute/become-a-committer/#an-apache-beam
>> -committer
>>
>

-- 
Cheers,
Gleb

Re: [ANNOUNCE] New committer announcement: Michael Luckey

[Connell O'Callaghan]

Excellent thank you for sharing Kenn!!!

Michael congratulations for this recognition of your contributions to
advancing BEAM

On Wed, Feb 27, 2019 at 11:52 AM Kenneth Knowles  wrote:

> Hi all,
>
> Please join me and the rest of the Beam PMC in welcoming a new committer:
> Michael Luckey
>
> Michael has been contributing to Beam since early 2017. He has fixed many
> build and developer environment issues, noted and root-caused breakages on
> master, generously reviewed many others' changes to the build. In
> consideration of Michael's contributions, the Beam PMC trusts Michael with
> the responsibilities of a Beam committer [1].
>
> Thank you, Michael, for your contributions.
>
> Kenn
>
> [1] https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-
> committer
>

[ANNOUNCE] New committer announcement: Michael Luckey

[Kenneth Knowles]

Hi all,

Please join me and the rest of the Beam PMC in welcoming a new committer:
Michael Luckey

Michael has been contributing to Beam since early 2017. He has fixed many
build and developer environment issues, noted and root-caused breakages on
master, generously reviewed many others' changes to the build. In
consideration of Michael's contributions, the Beam PMC trusts Michael with
the responsibilities of a Beam committer [1].

Thank you, Michael, for your contributions.

Kenn

[1] https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-
committer

Re: precommit tests: please ignore Python_pytest

[Udi Meiri]

I've added a flag in my latest push so that a commit-triggered job is not
created. It works :)

On Wed, Feb 27, 2019, 11:30 Pablo Estrada  wrote:

> Currently it's not possible, because we run a Seed job that sets the
> configuration globally. Lukazs Gajowy had talked to me about improvements
> to this process, but they've not been pursued further by anyone so far.
>
> TLDR: Currently it's not possible : (
> -P.
>
> On Wed, Feb 27, 2019 at 3:29 AM Maximilian Michels  wrote:
>
>> Thanks for the heads-up Udi. I noticed the GitHub check and figured that
>> it might not be fully-functional yet.
>>
>> It would be nice if there was a way to enable those hooks only for a
>> testing PR, such that they do not interfere with other PRs.
>>
>> Perhaps somebody has an idea how to do that?
>>
>> -Max
>>
>> On 27.02.19 01:13, Udi Meiri wrote:
>> > Hi all,
>> >
>> > I'm testing running Python tests using pytest, and I've added a
>> > temporary Jenkins jobs that seems to be triggering for PRs, even though
>> > I set triggerPathPatterns to an empty list. (file
>> > <
>> https://github.com/apache/beam/pull/7949/files#diff-1eadfdfe334e9d500efa54b427882c84R27
>> >)
>> >
>> > Please ignore any failures for this test.
>>
>


smime.p7s
Description: S/MIME Cryptographic Signature

Re: precommit tests: please ignore Python_pytest

[Pablo Estrada]

Currently it's not possible, because we run a Seed job that sets the
configuration globally. Lukazs Gajowy had talked to me about improvements
to this process, but they've not been pursued further by anyone so far.

TLDR: Currently it's not possible : (
-P.

On Wed, Feb 27, 2019 at 3:29 AM Maximilian Michels  wrote:

> Thanks for the heads-up Udi. I noticed the GitHub check and figured that
> it might not be fully-functional yet.
>
> It would be nice if there was a way to enable those hooks only for a
> testing PR, such that they do not interfere with other PRs.
>
> Perhaps somebody has an idea how to do that?
>
> -Max
>
> On 27.02.19 01:13, Udi Meiri wrote:
> > Hi all,
> >
> > I'm testing running Python tests using pytest, and I've added a
> > temporary Jenkins jobs that seems to be triggering for PRs, even though
> > I set triggerPathPatterns to an empty list. (file
> > <
> https://github.com/apache/beam/pull/7949/files#diff-1eadfdfe334e9d500efa54b427882c84R27
> >)
> >
> > Please ignore any failures for this test.
>

Re: Design Principles link broken

[Tanay Tummapalli]

Hi Max,

Thanks for your reply.
I'll open a PR to replace that link with a link to the contribution guide.

Thank You
Tanay Tummalapalli

On Wed, Feb 27, 2019 at 10:51 PM Maximilian Michels  wrote:

> Hi Tanay,
>
> As per this commit
>
> https://github.com/apache/beam/commit/abc68452cf5e0945674be50131a73698343c2916
> the page has been incorporated into the general contribution guide.
>
> Do you want to open a PR to fix the link in the style guide? I think we
> can replace it with a link to the contribute guide.
>
> Thanks,
> Max
>
> On 27.02.19 17:07, Tanay Tummapalli wrote:
> > Hey Everyone
> >
> > In the PTransform Style Guide section on the website, the link to Beam
> > Design Principles
> > 
> > (https://beam.apache.org/contribute/design-principles/) is broken. It
> > redirects to the contribution guide (https://beam.apache.org/contribute/
> ).
> >
> > This can be a great resource for new contributors. Can you please point
> > me to the correct URL for this?
> >
> > Thank You
> > Tanay Tummalapalli
>

Re: Design Principles link broken

[Maximilian Michels]

Hi Tanay,

As per this commit 
https://github.com/apache/beam/commit/abc68452cf5e0945674be50131a73698343c2916 
the page has been incorporated into the general contribution guide.


Do you want to open a PR to fix the link in the style guide? I think we 
can replace it with a link to the contribute guide.


Thanks,
Max

On 27.02.19 17:07, Tanay Tummapalli wrote:

Hey Everyone

In the PTransform Style Guide section on the website, the link to Beam 
Design Principles 
 
(https://beam.apache.org/contribute/design-principles/) is broken. It 
redirects to the contribution guide (https://beam.apache.org/contribute/).


This can be a great resource for new contributors. Can you please point 
me to the correct URL for this?


Thank You
Tanay Tummalapalli

Design Principles link broken

[Tanay Tummapalli]

Hey Everyone

In the PTransform Style Guide section on the website, the link to Beam
Design Principles  (
https://beam.apache.org/contribute/design-principles/) is broken. It
redirects to the contribution guide (https://beam.apache.org/contribute/).

This can be a great resource for new contributors. Can you please point me
to the correct URL for this?

Thank You
Tanay Tummalapalli

Re: precommit tests: please ignore Python_pytest

[Maximilian Michels]

Thanks for the heads-up Udi. I noticed the GitHub check and figured that 
it might not be fully-functional yet.


It would be nice if there was a way to enable those hooks only for a 
testing PR, such that they do not interfere with other PRs.


Perhaps somebody has an idea how to do that?

-Max

On 27.02.19 01:13, Udi Meiri wrote:

Hi all,

I'm testing running Python tests using pytest, and I've added a 
temporary Jenkins jobs that seems to be triggering for PRs, even though 
I set triggerPathPatterns to an empty list. (file 
)


Please ignore any failures for this test.