Re: Intro

[Kenneth Knowles]

Welcome! Thank you for saying hello!

Kenn

On Fri, Oct 22, 2021 at 9:10 AM Jean-Baptiste Onofre 
wrote:

> Welcome ;)
>
> Regards
> JB
>
> > Le 22 oct. 2021 à 15:52, Moritz Mack  a écrit :
> >
> > Hi all,
> >
> > I’m very much looking forward to start contributing to Beam and just
> want to briefly introduce myself.
> >
> > My name is Moritz (mosche) and I’m working together with Alexey and
> Etienne. Having worked mostly with Spark in the past, I’m excited to dive
> deeper into Beam 😊
> >
> > Looking forward to working with all of you!
> >
> > Kind regards from Munich,
> > Moritz
> >
> > As a recipient of an email from Talend, your contact personal data will
> be on our systems. Please see our privacy notice (updated August 2020) at
> Talend, Inc.
> >
>
>

Re: Intro

[Jean-Baptiste Onofre]

Welcome ;)

Regards
JB

> Le 22 oct. 2021 à 15:52, Moritz Mack  a écrit :
> 
> Hi all,
>  
> I’m very much looking forward to start contributing to Beam and just want to 
> briefly introduce myself.
>  
> My name is Moritz (mosche) and I’m working together with Alexey and Etienne. 
> Having worked mostly with Spark in the past, I’m excited to dive deeper into 
> Beam 😊
>  
> Looking forward to working with all of you!
>  
> Kind regards from Munich,
> Moritz
>  
> As a recipient of an email from Talend, your contact personal data will be on 
> our systems. Please see our privacy notice (updated August 2020) at Talend, 
> Inc. 
> 

Re: Intro

[Alexey Romanenko]

Welcome to Beam, Moritz!

—
Alexey

> On 22 Oct 2021, at 17:44, Etienne Chauchot  wrote:
> 
> Welcome onboard Moritz !
> 
> Best
> 
> Etienne
> 
> On 22/10/2021 15:52, Moritz Mack wrote:
>> Hi all,
>>  
>> I’m very much looking forward to start contributing to Beam and just want to 
>> briefly introduce myself.
>>  
>> My name is Moritz (mosche) and I’m working together with Alexey and Etienne. 
>> Having worked mostly with Spark in the past, I’m excited to dive deeper into 
>> Beam 😊
>>  
>> Looking forward to working with all of you!
>>  
>> Kind regards from Munich,
>> Moritz
>>  
>> As a recipient of an email from Talend, your contact personal data will be 
>> on our systems. Please see our privacy notice (updated August 2020) at 
>> Talend, Inc.  

Re: Intro

[Etienne Chauchot]

Welcome onboard Moritz !

Best

Etienne

On 22/10/2021 15:52, Moritz Mack wrote:


Hi all,

I’m very much looking forward to start contributing to Beam and just 
want to briefly introduce myself.


My name is Moritz (mosche) and I’m working together with Alexey and 
Etienne. Having worked mostly with Spark in the past, I’m excited to 
dive deeper into Beam 😊


Looking forward to working with all of you!

Kind regards from Munich,

Moritz

*As a recipient of an email from Talend, your contact personal data 
will be on our systems. Please see our privacy notice (updated August 
2020) at Talend, Inc. *

Re: Intro and ticket BEAM-10938

[Milan Cermak]

Thank you for the input. I've just opened a PR for the ticket 🤞

On 2020/09/22 17:08:06, Kenneth Knowles  wrote: 
> The way I use "Triage Needed" is to make sure there is some queue of
> incoming bugs that can be looked at. The level where I click "triaged" is
> when:
> 
>  - priority is right (https://beam.apache.org/contribute/jira-priorities/)
>  - components are right
>  - any needed tags
>  - bug type is right
>  - sometimes tag somebody who might know something about it
> 
> It doesn't mean there is any decision about anything else. The assumption
> is that most users and new contributors will just not know about these
> things so it is good to check and help make sure the ticket gets attention.
> If you are filing the ticket for yourself to implement, then I am sure it
> is getting attention :-)
> 
> Kenn
> 
> On Tue, Sep 22, 2020 at 9:45 AM Luke Cwik  wrote:
> 
> > Thanks for reaching out.
> >
> > "Triage needed" is the default state when a bug is opened and does not
> > mean that it is yet to be decided. Typically if there is something of note,
> > either the contributor asks on the dev@ mailing list about it and works
> > with the community or opens a PR and a reviewer will bring the PR to
> > discussion within the community. The former happens for "larger" things and
> > the "latter" is typically for smaller things when some kind of ambiguity in
> > a decision.
> >
> > I have added you as a contributor to the Beam JIRA project and assigned
> > BEAM-10938 to you. Feel free to open the PR and find a committer to review
> > it (ask the issue creator or a committer who is familiar with the code in
> > the location (via git blame) for a review and tag them with R: @nickname).
> >
> >
> > On Tue, Sep 22, 2020 at 9:37 AM Milan Cermak 
> > wrote:
> >
> >> Hi,
> >>
> >> I'm Milan, I'm a software engineer and I'm new to Beam.
> >>
> >> I've noticed this new issue in JIRA (
> >> https://issues.apache.org/jira/browse/BEAM-10938). Out of curiosity, I
> >> decided to dig deeper and see if I can add the functionality. I think I got
> >> it (you can see the diff here
> >> https://github.com/apache/beam/compare/master...milancermak:BEAM-10938),
> >> but then I've also noticed the status is "Triage needed" which, I assume,
> >> means it's not yet decided by the community if this should be worked on at
> >> all. Is that right? Should I send a PR or wait until the status clears? Any
> >> guidance is appreciated.
> >>
> >> FWIW, my JIRA username is milancermak
> >>
> >> Cheers,
> >>
> >> Milan
> >>
> >
> 

Re: Intro and ticket BEAM-10938

[Kenneth Knowles]

The way I use "Triage Needed" is to make sure there is some queue of
incoming bugs that can be looked at. The level where I click "triaged" is
when:

 - priority is right (https://beam.apache.org/contribute/jira-priorities/)
 - components are right
 - any needed tags
 - bug type is right
 - sometimes tag somebody who might know something about it

It doesn't mean there is any decision about anything else. The assumption
is that most users and new contributors will just not know about these
things so it is good to check and help make sure the ticket gets attention.
If you are filing the ticket for yourself to implement, then I am sure it
is getting attention :-)

Kenn

On Tue, Sep 22, 2020 at 9:45 AM Luke Cwik  wrote:

> Thanks for reaching out.
>
> "Triage needed" is the default state when a bug is opened and does not
> mean that it is yet to be decided. Typically if there is something of note,
> either the contributor asks on the dev@ mailing list about it and works
> with the community or opens a PR and a reviewer will bring the PR to
> discussion within the community. The former happens for "larger" things and
> the "latter" is typically for smaller things when some kind of ambiguity in
> a decision.
>
> I have added you as a contributor to the Beam JIRA project and assigned
> BEAM-10938 to you. Feel free to open the PR and find a committer to review
> it (ask the issue creator or a committer who is familiar with the code in
> the location (via git blame) for a review and tag them with R: @nickname).
>
>
> On Tue, Sep 22, 2020 at 9:37 AM Milan Cermak 
> wrote:
>
>> Hi,
>>
>> I'm Milan, I'm a software engineer and I'm new to Beam.
>>
>> I've noticed this new issue in JIRA (
>> https://issues.apache.org/jira/browse/BEAM-10938). Out of curiosity, I
>> decided to dig deeper and see if I can add the functionality. I think I got
>> it (you can see the diff here
>> https://github.com/apache/beam/compare/master...milancermak:BEAM-10938),
>> but then I've also noticed the status is "Triage needed" which, I assume,
>> means it's not yet decided by the community if this should be worked on at
>> all. Is that right? Should I send a PR or wait until the status clears? Any
>> guidance is appreciated.
>>
>> FWIW, my JIRA username is milancermak
>>
>> Cheers,
>>
>> Milan
>>
>

Re: Intro and ticket BEAM-10938

[Luke Cwik]

Thanks for reaching out.

"Triage needed" is the default state when a bug is opened and does not mean
that it is yet to be decided. Typically if there is something of note,
either the contributor asks on the dev@ mailing list about it and works
with the community or opens a PR and a reviewer will bring the PR to
discussion within the community. The former happens for "larger" things and
the "latter" is typically for smaller things when some kind of ambiguity in
a decision.

I have added you as a contributor to the Beam JIRA project and assigned
BEAM-10938 to you. Feel free to open the PR and find a committer to review
it (ask the issue creator or a committer who is familiar with the code in
the location (via git blame) for a review and tag them with R: @nickname).


On Tue, Sep 22, 2020 at 9:37 AM Milan Cermak  wrote:

> Hi,
>
> I'm Milan, I'm a software engineer and I'm new to Beam.
>
> I've noticed this new issue in JIRA (
> https://issues.apache.org/jira/browse/BEAM-10938). Out of curiosity, I
> decided to dig deeper and see if I can add the functionality. I think I got
> it (you can see the diff here
> https://github.com/apache/beam/compare/master...milancermak:BEAM-10938),
> but then I've also noticed the status is "Triage needed" which, I assume,
> means it's not yet decided by the community if this should be worked on at
> all. Is that right? Should I send a PR or wait until the status clears? Any
> guidance is appreciated.
>
> FWIW, my JIRA username is milancermak
>
> Cheers,
>
> Milan
>

Re: Intro & request to add me as a contributor

[Kenneth Knowles]

Welcome! That kind of feedback would be a huge contribution.

Kenn

On Mon, Oct 7, 2019 at 12:25 AM Ismaël Mejía  wrote:

> Hello and welcome !
>
> You can now self assign Jira tickets. You don't need any additional
> permissions to open PRs.
> User/customer feedback is really appreciated so feel free to bring more of
> that.
>
> Cheers,
> Ismaël
>
> On Mon, Oct 7, 2019 at 7:58 AM Zoltán Kauker 
> wrote:
> >
> > Dear All,
> >
> > I'm new to this community. I'm a cloud architect at Aliz Technologies,
> working with Beam at a lot of our customers and I think from time-to-time I
> can bring in some useful feedback which can be beneficial for everyone.
> >
> > In urgent cases, I'd like to contribute to the code as well so it would
> be great if you could add me.
> >
> > Jira username: Kauker
> > Github account: zkauker
> >
> > Cheers,
> > Zoltan
>

Re: Intro & request to add me as a contributor

[Ismaël Mejía]

Hello and welcome !

You can now self assign Jira tickets. You don't need any additional
permissions to open PRs.
User/customer feedback is really appreciated so feel free to bring more of that.

Cheers,
Ismaël

On Mon, Oct 7, 2019 at 7:58 AM Zoltán Kauker  wrote:
>
> Dear All,
>
> I'm new to this community. I'm a cloud architect at Aliz Technologies, 
> working with Beam at a lot of our customers and I think from time-to-time I 
> can bring in some useful feedback which can be beneficial for everyone.
>
> In urgent cases, I'd like to contribute to the code as well so it would be 
> great if you could add me.
>
> Jira username: Kauker
> Github account: zkauker
>
> Cheers,
> Zoltan

Re: Intro

[Kenneth Knowles]

Welcome!

On Wed, May 15, 2019 at 7:23 AM Cyrus Maden  wrote:

> Welcome!
>
> On Tue, May 14, 2019 at 4:36 PM Robert Burke  wrote:
>
>> Welcome aboard :D
>>
>> On Tue, 14 May 2019 at 13:28, Ahmet Altay  wrote:
>>
>>> Welcome! Added you as a contributor to JIRA.
>>>
>>> *From: *Damien Desfontaines 
>>> *Date: *Tue, May 14, 2019 at 1:24 PM
>>> *To: * 
>>>
>>> Hi folks,

 I'm Damien from the Anonymization team at Google. I might contribute a
 couple of PRs on the Go SDK. Can someone give me permission to assign Jira
 tickets to myself? My username is desfontaines.

 Thanks in advance!

 Damien

 --
 I'm working part-time, so I might not see your emails immediately. See
 go/man-ddf for more info =)

>>>

Re: Intro

[Cyrus Maden]

Welcome!

On Tue, May 14, 2019 at 4:36 PM Robert Burke  wrote:

> Welcome aboard :D
>
> On Tue, 14 May 2019 at 13:28, Ahmet Altay  wrote:
>
>> Welcome! Added you as a contributor to JIRA.
>>
>> *From: *Damien Desfontaines 
>> *Date: *Tue, May 14, 2019 at 1:24 PM
>> *To: * 
>>
>> Hi folks,
>>>
>>> I'm Damien from the Anonymization team at Google. I might contribute a
>>> couple of PRs on the Go SDK. Can someone give me permission to assign Jira
>>> tickets to myself? My username is desfontaines.
>>>
>>> Thanks in advance!
>>>
>>> Damien
>>>
>>> --
>>> I'm working part-time, so I might not see your emails immediately. See
>>> go/man-ddf for more info =)
>>>
>>

Re: Intro

[Robert Burke]

Welcome aboard :D

On Tue, 14 May 2019 at 13:28, Ahmet Altay  wrote:

> Welcome! Added you as a contributor to JIRA.
>
> *From: *Damien Desfontaines 
> *Date: *Tue, May 14, 2019 at 1:24 PM
> *To: * 
>
> Hi folks,
>>
>> I'm Damien from the Anonymization team at Google. I might contribute a
>> couple of PRs on the Go SDK. Can someone give me permission to assign Jira
>> tickets to myself? My username is desfontaines.
>>
>> Thanks in advance!
>>
>> Damien
>>
>> --
>> I'm working part-time, so I might not see your emails immediately. See
>> go/man-ddf for more info =)
>>
>

Re: Intro

[Ahmet Altay]

Welcome! Added you as a contributor to JIRA.

*From: *Damien Desfontaines 
*Date: *Tue, May 14, 2019 at 1:24 PM
*To: * 

Hi folks,
>
> I'm Damien from the Anonymization team at Google. I might contribute a
> couple of PRs on the Go SDK. Can someone give me permission to assign Jira
> tickets to myself? My username is desfontaines.
>
> Thanks in advance!
>
> Damien
>
> --
> I'm working part-time, so I might not see your emails immediately. See
> go/man-ddf for more info =)
>