As we wrap up the Python RSE, I've been thinking about the next steps.
The main thing I'm thinking is that, since
many of you will probably be tired out from doing the Python volume,
the R people (e.g. myself) haven't felt like we've been able to contribute as fully as the Python people, and
the R people will likely be doing most of the R RSE volume,
that the three R people (@cwickham, @k8hertweck, who also agree with this plan) take the lead on the R RSE book and act as the core team. So we take responsibility and make final decisions on the content of the R RSE book.
As usual, others can contribute as has been done with the Python RSE, the difference being that final decisions on the book are made by the core team. The biggest reason for this is to speed things up and get the next volume out faster. Basically, we each trust the decisions of the others in the core team and don't need to explicitly agree with a change or suggestion (i.e. silence is approval), though still recording the change if major. If a disagreement does arise, then we address it within the core team (preferably unanimously), with advice from others.
This isn't to say we are splitting off, more to make things more efficient and to speed things up.
The next biggest change is we will be moving the R RSE development over into a new repository, so we don't cloud the Python RSE final editing, nor disrupt the book and website build process. I'll be adding and pinning some overview Issues in the new repo for some new changes to doing things for those that are interested in contributing.
As we wrap up the Python RSE, I've been thinking about the next steps.
The main thing I'm thinking is that, since
that the three R people (@cwickham, @k8hertweck, who also agree with this plan) take the lead on the R RSE book and act as the core team. So we take responsibility and make final decisions on the content of the R RSE book.
As usual, others can contribute as has been done with the Python RSE, the difference being that final decisions on the book are made by the core team. The biggest reason for this is to speed things up and get the next volume out faster. Basically, we each trust the decisions of the others in the core team and don't need to explicitly agree with a change or suggestion (i.e. silence is approval), though still recording the change if major. If a disagreement does arise, then we address it within the core team (preferably unanimously), with advice from others.
This isn't to say we are splitting off, more to make things more efficient and to speed things up.
The next biggest change is we will be moving the R RSE development over into a new repository, so we don't cloud the Python RSE final editing, nor disrupt the book and website build process. I'll be adding and pinning some overview Issues in the new repo for some new changes to doing things for those that are interested in contributing.