I just added the CFP information about ApacheCon Asia 2022. Hope I can catch up with the train this month.
Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, May 2, 2022 at 11:03 PM Josh Fischer <j...@joshfischer.io> wrote: > > Gotcha. I’ll send it out tomorrow! > > On Mon, May 2, 2022 at 9:49 AM Sam Ruby <ru...@intertwingly.net> wrote: > > > On Mon, May 2, 2022 at 10:39 AM Josh Fischer <j...@joshfischer.io> wrote: > > > > > > I remember us agreeing to send it out on May 5. Since I'm not a member, > > > I'll leave that up to either Rich or Sam to send out. > > > > I had sent the last one out on the first Tuesday of the month, which > > happened to be the 5th last month. I'd recommend following a similar > > pattern as that will avoid weekends. For some months, this may need > > to be adjusted for holidays. > > > > To me, one of the purposes of this exercise is to see if someone other > > than the usual hyper-volunteers steps up, so I won't be sending the > > email. > > > > But I am a moderator for that list, and if I see content that matches > > the wiki page in the moderation queue this week, I will approve it. > > Whether the person sending it is an ASF member or not won't affect > > whether or not I approve the content. > > > > - Sam Ruby > > > > > Thank ya > > > > > > On Mon, May 2, 2022 at 9:21 AM Rich Bowen <rbo...@rcbowen.com> wrote: > > > > > > > The last one we sent, Sam sent directly to the members-notify list - > > > > which does, indeed, need to be done by a member. > > > > > > > > I've added one more (member-specific) item to the highlights. I feel > > > > like we're missing something important, but I cannot remember what it > > > > is. > > > > > > > > What is our send date? > > > > > > > > On Mon, 2022-05-02 at 08:57 -0500, Josh Fischer wrote: > > > > > The newsletter has been updated and just about ready for sending > > > > > out.. Not > > > > > sure of the whos or hows of getting this across the foundation. Is > > > > > there > > > > > a preferred way that I can get this distributed? Is this something > > > > > only > > > > > a member can/should do? > > > > > > > > > > On Wed, Apr 20, 2022 at 4:20 PM Josh Fischer <j...@joshfischer.io> > > > > > wrote: > > > > > > > > > > > We have room for another bullet point or two if anyone wants to add > > > > > > anything to the critical committer communications letter. We have > > > > > > about > > > > > > two weeks before it will be sent out. Link below. > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=210078929 > > > > > > > > > > > > - Josh > > > > > > > > > > > > On Tue, Apr 5, 2022 at 9:32 AM Sam Ruby <ru...@intertwingly.net> > > > > > > wrote: > > > > > > > > > > > > > On Tue, Apr 5, 2022 at 10:30 AM Josh Fischer > > > > > > > <j...@joshfischer.io> wrote: > > > > > > > > > > > > > > > > Created a starter with a few fun facts here: > > > > > > > > https://cwiki.apache.org/confluence/x/0YyFD > > > > > > > > > > > > > > > > Feel free to add or take away as you see fit. > > > > > > > > > > > > > > THANK YOU! > > > > > > > > > > > > > > > - Josh > > > > > > > > > > > > > > - Sam Ruby > > > > > > > > > > > > > > > On Tue, Apr 5, 2022 at 8:40 AM Sam Ruby > > > > > > > > <ru...@intertwingly.net> wrote: > > > > > > > > > > > > > > > > > Message has been posted. Next time it probably should be a > > > > > > > > > pure plain > > > > > > > > > text version. > > > > > > > > > > > > > > > > > > Anybody want to get started on May? Create the wiki page, > > > > > > > > > put some > > > > > > > > > content there, and then send it out the first week in May > > > > > > > > > after others > > > > > > > > > have been given the opportunity to contribute. > > > > > > > > > > > > > > > > > > - Sam Ruby > > > > > > > > > > > > > > > > > > On Thu, Mar 10, 2022 at 10:01 AM Rich Bowen > > > > > > > > > <rbo...@rcbowen.com> > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > 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 > > > > -- > Sent from A Mobile Device --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
