I think if someone wants to build a plugin model for datasets / file
formats (and refactor the existing "built-in" formats to use those
plugin APIs), that sounds like a fine idea to me. I don't think the
idea was for the API to be closed only to the formats that are
implemented inside the Arrow cod
In reviewing the RADOS PR I ran into another question. I recently
sent an email on the topic where the author wants their integration to
be part of the Arrow repo (I believe this is the case for the RADOS
PR). However, what about the case where the author doesn't want to be
part of the Gibhub rep
