Flowstone Guru Download area

[Exo]

This all reminds me I need to write up a formal policy and licence ect for what exactly is ok when uploading and downloading.

[KG_is_back]

I could share the password of the "Forum" account among the main uploaders so any of us with a spare bit of time could put stuff up.

Good idea... It would be a bad idea to make it fully public though - spam and deleting components uploaded form that account would be at risk.

[Perfect Human Interface]

Hey if you wanna share it just sign up to the site and give me your username via the Contact page and I will give you the option to upload

Ah, I thought you said this was only for "Gurus." I wouldn't say I'm there.

This all reminds me I need to write up a formal policy and licence ect for what exactly is ok when uploading and downloading.

Don't forget about usage rights... as in, how the authors are allowing their work to be used. Personal opinion, but I think you should require all uploads to adopt the same license (which would be basically free to use, personal or commercial, etc.). It would simplify things greatly and I sometimes don't like some of the licenses people apply to "free" works they provide.

[Exo]

I could share the password of the "Forum" account among the main uploaders so any of us with a spare bit of time could put stuff up.

Good idea... It would be a bad idea to make it fully public though - spam and deleting components uploaded form that account would be at risk.

Yes of course I will just give it to a hand full of people. So I would have it, you Trog and Martin to start. If other active members want to help then I could set them up with access on request.

[Exo]

Hey if you wanna share it just sign up to the site and give me your username via the Contact page and I will give you the option to upload

Ah, I thought you said this was only for "Gurus." I wouldn't say I'm there.

It is not meant as an exclusive "Guru club" anyone can request to upload. I would like the "Gurus" to get involved though simply because they have shared a lot of the best stuff over the years. Many "non Gurus" have shared great stuff too so I hope people that don't class themselves as one of the gurus still get involved. Everyone brings something different to the table.
My main reason of making people request to upload is so I can manage quality a bit better and also so that I am giving this ability to active forum members that have a history of sharing modules. You may have only shared the one module but you have history and if you think others will find it useful you can request to put it up.

This all reminds me I need to write up a formal policy and licence ect for what exactly is ok when uploading and downloading.

Don't forget about usage rights... as in, how the authors are allowing their work to be used. Personal opinion, but I think you should require all uploads to adopt the same license (which would be basically free to use, personal or commercial, etc.). It would simplify things greatly and I sometimes don't like some of the licenses people apply to "free" works they provide.

Yes I will write out a common licence that will apply to all downloads unless otherwise stated by the author.

[Exo]

I have already done the upload guidelines here they are...

This is a set of 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.


SCHEMATIC GUIDELINES...

1. Schematics should be as bug free as can resonably 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.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.

3.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.For consistency with other downloads it is advised that you include at least one screenshot of your schematic.
Also 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, I use Gimp for that. The cropped screenshot should be 720px by 220px.
Although it doesn't have to be this exact size but be aware that the height of screenshots is fixed at 220 pixels,
so the screenshot will be scaled up or down (without losing ratio) to fit a height of 220 so the closer you can get to that the better.


2.Give a good description of what the module does, please try not to make it too long. The description should just be long enough
to get the purpose across and any necessary information. If you really need to get across technical details to enable proper usage
then 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.


Well that is all I ask really, so basically just common sense requirements!

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

Thomas.

This will be sent as an attachment to people in the response email when they request to upload.

Just need to do the download licence now, but I am wondering whether to write my own or pick an existing not to restrictive licence, thoughts?

[Nubeat7]

thats the one i normally use for payed work...

maybe someparts wouldn't fit for the guru download site, but as a startpoint? its also very lawyer style english, its a modified version of my software conditions

Conditions of use for provided Flowstone modules and codes:
Preamble
In his capacity as legal proprietor, {developers name & adress} (hereafter "the licensor") grants the licensee of any {developer's} software, including all integral parts thereof pursuant to Paragraph 1, No. 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 modules and all included codes inside your own products as he like.
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.
3) Breach of License, Forfeiture
1. If the licensee breaches the conditions of this licensing agreement, all rights of use granted will expire. In this case he 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.
2. The licensee is liable to the licensor for all damage arising from breaches of this agreement.
4) Liability of the licensor
1. The licensor is liable in cases of intent and gross negligence as provided by law. He is also liable in case of negligent breaches of duty whose fulfilment 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.
2. The licensor is not liable in cases of minor breaches of other duties.
3. The licensor is not liable in cases of technical damages resulting from the use of the provided software.
6) Copyright Applicable Austrian Federal copyright laws remain unaffected.
5) Ancillary Agreements, Choice of Law, Prorogation
1. No oral agreements have been made. Amendments, including to this provision, must be in writing.
2. 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.
3. 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.
4. 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.

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."

[Exo]

@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.

[KG_is_back]

I would say, name should be mentioned in manual/somewhere if the module/module pack is mayor part of a schematic(for example Gui contains many knobs from GUI pack made by mr.XYZ or some module is crucial part of schematic functionality). Also I would add new RULE to the uploading - all modules must contain the name of the author in their tooltip help (if the author is known), to prevent using module 100 times and forgetting who made it.

[martinvicanek]

@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 their 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.

+1, and licensor should not be liable for anything.