prepare post about the release of the dev guide

[maelle]

@stefaniebutland is it ok if this gets published on the blog eventually? (or rather as a tech note?) what would be a good date?

We first need to actually release the new book version which would happen at the beginning of next week.

[karthik]

LGTM!

[stefaniebutland]

@maelle I'll suggest a date later today

[stefaniebutland]

I like this as a blog post rather than a tech note. It represents a major, central rOpenSci thing that I think we ought to give attention to.
Can publish 2019-05-16 (Thursday May 16) if that works for you. I already have earlier dates filled on the blog.

• quaterly -> quarterly
• "all of this white on rOpenSci blue" -> "all of this in white on rOpenSci blue" because my first thought was "white" was a typo of "while"
• "features rOpenSci hex logo" -> "features the rOpenSci hex logo"
• "how hard to read the links were in the former color!" -> "how hard it was to read the links in the former color!"
• @IndrajeetPatil -> Indrajeet Patil to be in same format as other people cited
• "including link to examples" -> "including links to examples"
• If "After acceptance" counts as guidance, can it be added as a third item #### under the previous heading? If not, should heading "After acceptance" parallel the former heading like "Updates to ...."?
• "direct users to rOpenSci forum" -> "direct users to the rOpenSci forum"
• "changes brought to" -> "changes incorporated into"
• "also head to the issue tracker!" doesn't quite sound right, so maybe -> "you too can head to the issue tracker!"

[maelle]

Tweet draft.

We've updated our #rstats book - rOpenSci Packages: Development, Maintenance, and Peer Review! 🎉

Highlights:

✨ The book now has a cover! Work by @LockeCreatives.

🔥 We now explicitly accept assignment with =, not only <-.

🔗 Read more: LINK

Image: cover, alt text from the post "cover of rOpenSci dev guide, showing a package production line with small humans discussing, examining and promoting packages"

[stefaniebutland]

will reply to main tweet with thanks to people named in the post

🙏 Thank you to folks who suggested improvements incorporated into the book @rmflight @wmlandau Katrin Leinweber @bikesRdata @patilindrajeets @hadleywickham Kevin Wright. We're listening!

@maelle do you know of twitters for Katrin Leinweber or Kevin Wright?
Did I miss anyone?

[stefaniebutland]

LGreatTM

[maelle]

Great idea to thank contributors in a reply to the first tweet! We're listening even when someone suggests we use LaTeX 😂 (for the PDF export, we had to do that 😿 )

do you know of twitters for Katrin Leinweber or Kevin Wright?

No. @katrinleinweber I don't think you have a Twitter account?

[katrinleinweber]

I sure do, just not obviously connected to my real name. Search for tweets with "github.com/katrinleinweber" ;-> Feel free to @ me in a tweet about the post, but please keep my real name linked to GitHub. Thank you!

[maelle]

Found you! 😉