3
edits
Line 107: | Line 107: | ||
* The add-on idea is interesting. Nice paper prototype! | * The add-on idea is interesting. Nice paper prototype! | ||
* Combining the educator and manager is an interesting approach. More questions to think about: Are these solutions solving the same problem? are they for same users? why people don't know about CC would install the add-on, and why someone already install the add-on need to know more about CC? | * Combining the educator and manager is an interesting approach. More questions to think about: Are these solutions solving the same problem? are they for same users? why people don't know about CC would install the add-on, and why someone already install the add-on need to know more about CC? | ||
=== Bram Pitoyo's comments (Mozilla) === | |||
First idea: | |||
Thinking about something that fits the existing workflow is good. Of course, there’s two sides of the equation: the user/remixer, and the creator/owner. Your educator idea hits the user/remixer. How can you extend it so that it can also be used from the side of the creator? | |||
Thought experiment: if imgur or Vimeo deploys an educator, what would it look like? | |||
Second idea: | |||
There’s a bit of a ‘preaching to the choir’ quality going on here. People who care about CC will look up and install the manager out of active curiosity, but people who don’t care might not be interested enough to find and install license manager in the first place. | |||
How would you build the manager in such a way that those who don’t know about CC will want to use it actively? |
edits