* Licencing of plugin code

[ColeValleyGirl]

Can somebody remind me what the licence is that plugins and code snippets are released under? Is it up to the author (and if nothing is stated then the code remains their copyright and can't be reused or modified?) If so I'll start adding a Creative Commons notice to my code...

[Jane]

Code snippets are covered by the CC statement shown at the bottom of the Wiki.

If you want the plugins to be CC I would add it in to be clear.

[tatewise]

I have to admit I'd not given the Code Snippets or Plugin licencing much thought.

The https://creativecommons.org/licenses/by-nc-sa/4.0/ says for Attribution:

You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.

It refers to the https://wiki.creativecommons.org/wiki/L ... ison_chart that goes into more detail.

I think Plugin authors who use Code Snippets need some advice about what should be included in their Plugin to satisfy the Attribution terms, such as details of the creator, attribution parties, copyright notice, licence notice, disclaimer notice, link to the material, etc, etc.

[ColeValleyGirl]

I agree, Mike -- at this point in time it's unclear whether somebody else's plugin is fair game for 'asset stripping' (if anyone wanted anything out of mine, fair play to them although I doubt they will) . Building on a complete plugin to release a new version or a replacement should warrant a discussion with the original author, but what about lifting general 'utility' routines? As in -- oh those 5 lines/50 lines/500 lines are night -- I'll borrow those.

[tatewise]

I also have no great qualms about asset stripping but the terms need to made clearer.
Whilst discussing licencing, does the same apply to the FH Downloads of Queries, Reports, etc, and the Member Web Sites?
Do users who upload to the Wiki need to be made more aware that they are giving away their copyright?

[ColeValleyGirl]

I think the notice at the bottom of the wiki should be sufficient -- especially as the contents are mostly a bit 'specialised' for the general public -- and it allows for 'otherwise noted' -- i.e. reserving rights..(And not everyone used to run a software licencing team... ) I suspect the wiki is a non-issue.

However, plugin code in the plugin store can come up with a general google... Maybe a code snippet to help people construct a licence and a bit of advice about it in the section on writing plugins. Those people who care can then either make stuff available for reuse or restrict it in some way. I don't think it needs to be a big issue -- I was just looking at some code and thinking "wonder if I can use that" and one piece of wondering led to another.

[tatewise]

But should we draw users attention to that notice ~ I have never really noticed it or realised its significance

[ColeValleyGirl]

For plugins, something on the page about writing plugins should be fine (and a snippet to include). For other 'FH downloadables', given that the wiki is promoted as a place to share them... I don't think there's any chance that anyone will worry. (Plus the amount of unique IP in most queries/reports etc. is small, and there is no way to embed a rights statement in them).

I really don't think it's a big deal, but something low-key on the Downloads page should be enough if we need anything at all.

[tatewise]

I was about to add some words to fhugdownloads:index|> Downloads and Links referring users to the terms at the end of the page.
BUT on reflection, if the Downloads can't embed an attribution statement, then the Wiki CC licence terms cannot be fulfilled.
So should the "Except where otherwise noted" escape clause come into play, and some other terms specified?

[ColeValleyGirl]

Mike, re simple downloads I think you're making too much of it -- people upload them to be shared (why else upload them) -- I think the licence's liberal use of 'if supplied' and 'reasonable' are adequate to without anything else being done.

[tatewise]

OK