big +1 to host the new letter draft to the wiki so every member can add some news on that.
Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Mar 31, 2022 at 4:08 AM Sam Ruby <ru...@intertwingly.net> wrote: > > On Tue, Mar 22, 2022 at 12:46 PM Rich Bowen <rbo...@rcbowen.com> wrote: > > > > Ok, looks like we have three volunteers - Josh Fisher, Dave Fisher, and > > Andrew Wetmore. So I don't feel like I'm doing this alone, which is > > good. > > > > What we need to do still is: > > > > 1) Pitch this to the membership to determine whether this should land > > on members@ or members-notify@ > > 2) Write sample newsletter: https://hackmd.io/0eeIQ7wDQnKr-LAgN6QqLA > > 3) Figure out intake tooling (could just be a Google Form) for getting > > content in > > 4) Figure out our schedule/deadlines to ensure that we get this out in > > a predictable cadence. > > > > I'm going to draft a proposal to send to members@ (probably won't > > happen today) and run it back past this thread, unless someone beats me > > to it. > > I'm a big fan of Cunninham's law: > https://meta.wikimedia.org/wiki/Cunningham%27s_Law > > Accordingly, I've taken the sample newsletter and posted it here: > https://cwiki.apache.org/confluence/display/ASFP/Member+Moment+-+April+2022 > > I've changed March to April. Added a mention of the June members > meeting. Changed the link to the ASF board meeting to the April > meeting. Added a link to the whimsy page that tracks members watch. > > The advantage of the "ASFP" wiki is that it is member private and all > ASF members have update access. > > Unless there is a strong objection or better proposal the content of > that page as it exists on April 5th will be sent to > members-notify,subject to approval by Joe Brockmeier. > > - Sam Ruby > > > --Rich > > > > 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 > > > > --------------------------------------------------------------------- > 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
