Re: Beam's recent community development work

[Ted Dunning]

Dang. I missed that.

Ross is exactly right here. GREAT idea.

I am going to push this all over.



On Mon, Jul 2, 2018 at 8:27 PM  wrote:

> There is one insight here that I particularly like and I believe helps me
> find a good compromise that I’ve struggled with for years. I’m a fan of CTR
> rather than RTC for committers. However, I recognize that a number of
> projects don’t share my views on this. I ***love*** your solution and will
> quote it in case people missed it because you said “As a minor point” – I
> think it is a key point:
>
>
>
> “As a minor point, we also changed our "review-then-commit" policy to
> require that *either* the reviewer or the author be a committer. Previously
> the reviewer had to be a committer. Rationale: if we trust someone as a
> committer, we should trust their choice of reviewer. This also helps the
> community, as it engages non-committers as reviewers.”
>
>
>
> I like your overall process, but I especially applaud this insight – thank
> you beam community.
>
>
>
> Ross
>
>
>
>
>
> From: Kenneth Knowles 
> Sent: Monday, July 2, 2018 4:47 PM
> To: dev 
> Cc: memb...@apache.org; dev@community.apache.org; Griselda Cuevas <
> g...@apache.org>
> Subject: Re: Beam's recent community development work
>
>
>
> Thanks for the guidance Ted,
>
>
>
> All of your points are well taken. I/we will definitely stay careful about
> phrasing encouragement emails and our guidelines.
>
>
>
> Kenn
>
>
>
> On Sat, Jun 30, 2018 at 8:45 AM Ted Dunning   > wrote:
>
>
>
> Ken,
>
>
>
> This is really good.
>
>
>
> I would like to emphasize one nuance, however. That is that when you get
> to the committer consideration step, there is a strong Apache tradition
> that the actual decision about committer-ship is not communicated to the
> candidate to avoid disappointment or campaigning during the vote.
>
>
>
> What you have could veer close to that, but I think that what you actually
> have in mind is just fine. I think that there could be a few tweaks to your
> process to emphasize how your efforts are OK.
>
>
>
> 1) when you contact a person and mention committer progress, please
> emphasize that it is a bit more like "your efforts have been noticed and
> appreciated. More of that sort of effort is something that often leads to
> becoming a committer. That actual process is confidential, however, so you
> won't know if or when it happens unless you get an invitation to become a
> committer"
>
>
>
> 2) the part about "do you want to become one, do you want feedback?" is
> golden just the way it is.
>
>
>
> 3) you mention "committer guidelines". This can be dangerous if it gets
> viewed as an application form or committer status checklist. This is a hard
> problem because it helps the PMC to have a list of things that are
> considered good qualities of a committer. I recommend keeping this danger
> in mind when composing emails to candidate committers. Above all else, try
> to avoid having the equivalent of an application form.
>
>
>
> Overall, I think that your results speak for themselves. Well done.
>
>
>
>
>
>
>
> On Fri, Jun 29, 2018 at 11:15 PM Kenneth Knowles  k...@google.com> > wrote:
>
> Hi all,
>
>
>
> The ASF board suggested that we (Beam) share some of what we've been doing
> for community development with dev@community.apache.org  dev@community.apache.org>  and memb...@apache.org  memb...@apache.org> . So here is a long description. I have included
> d...@beam.apache.org   because it is the
> subject, really, and this is & should be all public knowledge.
>
>
>
> We would love feedback! We based a lot of this on reading the community
> project site, and probably could have learned even more with more study.
>
>
>
> # Background
>
>
>
> We face two problems in our contributor/committer-base:
>
>
>
> 1. Not enough committers to review all the code being contributed, in part
> due to recent departure of a few committers
>
> 2. We want our contributor-base (hence committer-base) to be more spread
> across companies and backgrounds, for the usual Apache reasons. Our user
> base is not active and varied enough to make this automatic. One solution
> is to make the right software to get a varied user base, but that is a
> different thread :-) so instead we have to work hard to build our community
> around the software we have.
>
>
>
> # What we did
>
>
>
> ## Committer guidelines
>
>
>
> We published committer guidelines [1] for transparency and as an
> invitation. We start by emphasizing that there are many kinds of
> contributions, not just code (we have committers from community
> development, tech writing, training, etc). Then we have three aspects:
>
>
>
> 1. ASF code of conduct
>
> 2. ASF committer responsibilities
>
> 3. Beam-specific committer responsibilities
>
>
>
> The best way to understand is to follow the link at the bottom of this
> email. The important part is that you shouldn't be proposing a committer
> for other 

RE: Beam's recent community development work

[ross]

There is one insight here that I particularly like and I believe helps me find 
a good compromise that I’ve struggled with for years. I’m a fan of CTR rather 
than RTC for committers. However, I recognize that a number of projects don’t 
share my views on this. I ***love*** your solution and will quote it in case 
people missed it because you said “As a minor point” – I think it is a key 
point:

 

“As a minor point, we also changed our "review-then-commit" policy to require 
that *either* the reviewer or the author be a committer. Previously the 
reviewer had to be a committer. Rationale: if we trust someone as a committer, 
we should trust their choice of reviewer. This also helps the community, as it 
engages non-committers as reviewers.”

 

I like your overall process, but I especially applaud this insight – thank you 
beam community.

 

Ross

 

 

From: Kenneth Knowles  
Sent: Monday, July 2, 2018 4:47 PM
To: dev 
Cc: memb...@apache.org; dev@community.apache.org; Griselda Cuevas 

Subject: Re: Beam's recent community development work

 

Thanks for the guidance Ted,

 

All of your points are well taken. I/we will definitely stay careful about 
phrasing encouragement emails and our guidelines.

 

Kenn

 

On Sat, Jun 30, 2018 at 8:45 AM Ted Dunning mailto:ted.dunn...@gmail.com> > wrote:

 

Ken,

 

This is really good.

 

I would like to emphasize one nuance, however. That is that when you get to the 
committer consideration step, there is a strong Apache tradition that the 
actual decision about committer-ship is not communicated to the candidate to 
avoid disappointment or campaigning during the vote.

 

What you have could veer close to that, but I think that what you actually have 
in mind is just fine. I think that there could be a few tweaks to your process 
to emphasize how your efforts are OK.

 

1) when you contact a person and mention committer progress, please emphasize 
that it is a bit more like "your efforts have been noticed and appreciated. 
More of that sort of effort is something that often leads to becoming a 
committer. That actual process is confidential, however, so you won't know if 
or when it happens unless you get an invitation to become a committer"

 

2) the part about "do you want to become one, do you want feedback?" is golden 
just the way it is.

 

3) you mention "committer guidelines". This can be dangerous if it gets viewed 
as an application form or committer status checklist. This is a hard problem 
because it helps the PMC to have a list of things that are considered good 
qualities of a committer. I recommend keeping this danger in mind when 
composing emails to candidate committers. Above all else, try to avoid having 
the equivalent of an application form.

 

Overall, I think that your results speak for themselves. Well done.

 

 

 

On Fri, Jun 29, 2018 at 11:15 PM Kenneth Knowles mailto:k...@google.com> > wrote:

Hi all,

 

The ASF board suggested that we (Beam) share some of what we've been doing for 
community development with dev@community.apache.org 
  and memb...@apache.org 
 . So here is a long description. I have included 
d...@beam.apache.org   because it is the subject, 
really, and this is & should be all public knowledge.

 

We would love feedback! We based a lot of this on reading the community project 
site, and probably could have learned even more with more study.

 

# Background

 

We face two problems in our contributor/committer-base:

 

1. Not enough committers to review all the code being contributed, in part due 
to recent departure of a few committers

2. We want our contributor-base (hence committer-base) to be more spread across 
companies and backgrounds, for the usual Apache reasons. Our user base is not 
active and varied enough to make this automatic. One solution is to make the 
right software to get a varied user base, but that is a different thread :-) so 
instead we have to work hard to build our community around the software we have.

 

# What we did

 

## Committer guidelines

 

We published committer guidelines [1] for transparency and as an invitation. We 
start by emphasizing that there are many kinds of contributions, not just code 
(we have committers from community development, tech writing, training, etc). 
Then we have three aspects:

 

1. ASF code of conduct

2. ASF committer responsibilities

3. Beam-specific committer responsibilities

 

The best way to understand is to follow the link at the bottom of this email. 
The important part is that you shouldn't be proposing a committer for other 
reasons, and you shouldn't be blocking a committer for other reasons.

 

## Instead of just "[DISCUSS] Potential committer XYZ" we discuss every layer

 

Gris (CC'd) outlined this: people go through these phases of relationship with 
our project:

 

1. aware of it

2. interested in it / checking it out

3. using it 

Re: Beam's recent community development work

[Kenneth Knowles]

Thanks for the guidance Ted,

All of your points are well taken. I/we will definitely stay careful about
phrasing encouragement emails and our guidelines.

Kenn

On Sat, Jun 30, 2018 at 8:45 AM Ted Dunning  wrote:

>
> Ken,
>
> This is really good.
>
> I would like to emphasize one nuance, however. That is that when you get
> to the committer consideration step, there is a strong Apache tradition
> that the actual decision about committer-ship is not communicated to the
> candidate to avoid disappointment or campaigning during the vote.
>
> What you have could veer close to that, but I think that what you actually
> have in mind is just fine. I think that there could be a few tweaks to your
> process to emphasize how your efforts are OK.
>
> 1) when you contact a person and mention committer progress, please
> emphasize that it is a bit more like "your efforts have been noticed and
> appreciated. More of that sort of effort is something that often leads to
> becoming a committer. That actual process is confidential, however, so you
> won't know if or when it happens unless you get an invitation to become a
> committer"
>
> 2) the part about "do you want to become one, do you want feedback?" is
> golden just the way it is.
>
> 3) you mention "committer guidelines". This can be dangerous if it gets
> viewed as an application form or committer status checklist. This is a hard
> problem because it helps the PMC to have a list of things that are
> considered good qualities of a committer. I recommend keeping this danger
> in mind when composing emails to candidate committers. Above all else, try
> to avoid having the equivalent of an application form.
>
> Overall, I think that your results speak for themselves. Well done.
>
>
>
> On Fri, Jun 29, 2018 at 11:15 PM Kenneth Knowles  wrote:
>
>> Hi all,
>>
>> The ASF board suggested that we (Beam) share some of what we've been
>> doing for community development with dev@community.apache.org and
>> memb...@apache.org. So here is a long description. I have included
>> d...@beam.apache.org because it is the subject, really, and this is &
>> should be all public knowledge.
>>
>> We would love feedback! We based a lot of this on reading the community
>> project site, and probably could have learned even more with more study.
>>
>> # Background
>>
>> We face two problems in our contributor/committer-base:
>>
>> 1. Not enough committers to review all the code being contributed, in
>> part due to recent departure of a few committers
>> 2. We want our contributor-base (hence committer-base) to be more spread
>> across companies and backgrounds, for the usual Apache reasons. Our user
>> base is not active and varied enough to make this automatic. One solution
>> is to make the right software to get a varied user base, but that is a
>> different thread :-) so instead we have to work hard to build our community
>> around the software we have.
>>
>> # What we did
>>
>> ## Committer guidelines
>>
>> We published committer guidelines [1] for transparency and as an
>> invitation. We start by emphasizing that there are many kinds of
>> contributions, not just code (we have committers from community
>> development, tech writing, training, etc). Then we have three aspects:
>>
>> 1. ASF code of conduct
>> 2. ASF committer responsibilities
>> 3. Beam-specific committer responsibilities
>>
>> The best way to understand is to follow the link at the bottom of this
>> email. The important part is that you shouldn't be proposing a committer
>> for other reasons, and you shouldn't be blocking a committer for other
>> reasons.
>>
>> ## Instead of just "[DISCUSS] Potential committer XYZ" we discuss every
>> layer
>>
>> Gris (CC'd) outlined this: people go through these phases of relationship
>> with our project:
>>
>> 1. aware of it
>> 2. interested in it / checking it out
>> 3. using it for real
>> 4. first-time contributor
>> 5. repeat contributor
>> 6. committer
>> 7. PMC
>>
>> As soon as we notice someone, like a user asking really deep questions,
>> we invite discussion on private@ on how we can move them to the next
>> level of engagement.
>>
>> ## Monthly cadence
>>
>> Every ~month, we call for new discussions and revisit ~all prior
>> discussions. This way we do not forget to keep up this effort.
>>
>> ## Individual discussions
>>
>> For each person we have a separate thread on private@. This ensures we
>> have quality focused discussions that lead to feedback. In collective
>> discussions that we used to do, we often didn't really come up with
>> actionable feedback and ended up not even contacting potential committers
>> to encourage them. And consensus was much less clear.
>>
>> ## Feedback!
>>
>> If someone is brought up for a discussion, that means they got enough
>> attention that we hope to engage them more. But unsolicited feedback is
>> never a good idea. For a potential committer, we did this:
>>
>> 1. Send an email saying something like "you were discussed as a potential
>> 

Re: Speakers and booth support needed at the next Codemotion events

[Piergiorgio Lucidi]

Hi,

Il giorno lun 2 lug 2018 alle ore 16:26 Rich Bowen  ha
scritto:

> I've added these three events to
>
> https://docs.google.com/spreadsheets/d/13qjsoZBFXYz7LDqPLka8Wm4mwdwA3EitTYQBmcYnN5A/edit#gid=0
> and will try to get them into our @apachecommunity twitter schedule
> soon. If you can provide the missing information (basically a URL and a
> twitter handle) that will help. Thanks.
>

I have just added some informations in the spreadsheet.
I should be available to take care of the booth in Milan and also in
Berlin, we actually have Ignasi for Madrid :)

I'll ask if we can send proposals also after the CFP, but anyway I think
that for the keynote we can have more time.

Cheers,
PJ


>
> On 06/27/2018 04:59 AM, Piergiorgio Lucidi wrote:
> > Hi all,
> >
> > I have just received a new email from Mara Marzocchi (Co-founder at
> > Codemotion), they would like to involve us as a Community Sponsor without
> > paying any fee.
> > This means that we can have a dedicated space for a booth and they are
> > asking us to contribute with a keynote session for all of the following
> > events:
> >
> > - Codemotion Berlin 20 / 21 November
> > - Codemotion Milan 29 / 30 November
> > - Codemotion Madrid 30 November - 1 December
> >
> > Our proposals will be submitted to their program committee that will
> > moderate sessions for building the final schedule.
> > We could prepare different proposals and before submitting, we could
> share
> > our ideas with them for eventually improve the final proposal.
> > During the next weeks I can also pass by their office here in Rome to
> > discuss all the details.
> >
> > They are taking care of different topics around technologies, communities
> > and they are asking us also contents related to diversity in tech,
> > inspirational but also InnerSource. We can also participate in the CFP
> for
> > trying to get the opportunity to grab further sessions. They are starting
> > to involve Open Source communities, infact in the last event here in Rome
> > there were some Community spaces and meetup for Google, Elastic, OrientDB
> > and other Open Source communities.
> >
> > We have a wide range of topics that we could submit for Codemotion in
> > addiction to the keynote proposals, consider that they are interested in
> > all of these areas:
> >
> > - Software Architecture
> > - Cloud & Serverless
> > - Big Data
> > - DevOps
> > - Cybersecurity
> > - Blockchain
> > - IoT
> > - AI/Machine Learning
> > - Inspirational
> > - Diversity in Tech
> > - Front-End
> > - Design/UX
> > - AR/MR/VR
> > - Game Dev
> >
> > Link for all the details here:
> >
> https://codemotionworld.com/codemotion-berlin-milan-and-madrid-launch-their-call-for-papers/
> >
> > If we confirm, we should also give them some relevant speaker names for
> the
> > keynote sessions :)
> > They confess me that they are trying to improve the involvement of women
> so
> > it would be great to have a woman for one of the keynotes!
> >
> > What do you think?
> >
> > Cheers,
> > PJ
> >
>
> --
> Rich Bowen - rbo...@rcbowen.com
> http://rcbowen.com/
> @rbowen
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
> --
> Piergiorgio
> 

Re: Speakers and booth support needed at the next Codemotion events

[Rich Bowen]

I've added these three events to 
https://docs.google.com/spreadsheets/d/13qjsoZBFXYz7LDqPLka8Wm4mwdwA3EitTYQBmcYnN5A/edit#gid=0 
and will try to get them into our @apachecommunity twitter schedule 
soon. If you can provide the missing information (basically a URL and a 
twitter handle) that will help. Thanks.


On 06/27/2018 04:59 AM, Piergiorgio Lucidi wrote:

Hi all,

I have just received a new email from Mara Marzocchi (Co-founder at
Codemotion), they would like to involve us as a Community Sponsor without
paying any fee.
This means that we can have a dedicated space for a booth and they are
asking us to contribute with a keynote session for all of the following
events:

- Codemotion Berlin 20 / 21 November
- Codemotion Milan 29 / 30 November
- Codemotion Madrid 30 November - 1 December

Our proposals will be submitted to their program committee that will
moderate sessions for building the final schedule.
We could prepare different proposals and before submitting, we could share
our ideas with them for eventually improve the final proposal.
During the next weeks I can also pass by their office here in Rome to
discuss all the details.

They are taking care of different topics around technologies, communities
and they are asking us also contents related to diversity in tech,
inspirational but also InnerSource. We can also participate in the CFP for
trying to get the opportunity to grab further sessions. They are starting
to involve Open Source communities, infact in the last event here in Rome
there were some Community spaces and meetup for Google, Elastic, OrientDB
and other Open Source communities.

We have a wide range of topics that we could submit for Codemotion in
addiction to the keynote proposals, consider that they are interested in
all of these areas:

- Software Architecture
- Cloud & Serverless
- Big Data
- DevOps
- Cybersecurity
- Blockchain
- IoT
- AI/Machine Learning
- Inspirational
- Diversity in Tech
- Front-End
- Design/UX
- AR/MR/VR
- Game Dev

Link for all the details here:
https://codemotionworld.com/codemotion-berlin-milan-and-madrid-launch-their-call-for-papers/

If we confirm, we should also give them some relevant speaker names for the
keynote sessions :)
They confess me that they are trying to improve the involvement of women so
it would be great to have a woman for one of the keynotes!

What do you think?

Cheers,
PJ



--
Rich Bowen - rbo...@rcbowen.com
http://rcbowen.com/
@rbowen

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Speakers and booth support needed at the next Codemotion events

[Sharan Foga]

Hi PJ

Thanks for following up on this. I think it could be a great opportunity for us 
to promote the ASF and the Apache Way to a whole new audience. 

The CFP deadline for Berlin and Milan is tomorrow (3rd July) and the Madrid 
deadline is 17th July so if you want to submit anything then it needs to be 
done pretty much now :-)

Remember we are also looking for booth volunteers to help out at each of these 
events, so if you are interested then please let us know.

Thanks
Sharan

   

On 2018/06/27 08:59:05, Piergiorgio Lucidi  wrote: 
> Hi all,
> 
> I have just received a new email from Mara Marzocchi (Co-founder at
> Codemotion), they would like to involve us as a Community Sponsor without
> paying any fee.
> This means that we can have a dedicated space for a booth and they are
> asking us to contribute with a keynote session for all of the following
> events:
> 
>- Codemotion Berlin 20 / 21 November
>- Codemotion Milan 29 / 30 November
>- Codemotion Madrid 30 November - 1 December
> 
> Our proposals will be submitted to their program committee that will
> moderate sessions for building the final schedule.
> We could prepare different proposals and before submitting, we could share
> our ideas with them for eventually improve the final proposal.
> During the next weeks I can also pass by their office here in Rome to
> discuss all the details.
> 
> They are taking care of different topics around technologies, communities
> and they are asking us also contents related to diversity in tech,
> inspirational but also InnerSource. We can also participate in the CFP for
> trying to get the opportunity to grab further sessions. They are starting
> to involve Open Source communities, infact in the last event here in Rome
> there were some Community spaces and meetup for Google, Elastic, OrientDB
> and other Open Source communities.
> 
> We have a wide range of topics that we could submit for Codemotion in
> addiction to the keynote proposals, consider that they are interested in
> all of these areas:
> 
>- Software Architecture
>- Cloud & Serverless
>- Big Data
>- DevOps
>- Cybersecurity
>- Blockchain
>- IoT
>- AI/Machine Learning
>- Inspirational
>- Diversity in Tech
>- Front-End
>- Design/UX
>- AR/MR/VR
>- Game Dev
> 
> Link for all the details here:
> https://codemotionworld.com/codemotion-berlin-milan-and-madrid-launch-their-call-for-papers/
> 
> If we confirm, we should also give them some relevant speaker names for the
> keynote sessions :)
> They confess me that they are trying to improve the involvement of women so
> it would be great to have a woman for one of the keynotes!
> 
> What do you think?
> 
> Cheers,
> PJ
> 
> -- 
> Piergiorgio
> 

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Speakers and booth support needed at the next Codemotion events

[Ignasi Barrera]

Thanks for sharing the initiative, PJ!

I can help to staff the booth at the Madrid event, so count on me to
coordinate that if needed. I can do some talks about open source, the
Apache way, or cloud too.


Cheers,

I.


On 27 June 2018 at 10:59, Piergiorgio Lucidi  wrote:

> Hi all,
>
> I have just received a new email from Mara Marzocchi (Co-founder at
> Codemotion), they would like to involve us as a Community Sponsor without
> paying any fee.
> This means that we can have a dedicated space for a booth and they are
> asking us to contribute with a keynote session for all of the following
> events:
>
>- Codemotion Berlin 20 / 21 November
>- Codemotion Milan 29 / 30 November
>- Codemotion Madrid 30 November - 1 December
>
> Our proposals will be submitted to their program committee that will
> moderate sessions for building the final schedule.
> We could prepare different proposals and before submitting, we could share
> our ideas with them for eventually improve the final proposal.
> During the next weeks I can also pass by their office here in Rome to
> discuss all the details.
>
> They are taking care of different topics around technologies, communities
> and they are asking us also contents related to diversity in tech,
> inspirational but also InnerSource. We can also participate in the CFP for
> trying to get the opportunity to grab further sessions. They are starting
> to involve Open Source communities, infact in the last event here in Rome
> there were some Community spaces and meetup for Google, Elastic, OrientDB
> and other Open Source communities.
>
> We have a wide range of topics that we could submit for Codemotion in
> addiction to the keynote proposals, consider that they are interested in
> all of these areas:
>
>- Software Architecture
>- Cloud & Serverless
>- Big Data
>- DevOps
>- Cybersecurity
>- Blockchain
>- IoT
>- AI/Machine Learning
>- Inspirational
>- Diversity in Tech
>- Front-End
>- Design/UX
>- AR/MR/VR
>- Game Dev
>
> Link for all the details here:
> https://codemotionworld.com/codemotion-berlin-milan-and-
> madrid-launch-their-call-for-papers/
>
> If we confirm, we should also give them some relevant speaker names for the
> keynote sessions :)
> They confess me that they are trying to improve the involvement of women so
> it would be great to have a woman for one of the keynotes!
>
> What do you think?
>
> Cheers,
> PJ
>
> --
> Piergiorgio
>

Re: [ANNOUNCE] Apache Dubbo (incubating) Shanghai meetup on June, 23rd

[Huxing Zhang]

Hi,

The Dubbo Shanghai Meetup has been held successfully on June 23rd.

I would like to share some of the statistics:

* Number of registration: ~700
* Number of on site check-in: 300+
* Live stream watches: 1+

Event details: 
https://github.com/apache/incubator-dubbo/wiki/20180623-Shanghai-Meetup
(slides and articles for each topic available)

Cheers!

On Thu, Jun 21, 2018 at 5:16 PM, Huxing Zhang  wrote:
> Hi All,
>
> The Apache Dubbo community is pleased to announce the Shanghai meetup,
> which will be held on June 23rd.
>
> Details can be found here:
> https://github.com/apache/incubator-dubbo/wiki/20180623-Shanghai-Meetup
>
> --
> Best Regards！
> Huxing



-- 
Best Regards！
Huxing

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org