Any word on this?

I'm a part of another community that wants to adopt a similar RFC process to that used in the Rust community, but I noticed that the rust-lang/rfcs repo does not seem to have a license by which we could appropriately copy and attribute your work.

One additional wrinkle for this repo might be that the RFCs themselves might need a different license than that of the description of the process for contributing. For example, you might want to use the same license as Rust for the RFCs themselves, while using a Creative Commons license of some kind for the description of the process.

As a nifty side-note, coincidentally, @edunham is one of the people who led me here, as I went to her LFNW 2016 talk on "Rust's Community Automation" because I'm trying to guide a growing language community for Pony.

Does this repo need a LICENSE or COPYING file? #1259

Description

edunhamopenedon Aug 17, 2015

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

edunham
openedon Aug 17, 2015