[Rust-VMM] GitHub organization
fandree at amazon.com
Wed Jan 9 09:20:04 UTC 2019
My personal preference is to have one repository per crate. I am also not aware of other rust crates (published on crates.io) that share the same repository. It would be interesting to find if such projects exist to see how easy it is to publish the crates and make sure that you don't mess up versions. Another reason I would like to have them as separate crates is because I assume that not all rust-vmms (e.g. Firecracker) will use all crates in rust-vmm.
When we get to a "critical mass" of crates that can be used to create a VMM, we can also create a vmm repo that uses all the independent crates.
What do you say?
From: Josh Triplett <josh at joshtriplett.org>
Sent: Tuesday, January 8, 2019 10:28 PM
To: Samuel Ortiz
Cc: rust-vmm ML
Subject: Re: [Rust-VMM] GitHub organization
On Tue, Jan 08, 2019 at 09:42:43AM +0100, Samuel Ortiz wrote:
> Jonathan and I created a rust-vmm GitHub organization for hosting the
> potential crates and project related to this project:
> The initial goal for this org is to be a collaboration ground for new
> crates. We should collectively decide how it gets organized in terms of
> teams, repos and rights. At the moment Jonathan and myself are the 2
> admins, but that can be changed at any time.
> Please let me know if you'd like to be added as a member of this new
Please add me, and I'd be happy to help with this.
I would suggest that we either have one repo per crate, or one repo with
a workspace setup that builds (and tests) all crates. The former makes
it easier to work with individual crates, but harder to coordinate
changes across all of them. The latter makes it easier to make
cross-crate changes, but harder to remember things like updating
versions and dependencies correctly.
Rust-vmm mailing list
Rust-vmm at lists.opendev.org
Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
More information about the Rust-vmm