My thoughts too (and BTW. I think this is great to start discussion before we do it).
I think asking people is one thing which is important, but often you might get answers from people who are outspoken, loud, and have a lot of time - which I think is not the crowd we want to engage. As one of the "loud" people, I see the need of getting others engaged. I think from earlier discussions we see that there is a huge group of people that we miss on and while they might just start reading when they see a positive and "personal" content, it's unlikely they will engage now and tell what they need, I am afraid. I personally think the big point of the idea here is to make people more curious about what's going on, and make them aware that ASF might be a "friendly" and "safe" (but also not welcoming to disruption) environment - one where they will not be afraid to speak and participate (and engage later). This is my "big hairy goal" to achieve at least when I think of it :). I thought a bit about it, I tried to think of what was the best way to make "use" of the loud people we have to get to the "not loud" ones. My proposal/idea (not super well formed though) is - maybe we could reach out to some of those "loud" people like me and ask them directly. We ask them to identify someone in their area of influence who is "not loud", but does some fantastic things (and ask them personally to provide some few paragraph statements of what they are proud of. I think this might be the best way to "make a good use" those loud people (like me) to do community building (this has few nice properties - this might give the "loud" people some achievement, and make them proud that they helped someone to step up, it might show them that they can achieve more positive things by encouraging others and few more things I can think of). This also has the potential of a "snowball" effect as the people who step-up might later encourage others. I am not sure what's the best way to reach out to those "loud" people - but maybe simply reaching out to them personally is best. Almost by definition, we all know who those "loud" people are, we could probably split between ourselves who we reach out to if we know them better or interact with them. That might be a good seed and "test" if we can get something this way. WDYT? J. On Wed, Mar 30, 2022 at 6:35 PM Rich Bowen <rbo...@rcbowen.com> wrote: > > On Tue, 2022-03-29 at 15:51 -0500, Josh Fischer wrote: > > Hey All, > > > > Some random thoughts/questions: > > > > I'm looking at the content on the newsletter page and my first few > > thoughts > > are "I don't know what to include" and probably more important "what > > do > > people want to read?". Would it be helpful to ask readers what they > > want to > > hear about in the newsletter? I see the line "*If you have a message > > to > > send to the membership, join us on the comdev mailing list > > <https://lists.apache.org/list.html?dev@community.apache.org> to find > > out > > how." *It's possible this line already takes care of that question. > > Should > > we try to engage readers via some other means? Whether it be a web > > form or > > something else? If so, how would we go about standing something like > > this > > up? > > While I'm open to anything, I think that keeping this as lightweight as > possible is probably the path to actually succeeding. Perhaps just a > Google Form initially to collect content suggestions. > > I'd also encourage us to keep the newsletter itself as brief as > possible - just the stuff that members *must* know, and possibly links > to places (the blog? project lists?) where they can dig deeper. > > That's, of course, just my opinion, and I am sure that if we are > successful, it will evolve over time. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
