search

phpoxford / spires-irc

Spires IRC client and mock server.
MIT License
0 stars 4 forks source link

License needed #1

Closed olorton closed 8 years ago

olorton commented 8 years ago

Obviously open source, but which?

ascii-soup commented 8 years ago

For this library, I'm wondering if we should go with something like "Feel free to use it in open source software but not commercial software." - my knowledge of licenses is pretty thin, so does anyone know what that type of license might be?

olorton commented 8 years ago

When it comes to FOSS licenses I'm more of a fan of:

The reason for this is with both of these, there can be ambiguity, people get confused by these things. I'd rather others used our stuff and we don't need to worry about people breaching the license agreement.

I'd be interested to hear arguments against this though. I don't actually care about the licensee, I just don't like using other people's code if I cannot work out if I am breaching the license or not.

martindilling commented 8 years ago

I usually go with https://opensource.org/licenses/MIT, mostly because it's open for whatever and it's very easy to understand ;)

liquorvicar commented 8 years ago

Would be happy to go with MIT although do we want to keep some kind of attribution in case of any derived projects/forks etc? (Or is that what @olorton calls "infectious"?)

garethellis36 commented 8 years ago

Happy to go with whatever.

olorton commented 8 years ago

@liquorvicar MIT is attribution friendly. See http://choosealicense.com/

The MIT License is a permissive license that is short and to the point. It lets people do anything they want with your code as long as they provide attribution back to you and don’t hold you liable.

I suggest we also agree on if, what, or how we want to include the (c) notice.

    <?php

    /**
     * Copyright (c) 2016 The PHP Oxford User Group (github.com/phpoxford/spires)
     * License: MIT (github.com/phpoxford/spires/LICENSE.md)
     */
ascii-soup commented 8 years ago

It's probably a good idea to include both a LICENSE file and include it in each file header. It's probably worth us adding a guide on proper attribution (something people can copy/paste to attribute)

olorton commented 8 years ago

+1 @ascii-soup let's do both, where should we document the proper attribution, in the readme, contributing, both, or elsewhere?

olorton commented 8 years ago

Is everyone happy with this, my PR is prepared.