Writing September/October newsletter

[gedankenstuecke]

To get the ball rolling, here's the template. What we'd need are news on

• Public board meeting?
• BOSC (@nlharris would you be willing to write up a few words?)
• Event fellowships (last rounds & upcoming ones)
• GSoC: Do we want to recruit someone to help as an org admin? No one reached out after BOSC afaik

[peterjc]

Does the timing make sense to announce our planned public board meeting for OBF officer elections?

[gedankenstuecke]

Yeah, I wondered about that, I guess it depends on how quickly we get this out. Personally I'd be in favour of announcing it through the newsletter too (also gives us a reason to not drag our feet 😉 )

[nlharris]

Yes! We should nail down the date for the public Board meeting and announce it in the newsletter, which should be sent out about two weeks before the meeting. Thank you, Bastian, for volunteering to do the newsletter! I'd be happy to help edit etc.

[gedankenstuecke]

Thanks @nlharris! Are you okay for me to use your BOSC report blog post to make a summarized version for the newsletter? 🙂

[nlharris]

Yes indeed! In fact, I was going to suggest that. 🙂

BTW, if you're ever short of content, I recently put together this page: https://www.open-bio.org/bosc-dei/

[gedankenstuecke]

Thanks amazing, thanks @nlharris!

[gedankenstuecke]

I took a stab at it @nlharris

[nlharris]

looks good. i have minor suggestions but will wait until the newsletter is more complete before doing an editing pass.

[jiywang3]

Would you mind adding the following (with some modification) into the news letter?

In 2023 BOSC Hackathon, iCn3D viewer (https://www.ncbi.nlm.nih.gov/Structure/icn3d/) got a new feature to show isoforms and exons as tracks with the button "Add Track" in the "Sequences & Annotations" window via the menu "Analysis > Sequences & Annotations". One example is at https://structure.ncbi.nlm.nih.gov/icn3d/share.html?pA3pPu7LxdiuZDVX7:

Users can also predict structures from sequences using ESMFold directly in iCn3D via the menu "File > Predict by Seq. > ESMFold". Other features of iCn3D are listed in its GitHub page: https://github.com/ncbi/icn3d.

[nlharris]

Thanks for contributing that, @jiywang3! I think it would be great if the CoFest organizers and participants put together a CoFest 2023 report, with the above and also brief summaries of some of the other CoFest projects. That would be best as a separate document (e.g. a post on the OBF blog), which we could then point to from the newsletter. Flagging @hmenager and @jejust to consider this.

I think adding a detailed, illustrated summary of just one of the CoFest projects is out of scope for the OBF newsletter.

[gedankenstuecke]

Thanks @jiywang3, I've added it as a very brief "project update note" in the respective section. As @nlharris said anything longer would probably be better as its own report on CoFest more broadly (e.g. for the OBF blog!)

[gedankenstuecke]

thanks for the approval @nlharris! I'll be traveling from basically now (sitting at the airport) and won't be fully back online again before the 25th! Which is just to say: If the missing date is fixed while I'm gone it would be amazing if someone else could send it out to not block on me! 🙂

[jejust]

That would be best as a separate document (e.g. a post on the OBF blog), which we could then point to from the newsletter.

I think adding a detailed, illustrated summary of just one of the CoFest projects is out of scope for the OBF newsletter.

I will prepare a draft this week. Even if it's not complete yet, we'll have something to put on the blog and to link from the newsletter.

BTW, I counted 29 physical attendees to the CoFest (based on the registration speadsheet, the left-over badges and counting the persons who popped-up during the event without registering). Ten more persons had registered to attend online.

[gedankenstuecke]

That's great, thanks @jejust!

[nlharris]

The CoFest 2023 report is now published here: https://www.open-bio.org/2023/09/29/bosc-collaborationfest-2023-report/

[gedankenstuecke]

Thanks added in by #36!