Hi Brittany, I gave the newsletter a look, but I still have two questions about it:
1. Who's the intended audience for this newsletter, devs or users? Because I imagine there would probably be a difference in content between the two. Dev news might include infrastructure changes that are irrelevant to users (like news about our testing, or our repo, etc.), as well as mentioning changes that might be in the master branch but have not yet been released. And vice versa, if it's aimed at users it will probably need to be constrained to features that have been released, so users don't expect features they can't actually use yet. 2. Along similar lines, are SDK feature announcements appropriate for this newsletter? (For example, announcing that SplittableDoFn is available for implementing sources in the Go SDK.) If the newsletter is aimed at users, I imagine that new features are probably more appropriate in the Beam release changelog (with maybe some highlights called out here). On the other hand, if it's dev focused, then this seems like a good platform to share progress that we as a community have made on various different projects, I'm just not sure what section would be most appropriate for it. Aside from those two questions, this newsletter looks really cool! I especially like the social media and online engagement sections. For someone like me who rarely pays attention to social media, it's nice to see a summary like that. Thanks, Daniel Oliveira On Mon, Oct 26, 2020 at 11:06 AM Brittany Hermann <[email protected]> wrote: > Hi everyone, > > I am thinking of creating a monthly Beam Community newsletter like this: > https://docs.google.com/document/d/1_t6xKoOQVwgn2edmRVh1ViudmbnNM3BwZyguKAwwjfA/edit?usp=sharing > > My intention would be to send this out once a month. Could you please add > in any updates that you would like to share with the community by 10/28 at > 11:59 pm PST? I am planning to edit and send the final version through the > mailing list on 10/30. > > Thank you! > -Brittany Hermann > > >
