Add a bit more content to the security chapter

[maelle]

At least a link to the comm call. https://ropensci.org/commcalls/2019-05-07/

[maelle]

Working even a bit more on this chapter would be a huge gain for the guide.

[maelle]

It could be postponed to another release though.

[maelle]

Another topic that might be worth discussing in the chapter is how to handle private keys/other credentials (area where @sckott for instance has a lot of expertise 😉)

• How to protect your users

  • Where to recommend they store the credentials and why
  • Not printing it?
  • In rOpenSci issue template, it's written not to give one's key. If they do tell them.

• As a developer

  • How to share your key with CI systems
  • Consequence of credentials needed for PRs, probably it means some tests have to be skipped, since there's no easy approach https://discuss.ropensci.org/t/github-pat-needed-in-tests-and-pull-requests-on-travis/1550/7

[sckott]

Good idea @maelle

happy to add some info about this. - also should note about testing as well, make sure not to expose credentials in test suites

[maelle]

If you can do a PR it'd be grand. The chapter would only have this subsection for now but it is better than nothing, and an important subsection.

[sckott]

okay

[maelle]

@sckott when you add your subsection make sure to update the summary at the beginning of the chapter ("not fully written" or so) :-)

[sckott]

@maelle

I haven't got around to this yet. right now the chapter looks like:

Do we want to leave that as is? Or leave it out of this next version?

[maelle]

Please leave it as is, it can improve in the next milestone and the links are better than nothing 🙂

[sckott]

sounds good, thanks