License Proposal

USER APPEARANCE:

I have 3 pages which imitate SCP pages: http://dorktoast.wikidot.com/scp-4461 http://dorktoast.wikidot.com/scp-5288 and http://dorktoast.wikidot.com/scp-1333

Step 1: At the bottom of each page, on the left, you'll see a tiny pair of glasses that when you roll over it, it says "Licensing". Click it.

Annotation-licensing

Step 2: Visit http://dorktoast.wikidot.com/license-list. Notice that the content of the boxes matches.

Update: This template was tested on the wiki. The results are here.

USER IMPLEMENTATION:

Licensing, and users, will be instructed to use the following at the bottom of every page:

[[include :scp-wiki:license-box]]
=====
License Information here.

You can put lots of stuff between the two section breaks.
=====
[[include :scp-wiki:license-box-end]]

HOW IT WORKS:

the license-box template creates a collapsible with the "licensing" class. The top part of this box includes basic "how to cite this page" information which is generated via listpages.
"=====" creates a section break (also known as <div class="content-separator">) putting the content into what Wikidot identifies as Section {2}.
the second "=====" ends section {2} by creating another separator.
the license-box-end template closes the section break, collapsible and the list box.
the license-list page uses the "Content{n}" magic-word to pull only text from section {2} on pages tagged with "licensebox" (which could be any tag, or ideally no tag at all.)

Note: when implemented into the wiki, it would be localized and not pulled from the dorktoast wiki.

POTENTIAL BENEFITS:

  • Having an auto-generated license page is a Creative Commons best practice and is highly recommended for projects of our size.
  • Now there's a one-stop-shop for "where did that thing come from" and "how do I use this thing under Creative Commons".
  • By citing exactly where things come from on-page, licensing staff (or any staff, for that matter) wouldn't have to go digging in the forum pages to find sources.
  • It provides a single place to grab a citation for people making derivative and adaptive works.
  • By delineating what content is licensed in what way, we could potentially begin using other image and content licenses such as FAL, GFDL, etc by noting that content's specific license as being separate from that of the main wiki. We could potentially not have to outright replace images that aren't CC-BY-SA but are under certain other licenses like the Pixabay license or certain flickr licenses. it would save us tons of heartache and drama. This is a super cool benefit!

POTENTIAL OBSTACLES:

  • Pages that use the content section break "=====" will need to be tweaked. For that reason, this would require a small amount of buy-in from tech team regarding adoption of the currently-not-often-used section break. (It is worth mentioning that I have yet to encounter an article which uses that section break. I am sure one exists but I haven't found it.) Note that the section break is different from the commonly used page break (-----) This is resolved! No pages currently use the section break.
  • A page which improperly uses this template could break the table on the license page (but this would be an easy fix because we'd be able to see exactly where it was broken, go to that page, and fix it)
  • If the Wiki were to ever move to a different platform, this would break (I mean, that applies to a lot of things, but it's true so I added it here.)
  • In fringe cases, the glasses icon could look weird on different themes. However, it's made to "inherit" parent styles, so it should look like the theme's own collapsible. I have tested this on 5 different Black Highlighter themes, Sigma-9, and a few other non-black-highlighter themes with no issues. Update: The visual style of the license template can be altered. I've created [dorktoast.wikidot.com/scp:license-proposal-visual-options a few live demos of different potential styles for our license box button.]
  • We'd have to go apply these licenses by hand on already-existing pages. But I volunteer to help do that. Update: It's actually really easy. I've even created a javascript generator on this page (Click the box-ify-er) to make it easier!
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License