I had had a first read. I'm away without a computer so I'll follow this up with some more detailed feedback in a couple of days.
Another question that came to me is licensing code in blogs, instructional materials, and bookdown books etc. In the past I've created a license file that makes statements about the content being CC-by and code being MIT but again this feels a bit adhoc. It would be good to research a recipie for this.
I think we could also flesh out the structure of the bookdown resource a bit more, providing an indicative chapter structure. I'll have a think about this.
Likewise it might be possible to make some general statements about what our package API might look like.
Have we contacted an ISC member for feedback on the idea yet? I think this is a recommendation they make.
I had had a first read. I'm away without a computer so I'll follow this up with some more detailed feedback in a couple of days.
Another question that came to me is licensing code in blogs, instructional materials, and bookdown books etc. In the past I've created a license file that makes statements about the content being CC-by and code being MIT but again this feels a bit adhoc. It would be good to research a recipie for this.
I think we could also flesh out the structure of the bookdown resource a bit more, providing an indicative chapter structure. I'll have a think about this.
Likewise it might be possible to make some general statements about what our package API might look like.
Have we contacted an ISC member for feedback on the idea yet? I think this is a recommendation they make.