Merge branch 'master' into header-keyboard

Author: zackkrida

Pipfile

@@ -5,6 +5,9 @@ verify_ssl = true
 
 [packages]
 black = "==19.10b0"
+# Cryptography 3.4+ requires Rust to build
+# https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst
+cryptography = "==3.3.2"
 flake8 = "*"
 lektor = "*"
 # Werkzeug added and pinned to mitigate this issue:

Pipfile.lock

@@ -0,0 +1 @@
+username: Ishan Thilina

content/archives/old-tech-blog/authors/Ishan-Thilina/contents.lr

@@ -0,0 +1 @@
+username: Thanish

content/archives/old-tech-blog/authors/THanish/contents.lr

@@ -0,0 +1 @@
+username:  Dinishika Weerarathna

content/archives/old-tech-blog/authors/dinishi/contents.lr

@@ -0,0 +1 @@
+username: Ethan Lim

content/archives/old-tech-blog/authors/ethanlim/contents.lr

@@ -1 +1 @@
-username: igorlukanin
+username: Igor Lukanin

content/archives/old-tech-blog/authors/igorlukanin/contents.lr

@@ -0,0 +1,90 @@
+title: Creative Commons Drupal Module
+---
+categories:
+API
+development
+GSoC
+software
+tools
+---
+author: blaise
+---
+body:
+
+Creative Commons provides vast number of public copyright licenses for people who want to enable free distribution of their work. Creative Commons licenses currently covers over **1.6 billion resources**. These license files are then translated to multiple different languages and ported for [different jurisdictions](https://wiki.creativecommons.org/wiki/CC_Ports_by_Jurisdiction) for international usage. People link to the respective licenses along with their licensed works. These license files are in the form of `html` files, stored in [creativecommons/creativecommons.org](https://github.com/creativecommons/creativecommons.org/tree/master/docroot/legalcode) repo.
+
+### Problem Statement
+There are currently two Creative Commons (CC) modules for Drupal. CC Lite only offers limited functionality, but the CC module has not been updated for a long time and doesn't support current versions of Drupal.
+
+### Planning
+*  update the Creative Commons module, referencing and possibly building on Creative Commons lite, to support Drupal 6\
+*  expand its functionality to embed and detect license information for some file uploads.
+
+### Summary
+The Creative Commons module allows users to assign a Creative Commons license to
+the content of a node, or to specify a site-wide license. It uses to Creatve
+Commons API to retrieve up-to-date license information. Licenses are diplayed
+using a Creative Commons Node License block and the Creative Commons Site
+License block. The module also supports some license metadata fields. License
+information is output using ccREL RDFa inside the blocks, and can optionally be
+output as RDF/XML in the body of a node.
+
+Creative Commons search is available at /search/creativecommons/, and (if the
+Views module is installed and enabled) a Creative Commons view is available at
+/creativecommons. Creative Commons license information and metadata are
+available to the Views module.
+
+For a full description of the module, visit the project page:
+  http://drupal.org/project/creativecommons
+
+To submit bug reports and feature suggestions, or to track changes:
+  http://drupal.org/project/issues/creativecommons
+
+### Requirements
+None
+
+### Installation
+* Install as usual, see [Installing contributed modules (Drupal 5 and 6) |
+  Drupal.org](http://drupal.org/node/70151) for further information.
+
+### Configuration
+* Configure user permissions in Administer >> User management >> Permissions >>
+  creativecommons module:
+
+  - administer creative commons
+
+    Users can customize the module settings in Administer >> Settings >>
+    Creative Commons
+
+  - attach creative commons
+
+    Users will be able to attach license information to the content of a node.
+
+  - use creative commons user defaults
+
+    Users will be able to set their own defaults, independent of site defaults
+    (but still subject to site license availability settings).
+
+* Set available license types, required/available metadata and display settings
+  Administer >> Settings >> Creative Commons. To make it mandatory to specify a
+  license, simply make the 'None' type unavailable.
+
+* Set default license type and jurisdiction in Administer >> Settings >>
+  Creative Commons >> site defaults. Here, you can set the default license to be
+  used as a site-wide license if you wish, and you can include any relevant
+  metadata.
+
+* Enable Creative Commons licensing for desired content types in Administer >>
+  Settings >> Creative Commons >> content types. For example, you might wish to
+  allow Creative Commons licensing for blog posts, but not forum posts.
+
+* In your Drupal user account settings, you can set a jurisdiction or default
+  license to override the site defaults.
+
+
+CC Drupal is only possible due to the support and guidance of my mentors [Kevin Reynen](http://drupal.org/user/48877) and `CC Tech Staff Member`, who have been very supportive on every step of the project.
+
+The project is approaching its completion. Can't wait to see it in production.
+
+---
+pub_date: 2009-09-23

content/archives/old-tech-blog/entries/cc-drupal/contents.lr

@@ -0,0 +1,49 @@
+title: Creative_Commons_LibreOffice_Plugin_Updates
+---
+categories:
+Add-In
+GSoC
+OpenOffice
+opensource
+---
+author: Ishan-Thilina
+---
+body:
+
+This year Creative Commons has a much more limited focus on what we would like to see out of Google Summer of Code than in previous years.
+
+### Installation
+The latest version of the plugin is 0.7.0, available for download from the [OpenOffice.org Extension site](https://extensions.openoffice.org/en/project/ccooo)
+To install:
+
+* Download the plugin
+* Open OpenOffice.org
+* Go to the `Tools` menu and select `Extension Manager`. Click `Add` and select the file you downloaded.
+* After the installation process completes, restart OpenOffice.org. The Creative Commons menu options will be located at the bottom of the `Insert` menu.
+
+Debian/Ubuntu (& other variants) users:
+* Debian/Ubuntu (& other variants) users may have problems if the plugin installed using the Extension Manager.
+* They may need to install the plugin using the terminal.
+* To install use /usr/lib/openoffice/program/unopkg gui -f ccooo.oxt
+
+### Problem Statement
+The current Creative Commons LibreOffice (OpenOffice) plugin is written in Java. This project is aimed to port the current plugin to Python while rectifying the problems in the current plugin.
+
+### Solution
+The Python port of the Creative Commons Add-in for LibreOffice and OpenOffice.org which allows license information to be embedded in OpenOffice.org and LibreOffice Writer, Impress, Draw and Calc documents.
+
+For more information visit [the official addin page](https://wiki.creativecommons.org/wiki/OpenOfficeOrg_Addin) of Creative Commons
+
+### Testing
+Download the out.oxt file. Install it via the LibreOffice Extension Manager (Tools --> Extension Manager).
+
+Then go to `Insert` `--> ` `Creative Commons`. By using the first option you can insert the license information to the document. The second option is for changing those data.
+
+### Knowledge Prerequisite
+`Python` ,`Shell`
+
+CC LibreOffice is only possible due to the support and guidance of  `CC tech staff member`, who have been very supportive on every step of the project.
+The project is approaching its completion. Can't wait to see it in production.
+
+---
+pub_date: 2012-07-15

content/archives/old-tech-blog/entries/cc-libreoffice-plugin-updates/contents.lr

@@ -0,0 +1,48 @@
+title: Creative Commons Media Fingerprinting Library
+---
+categories:
+Add-In
+GSoC
+opensource
+---
+author: ethanlim
+---
+body:
+
+CC would prefer that all content on the Web include correct licensing metadata. Alas, that is not the case. So we're interested in code that will allow us to identify a given item across the Web, even if there's no metadata alongside (or within) it. The tricky part is: people often crop or resize images, clip videos, re-encode content, or quote only pieces of text. So a simple hash is not sufficient: we need more intelligent fuzzy matching. That's what this project is about.
+
+### Expected Results
+A library that provides two methods:
+*  Given a media file, output a fingerprint, and
+*  Given a file and a fingerprint, return the likelihood of the file matching the original file.
+
+You can focus your efforts on only one or two media types, or you can do more if it's possible.
+The library can be in a low-level language (C/C++) or you can use a higher-level language (JavaScript) if it's feasible. Speed is not a major concern at this point.
+Bonus: An additional API/method to detect content inside other files (e.g., a PowerPoint file that includes a CC licensed image, or a still image inside a video).
+
+### Notes/Resources
+The first task is to decide on a strategy to compare two items and decide how similar they are. Some choices are:
+* Hamming distance (bitwise AKA Manhattan distance)
+* Euclidean distance (plane distance, also good in higher dimensions)
+* Set similarity (Jaccard index; MinHash)
+
+For this project, set similarity seems like the best choice. It would potentially allow us to detect works remixed into other works, if some portion of them has remained intact in some way. The technique involves distilling a document into a set of things, and comparing two documents is simply the ratio of things they have in common to things they do not.
+
+A good way to start is with text, and involves a technique called shingling. For something like images, we'll need more work to determine which "interesting" features of the image to consider (to generate the set of things). This is called "keypoint extraction" and involves using standard algorithms to find vectors of floats that describe each keypoint. Since for images two keypoint vectors might be very similar but not identical, some additional work in clustering and mapping to example keypoints is required for images.
+Some reading:
+* Chapters 1 and 3 of [Mining Massive Datasets](http://infolab.stanford.edu/~ullman/mmds.html)
+* [building shingles in text](https://lingpipe-blog.com/2011/01/12/scaling-jaccard-distance-deduplication-shingling-minhash-locality-sensitive-hashi/)
+* [Introduction to Information Retrieval](https://nlp.stanford.edu/IR-book/)
+* [OpenCV](https://opencv.org/) for extracting things (features) of images
+* BRISK / FREAK: algorithms for "keypoint extraction", for images
+* [pHash.org](http://www.phash.org/) might be something we can use.
+
+### Knowledge Prerequisite
+`Media formats/encodings` ,`JavaScript` ,`C/C++.`
+
+CC MEDIA FINGERPRINTING LIBRARY is only possible due to the support and guidance of my mentors [Dan Mills](#) or ` other CC tech staff member`, who have been very supportive on every step of the project.
+
+The project is approaching its completion. Can't wait to see it in production.
+
+---
+pub_date: 2013-07-15