Flowstone Guru Download area

[Nubeat7]

@Nubeat 7 thanks yes that could be a starting point.

for me point 2 would be important:
"2) Express forbidden uses
The licensee is not allowed to sell, share or provide any of the provided Flowstone modules and codes, partially or wholly, in its original or altered form, to other people."

I wouldn't necessarily mind people selling there work that contained some of mine as long as the majority was theirs and it was clear they wasn't just trying to profit from my freely available work.
So for me the area is a bit gray around this.
I wouldn't be happy with something overly strict, the main benefit of a licence as far as Flowstone Guru and modules go is making a credit to the author required or making clear that if you are going to charge for work your contribution should be very significant.

So really it a balancing act I don't want to write something overly restrictive but also don't want something that just says "Do what the hell you want" although some might be OK with that, but I bet they would think again if someone just re skinned there work and made money off it.

what i meant with that is notthe app what someone builds with it, its about the modules and codes itself, so that it is clear that nobody sells or share any modules on other sites without permission..

and licensor should not be liable for anything.

sure, it wouldn't fit here

as said this is for payed work so its pretty 'hard', also all the local suff cannot used for it after the devs are from different countries, its just to give the one or other idea

[Perfect Human Interface]

From my perspective it seems that usually sites that offer free goodies like this have some set common licenses like Creative Commons etc. that can be explained in a line or two but can also be looked up for a more in-depth explanation.

I just really think giving people the option to choose the license for their stuff in this case isn't the way to go. That may sound crazy, but some of those licenses can be very frustrating and limiting and even complicated, even though they look like a really good idea to the author. Everything would be so much easier if there was one and only one license across the whole site.

[JB_AU]

Conditions of use for provision of Flowstone(tm) modules and code(s):
Preamble
In the capacity as legal proprietor, {developers name & address} (hereafter "the licensor") grants the licensee of any {developer's} software, including all integral parts thereof pursuant to clause 1 of this agreement (hereafter "software"), the right to use the software. The licensee may use this software solely in accordance with the following conditions.
1) Purpose
The licensee is allowed to use and change the provided Flowstone module(s) and all included code(s) inside their own products, as the end user likes.
2) Express forbidden uses
The licensee is not allowed to sell, share or provide any of the provided Flowstone module(s) and code(s), partially or wholly, in its original or altered form, except where written consent from the originating author is allowed.
3) Breach of License; Forfeiture
A. If the licensee breaches the conditions of this licensing agreement, all rights of use granted will expire. In this case, the user will be required to immediately destroy the original software and any back-up copies or, if requested, return them to the licensor. Installations and electronically stored copies are to be deleted in such a way that they cannot be recreated or restored.
B. The licensee is liable to the licensor for all damage arising from breaches of this agreement.
4) Liability of the licensor ??? (say what? jumble )
A. The licensor is liable in cases of intent and gross negligence as provided by law. The licensor is also liable in case of negligent breaches of duty whose fulfillment makes possible the due performance of this agreement at all, the breach of which endangers the achieving of the purpose of the agreement and on whose observation the acquirer regularly relies. In the case or negligent breach of such duties, liability is limited to the foreseeable damage typical in agreements of this type.
B. The licensor is not liable in cases of minor breaches of other duties. (?What duties?)
C. The licensor is not liable in cases of technical damages resulting from the use of the provided software. (in an inappropriate manner ? Limited Liability)
6) Copyright Applicable Austrian Federal copyright laws remain unaffected. (Laws of the Commonwealth?)
5) Ancillary Agreements, Choice of Law, (Prorogation) <<- (Do you mean interpretation?)
A. No oral agreements have been made. (I can ignore the first 5 clauses ?) Amendments, including to this provision, must be in writing.
B. The laws of the Federal Republic of Austria apply to the exclusion of the provisions of the UN Convention on the International Sale of Goods. The language of the agreement is German.(Laws of the Commonwealth?)or only German??) (Statutes of limitations in Germany?)
C. This agreement has been translated into several other languages. In the case of contradictions, matters of interpretation and lack of clarity, the German version will take precedence over the other versions.
D. If the parties are either merchants or legal entities in public law, the sole legal venue for all disputes arising from this agreement is Vienna, Federal Republic of Austria.

Is this a Global agreement? Democratic Countries are part of the Commonwealth , Copyright Legislation is pertain-able to Commonwealth countries.
The statute of laws pertaining solely to Germany are for German citizens.
Laws pertaining to the Commonwealth apply as a whole to Democratic countries.

My 2c worth

[Xtinct]

Does it not just boil down to,
1) Do not sell the modules / code "as is", or without significant change. (enter penalty here)
2) Use at your own risk.
Put it into lawyer speak and away you go

Though you might end up writing ten pages on what significant means

[Tronic]

This software is provided 'as-is', without any express or implied
warranty. In no event will the authors be held liable for any damages
arising from the use of this software.

Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not
claim that you wrote the original software. If you use this software
in a product, an acknowledgment in the product documentation would be
appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.

[Nubeat7]

Democratic Countries are part of the Commonwealth , Copyright Legislation is pertain-able to Commonwealth countries.
The statute of laws pertaining solely to Germany are for German citizens.
Laws pertaining to the Commonwealth apply as a whole to Democratic countries.

maybe some people in the Commonwealth believe in this, but you need to know that there are existing souverain democratic countries outside the Commonwealth too. (austria btw, is one of this countries)

[JB_AU]

@Tronic ever thought of being a policy writer, clear & meaningful writs are hard to come by, nicely put!

@nubeat7 sovereign states, by imperial nature are states of common wealth , they are by natural commerce. (goods & services). Sovereign , so-ve-reign (by their ruling) or places that hold the old lore where Kings, Queens & Nobility made rulings & notably where the first generation of governments.
English or another Countries Laws are separate to Commonwealth Law, Every country has their own laws, yet countries of the Commonwealth share the same Commonwealth Laws.

I hope this clarifies things.

[Nubeat7]

to be honest i don't know which common wealth you are talking about, the only commonwealth i know are the 'commonwealth of nations' which are the old colonial states of great britain and the commonwealth of amerika, austria isn't included in one of these, the only thing else is the UN Convention on the International Sale of Goods which is named in point 5) B)

anyway as i mentioned before, this is just for taking the one or other idea and that all the local stuff will not fit for FS Guru, the conditions above are written by a lawyer and fits my personal needs, so we don't need to discuss about things in detail where i already said that they will not fit here.

[tester]

Can't you just use existing Creative Commons descriptors instead of inventing the wheel from scratch? With possibility to select licences? The easiest way: CC-BY. The harder way: CC-BY-NC. Or CC0.

If there is someone who won't wish to play fair, they will not play fair anyway. And your resources to stop them are limited.

[Exo]

Can't you just use existing Creative Commons descriptors instead of inventing the wheel from scratch? With possibility to select licences? The easiest way: CC-BY. The harder way: CC-BY-NC. Or CC0.

If there is someone who won't wish to play fair, they will not play fair anyway. And your resources to stop them are limited.

I have been looking into creative commons and they are not recommend for software. Also looking at all the other common open source licenses they do not look suitable either, they are too complex and many things they say just don't apply to what we are doing here.

I think writing a basic license perfectly adapted for Flowstone modules is the best way to go.

I wrote one up based on the one posted by Tronic (thanks for that)

This module(s) is/are provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this/these module(s).

Permission is granted to anyone to use this module for any purpose, including commercial applications, and to alter it and redistribute it (but only as part of other original works), subject to the following restrictions:

1. The origin of this module must not be misrepresented; you must not claim that you wrote the original module(s). If this module(s) forms a significant part of your product you must include a credit to the original author somewhere either in the product itself or in the products documentation.

2.You may not sell this module(s) 'as-is' either in its original form or as a VST or EXE. It is also not okay to make purely cosmetic changes and then resell the module(s) either in module form or as a VST or EXE. Cosmetic changes would constitute changing the graphics used without any real change to the modules functionality.
If you have made very significant changes/improvements then you may charge for your work but the original author is still required to be credited with their contribution, for without their work yours would not exist.

3.You may charge for work that uses this/these module(s) as long as you have created a significant new creative work.
It is possible that your work may contain nothing but modules released under this licence but if as a whole your work can be classed as original and more than the "sum of its parts" then this license permits charging for your work in that case.

4.You may not redistribute the module unless you have made significant improvements/changes. You may only link to the original file on Flowstone Guru.
If you have made improvements consider trying to contact the author first to see if they want to include your improvements before releasing a separate version.

5. Altered modules must be plainly marked as such, and must not be misrepresented as being the original module. Best practice is to edit the tooltip with "Edited by <Your Name>".

6.The "Tooltip help" which contains information of the module and the authors name must not be removed under any circumstances, although it may be edited as long as the original authors name is not removed.

What do you think? Maybe number 3 is a bit ambiguous?

Here also is an updated Uploading Guidelines, that is worded in a slightly stricter manner....

This is a set of rules/guidelines that you should follow when uploading schematics to Flowstone Guru.

Please do your best to adhere to these, of course they are not strictly enforced in anyway (I'm not Apple) but it will help keep a level of consistency and quality among downloads. Although I do reserve the right to remove your ability to upload if you blatantly ignore them all.
By uploading your work you are implicitly agreeing to the "Flowstone Guru Module License" so please make sure you read that first before uploading. The License can be found at <insert Link to License Here>

SCHEMATIC GUIDELINES...

1.Schematics should be as bug free as can reasonably be expected of "stable" software. Of course there will be the odd bug but modules should be fully tested before uploading and not classed as "beta", so "finished" modules only please.

2.You must include a "Tooltip help" at the top level of your module. This should include the name of the module and a short description if the name is not descriptive enough. This should be followed by a version number then your author name, adding the year is optional.
An example from The Dev Toolkit: "Integer Sum \n Sums integer values with the add trigger. \n V1.0 by Exonerate 2008"

The tooltip is very important because it means your author name will follow the module around so no one can forget who made it and you can be properly credited for your work. Having a quick description is handy too.

3.Keep it tidy! Your schematic should be tidy and readable. So avoid crossing over wires, keep everything nicely structured in modules and make sure to name all your inputs and outputs! (well the majority anyway).
This post by Trogluddite http://flowstone.guru/blog/so-you-want- ... ic-do-you/ has some great tips for keeping things clean and tidy.

4.It is advised that you set up a test schematic showing your module in use. This way the downloader has everything set up for them to test straight away. This will help them learn how the module is supposed to be used. Of course if you are releasing a pack of many modules then this isn't quite as feasible.


DOWNLOAD PAGE GUIDELINES...

1.It is required that you include at least one screenshot of your schematic. Screenshots enable the downloader to see what they are getting which may encourage more downloads.
To get the screenshot zoom in a bit and then capture a screenshot via the "View" menu in Flowstone.
Once you have your screenshot you will need to crop it in photo editing software such as Gimp.
The cropped screenshot height should be exactly 220 pixels and the width anywhere between 400 and 720 pixels.
Please note you can upload images of a different height but the resulting image will be scaled to fit 220 pixels which may affect the image quality.

2.Give a good description of what the module does and please try not to make it too long. The description should just be long enough to get its purpose across and any necessary information. If you really need to get across technical details to enable proper usage then please put this as a comment in the top level of the schematic, or you may want to add a manual.
You can add a manual along side the main download as multiple files are supported.

3.When updating a file please use the "Changelog" feature of the Download Edit page detailing the changes you have made.


Thanks for sharing and taking the time to upload your work,

Thomas.

Of course these are still subject to change, so any input will be helpful.

Cheers,
Exo