Facilitating the use of other licenses while still suggesting how to apply them. Thus hoping to avoid creating 'yet another license', while still respecting the contributors work.
Therefore you are not require to follow any of these suggestions, but you must however abide by the requirements of the underlaying license.
The work associated with this license should specify what is the underlaying license.
If non are specified the default license is:
It is quite restrictive so most work use one of these licenses:
You must obey/abide/respect the underlaying license.
The Creative Commons licenses are flexible and simpler to read, but not open source and not designed for software. The Gnu ones are more 'free', but more pedantic and militant.
You may refer to anything licensed with flurdy's license of respect, as only licensed by the underlaying license.
The underlaying license will tell you how to behave legally.
This document will advice you on behaving ethically.
The suggestions are meant to assist people in understanding how the creator would like you to apply the license. And how you can assist others and the creator by respecting these suggestions.
Those who respect these suggestions will be celebrated.
Those who ignore these suggestions may be shunned, cursed a bit, or just responsible for a sigh.
If this work is software related, please consider the license to cover both the source code and the compiled results.
The underlaying license usually define what type of attribution is required.
This is however how the creator expect you to attribute
the work covered by this license.
This is how the creator at least expects to be attributed.
If you do no rely on this work too much, then it is fine to do this.
Include a paragraph in the about page. With relevant links to this license page and the work covered by this license's page.
Include a paragraph in the release notes. With relevant links to this license page and the work covered by this license's page.
A sentence in the reference section. More detail if your work is larger textual document.
If you do rely on this work a lot, then this is how the creator hope you would attribute his work.
A text sentence, tag image or logo link to the project on the front page. More than a paragraph in the about page, perhaps a seperate document about the work and its association with your work.
More than a paragraph in the release notes, perhaps a seperate document about the work and its association with your work. The description of the project it self should perhaps mention this work.
Mention in the introduction. Perhaps some detail on how you work relates to the licensed work. Include a proper url link.
The underlaying license may disallow or dictate how you should distribute this work, and any modification or extensions you build upon and interact with it.
For a license that require you to share your work based on this work, this is how the creator would like you to share it.
Even where sharing is not a requirement, then these are strong suggestions.
If you want to or have made modifications, tweaks, enhancements, alternatives etc of this work, then please share this with us in a proper way.
Submit patches, comment in forums, add tasks, add alternative modules etc., so that others are aware of these modidications.
Hiding it in the deepest darkest corners of your web site is not the easiest way for us or anyone else to find out about it.
If you extend this work, or integrate this with other work, then please share this work with the same license. All or parts of it, or just some of the knowledge you gained from it.
Donations are not required, but they are appreciated.
If you market and attribute well, share and contribute back a lot of work, then that more than compensates for donations.
If you found this work usefull, then compensating the creators time and supporting further work will benefit you as well.
While donations for private individual are not expected, commercial organisation, should consider the value this work contributes to their operation.
Donations depending on how much this work is used.
If you are using this work a lot, depend on it even, then please contribute by makeing a one off donation to the people/organisation/project behind this work.
This should reflect the use and size of your organisation.
Donations depending on how much revenue your organisation make by using this work.
If your product is selling well, and this work is a part of it but maybe not a core part, then still make a donation.
If you are very productive and this work is a core part of the reason for your revenue turn over, then please make a sizable donation.
Please make a recuring donation to reflect the continuing use of this work.
Disclaimer: This was not written by a lawyer, but the Creative Commons or the Free Software Organisation can assist in legal matters.
This is an early version, hence the alpha version state, so some details will be more clearer defined in later versions. Comments, discussions and suggestions are appreciated.
Unless fully released the author reserves the right
to make minor changes to this license version.
Fully released versions require new version number if any changes are made.
The online version of this is at flurdy.com/docs/license/respect/.
The license text itself is licensed under
a
Creative Commons Attribution 2.0 England & Wales License.