hi Andy, I think it's fine for you to claim the "arrow" or "apache-arrow" real estate on crates.io so no one else does, we just can't call it a "release" unless the artifact (or the source tarball that generates it) goes through the ASF release process.
For Rust, we'll need to decide whether to release on-cycle with the rest of Apache Arrow or release separately like JavaScript is doing. The latter means more release management work (given the velocity of the JavaScript ecosystem we felt it was worth it there). > Is there a github team for the Apache Arrow project? Committers are members of the "apache" GitHub org > Or is there a list of committers that should be the crate owners? As long as one or more PMC members can administer the crate, I think that's fine. That's what we're doing with PyPI and NPM Thanks Wes On Wed, Mar 28, 2018 at 11:08 PM, Andy Grove <[email protected]> wrote: > Assuming the Rust Arrow PR is merged, we will want to start publishing > releases to crates.io at some point. In fact, we should publish the 0.1.0 > sooner rather than later to reserve the name "arrow" as crates.io operates > on a first-come first-served basis. > > For those not familiar with the Rust ecosystem, crates.io is the equivalent > of Java's "maven central" and publishing a project is as simple as running > the "cargo publish" command. > > The first person to publish the crate becomes the crate owner (they have to > authenticate with crates.io via github) but they can add other owners > (github people or teams). > > So, if we don't publish it soon, anyone else could and we would not have > access to the crate and we would have to pick a new name. > > Is there a github team for the Apache Arrow project? If not, should one be > created? Or is there a list of commiters that should be the crate owners? > > Thanks, > > Andy.
