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? On Tue, Mar 29, 2022 at 10:30 AM Rich Bowen <rbo...@rcbowen.com> wrote: > FYI, as some of you are aware, I started a new job earlier this month, > and that is consuming *all* of my brain-cycles. If someone else wanted > to step up and start organizing the April newsletter, that would be > great - although we're alreay behind schedule for that. Failing that, > it seems more likely that I would be able to be involved in a May > newsletter. Please don't think that this has to be led by me - ideally, > we'd each take turns as editor-in-chief, rather than create yet another > SPOF. Thanks. > > On Thu, 2022-03-10 at 10:00 -0500, Rich Bowen wrote: > > Problem: Members (and, more generally, committers) are less engaged > > with > > the larger Foundation than at any point in our history. Meanwhile, > > the > > mechanisms for getting more engaged (eg, the members mailing list) > > are a > > firehose of unrelated content that is very frustrating to the casual > > participant - even those who desire a deeper engagement - and, in > > practice, are completely off-putting. Committers, meanwhile, have no > > real avenue, outside of their project, for further engagement. > > > > I've been struggling with ways to address this for years, and they > > all > > tend to founder on the rocks of "People should just be doing X!" > > which, > > in each case, is true, but also dismissive and ultimately unhelpful. > > > > I would like to propose that we are more proactive about reaching out > > to > > our community in tiny, consumable bites, that hint at a larger feast > > that they're missing out on. > > > > Here's my proposal, but I cannot (and will not) tackle this alone, > > because that guarantees failure, which guaranteed less participation > > the > > next time we suggest something like this. > > > > Proposal/Brainstorming doc: https://hackmd.io/JaLaGy56T8qT3ODABLVswA > > > > It's an intentionally simple idea - a minimum viable idea, one might > > say. > > > > I want to know who's going to help make it a reality. Not > > particularly > > interested in "that's a great idea", as much as "I will help make it > > happen." > > > > This will involve engagement with Events, M&P, and Board, at a > > minimum, > > but over time we'd hopefully engage everyone at the Foundation in > > content creation. But, even then, I want to keep this tiny and > > consumable - content that you can absorb in 2-5 minutes, always with > > a > > "to get more engaged ..." call to action aspect to it. > > > > Come help me develop community. > > > > --Rich > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
