search

tuura / plato

A DSL for asynchronous circuits specification
Other
12 stars 2 forks source link

No LICENSE file #8

Closed mvdan closed 8 years ago

mvdan commented 8 years ago

I just noticed that none of our repos have a LICENSE file nor are stated to be under any specific license. That means that they are not free software, as per the GitHub rules if I recall correctly.

I would suggest the BSD 3-clause, which is a permissive license (similar to MIT or BSD 2-clause), but which also protects the names of the copyright holders and contributors. It's used in many open source projects nowadays like Tor and Go.

snowleopard commented 8 years ago

Done. Used a standard BSD 3-clause template. Feel free to propose changes if you like.

I'll add the same license in other projects as well.

mvdan commented 8 years ago

SGTM. As long as everyone is fine with giving up their copyright to you :)

snowleopard commented 8 years ago

@mvdan I don't think it is common to explicitly list all contributors in copyright lines -- is there a standard approach to this? Shall it be Tuura team instead? I admit I'm often confused as to how this should work.

mvdan commented 8 years ago

I'd go for Tuura authors, and then listing them in an AUTHORS file as name and e-mail.

See:

https://github.com/golang/go/blob/master/LICENSE https://github.com/golang/go/blob/master/AUTHORS

I know this sounds overly complex, but it's really the easiest way to do it. Another way to do it would be to have a license header per-file with the copyright holders, which you can bet is more verbose and complicated.

I'll only contribute to this repo for now so I'm not worried myself about what you do with the other repos, but you might want to do the same.

snowleopard commented 8 years ago

I'd go for Tuura authors, and then listing them in an AUTHORS file as name and e-mail.

This looks like a good solution, let's use it. (Apparently things get far more complicated when AUTHORS contains companies, which brings CONTRIBUTORS into play. Crazy.)

I wouldn't want to bother with per-file copyright holders.

mvdan commented 8 years ago

Yeah, there is also the world of CLAs and giving up copyright ownership, and things can get ugly.

snowleopard commented 8 years ago

OK, done. @mvdan @jrbeaumont Please add your names and emails you'd like to use to AUTHORS.

mvdan commented 8 years ago

Daniel Martí <mvdan@mvdan.cc>

jrbeaumont commented 8 years ago

jonathan.r.beaumont@googlemail.com

I apologise I would do this myself but I am currently away without any decent access to a computer.

snowleopard commented 8 years ago

@jrbeaumont No problem, I added you to the list.

snowleopard commented 8 years ago

@mvdan I wonder what are the usual rules for qualifying as an author. If I go and add a comment to the Go project, that wouldn't be enough to suddenly get listed as an author, or would it?

mvdan commented 8 years ago

I'm not sure, actually, and it doesn't specify. Anyone having authored a commit seems like the easiest way to do it.

snowleopard commented 8 years ago

Somehow it doesn't feel right, because it devalues the list. But then almost everything about copyright & other IP issues feels wrong, so nothing surprising.