David Anthoff

I'm not really convinced that moving the code into the main arrow repo is a good idea. Here are some issues I see: - The julia package manager right now...

> I don't see why packaging and development process need to be tightly coupled. Well, it is on julia, for all practical purposes. > You only need to update the...

Maybe the best strategy would be to get the test stuff up and running first, and once julia 1.0 is released (I mean the final version, not the alpha), take...

Does anyone know what `]dev Arrow` would do if the code was in the mono-repo?

I think the ``RecordBatch`` and then the ``Buffer`` are essentially the pointers to the data? But yes, that whole writing seems not super clear... I think the Feather format is...

Maybe one can figure it out by looking at existing implementations? The Typescript one is probably easy to digest.

> de-register this Arrow.jl > if you have a full working version, we can make sure that Arrow.jl is registered to that I don't think these are options, even with...

Just to second that, code coverage right now is sparse :) https://codecov.io/gh/ExpandingMan/Arrow.jl

There is also a story for this via FileIO.jl: if your figure object implements ``show`` methods for SVG, PNG, PDF or EPS, it automatically hooks into the FileIO.jl ``save`` method,...

No, it just gives us a shared ``saved`` method that lots and lots of packages can use, that is pretty much it.