3 ms·
About 2-3 hours. In contrast to some other newsletters, I'm actively trying to summarise upstream development and development discussion rather than just linkin
by asb 12y ago
About 2-3 hours. In contrast to some other newsletters, I'm actively trying to summarise upstream development and development discussion rather than just linking to related projects. This involves reading all the mailing list posts and commits. If I came across an interesting project on Github and it's a quiet week for news/blog posts I might save it for later. Otherwise I just include it as it comes. I could certainly do a better job of summarising mailing list discussion, for an in-depth thread on a technical topic it can be very time consuming to do it justice.
- fredleblanc 12y agoThat's great. In my research of what makes a good newsletter, it wholly seems to be a combination of aggregation and curation. Not just collecting links to interesting things, but highlighting what makes them interesting to you, the curator. (From there, it seems that you develop an audience of people that like your point of view).