I'd imagine some sort of top-line status report could be a level of detail that would work? Essentially, the main part of the email would be a few bullet points about what's going on, and a secondary part could go into more details on each point or link to further details. I'm imagining the type of report that leadership typically reads in other corporations. Not at the level of detail of board minutes of course.
On Wed, Jun 8, 2022 at 7:32 AM Josh Fischer <j...@joshfischer.io> wrote: > > For sure. Make it the way you think it will be best for readers. > > On Wed, Jun 8, 2022 at 4:28 AM Jarek Potiuk <ja...@potiuk.com> wrote: > > > I am happy to, but I am afraid as chief-editor I will opt for a bit longer > > digest. > > > > BTW. I am thinking on how to experiment and see the actual usefulness of it > > rather than "anecdotal feedback". The fact that few people complained about > > messages being too long, does not mean that the others would not like it a > > bit longer and more useful. I don't know how but will think about it - I > > would love to see some objective, measurable data on it to be able to make > > decisions. > > > > J. > > > > > > On Wed, Jun 8, 2022 at 1:44 AM Josh Fischer <j...@joshfischer.io> wrote: > > > > > The June newsletter was recently sent to members-announce@a.o. > > > > > > Let's target to release the next on July 5, 2022. Anyone want to take > > > point for July? > > > > > > Link for next template is below: > > > > > > https://cwiki.apache.org/confluence/x/Cg31D > > > > > > -- > Sent from A Mobile Device --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
