Hi Robert,
The way I thought about the newsletter is, as you propose, to put the minimal amount of information to catch people’s interest, and then send them a unified PDF (testing HDF5+testing Zarr+how to use the treatment package) with essentially a tutorial that first presents a replicable example and then opens to an integration in existing codes to get an initial feedback.
For the newsletter, I can technically wait as long as I want but because the deadline for abstract submission to BioBrillouin falls on October 1st, I think it would be best not too wait too long either (although most people might not need the reminder). I was therefore thinking of sending the newsletter by the end of the week. Since we’ll then send people the PDF, this would buy at least 1 and potentially 2 weeks for fixing the bugs you have found in your code and writing your steps to test your solutions.
Following Kareem’s idea, I’ve put together a list of questions (cf. document attached) we could build on to ask people for feedback. Don’t hesitate to modify it!
Best,
Pierre
Pierre Bouvet, PhD
Post-doctoral Fellow
Medical University Vienna
Department of Anatomy and Cell Biology
Wahringer Straße 13, 1090 Wien, Austria