Website for promoting sharing-friendly licenses/Wiki

From LibrePlanet
< Website for promoting sharing-friendly licenses
Revision as of 19:25, 6 October 2009 by Simonft (talk | contribs) (How can I solve this problem?)
Jump to: navigation, search

Please feel free to improve the following draft:

Main subjects

  • What's the copyright concept? (A government monopoly)
  • What's wrong with a full copyright? (Too restrictive)
  • Why should I care? (It's the future of the community)
  • Oh, no! That's totally communism! (Freedom isn't communism nor capitalism)
  • What about my rights? (Community first. Public long-term benefit is way more important then the private short-term one)
  • How can I solve this problem? (Use sharing-friendly licenses like CC's)
  • What's the best license? (There is no 'best' license. But freer is better)
  • Who has applied this idea? (GNU Project, Wikipedia, over than 100-million photos on Flickr, music websites)
  • How can I apply it?
  • About us and the license. (GNU Generation, CC-BY-SA, Javascript Trap)

The contents

Home page/screen

Find some suitable free* photos to be used here.
*Any work licensed and any version of cc-by or cc-by-sa.
Share a passion!

Art is the artist's passion, it used to be shared. Sharing gives us the chance to get the best of our human culture. GNU Generation Project tries to explain the importance of sharing in this website.

What's the copyright concept?

The copyright is a monopoly enforced by the government on certain work for the creator or owner of that work. The copyright system is said to be in the good of the community. 300 years ago, when the concept of copyright was thought of, it prohibited individuals from doing things that they weren't able to do regardless. No individual was able to make as little as ten copies of something, making it almost impossible to seriously violate the law. It only affected wealthy people with expensive printing facilities. So it was fine for us to give up a right we had no use for and to accept such a system. But does this system work that way anymore?

What's wrong with a full copyright?

O.K., I think it needs to be rewritten. Who will volunteer for that?--OsamaK 11:53, 5 October 2009 (UTC)

We, individualsSuggest another word!, used to do whatever we could to help our neighbors and friends. Is this true? Three-hundred years ago, we lent them our copies of books and let them copy them by hand if they wanted to (and they did the same to us!). But why should we do that now in the age of network computers? We can simply right click on a file and make hundreds of copies within minutes! The copyright system is affecting us harmfully we cannot be good neighbors and friends anymore if we choose to obey the law. I don't think that this is the right argument to make. Just because it is stopping us from doing something that we can do is not a good reason to remove it. It is much easier for people to kill other now, should we repeal the laws on these ground? I think we should show how it is harmful to creativity.

Why should I care?

It's always good to live in a collaborative community where you give and receive freely, where you build upon other people's work and share the amazing results with your friends and neighbors.

The Internet is a wonderfully powerful tool for creating such a community, and we, as a whole, should never try to restrict the power of that tool. The restrictions of the copyright system really only benefit the big media corporations, and we're the victims of this system.

In order to solve this problem, we need to start changing the situation from bottom up so we can all get the advantage of shared knowledge and creativity. Don't we have the right to enjoy our human culture? Doesn't our community, as well as the whole of humanity, have the right to enjoy the progress we as whole have made? What would a good citizen do?

What about my rights?

When you write an article, sing a song or take a photo, you're actually building upon the past, and upon the knowledge you have gleaned from many resources. And when you publish that work, you're no longer the only one who's affected by any restrictions you might think of.

You have rights, but your community should have some rights too. And you should only use restrictions that don't harm that community.

When you support the sharing community, you have some rights over your work, and you'll also have some rights over other works done by community members. You'll save a lot of time by standing on the shoulders of your community, and so will they.

Who has applied this idea?

Many. Here are some examples:

How can I solve this problem?

To solve this problem, you're going to need a license. A license is a set of terms that gives certain legal permissions on how someone can and cannot use the work. There are many ready-to-use sharing-friendly licenses that allow you to give the permissions you want to give. It is as easy as saying "this picture/song/article is licensed under X license".

We believe that a sharing-friendly license is the one that at the very least gives the right to share an unmodified version of the work with anybody, so long as it is for non-commercial purposes. There are many licenses that go beyond that, and give the freedom to modify and sell the work with few or no conditions.

Sometimes it's enough merely to give sharing-friendly license to live in a moral collaborative community,[1] but in other cases, the community needs to have some other rights such as modifying or even selling the work.[2]

At the end, it's all up to you. You'll need to see what freedoms the community needs and what restrictions you need and can impose on your work without harming the community.

The following is a table of some licenses that we like, with some usage examples:

License Sharable? Attribution?[3] Modifiable?[4] Commercial?[5] Share Alike?[6] Attach license?[7] Notes Recommend use
Public Domain Green check.svg Red x.svg Green check.svg Green check.svg Red x.svg Red x.svg
CC-BY Green check.svg Green check.svg Green check.svg Green check.svg Red x.svg Red x.svg
CC-BY-SA Green check.svg Green check.svg Green check.svg Green check.svg Green check.svg Red x.svg Educational works.
CC-BY-ND Green check.svg Green check.svg Red x.svg Green check.svg - Red x.svg Articles and books that explain opinions or experiences, including research papers.
CC-BY-NC Green check.svg Green check.svg Green check.svg Red x.svg Red x.svg Red x.svg
CC-BY-NC-SA Green check.svg Green check.svg Green check.svg Red x.svg Green check.svg Red x.svg
CC-BY-NC-ND Green check.svg Green check.svg Red x.svg Red x.svg - Red x.svg
GFDL Green check.svg Green check.svg Green check.svg Green check.svg Green check.svg Green check.svg Software manuals.

Notes

  1. ^ This is true in case of an article or a book that explains your own opinion or experience. Actually, nobody needs to have more than a sharing-friendly license to lead a moral life with this book.
  2. ^ This is true in case of educational works. More information, experiments and facts can be added to improve the work and it'd be even more useful if people could use it for commercial purposes.
  3. ^ The user must mention the original creator name(s) when they share the work.
  4. ^ That means that the user can modify, improve and build upon the work. This opens very large portal of creativeness. That's most obviously seen in the field of musics and photographs where people're frequently building upon other works and get amazing results.
  5. ^ That means that the user can use and distribute the work commercially without future permission. This is useful in case of educational and reference works, where they're basically meant to be as useful as they can be (even if they were used profitably) and where the commercial use can (and usually does) support the funding of the project. It can also be useful for opinion and other kinds of works to promote and spread them.
  6. ^ Any modified version of the work must be under the same license or a license similar to it. That's only possible for the licenses that allow the modification in the first place.
  7. ^ A full version of the license must be attached with the work (or linked in case it's used online). This can be useful to let anyone who gets the work to get their rights, but it can be a disadvantage for small printed works like photos and article (where the one who shares must attach about 4 pages of the licenses).

How can I apply it?

on Flickr

Flickr provides native support for Creative Commons licenses. Here is how you can do it:

  1. After choosing the license from How can I solve this problem?, change your default uploading license. This will be the default license on your new works once you upload them.
  2. Change all of your old Flickr photos to the Creative Commons license you chose pervasively.

On my blog

Add a footer indicating the license you are using.

About us and the license

We're a sub-project of GNU Generation initiative by the Free Software Foundation. We are all pre-university students that believe in free software and free culture. We ask you to join us in that initiative, where we meet to find and invent ways to support the free software community.

You're free to use all of this website text and images under CC-BY-SA. All Javascripts are under GNU GPL license version 3 or any later version with the following exception:

As a special exception to the GPL, any HTML file which merely makes function calls to this code, and for that purpose includes it by reference shall be deemed a separate work for copyright law purposes. If you modify this code, you may extend this exception to your version of the code, but you are not obligated to do so. If you do not wish to do so, delete this exception statement from your version.

Content guidelines

  • It should be easy-to-read for both, young and old, beginners and experts.
  • It should be 100% correct English. (I, Osama, may not be able to achieve that, so we're going to need some native English speakers).
  • It should be translator-friendly. We'll encourage people to translate it.
  • It will be licensed under CC-BY-SA 3.0.
  • It should focus on ethics as well as the practical advantages.

Technical details

  • The website will be a static HTML (not PHP, Python, etc) with Javascript, CSS and images.
  • It should be as much attractive as we can make it.
  • It should pass W3 validation test.

Designing details

The design:

  • needs to be simple and lightweight.
  • needs to be original.
  • needs to be translator-friendly.
  • as whole, needs to be free. (including any 10+ lines Javascript and CSS).

Designers

Click "Edit" and sing below (~~~~) as a designer:

Similar websites to learn from