Hi Wes,
Le 29/07/2018 à 01:44, Wes McKinney a écrit : > I believe the best way to remedy the situation is to adopt a > "Community over Code" approach and find a way for the Parquet and > Arrow C++ development communities to operate out of the same code > repository, i.e. the apache/arrow git repository. I think this is reasonable. I think the only reasonably solution would be to migrate the Python Parquet bindings to the parquet-cpp repository, to avoid the circulary dependency (then parquet-cpp would depend on arrow but not the other way round). But I agree the monorepo approach would probably produce the least development friction. >From a community standpoint, I think it all depends whether it's ok to subsume parquet-cpp development under the Arrow umbrella. Perhaps the Apache foundation has to give their approval? I don't know how project governance works. > The only Parquet C++ committer who is not an Arrow committer is Deepak > Majeti. I think the issue of commit privileges could be resolved > without too much difficulty or time. That's an important data point, thanks. Regards Antoine.
