Giter Club home page Giter Club logo

faq's Introduction

faq

Creative Commons FAQ page: https://creativecommons.org/faq/

Code of conduct

CODE_OF_CONDUCT.md:

The Creative Commons team is committed to fostering a welcoming community. This project and all other Creative Commons open source projects are governed by our Code of Conduct. Please report unacceptable behavior to [email protected] per our reporting guidelines.

Contributing

See CONTRIBUTING.md.

Content Updates

⚠️ Do not modify the index.html files in faq/. They are generated by the build script.

Only modify the markdown files (faq-en.md and faq-fr.md).

Deployment

  1. On your local computer:
    1. Ensure that you have pandoc installed (it is availble via Homebrew on macOS)
    2. Generate new index.html files:
    ./build.sh
    1. Review changes:
    git diff
    1. Commit changes and submit pull request
  2. On the salt-prime server, test highstate
    sudo salt index__prod__us-east-2 state.highstate saltenv=${USER} test=True
  3. On the salt-prime server, apply highstate
    sudo salt index__prod__us-east-2 state.highstate saltenv=${USER}

License

Code

CC0 1.0 Universal (CC0 1.0) Public Domain Dedication button

bin/COPYING: The code (build.sh) is dedicated to the public domain under the CC0 1.0 Universal (CC0 1.0) Public Domain Dedication.

Content

CC BY 4.0 license button

LICENSE: The content (.md, .html, and .png files) is licensed under a Creative Commons Attribution 4.0 International License.

faq's People

Contributors

code-n-chill avatar ferdnyc avatar hugosolar avatar keshav861 avatar kgodey avatar mattl avatar mmoreshead avatar ohneeigenschaften avatar possumbilities avatar sarahpearson avatar shafiya-heena avatar syeda-mal avatar timidrobot avatar xolotl avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

faq's Issues

Insert new text (in FAQ answer font size) immediately following the section header Donnees

Text:

Cette page remplace les Bases de Données et Creative Commons.

Une grande partie de la valeur potentielle des données profite à la société au sens large - plus de données a le potentiel de faciliter une meilleure collaboration scientifique et la reproductibilité, des marchés plus efficaces, l'augmentation de la transparence du gouvernement et des entreprises, et globalement à accélérer la découverte et la compréhension des solutions des besoins sociaux planétaires.

Une grande partie de la valeur potentielle de données, en particulier sa large valeur à l’échelle de la société, est réalisée par l'utilisation à travers les frontières organisationnelles. Comment cela se produit légalement? De nombreux sites donnent la permission stricte d'utiliser des données selon des conditions de service. Beaucoup de partage de données ad hoc se produit également entre les chercheurs. Et de plus en plus le partage des données est facilité par la distribution, en vertu de certaines normes, d’outils juridiques publics utilisés pour gérer les droits d'auteur et des restrictions similaires qui pourraient autrement limiter la diffusion ou la réutilisation des données, par exemple les licences CC ou CC0 dédiées au domaine public.

De nombreuses organisations, institutions et gouvernements utilisent des outils de CC pour les données. Pour les études de cas sur la façon dont ces outils sont appliqués, voir:

Utilisations des licences CC avec des données et des bases de données: Utilisations de CC0 avec des données et des bases de données.

Revise a page on the CC public wiki

This is an Outreachy contribution task. Multiple people may complete this task, it will not be closed until the Outreachy winter 2019 contribution period ends.


The Creative Commons Wiki has a lot of old/inaccurate content. Revise one wiki page and post a link to your contribution here. Please ask questions about any content you are unsure of.

To get edit access to the wiki, please sign up for a CCID here and tell us about it in #cc-gsoc-outreachy on Slack. We will give your account edit permissions.

Update two existing FAQ with reference to new resource

Description

We have created a new online resource to replace two existing questions in the main FAQ. (This is part of our ongoing gradual effort to make the explanatory resources more discoverable and user-friendly.)

Requested change

Please replace the existing answers to What can I do if I offer my material under a Creative Commons license and I do not like the way someone uses it? and What happens if I offer my material under a Creative Commons license and someone misuses them? with the following:

"Please see our Guide on What to do if Your CC-Licensed Work is Misused."

Move links in toc into <details> tags to make page more user friendly

Is your feature request related to a problem? Please describe.
This isn't necessarily a problem, just something I think would be a good change. The FAQ page has a lot of links at the top, and they're all packed together. I think it would be more user friendly to separate them into <details> elements, and allow them to drop down instead of having all visible, all the time. This would (in my opinion) make it easier to find what a user would want by searching categorically, instead of trying to parse the sea of blue letters.

Describe the solution you'd like
Make the "section heading" parts into <details> elements.

Describe alternatives you've considered
I can't think of anything other than putting the links into dropdowns...

I would be happy to work on this, pending approval, of course :)

Demo knowledge base software

This is an Outreachy contribution task. Multiple people may complete this task, it will not be closed until the Outreachy winter 2019 contribution period ends.


Enter some of CC’s FAQs into a knowledge base software so that they can be searched by keywords. Please make clear that it is not official CC FAQs and just a test project. Post the link to this knowledge base here.

Insert this FAQ and text just after this section heading: Des restrictions supplémentaires sur le matériel Lucency

[it was omitted by accident]

Que faire si je reçois du matériel sous licence CC alourdit par des mesures techniques efficaces (tels que les DRM)?

Si vous avez reçu du matériel sous licence CC qui est alourdit par de mesures techniques efficaces (comme les DRM), vous pouvez être autorisés ou non, selon les circonstances, à le briser. En publiant le matériel sous une licence CC, le concédant de licence accepte de ne pas faire valoir les droits qu'il pourrait avoir pour empêcher le contournement des mesures techniques efficaces. (ceci est implicite en vertu des licences 3.0 et non pas explicite.) Toutefois, s’il l’a téléchargé vers un site ou un autre canal de distribution qui applique lui-même ces mesures, ce site peut avoir le droit de vous empêcher de les contourner, même si le concédant de licence ne peut pas le faire lui-même.

Notez que les lois anti-contournement ne peuvent pas engager la responsabilité pénale dans certaines juridictions.

[Bug] Footnotes in HTML are semantically incorrect

Description

faq/faq/index.html

Lines 3747 to 3756 in 0bf0734

<h2 id="notes">Notes</h2>
<section id="footnotes" class="footnotes footnotes-end-of-document"
role="doc-endnotes">
<hr />
<ol>
<li id="fn1"><p>Key Publications, Inc.&#xA0;v. Chinatown Today Publishing
Enterprises Inc., 945 F.2d 509 (2d Cir. 1991).<a href="#fnref1"
class="footnote-back" role="doc-backlink">&#x21A9;&#xFE0E;</a></p></li>
</ol>
</section>

#76 (comment):

This isn't semantically correct. The h2 of "notes" would need to be inside the section element, as a section generally requires a heading element to denote it.

It could be argued that of the two, the aside is actually a more appropriate element, but it too would need the h2 to be within it as well. An aside does not require a heading element within it, but if one appears for it, it must appear within it.

The MOST semantic, and likely correct route, would be for the endnotes to appear (with the associated h2) within a footer element (instead of a section or aside). As they are meant to be footnotes for the main section, that is the next parent level sectioning element and they would then be semantically associated as the "footer of the main area", which is much more accurate to what the footnotes are in this case.

sooo...

<footer>
<h2 id="notes">Notes</h2>
notes here
</footer>
</main>

As divs are semantically meaningless whether it appears before or after the closing div tag is semantically irrelevant, just whichever one wouldn't throw off the visual styling.

Expectation

HTML should be semantic and provide best possible support for accessibility aids

Create a short video answering an FAQ

This is an Outreachy contribution task. Multiple people may complete this task, it will not be closed until the Outreachy winter 2019 contribution period ends.


Create a short video (which does not have to be fancy!) that answers a particularly important CC FAQ. Post the link to your video here.

Change references to Search

FAQ has a lot of references to the search as search.creativecommons.org, should it point to the new ccsearch?

[Bug] Dead link for examples in FAQ

Description

In the section How should I decide which license to choose?, there is a link to examples that demonstrate how various licenses fit into licensors’ overall strategies.

The link is https://creativecommons.org/examples, which redirects to https://creativecommons.org/share-your-work/licensing-types-examples

Reproduction

  1. Go to https://creativecommons.org/faq/#how-should-i-decide-which-license-to-choose
  2. Click on a list of examples
  3. See error.

Expectation

There should be a list of examples in the destination, or the link should not be mentioned at all.

Clarify some points in light of CC0

Problem Description

I know the CC0 has it's own FAQ - but some phrases in the FAQ is unclear to me at least on whether they apply to CC0 or not.

All CC licenses are non-exclusive: creators and owners can enter into additional, different licensing arrangements for the same material at any time (often referred to as “dual-licensing” or “multi-licensing”). However, CC licenses are not revocable once granted unless there has been a breach, and even then the license is terminated only for the breaching licensee.

I'm no lawyer, and I don't quite know if dual-licensing of CC0 is possible or not or if the public domain dedication is exclusive or not. I think if the text above does not apply to CC0 (which I think it may not) then it should be made clearer.

Proposed Solution

Make it clear whether CC0 is included in statements like "All CC licenses"

Some links at FAQ page broken and need to be fixed/replaced

The FAQ page (https://creativecommons.org/faq/) has some or many broken links.

Some more, but they are too lengthy to describe.

Identify instances of excellent FAQs

This is an Outreachy contribution task. Multiple people may complete this task, it will not be closed until the Outreachy winter 2019 contribution period ends.


Identify ten instances of excellent FAQs that exist on other organizations’ or companies’ websites. Post your research here.

Remove references to CC Affiliates

There's a lot of references to the Affiliates and we should change that for a language more connected with the CC Network.

@simeonoriko can work on updating information there regarding CC Chapters and Network Platforms

Recommend open source knowledge base software

This is an Outreachy contribution task. Multiple people may complete this task, it will not be closed until the Outreachy winter 2019 contribution period ends.


Research open source knowledge base software and write up a set of recommendations about what you think CC should be using. Post your recommendations here.

[Feature] aside block design improper

Problem

the problem is that the yellow block at the right side of the website https://creativecommons.org/faq/ is much longer than it should be.

Description

we have to reduce the size of the block to the end of the text not to the end of the page. this will improve the visibility and atteaction of the website.

Alternatives

Additional context

Orignal:-
image
it is till the end.

Expected:-
image

Implementation

  • I would be interested in implementing this feature.

Insert explanatory language under French version of Adapter's chart

Abréviations
• BY = Attribution seulement
• BY-ND = Attribution - Pas de Modification -Pas de travaux dérivés
• BY-NC-ND = Pas de travaux dérivés de Paternité-NonCommercial-
• BY-NC = Attribution-NonCommercial
• BY-NC-SA = Attribution-ShareAlike NonCommercial-
• BY-SA = Attribution-ShareAlike
• PD = Dédié à ou marqué comme étant dans le domaine public par l'intermédiaire de l'un de nos outils de domaine public ou autres documents du domaine public; des adaptations de matériaux dans le domaine public peuvent être construits sur et autorisés par le créateur dans les conditions de licence souhaités.

Fix broken links in English FAQ

The links in this text are broken (see bolded, italicized text where links exist but are broken):

If you're looking for legal advice about using CC licenses and other tools, we recommend contacting the Creative Commons affiliate in your jurisdiction. CC affiliates are highly connected to the communities of copyright lawyers in their countries. We also offer a list of lawyers and organizations who have identified themselves as willing to provide information to others about CC licensing issues.

Broken FAQ link: considerations for licensors and licensees

From message received on website:

I found a broken link on the FAQ page. It's under For Licensors - Choosing a License - What things should I think about before I apply a Creative Commons license?

The first hyperlink in this FAQ ("some things that you should consider") goes to a 404 not found page. I believe it is supposed to direct to the "Considerations for licensors and licensees" wiki page (https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees).

French FAQs: additional formatting fixes

(1) Capitalize the word "les" at the beginning of this FAQ: les organisations gouvernementales et inter-gouvernementales peuvent-elles utiliser des licences CC ?

(2) Change font of this text so same size as text just above it: "CC offre des données sur les meilleures pratiques pour le marquage de votre matériel et sur la façon de marquer les matériels dans différents médias."

(3) Change font of example notice text so same size as other text in the answer to the FAQ: "« Le texte et les illustrations de ce document sont autorisées par Red Hat sous une licence non-adaptée Creative Commons Attribution - Partage dans les Mêmes Conditions 3.0 (“ CC-BY-SA “). . . . Red Hat, Red Hat Enterprise Linux, le logo du Shadowman, JBoss, MetaMatrix, Fedora, le logo de Infinity, et RHCE sont des marques de Red Hat, Inc., déposées aux États-Unis et dans d’autres pays. Pour les lignes directrices sur les utilisations autorisées des marques de Fedora, consultez https://fedoraproject.org/wiki/Legal:Trademark_guidelines"

(4) This text, "Vous devez également indiquer si vous avez" is in large font, and is actually the beginning of the sentence that is continued on the next line. Change font size and join with rest of sentence.

(5) Remove html code (####) appearing in this section: Puis-je utiliser des mesures techniques efficaces (tels que les DRM) quand je partage le matériel sous licence CC?

(6) This FAQ is in larger font size than other equivalent FAQs within the section, harmonize: Qu’advient-il si l’auteur décide de révoquer la licence CC qui s’applique sur du matériel que j’utilise ?

(7) Same as (6), for this FAQ: Quels sont les droits sui generis sur les bases de données?

(8)This text, "CC ne recommande pas l'utilisation de ses" is in large font, and is actually the beginning of the sentence that continues on the next line. Change font size and join with rest of sentence.

Create page with 10 most important FAQs

This is an Outreachy contribution task. Multiple people may complete this task, it will not be closed until the Outreachy winter 2019 contribution period ends.


Review CC’s FAQs and design a user friendly page that incorporates what you believe to be the ten most important ones. Make a new folder in this repository with your HTML and CSS files and submit it as a pull request.

Usage of CC Vocabulary is recommended but not required.

English FAQs: remove HTML coding

(1) HTML coding showing in various places under this FAQ: If I derive or adapt material offered under a Creative Commons license, which CC license(s) can I use? Remove and bold headings.

(2) HTML coding showing at end of the text just after Data heading (it's an :)

Broken link in FAQ

Email from user:

Hi, I just wanted to bring your attention to a broken link:
https://creativecommons.org/faq/
under this question:

What if I change my mind about using a CC License?

There's a link to this: https://creativecommons.org/faq/Considerations%20for%20licensors%20and%20licensees
I believe the correct link is one of these, but I'll let you sort that out:
https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees
or
https://creativecommons.org/share-your-work/licensing-considerations/version4/

Fix font sizes of headings so uniform throughout in English FAQs

The actual FAQ question and any subsection header should be larger than the text of the answer, and the main section header still larger.

Here is an example of getting it right:

For Licensors is larger than the subsection heading "Choosing a license", and that the actual question "What things should I think about before I apply a Creative Commons license?" are larger than the text of the answer.

Here is an example of where it's wrong -- appears to just be under the Data FAQs. But, e.g., this question: Can databases be released under CC licenses?, is the same font size as the text of the answer, as is the case thereafter.

Additional comment: note that this is different than the French. In the French, the Section header is largest, then the Subsection header, and then the question. E.g,
Choisir une licence (Section header is largest)
Pour les concédants de licence (Subsection header is smaller)
A quoi penser avant de demander une licence Creative Commons (question is still smaller)

Would be nice if the French and the English were the same.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.