Wes McKinney

You all might look into the experience of the conda-forge community around this, which has automated builds of thousands of Python packages and their C/C++ binary dependencies (including whole compiler...

The next steps would be to collect any Arrow-relevant IP and make a code donation to the Apache Arrow project (like we did with Go http://incubator.apache.org/ip-clearance/arrow-go-library.html and Ruby), then continue...

> In general I find all the legalistic tomfoolery horrifying, but I won't let that stop us unless there actually is some problem here. When you're talking about software redistribution,...

> It would probably be convenient if we could keep a mirror in an Arrow.jl repo somewhere, as that would probably simplify its installation with the Julia package manager, not...

> The julia package manager right now is really built around the notion of one repo per package. Deviating from that will make things a lot more complicated (if it...

> I don't understand the thinking behind why it is so important to have so many languages in that one repo. This project is held together by its inter-language binary...

The relationship between the different Arrow implementations is different from a normal package dependency. We have made deliberate changes to the binary format over the last 2.5 years, and it's...

Building complete binary read and write support and also being able to interface with the JSON integration test format is a sort of big project, I'd guess at least 80...

@ExpandingMan I'd say the sooner we can get the Julia code shepherded into the Apache project, the better; waiting is likely to create more work for the PMC if you...

> As I've said, I don't really see why we'd have $\ge 80$ man-hours of work ahead of us to have a minimal implementation that's useful for IPC and compliant...