Strategizing

[r-barnes]

For various discussions regarding the direction of the project.

I think the current note is that DGGRIDv8 has changed its API. I haven't fixed up the code rewriters that pull from upstream, so we're not tracking upstream at the moment. That's probably okay for a bit, though #70 asks about that.

@SebKrantz and @edzer have collaborator access to the repo which, I think, should give them the ability to make merges without having to loop me in.

CC: @SebKrantz @edzer @sahrk

[SebKrantz]

@r-barnes do you want to remain the CRAN maintainer? Otherwise I'd be willing to take that over (assuming that @edzer is not interested?) to handle smaller releases like the present one without your necessary involvement. In that case, the repository policy states:

"When a new maintainer wishes to take over a package, this should be accompanied by the written agreement of the previous maintainer (unless the package has been formally orphaned)."

In this case I would suggest that you submit 3.1.0 to CRAN, indicating me as the maintainer in the description, and replying to the submission e-mail copying me in at [email protected] and communicating the change of maintainer. But let me know what your thoughts are on this.