Closed andreeaflorescu closed 5 years ago
Could we also add Apache2 license files to the template?
@jiangliu yap, adding it.
Could we also add Apache2 license files to the template?
And the BSD-3 Clause one.
This makes a lot of sense to me.
@sameo about the BSD-3 Clause one: for code that's new and not coming from CrosVM is the BSD-3 clause one required? I would like to better understand this. Probably will drop an email to the rust-vmm email list as well.
I was thinking that for code that comes from CrosVM we need to have Apache + BSD 3 clause, but for code from Firecracker/new code can we have Apache + MIT instead?
BTW, let's first decide if we want a template. We can then create an empty repository and add the template as the first PR. We can comment on the PR on other things we should add to the template.
This is must-to-have repo:)
Should we name this repository crate-template
as it is going to be used only for repositories that are crates?
This LGTM, let's do it.
crate-template
sounds fine to me.
Created repo: https://github.com/rust-vmm/crate-template
Repository Name: rust-vmm-repo-template
Short Description
Proposed repository template here: https://github.com/andreeaflorescu/rust-vmm-repo-template
The template is still WIP because I didn't give it much thought, so I will probably update it. GitHub blogpost about repository templates: https://github.blog/2019-06-06-generate-new-repositories-with-repository-templates/
Why is this crate relevant to the rust-vmm project?
This repository will be a template for all repositories added to rust-vmm. This should speed up creating new projects in rust-vmm.