Footer links to license, terms of use etc

[rufuspollock]

License for site:

• License for data by default is Open Data Commons by (we should put this in the sign up step as well) but state this can be varied on a per app basis (apps should state something in their description ...?)
• License for each app is set in the app description or source code (??)
• General content license is CC-By-SA

Also suggest links for terms of use could also add About and Terms of Use for good measure.

[teleyinex]

@rgrp I've created the Terms of Use (TOU) page based on the current text in the OKF's TOU. However I've modified it a bit as in some cases it does not fit within the scope of PyBossa and/or Crowdcrafting and/or ForestWatchers.net general and real cases.

The reasons are the following:

• PyBossa is a joint effort by several institutions, so all of them should agree on a minimum barebone TOU. I think we need to involve the legal institutions from CCC and OKFN to agree on the document, meanwhile we can keep the current version as it is better to have something than nothing.
• There are some institutions that are actually running their own instances of the PyBossa server (i.e. ForestWatchers or CrowdCrafting) having the servers out of UK, so the sentence: This agreement is made under the laws of England and Wales. could be misleading and I don't know if we can even have it in the TOU due to this issue. For this reason I've created the option of allowing every institution to have their own version.
• In the current OKF TOU there is a section for payed services, and right now PyBossa/crowdcrafing does not offer at all those services, so I've removed that section for the moment. We will need to clarify this point.
• I removed this line We would hope that the following would go without saying but, please take note of our because I do not know if it is a broken sentence or if actually links with the next paragraph. Should I restore it?
• I removed this point The API supplied with our Public Domain Works project is not guaranteed to provide an answer with 100% certainty. Copyright law is complex and there may be obscure cases that are not handled correctly. It is intended to be a starting point, not the word of God. because PyBossa does not have a Public Domain Works project and it doesn't fit at all.

As you can see there are several cases that need further discussion, but the bare bones TOU is there. Now we only need to involve all the legal people to agree on the text and adapt it properly for the current service.

Final notes: the TOU has been always linked from the signin and create pages, but maybe we need to make it bigger. Regarding your question marks about licenses for apps and data I would suggest to re-use the same approach as Mozilla does with the extensions: a drop down menu when you create the app so the owner can choose a license for the source code and data (this will involve a change in the Apps table as it will be good for doing searches based on licenses)

Update: I'll mail this issue to all the participants, so we can start the discussion.

[rufuspollock]

I guess my one concern here with forking is that as the original gets updated this goes out of sync. I understand some things like PDW are not relevant but that would just be ignored (ditto for paid services).

[teleyinex]

Hi,

Yes, I agree, but my main concern is that we will be dealing not only with OKF but also with CCC which represents another three different entities that will like to analyze the terms expressed in the document, so I think that we actually need to address this properly with all the involved stakeholders.

Daniel

[teleyinex]

After consulting with the SF lawyer, everything is fine. Thus, closing it.