> On 31.03.2017, at 15:07, Rich Bowen <rbo...@rcbowen.com> wrote: > > As you probably know, I have been pondering a (bi?)monthly community > newsletter for some time.
Since it is quite some effort to produce one, it might be a good idea to also get some idea about how well it reaches people. Did you consider (how) to measure the impact of such a newsletter? In an email-based newsletter, you could include a web-bug. Not sure if such a web-bug would be preserved when the mail is archived though. An alternative could be a blog-based newsletter with proper analytics. It would be possible to refer to it easily from Twitter and other channels. One of these channels could also be comitters@a.o. You could probably even include some kind of channel-specific campaign ID to figure out if committes@a.o. is a good channel. Btw. apparently comitters@a.o is not an archived mailing list but an alias [1]. Unless you want the newsletter to be a private thing going only to committers, having a public (blog) spot and pointing people to that might be preferable anyway. Just my 2 cents, -- Richard [1] https://issues.apache.org/jira/browse/INFRA-12068 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
