Creative Commons - User contributions [en]

Video

2013-05-02T05:41:55Z

Ronisarono: Video ronisyahrony

Blogger

2013-05-02T04:53:42Z

Ronisarono: RONISYAHRONY AWOULD

[[Category:Role]]
[[Category:Person]]
[[Category:Portal]]
[[Category:Blog]]
[[Category:Blogger]]
[[Category:Guide]]
[[Category:HOWTO]]

So, you are a blogger? How can you best use Creative Commons licensing to promote your work? This page aims to document best practices. Also, blogger on this page is used in a very large context meaning all forms of blogging including videoblogging, podcasting, etc. Please help us make this page brilliant!

==RONISARONO==

=== License Ronisyahrony ===

Follow the steps of the [http://creativecommons.org/license license chooser] to select and apply the license that fits your use.

=== Marking Your Work ===

It is important to clearly show how your content is licensed physically. See the [[Marking]] page to find current video license marks and to learn more about how to properly "Mark" your content.

=== Publish Sosial ===

Use a service for publishing your content

{{incomplete}}

=== Use

== See Also ==

* [[Podcasting Legal Guide]] - guide about podcasting and the law

== External Links ==

* [http://www.eff.org/bloggers/ EFF's Legal Guide to Blogging]

* [http://www.littleearner.co.uk/ftc-blogging-guidelines/ New FTC Blogging Guidelines]

Video

2013-05-02T04:12:16Z

Ronisarono: Ronisyahrony

[[Category:Video]]
[[Category:List]]
[[Category:Media]]
[[Category:Licensed]]

This is a partial list of Creative Commons licensed video media. Part of the [http://creativecommons.org/video original page] is now ported here.

==RONISARONO ==

* [[Films]]
* [[Video]]
* Add your type here please...

== Featured Video Sites ==

{{#ask:
[[format::MovingImage]]
|mainlabel=Name
|?mainurl=Website
|?size=Size
}}

== External Links ==

* [http://newteevee.com/]
* [http://hive.ntticc.or.jp/]
* [http://www.archive.org/details/prelinger Prelinger Archives]
* [http://cyberlaw.stanford.edu/documentary-film-program/film/a-fair-y-use-tale A Fair(y) Use Tale]
* [http://creativecommons.org/weblog/entry/4380 Shipwreck Central]
* [http://creativecommons.org/weblog/entry/4275 SpaceShipOne event recollections]
* [http://creativecommons.org/weblog/entry/4233 Panorama Ephemera]
* [http://creativecommons.org/weblog/entry/3862 Youth Media Distribution]
* [http://creativecommons.org/weblog/entry/3790 Nothing So Strange Movie]
* [http://entropy.tuxfamily.org Entropy killed the Cat - french-speaking diffusion & creation of CC-licensed films]
* [http://www.legittorrents.info/index.php?page=torrents&search=&category=1 Legit Torrents Movies - includes CC-licensed films]
* Please add to the list...

CCWiki:Translate

2013-05-02T03:56:19Z

Ronisarono: Ronisyahrony awould

This is a multilingual wiki; content can be translated into multiple languages regardless of the original language.

==RONISARONO==

This article describes how to go about translating virtually any page in the CC wiki. In order for translations to be organized, up to date, and associated with the correct source page, certain steps need to be taken. This is a brief overview of the steps required to translate a page ''correctly''. For more detailed information about special rules and exceptions, please see the full documentation below, starting at subsection [[#Preparation | Preparation]].

The first step in translat

== Preparation ==

The following templates are used to manage translations in the pages that are written in English:

* [[Template:Translations]]
* [[Template:Translated From]]

There is a third, [[Template:Diff since trans]], which is a support template used by the second, and not meant for general use. They are language interfaces that provide, to the real code behind, strings to be displayed to users, in English.

If these templates have not yet been translated to your language, you should translate the '''three''' of them first (see next section for how to do this — also see the European Portuguese (Pt:) versions of the templates for a practical example; you can, inclusively, translate the parameter names of the templates).

Once these have been translated to your language, you should use the translated versions on all pages written in your language, instead of the English ones. Generally, the English templates should be used in the pages in English, the German translations in the pages in German, the Hebrew translations in the pages in Hebrew, and so forth.

== Translating ==

Follow these steps to translate an article. For the purposes of illustration, the article is called '''Example Content''' and we will translate the article to Spanish.

* Create a new article called '''Es:Contenido del Ejemplo'''. The contents should be a translation of '''Example Content'''. Note that the page name is made up of the language code and the translated title, separated by a colon (:). See ''[[#Naming Translated Pages|Naming Translated Pages]]'' below for additional details
* To the bottom of page '''Es:Contenido del Ejemplo''' add the Spanish equivalent of:
<pre>
{{Translated From
| source = Example Content
| rev = <revision ID of page Example Content>
}}
</pre>
* To the bottom of '''Example Content''' add:
<pre>
{{Translations
| articles = Es:Contenido del Ejemplo
}}
</pre>
:'''''Note:''' To get the <code><revision ID of page '''Example Content'''></code>, go to page '''Example Content''' and place the pointer over the link "Permanent link" at the top of the page; the revision ID will appear at the end of the URL near the bottom of your browser. It is also available from the history of the page, placing the pointer over the link to the last revision. Is is also shown in the languages box, in the link to the source language.''

:'''''Note:''' If an article is available in more than two languages, separate the translated article names with commas in template <code>Translations</code>.''

:'''''Note:''' For pages outside the main namespace, the namespace must always be specified at the beginning of the name.''

A languages box appears at the bottom of each article. The box lists all languages in which the article is available. On translation pages, the box has a special behaviour: one of two indicators will appear after the name of the language of the page:

* A ✔ if the latest revision of '''Example Content''' is equal to the revision ID supplied in parameter <code>rev</code>. This indicates that '''Es:Contenido del Ejemplo''' is up-to-date, since it is based on the latest version of the source page.
* A "(synchronise)" link if the latest revision of '''Example Content''' is different from the revision ID supplied in parameter <code>rev</code>. This indicates that '''Es:Contenido del Ejemplo''' is outdated. Clicking the "(synchronise)" link produces a list of the changes made to '''Example Content''' since it was translated. To bring the translation into synch again, incorporate those changes in '''Es:Contenido del Ejemplo''' and update the revision ID to the latest one.

Eventually you will be able to read the entire wiki in your language.

==Ronisarono, Translated Pages ==

The page name of pages outside the main namespace must be preceeded by RONISYAHRONY" (see subsection [[#Namespace Prefix|Namespace Prefix]] below for details).
When RONISARONO translated page, the original page name should be translated.

To distinguish between identically spelt translated titles in different bahasa, language code prefixes are used (see subsection [[#bahasa Code Prefix|bahasa Code Prefix]] below for details).

The Bcode prefix should be

== Categorisation of pages ==

There are a couple of issues with the categorisation of pages.

By default, in [http://www.mediawiki.org/wiki/Help:Categories categories], the pages are sorted according to their full name, ''including'' the namespace. All pages in the "Category:" namespace, for example, will be listed in categories under the heading "C".

Additionally, since we prefix page names with the language code, even in the main namespace there will be sorting issues. For example, by default all pages in the main namespace written in German will be listed in categories under the heading "D", because all pages in German start with "De:".

To overcome these limitations, the translation templates automatically assign a default [http://www.mediawiki.org/wiki/Help:Categories#Sort_key sort key] to pages, which causes the page to be sorted under the part of its name ''after'' the language code. For most purposes this will be sufficient and users won't need to worry about categorisation (check [[Template:Sort key of page]] for precise details).

If, however, the default sort key ever turns out to be incorrect, it can be overriden as usual by:

<pre>
[[Category:Name|Sort key override]]
</pre>

on each category, or by a separate:

<pre>
{{DEFAULTSORT:Sort key override}}
</pre>

which applies to all the categories of the page. In principle, this should only be necessary when MediaWiki's handling of the initial caracters of the default sort key is undesired. For example, MediaWiki groups pages starting by A, À, Á, Ä, etc., under separate headers, instead of grouping all such pages under the heading A. If the name of a page (after the language prefix) starts by one such character, you may need to override the key.

{{Translations|
| articles = CC Wiki:Pt:Tradução, CC Wiki:Ksh:Övversäze, CC Wiki:de:Übersetzen
}}

[[Category:Translation Project]]

CCWiki:Translate

2013-05-02T03:44:25Z

Ronisarono: Ronisarono

This is a multilingual wiki; content can be translated into multiple languages regardless of the original language.

==RONISARONO==

This article describes how to go about translating virtually any page in the CC wiki. In order for translations to be organized, up to date, and associated with the correct source page, certain steps need to be taken. This is a brief overview of the steps required to translate a page ''correctly''. For more detailed information about special rules and exceptions, please see the full documentation below, starting at subsection [[#Preparation | Preparation]].

The first step in translat

== Preparation ==

The following templates are used to manage translations in the pages that are written in English:

* [[Template:Translations]]
* [[Template:Translated From]]

There is a third, [[Template:Diff since trans]], which is a support template used by the second, and not meant for general use. They are language interfaces that provide, to the real code behind, strings to be displayed to users, in English.

If these templates have not yet been translated to your language, you should translate the '''three''' of them first (see next section for how to do this — also see the European Portuguese (Pt:) versions of the templates for a practical example; you can, inclusively, translate the parameter names of the templates).

Once these have been translated to your language, you should use the translated versions on all pages written in your language, instead of the English ones. Generally, the English templates should be used in the pages in English, the German translations in the pages in German, the Hebrew translations in the pages in Hebrew, and so forth.

== Translating ==

Follow these steps to translate an article. For the purposes of illustration, the article is called '''Example Content''' and we will translate the article to Spanish.

* Create a new article called '''Es:Contenido del Ejemplo'''. The contents should be a translation of '''Example Content'''. Note that the page name is made up of the language code and the translated title, separated by a colon (:). See ''[[#Naming Translated Pages|Naming Translated Pages]]'' below for additional details
* To the bottom of page '''Es:Contenido del Ejemplo''' add the Spanish equivalent of:
<pre>
{{Translated From
| source = Example Content
| rev = <revision ID of page Example Content>
}}
</pre>
* To the bottom of '''Example Content''' add:
<pre>
{{Translations
| articles = Es:Contenido del Ejemplo
}}
</pre>
:'''''Note:''' To get the <code><revision ID of page '''Example Content'''></code>, go to page '''Example Content''' and place the pointer over the link "Permanent link" at the top of the page; the revision ID will appear at the end of the URL near the bottom of your browser. It is also available from the history of the page, placing the pointer over the link to the last revision. Is is also shown in the languages box, in the link to the source language.''

:'''''Note:''' If an article is available in more than two languages, separate the translated article names with commas in template <code>Translations</code>.''

:'''''Note:''' For pages outside the main namespace, the namespace must always be specified at the beginning of the name.''

A languages box appears at the bottom of each article. The box lists all languages in which the article is available. On translation pages, the box has a special behaviour: one of two indicators will appear after the name of the language of the page:

* A ✔ if the latest revision of '''Example Content''' is equal to the revision ID supplied in parameter <code>rev</code>. This indicates that '''Es:Contenido del Ejemplo''' is up-to-date, since it is based on the latest version of the source page.
* A "(synchronise)" link if the latest revision of '''Example Content''' is different from the revision ID supplied in parameter <code>rev</code>. This indicates that '''Es:Contenido del Ejemplo''' is outdated. Clicking the "(synchronise)" link produces a list of the changes made to '''Example Content''' since it was translated. To bring the translation into synch again, incorporate those changes in '''Es:Contenido del Ejemplo''' and update the revision ID to the latest one.

Eventually you will be able to read the entire wiki in your language.

== Naming Translated Pages ==

The page name of pages outside the main namespace must be preceeded by the namespace (see subsection [[#Namespace Prefix|Namespace Prefix]] below for details).

When naming the translated page, the original page name should be translated.

To distinguish between identically spelt translated titles in different languages, language code prefixes are used (see subsection [[#Language Code Prefix|Language Code Prefix]] below for details).

The language code prefix should be followed by a colon (:) in all namespaces except "File:", where a space ( ) must be used instead (see subsection [[#Exception for the {{ns:file}}: namespace|Exception for the {{ns:file}}: namespace]] below for details).

So:

* [[Ru:Заглавная страница]] is the translation of [[Main Page]] to Russian (ru:)
* [[He:ברוכים הבאים]] is the translation of the same [[Main Page]] to Hebrew (he:)

* [[CC Wiki:De:Übersetzen]] is the translation of this page, [[CC Wiki:Translate]], in the "CC Wiki:" namespace, to German (de:)
* [[:Category:Ksh:Projäk]] is the translation of [[:Category:Project]], in the "Category:" namespace, to Colognian (ksh:)
* [[Template:Ar:مشاركة الأعمال الإبداعية]] is the translation of [[Template:Sharing Creative Works]], in the "Template:" namespace, to Arabic (ar:)

* [[:File:Pt Casos de estudo.png]] is the translation of [[:File:Casestudies-splash.jpg]], in the "File:" namespace, to European Portuguese (pt:)

: ''Again, please note that, for files, a space ( ) is used after the language code, instead of a colon (:).''

* [[Case Studies/Silvia O in the remix culture]] is the translation of [[Case Studies/Es:Silvia O in the remix culture]], a subpage of [[Case Studies]] in the main namespace, into English (no language code used)

=== Language Code Prefix ===
The language code must be supported by MediaWiki. A full list of the supported language codes can be found at [http://translatewiki.net/wiki/Special:SupportedLanguages TranslateWiki: SupportedLanguages].

=== Namespace Prefix ===

If the original page title has a [http://www.mediawiki.org/wiki/Help:Namespaces namespace] prefix, the same prefix needs to appear before language prefixes in the name of the translated page. For example, if you are translating this page (<tt>CC Wiki:Translate</tt>) into Spanish (<tt>es</tt>), the resulting page name would start with <tt>CC Wiki:Es:...</tt>.

==== Exception for the {{ns:file}}: namespace ====

When translating images, follow the language prefix guidelines above with the exception that the prefix should be followed by a space ( ) rather than a colon (:). For example, the Portuguese (pt) translation of [[:File:Casestudies-splash.jpg]] is [[:File:Pt Casos de estudo.png]].

This exception is justified by the fact that MediaWiki automatically changes colons to dashes (-) in the title of the file description page. Since dashes are already used to separate language, region and script codes, using a space instead of a dash allows the page name to be exploded unambiguosly.

== Categorisation of pages ==

There are a couple of issues with the categorisation of pages.

By default, in [http://www.mediawiki.org/wiki/Help:Categories categories], the pages are sorted according to their full name, ''including'' the namespace. All pages in the "Category:" namespace, for example, will be listed in categories under the heading "C".

Additionally, since we prefix page names with the language code, even in the main namespace there will be sorting issues. For example, by default all pages in the main namespace written in German will be listed in categories under the heading "D", because all pages in German start with "De:".

To overcome these limitations, the translation templates automatically assign a default [http://www.mediawiki.org/wiki/Help:Categories#Sort_key sort key] to pages, which causes the page to be sorted under the part of its name ''after'' the language code. For most purposes this will be sufficient and users won't need to worry about categorisation (check [[Template:Sort key of page]] for precise details).

If, however, the default sort key ever turns out to be incorrect, it can be overriden as usual by:

<pre>
[[Category:Name|Sort key override]]
</pre>

on each category, or by a separate:

<pre>
{{DEFAULTSORT:Sort key override}}
</pre>

which applies to all the categories of the page. In principle, this should only be necessary when MediaWiki's handling of the initial caracters of the default sort key is undesired. For example, MediaWiki groups pages starting by A, À, Á, Ä, etc., under separate headers, instead of grouping all such pages under the heading A. If the name of a page (after the language prefix) starts by one such character, you may need to override the key.

{{Translations|
| articles = CC Wiki:Pt:Tradução, CC Wiki:Ksh:Övversäze, CC Wiki:de:Übersetzen
}}

[[Category:Translation Project]]

Case Studies/Yunyu

2013-05-02T03:33:10Z

Ronisarono:

{{Case Study
|Description=Yunyu is a successful unsigned singer/songwriter in Sydney, Australia, who uses Creative Commons licences for promotional purposes.
|Mainurl=http://www.yunyu.com.au
|Author=Yunyu
|User_Status=Creator
|Tag=JJJ Unearthed, music, business model, CD Baby, Earshot Music, iTunes, usync, MySpace, Facebook, YouTube
|License short name=CC BY-NC-SA
|Format=Sound
|Country=Indonesia
|Quote=The ease with which I have allowed podcasters, bloggers and the like to use my music could only have helped me make my living as a musician.
|Quote_Attribution=Yunyu
|Image_Header=http://www.yunyu.com.au/gallery/albums/userpics/10001/normal_IMG_8538.jpg
|License=http://creativecommons.org/licenses/by-nc-sa/2.0/
}}
== Overview ==
[http://www.yunyu.com.au Yunyu] is an understated, self-proclaimed member of the emerging (and in many cases emerged) generation of bedroom-based artists who may not, without the Internet, have ever seen the cold light of day. She is a classically-trained musician, though she admits to having been bored by "RONISYAHRONY" of that genre. Yunyu first saw [http://yunyu.com.au/home/bio/ success] before ever having played a live gig, via the [http://www.triplejunearthed.com Triple J Radio 'Unea

Case Studies/Yunyu

2013-05-02T02:54:45Z

Ronisarono: Ronisyahrony awould

{{Case Study
|Description=Yunyu is a successful unsigned singer/songwriter in Sydney, Australia, who uses Creative Commons licences for promotional purposes.
|Quote=The ease with which I have allowed podcasters, bloggers and the like to use my music could only have helped me make my living as a musician.
|Quote_Attribution=Yunyu
|Image_Header=http://www.yunyu.com.au/gallery/albums/userpics/10001/normal_IMG_8538.jpg
|Mainurl=http://www.yunyu.com.au
|Author=Yunyu
|User_Status=Creator
|Tag=JJJ Unearthed, music, business model, CD Baby, Earshot Music, iTunes, usync, MySpace, Facebook, YouTube
|License short name=CC BY-NC-SA
|License=http://creativecommons.org/licenses/by-nc-sa/2.0/
|Format=Sound
|Country=Australia
}}
== Overview ==
[http://www.yunyu.com.au Yunyu] is an understated, self-proclaimed member of the emerging (and in many cases emerged) generation of bedroom-based artists who may not, without the Internet, have ever seen the cold light of day. She is a classically-trained musician, though she admits to having been bored by the restrictions of that genre. Yunyu first saw [http://yunyu.com.au/home/bio/ success] before ever having played a live gig, via the [http://www.triplejunearthed.com Triple J Radio 'Unearthed' competition] (a new talent competition hosted by Australian national broadcaster, [http://www.abc.net.au/triplej/ JJJ]). Following her being 'unearthed,' Yunyu received radio airplay all over the globe, including some chart domination on Canadian college radio.

Yunyu uses the services of several online businesses to sell and share her music. For both physical and digital distribution, Yunyu's business model utilises a number of different music platforms. She has CDs and mp3s available for purchase from US independent distributor, [http://www.cdbaby.com CD Baby]. CDs are also available from the Australian independent store [http://www.earshotmusic.com.au Earshot Music], while paid digital downloads are available from [http://www.itunes.com/store/ iTunes]. Yunyu also offers fans the option of buying CDs directly from her.

As with a number of independent bands, Yunyu uses the services of a company called [http://www.usync.net Usync]. The service provides a 'backstage pass' to paying fans, who can then get access to exclusive content in the 'backstage' area of the Usync website. The service essentially brings ticket sales, music sales, news announcements and other components of a music business model into the one location or interface.

Popular online radio station [http://www.last.fm 'Lastfm'] also assists in the proliferation of Yunyu's music, together with social networking platforms like [http://www.myspace.com/yunyu/ MySpace] and [http://www.facebook.com Facebook].

== RONISYAHRONY ==
RONIS uses the [http://creativecommons.org/licenses/by-nc-sa/2.0/ Creative Commons NonCommercial-Attribution-Sharealike 2.0 licence] for promotional purposes. Two of her songs, ''A Prayer'' and ''Lenore's Song,'' are available under this licence as [http://www.yunyu.com.au/home/music#videos streaming music videos]. Whilst her site does not include any downloadable tracks, Ronisarono blog on [http://yunyu.com.au/home/creative-commons/ her webpage] that, though only two of her songs are

== Motivations ==
Yunyu's experience using the Internet as a distribution and promotional platform makes her use of Creative Commons licences a logical step. To enhance CC’s presence in the music community, Yunyu thinks that there could be more done to spread the word about the licences, suggesting that 'maybe a few CC roadshows are in order for creators and the like.'

While the benefits of Creative Commons licences are obvious from the above discussion, Yunyu cites difficulties with Creative Commons licensing as far as other artists or content producers understanding the licences:
:'There is, when I speak to some creators, a certain misconception that Creative Commons equals public domain which is not true. So there is a general perception that they have lost some income due to putting their work under Creative Commons licenses but I beg to differ because I think I have benefited from the spread of my work through this channel.'

== Media ==
<nowiki><object width="425" height="355"><param name="movie" value="http://www.youtube.com/v/EzSstcvLmYM&hl=en"></param><param name="wmode" value="transparent"></param><embed src="http://www.youtube.com/v/EzSstcvLmYM&hl=en" type="application/x-shockwave-flash" wmode="transparent" width="425" height="355"></embed></object></nowiki>