Skip to content
This repository has been archived by the owner on Apr 9, 2021. It is now read-only.

Tech Product Roadmap 2015

Jump to bottom
Rob Myers edited this page Oct 23, 2015 · 5 revisions

Introduction

Creative Commons technology needs a refresh. This document sets out our plans to revisit our technology efforts.

Overview

At the end of 2014, Creative Commons approved a four point strategy with the following objectives: growing the commons, building a movement, advancing policy and advocacy, and ensuring our sustainability. This roadmap turns that strategy into concrete action in the form of software development and technical infrastructure projects.

Our priorities are to lead the development of tools to support CC’s strategic objectives, to renew and revitalise CC’s existing systems, and to support CC’s staff and affiliates as they also pursue these objectives. In order to do this we need input and support from CC’s affiliates, supporters and partners in the wider community.

To grow the commons we are enhancing CC licensing and search tools. To help in building a movement we are supporting affiliates with new sites and improved translation. To support the advancement of policy and advocacy we are building a new OER registry and incorporating tools to support advocacy staff and affiliates in their efforts. And to ensure our sustainability we are updating CC’s long-standing technical infrastructure and building tools to support evidence-based decision making with licensing metrics.

We welcome feedback and questions about this roadmap from CC’s network of affiliates and supporters, from domain experts and from the general public.

Schedule

Q2 2015 (May/June)

Website

  • Package logos/buttons for web dev (make Bower/npm/composer installable?). - No, people should link to them.
  • Incorporate Trilogy Interactive changes
  • Improve key high traffic pages. Front page, donate, change.
  • Website enhancements: homepage.
  • Update CC font to include all logos

CC Wiki

  • Migrate wiki content to a new wiki
  • New wiki supports CCID

Board wiki

  • Work with Mari to get board wiki operational

Infrastructure

  • Get all machines on Salt
  • Build a spreadsheet of all SSL certs with expiration dates
  • Update most machines to new SSL wildcard
  • Initial steps on a CC ‘dashboard’
  • Build a plan for handling affiliate websites/domains/tech/SSL

CCID

  • Support logins from Phabricator (GitHub, Twitter, etc)
  • Warn people that cc.net openid will be taken down in 6 months
  • Dashboard can check for accounts and reset passwords.

The List

  • Scope Consumer MVP.
  • Fundraising
  • Anonymous logins
  • Gratitude

Chooser

  • Mobile-friendly/mobile-first mockup.
  • If this then that style
  • Make sure it works on 320px wide displays
  • UI: “Wizard” design, links to tutorials, example media, shortcut for the experienced. Like The List app introduction/signup.
  • Attempt at integrating this into QDP.
  • Initiate community review process for changes. Identify the challenges, create mockups of drafts, give people something to react to.
  • PD-JX Mark Mockup (July 13th deadline)

OER Registry

  • Initial discussion with community
  • Gather design requirements

Platform stuff

  • Prep a release of “Creative Commons” WordPress plugin
  • Run the name by Diane/Sarah
  • Reactivate our WP Plugin account

Open Policy Registry

  • openpolicyregistry.org
  • put up a page
  • collect email addresses?

Q3 2015 (July - September)

Website

  • Move blog to its own subdomain (blog.creativecommons.org, redirect to it) and use semantic urls.
  • Stay with WordPress for blog.
  • Audit website design and usability
  • Commission new design or create internally.
  • Redesign front page.
  • (This but not this): what is our service/the value of us/logos of all the platforms that use our licenses. Don’t look like a consumer service, but get across core messages about the value of what CC does.

Infrastructure

  • Move the a*.creativecommons.org (ie. a8.creativecommons.org) servers to BigV
  • api (a8) is the big one, there are a few others
  • Build out new list server
  • New License Chooser database server
  • Dashboard can un/register people from lists and show a list of Freshdesk tickets
  • Dashboard can also show daily financial totals, number of people on our mailing list

Search

  • Establish scope and requirements.
  • Contact and discuss with (potential) partners.
  • Ensure we can search across additional platforms as they integrate CC licensing
  • Ensure License Chooser and Open Policy (OER?) Registry support chosen strategy.

License Chooser

  • Initial version with CCID/anonymous workflow and any required APIs for compatibility with existing workflows.
  • As a beta

Open Policy Registry

  • Implement using a simple form-based CMS e.g. Plone.
  • Login (CCID) / user role management.
  • Forms and presentation for policies and associated data.
  • Workflow for adding and evaluating new policies.

Q4 2015 (October - December)

Website

  • New template (theme) implemented and applied based on redesign.
  • Site should feel modern, open (less cramped), have obvious calls to action - foreground the key things.
  • Move static/rarely updated content to Jekyll.
  • Create build system to generate Apache configuration for serving license files more transparently.

License Chooser

  • Offer Modern metadata JSON-ld, HTML5-compatible microformats.
  • Accompanying and embedded: JSON-LD and microformats alongside XMP.
  • Issue: Social media removes embedded metadata (which can be important for privacy).
  • Allow the user to embed metadata in works as part of the License Chooser workflow. Upload your file, do what the list does & embed metadata.
  • Generate a QR code for the license, title, description, etc in some kind of JSON. Used for book scanning, archiving, etc.

Search

  • Chunk-o-work.

Open Policy Registry

  • Multi-field search engine (e.g. jurisdiction AND policy type AND license AND five star rating)
  • Rating/ranking of policies.

Q1 2016 (January - March)

CCID/CC.NET

  • Decommission CC.NET.
  • CCID profiles are a thing now.
  • Dashboard: CC.NET to CCID profile redirection

License Chooser

  • Archiving of submitted works
  • Do not host media ourselves, this would be prohibitively expensive.
  • Partner with Internet Archive to store media on their servers
  • Include metadata with uploaded files.
  • How does this interact with 3rd party media publishing service partners/users?
  • Metadata archiving.
  • Send to 3rd party metadata store?
  • Bitcoin blockchain - store hash of public dump of license data?

Search

  • Chunk-o-work.

Buttons

  • Visual redesign
  • They are hard to read. Legibility, accessibility, modernity.
  • People will notice immediately if they change - positive impact, visibility.
  • Make sure they’re beautiful to aid acceptance of new functionality.
  • Talk to services about tipping/monetization integration. ##Q2 2016 (April - June)

Chooser

  • Gathering and presentation of user work analytics
  • Geolocation of views/clicks
  • Number of views
  • Number of clicks
  • Average/peak numbers.
  • Corelated search terms.
  • Referrers.

Buttons

  • Additional functionality.
  • gratitude (likes (someone liked your image), messages?)
  • Collaborate button -- link CCID to social/Social
  • e-commerce (tips a la changetip, subscriptions, a la patreon)
  • donations (secondary/enhanced button option to donate to CC)
  • etc. (work w/ Platform).
  • Opt-in.

Q3 2016 (July - September)

License Chooser

  • Bulk licensing workflow, e.g for large-scale open licensing from open policies.
  • Service integration -associate CCID with flickr, when you upload image through chooser it’s added to FLickr with correct metadata.

Q4 2016 (October - December)

Curation - EVALUATE

  • Showcases CC content and the breadth of the commons.
  • Relatively high cost to present, store and administer/police.
  • Don't compete with platform partners?
  • Models: storify, pinterest, ... ?

License Chooser

  • Aggregation and presentation of analytics for CC
  • Social drivers/virality (invitations a la Basecamp)

Our Development Methodology

  • Create GitHub project
  • Create skeleton PHP project.
  • Gather organizational objectives & stakeholder requirements (e.g. grant funders) -> translate into project requirements -> create design to satisfy requirements.
  • Sketch out technical structure and interface requirements.
  • Propose to stakeholders and community.
  • Incorporate feedback, rinse, repeat.

Objectives

Streamlined (“one click”) CC licensing process.

  • Part of Chooser work.

CC Analytics.

  • Part of Chooser work.

Improved search of all CC licensed works.

  • Same as now, we marshal queries to other APIs. e.g. forward individual searches to flickr api, cache in Redis.
  • Faster, more useful.
  • Easier to extend & scale.

User data analytics.

Improved Buttons

  • Graphic design refresh.
  • Added functionality.
  • ASCII art CC license buttons plz.
  • 3D buttons for 3D printing, games etc.

OER Registry upgrade.

  • Project started.
  • Streamlined licensing workflows for large-scale open licensing to support open policies.
  • Need to scope. Include in chooser work (“Do you want to bulk license work?”)? Some sort of CSV import? Or simply produce tools to use the API?
Clone this wiki locally