Re: [DISCUSS] State of the project: Community growth

[Kenneth Knowles]

On Tue, Jan 23, 2018 at 4:50 PM, Robert Bradshaw 
wrote:

> +1 to having a "beginner" label. Actually, we have one, but it's
> hardly used: https://issues.apache.org/jira/browse/BEAM-1565?jql=
> project%20%3D%20BEAM%20AND%20labels%20%3D%20beginner%
> 20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> and is hard to discover. We should probably link to the Jira search
> itself.
>

+1! I had thought we were standardizing around "starter" but actually I
didn't choose it and I don't think it is a great name. In the very early
days I tagged them with every label I could think of, like "beginner" and
"newbie" also. I thought we had a link to it... if we don't, we should, and
if we do it should be really loud.

Kenn

Re: [DISCUSS] State of the project: Community growth

[Robert Bradshaw]

+1 to having a "beginner" label. Actually, we have one, but it's
hardly used: 
https://issues.apache.org/jira/browse/BEAM-1565?jql=project%20%3D%20BEAM%20AND%20labels%20%3D%20beginner%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
and is hard to discover. We should probably link to the Jira search
itself.

I also like the idea of cross-branding, e.g. when we write a connector
to X, it might be worth having a callout on X's site about it as well
as our own.

I think we're doing well on events, but +1 to having an
easy-to-discover common calendar to find them.

In my experience the key to getting more users is to have happy users,
and best happy users that talk. We should consider inviting users to
do blog posts, etc. (which tend to be very technically focused).


On Tue, Jan 16, 2018 at 8:30 AM, Ismaël Mejía  wrote:
> Some ideas I have around the issues mentioned before:
>
> * Annual User Survey
>
> One important thing we should do is some sort of annual survey of
> users to have some feedback on the state of the Beam from the users
> point of view, we can take for example as a template the survey done
> by the Rust community or others, and maybe run it like we did for the
> Java 8 poll on twitter.
>
> https://blog.rust-lang.org/2017/09/05/Rust-2017-Survey-Results.html
>
> * An event webpage / calendar
>
> So everyone who organizes an event can add their events there and we
> can also share them in advance in the mailing lists.
>
> Regards,
> Ismaël
>
> On Tue, Jan 16, 2018 at 4:17 AM, Austin Bennett
>  wrote:
>> Think that Beam's great, so happy to grow community -- by my individual
>> involvement and to encourage others.
>>
>> 1). Users:  I think that this can follow from the others being done well
>> 2).  Contributors: some other projects mark very simple contributions for
>> newcomers to find as onramping.  Hadn't noticed that here in the little I
>> had explored.
>> 3-5). Community/Event/Brand:  Beam is inherently collaborative given its
>> model and what I understand of purpose (different runners, batch/stream,
>> etc).  An easy place to start will be places that play very well and/or
>> integrate with.
>>
>>
>>
>> On Mon, Jan 15, 2018 at 3:27 PM, Griselda Cuevas  wrote:
>>>
>>> Hi Everyone,
>>>
>>>
>>> Thanks Davor for starting the discussion around the state of the Apache
>>> Beam in 2017[1]. In this fork of that conversation, I’d like to continue the
>>> dialogue around how should we grow our community in alignment to the
>>> project's vision, goals & values.
>>>
>>>
>>> Here are some areas and prompts to guide the conversation. If there are
>>> other ideas related to community growth missing here, please add them in
>>> this thread as well.
>>>
>>> New users: How could the community help potential and new users learn
>>> about Beam? How can we support questions from users better?
>>>
>>> New contributors: What are our contributions Best Practices and how can we
>>> share them with new members? How could the community help new contributors
>>> ramp up faster in our Project’s dev environment? How could we empower new
>>> developers to contribute to Beam’s core features?
>>>
>>> Community engagement: What type of activities and efforts would you like
>>> to see to increase our community engagement?
>>>
>>> Events: What events should we attend? What events should we sponsor? How
>>> could we support community led events better?
>>>
>>> Brand building: What efforts do you think we should do to build our brand?
>>> What use cases, ideas, talks, etc. should we collaborate on to give the
>>> project more visibility?
>>>
>>>
>>> If there’s interest, I’d also be happy to host a virtual meeting for
>>> anyone who’d prefer that avenue of discussion and will make sure that any
>>> new ideas or details are brought back to the discussion threads after that.
>>> Express interest in a virtual meeting in this thread so I can coordinate.
>>>
>>>
>>> Thanks, and let’s make this an exciting community!
>>>
>>> Gris Cuevas
>>>
>>>
>>>
>>> [1]https://lists.apache.org/thread.html/f750f288af8dab3f468b869bf5a3f473094f4764db419567f33805d0@%3Cdev.beam.apache.org%3E
>>
>>

Re: [DISCUSS] State of the project: Community growth

[Ismaël Mejía]

Some ideas I have around the issues mentioned before:

* Annual User Survey

One important thing we should do is some sort of annual survey of
users to have some feedback on the state of the Beam from the users
point of view, we can take for example as a template the survey done
by the Rust community or others, and maybe run it like we did for the
Java 8 poll on twitter.

https://blog.rust-lang.org/2017/09/05/Rust-2017-Survey-Results.html

* An event webpage / calendar

So everyone who organizes an event can add their events there and we
can also share them in advance in the mailing lists.

Regards,
Ismaël

On Tue, Jan 16, 2018 at 4:17 AM, Austin Bennett
 wrote:
> Think that Beam's great, so happy to grow community -- by my individual
> involvement and to encourage others.
>
> 1). Users:  I think that this can follow from the others being done well
> 2).  Contributors: some other projects mark very simple contributions for
> newcomers to find as onramping.  Hadn't noticed that here in the little I
> had explored.
> 3-5). Community/Event/Brand:  Beam is inherently collaborative given its
> model and what I understand of purpose (different runners, batch/stream,
> etc).  An easy place to start will be places that play very well and/or
> integrate with.
>
>
>
> On Mon, Jan 15, 2018 at 3:27 PM, Griselda Cuevas  wrote:
>>
>> Hi Everyone,
>>
>>
>> Thanks Davor for starting the discussion around the state of the Apache
>> Beam in 2017[1]. In this fork of that conversation, I’d like to continue the
>> dialogue around how should we grow our community in alignment to the
>> project's vision, goals & values.
>>
>>
>> Here are some areas and prompts to guide the conversation. If there are
>> other ideas related to community growth missing here, please add them in
>> this thread as well.
>>
>> New users: How could the community help potential and new users learn
>> about Beam? How can we support questions from users better?
>>
>> New contributors: What are our contributions Best Practices and how can we
>> share them with new members? How could the community help new contributors
>> ramp up faster in our Project’s dev environment? How could we empower new
>> developers to contribute to Beam’s core features?
>>
>> Community engagement: What type of activities and efforts would you like
>> to see to increase our community engagement?
>>
>> Events: What events should we attend? What events should we sponsor? How
>> could we support community led events better?
>>
>> Brand building: What efforts do you think we should do to build our brand?
>> What use cases, ideas, talks, etc. should we collaborate on to give the
>> project more visibility?
>>
>>
>> If there’s interest, I’d also be happy to host a virtual meeting for
>> anyone who’d prefer that avenue of discussion and will make sure that any
>> new ideas or details are brought back to the discussion threads after that.
>> Express interest in a virtual meeting in this thread so I can coordinate.
>>
>>
>> Thanks, and let’s make this an exciting community!
>>
>> Gris Cuevas
>>
>>
>>
>> [1]https://lists.apache.org/thread.html/f750f288af8dab3f468b869bf5a3f473094f4764db419567f33805d0@%3Cdev.beam.apache.org%3E
>
>

Re: [DISCUSS] State of the project: Community growth

[Austin Bennett]

Think that Beam's great, so happy to grow community -- by my individual
involvement and to encourage others.

1). Users:  I think that this can follow from the others being done well
2).  Contributors: some other projects mark very simple contributions for
newcomers to find as onramping.  Hadn't noticed that here in the little I
had explored.
3-5). Community/Event/Brand:  Beam is inherently collaborative given its
model and what I understand of purpose (different runners, batch/stream,
etc).  An easy place to start will be places that play very well and/or
integrate with.



On Mon, Jan 15, 2018 at 3:27 PM, Griselda Cuevas  wrote:

>
>
>
>
>
>
>
> *Hi Everyone, Thanks Davor for starting the discussion around the state of
> the Apache Beam in 2017[1]. In this fork of that conversation, I’d like to
> continue the dialogue around how should we grow our community in alignment
> to the project's vision, goals & values.Here are some areas and prompts to
> guide the conversation. If there are other ideas related to community
> growth missing here, please add them in this thread as well. 1. New users:
> How could the community help potential and new users learn about Beam? How
> can we support questions from users better?2. New contributors: What are
> our contributions Best Practices and how can we share them with new
> members? How could the community help new contributors ramp up faster in
> our Project’s dev environment? How could we empower new developers to
> contribute to Beam’s core features? 3. Community engagement: What type of
> activities and efforts would you like to see to increase our community
> engagement?4. Events: What events should we attend? What events should we
> sponsor? How could we support community led events better?5. Brand
> building: What efforts do you think we should do to build our brand? What
> use cases, ideas, talks, etc. should we collaborate on to give the project
> more visibility?If there’s interest, I’d also be happy to host a virtual
> meeting for anyone who’d prefer that avenue of discussion and will make
> sure that any new ideas or details are brought back to the discussion
> threads after that. Express interest in a virtual meeting in this thread so
> I can coordinate.Thanks, and let’s make this an exciting community!Gris
> Cuevas[1]https://lists.apache.org/thread.html/f750f288af8dab3f468b869bf5a3f473094f4764db419567f33805d0@%3Cdev.beam.apache.org%3E
> *
>

[DISCUSS] State of the project: Community growth

[Griselda Cuevas]

*Hi Everyone, Thanks Davor for starting the discussion around the state of
the Apache Beam in 2017[1]. In this fork of that conversation, I’d like to
continue the dialogue around how should we grow our community in alignment
to the project's vision, goals & values.Here are some areas and prompts to
guide the conversation. If there are other ideas related to community
growth missing here, please add them in this thread as well. 1. New users:
How could the community help potential and new users learn about Beam? How
can we support questions from users better?2. New contributors: What are
our contributions Best Practices and how can we share them with new
members? How could the community help new contributors ramp up faster in
our Project’s dev environment? How could we empower new developers to
contribute to Beam’s core features? 3. Community engagement: What type of
activities and efforts would you like to see to increase our community
engagement?4. Events: What events should we attend? What events should we
sponsor? How could we support community led events better?5. Brand
building: What efforts do you think we should do to build our brand? What
use cases, ideas, talks, etc. should we collaborate on to give the project
more visibility?If there’s interest, I’d also be happy to host a virtual
meeting for anyone who’d prefer that avenue of discussion and will make
sure that any new ideas or details are brought back to the discussion
threads after that. Express interest in a virtual meeting in this thread so
I can coordinate.Thanks, and let’s make this an exciting community!Gris
Cuevas[1]https://lists.apache.org/thread.html/f750f288af8dab3f468b869bf5a3f473094f4764db419567f33805d0@%3Cdev.beam.apache.org%3E
*